Never been able to get MySensors to work



  • Two years of experimenting with MySensors, and I've never been able to make it work.

    Trying to do the following:

    Raspberry Pi 3+ running OpenHABian.

    NRF2401 Radio attached to Rasp Pi GPIO pins as described here: https://www.mysensors.org/build/raspberry

    MySensors 2.4 JAR file installed per this thread: https://forum.mysensors.org/topic/6694/openhab-2-4-mysensors-serial-gateway-how-to-install/2

    Serial Gateway configured and status of "Online" in Paper UI

    Simple Temp and Humidity node with NRF2401 radio (with capacitor on the VCC/GND), using the vanilla sketch from here: https://www.mysensors.org/build/humidity

    Doesn't work; just hasn't worked, ever. I've been banging my head against the desk for the last 2 days, just dying to get MySensors to work. It promises all the bells and whistles for cheap home automation, but despite my every effort, I cannot even read a simple DHT11.

    I've followed so many tutorials, flashed the Pi so many times, and none of them work. If anyone cares, here's the output from my node:

    373772 TSM:FPAR
    375371 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    377379 !TSM:FPAR:NO REPLY
    377381 TSM:FPAR
    378981 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    380989 !TSM:FPAR:NO REPLY
    380991 TSM:FPAR
    382590 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    384599 !TSM:FPAR:FAIL
    384601 TSM:FAIL:CNT=7
    384603 TSM:FAIL:DIS
    384605 TSF:TDI:TSL
    444607 TSM:FAIL:RE-INIT
    444609 TSM:INIT
    444615 TSM:INIT:TSP OK
    444618 TSF:SID:OK,ID=199
    444620 TSM:FPAR
    446220 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    448228 !TSM:FPAR:NO REPLY
    448230 TSM:FPAR
    449829 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    451838 !TSM:FPAR:NO REPLY
    451841 TSM:FPAR
    453440 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    455448 !TSM:FPAR:NO REPLY
    455450 TSM:FPAR
    457050 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    459058 !TSM:FPAR:FAIL
    459060 TSM:FAIL:CNT=7
    459062 TSM:FAIL:DIS
    459064 TSF:TDI:TSL
    519066 TSM:FAIL:RE-INIT
    519068 TSM:INIT
    519074 TSM:INIT:TSP OK
    519077 TSF:SID:OK,ID=199
    519079 TSM:FPAR
    520679 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    522687 !TSM:FPAR:NO REPLY
    522689 TSM:FPAR
    

    Just this, over and over again

    and on the gateway side of things:

    May 17 18:33:32 INFO  Starting gateway...
    May 17 18:33:32 INFO  Protocol version - 2.3.1
    May 17 18:33:32 DEBUG Serial port /dev/ttyUSB0 (115200 baud) created
    May 17 18:33:32 DEBUG MCO:BGN:INIT GW,CP=RNNGL---,REL=255,VER=2.3.1
    May 17 18:33:32 DEBUG TSF:LRT:OK
    May 17 18:33:32 DEBUG TSM:INIT
    May 17 18:33:32 DEBUG TSF:WUR:MS=0
    May 17 18:33:32 DEBUG TSM:INIT:TSP OK
    May 17 18:33:32 DEBUG TSM:INIT:GW MODE
    May 17 18:33:32 DEBUG TSM:READY:ID=0,PAR=0,DIS=0
    May 17 18:33:32 DEBUG MCO:REG:NOT NEEDED
    May 17 18:33:32 DEBUG MCO:BGN:STP
    May 17 18:33:32 DEBUG MCO:BGN:INIT OK,TSP=1
    May 17 18:33:32 DEBUG TSM:READY:NWD REQ
    May 17 18:33:32 DEBUG TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
    May 17 18:33:34 DEBUG TSF:MSG:READ,0-0-0,s=0,c=0,t=0,pt=0,l=0,sg=0:
    May 17 18:33:34 DEBUG !TSF:MSG:LEN=0,EXP=7
    May 17 18:33:34 DEBUG TSF:MSG:READ,0-0-0,s=0,c=0,t=0,pt=0,l=0,sg=0:
    May 17 18:33:34 DEBUG !TSF:MSG:LEN=0,EXP=7
    May 17 18:33:34 DEBUG TSF:MSG:READ,0-0-0,s=0,c=0,t=0,pt=0,l=0,sg=0:
    May 17 18:33:34 DEBUG !TSF:MSG:LEN=0,EXP=7
    

    I'm at my wit's end. I don't understand why this has to be so difficult. In all of my years of working in tech, I'm just baffled.

    plea/rant over.


  • Mod

    @iamtheghost said in Never been able to get MySensors to work:

    May 17 18:33:34 DEBUG TSF:MSG:READ,0-0-0,s=0,c=0,t=0,pt=0,l=0,sg=0:
    May 17 18:33:34 DEBUG !TSF:MSG:LEN=0,EXP=7

    Data is coming in at the gateway's side, but the data appears to be corrupted somehow. Judging from the log all incoming data is received as zeroes only (TSF:MSG:READ only reports zeroes, and the message length in the data (!TSF:MSG:LEN) is unexpectedly 0). The actual on-air data likely wasn't all zeroes, so I would primarily suspect the gateway.

    Triple check the wiring of your Raspberry Pi to the nRF24. Make sure you have a capable, stable power supply, that all GNDs are connected and add a decoupling capacitor between the nRF24 VCC and GND connections (see https://www.mysensors.org/build/connect_radio "Connecting a Decoupling-Capacitor").
    Make sure the radio is powered from 3.3V and try with a different radio. Use standard, non-amplified, genuine nRF24 radios.

    If things still so not work, then add

    #define MY_DEBUG_VERBOSE_RF24
    

    to the top of both sketches, reflash/rebuild and post full debug logs of node + gateway (incl. startup statements) configure/commandline for the RPi gateway and both sketches.



  • @yveaux said in Never been able to get MySensors to work:

    #define MY_DEBUG_VERBOSE_RF24

    I have capacitors installed on all radios. I have tried with both the nrf24l01+pa+lna radio and the normal nrf24l01 radio. Both authentic, no "blobs", real chips.

    My radio on the RPi:
    raspberry pi with nrf24l01

    My DHT11 node:
    Imgur

    I don't feel like either of these are horrible soldering jobs. I've been making electronics for years, but maybe I'm wrong.

    Followed this guide "to the T", with the exception of having to install Java 8 SDK JRE manually because the PPA is now discontinued and no longer works as described in that tutorial.

    Content of file from /home/pi/mysensors/examples_linux/mysgw.cpp:

    /*
     * The MySensors Arduino library handles the wireless radio link and protocol
     * between your home built sensors/actuators and HA controller of choice.
     * The sensors forms a self healing radio network with optional repeaters. Each
     * repeater and gateway builds a routing tables in EEPROM which keeps track of the
     * network topology allowing messages to be routed to nodes.
     *
     * Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
     * Copyright (C) 2013-2018 Sensnology AB
     * Full contributor list: https://github.com/mysensors/MySensors/graphs/contributors
     *
     * Documentation: http://www.mysensors.org
     * Support Forum: http://forum.mysensors.org
     *
     * This program is free software; you can redistribute it and/or
     * modify it under the terms of the GNU General Public License
     * version 2 as published by the Free Software Foundation.
     */
    
    #include <iostream>
    #include <cstdio>
    #include <unistd.h>
    #define MY_DEBUG_VERBOSE_RF24
    // For more options run ./configure --help
    
    // Config file
    #define MY_LINUX_CONFIG_FILE "/etc/mysensors.conf"
    
    // How many clients should be able to connect to this gateway (default 1)
    #define MY_GATEWAY_MAX_CLIENTS 10
    
    // Serial config
    // Enable this if you are using an Arduino connected to the USB
    #define MY_LINUX_SERIAL_PORT "/dev/ttyUSB0"
    // Enable this if you need to connect to a controller running on the same device
    // You also need to define MY_LINUX_SERIAL_PORT above with the symlink name for the PTY device
    #define MY_LINUX_SERIAL_IS_PTY
    // Grant access to the specified system group for the serial device
    #define MY_LINUX_SERIAL_GROUPNAME "tty"
    
    // MQTT options
    //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68
    //#define MY_PORT 1883
    //#define MY_MQTT_CLIENT_ID "mysensors-1"
    //#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway1-out"
    //#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway1-in"
    // Enable these if your MQTT broker requires username/password
    //#define MY_MQTT_USER "username"
    //#define MY_MQTT_PASSWORD "password"
    
    // Flash leds on rx/tx/err
    //#define MY_DEFAULT_ERR_LED_PIN 12  // Error LED pin
    //#define MY_DEFAULT_RX_LED_PIN  16  // Receive LED pin
    //#define MY_DEFAULT_TX_LED_PIN  18  // Transmit LED pin
    // Inverse the blinking feature
    //#define MY_WITH_LEDS_BLINKING_INVERSE
    
    // Enable software signing
    //#define MY_SIGNING_SOFT
    // Enable signing related debug
    //#define MY_DEBUG_VERBOSE_SIGNING
    // Enable this to request signatures
    //#define MY_SIGNING_REQUEST_SIGNATURES
    // Enable this to to weaken security for gradual deployment purpose
    // (see signing documentation for details)
    //#define MY_SIGNING_WEAK_SECURITY
    
    // Enables RF24 encryption (all nodes and gateway must have this enabled, and all must be
    // personalized with the same AES key)
    //#define MY_RF24_ENABLE_ENCRYPTION
    / Enable inclusion mode if your HA Controller supports it (e.g. Vera Controller)
    //#define MY_INCLUSION_MODE_FEATURE
    // Enable Inclusion mode button on gateway
    //#define MY_INCLUSION_BUTTON_FEATURE
    // Set inclusion mode duration (in seconds)
    //#define MY_INCLUSION_MODE_DURATION 60
    // Digital pin used for inclusion mode button
    //#define MY_INCLUSION_MODE_BUTTON_PIN  3
    
    #include <MySensors.h>
    
    #define ARDUINO 100
    // This space is intended to be used to include arduino libraries
    
    #undef ARDUINO
    
    void setup()
    {
            // Setup locally attached sensors
    }
    
    void presentation()
    {
            // Present locally attached sensors here
    }
    
    void loop()
    {
            // Send locally attached sensors data here
    }
    

    Output of dmesg | grep tty:

    dmesg | grep tty
    [    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000  dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=61399ee0-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
    [    0.000910] console [tty1] enabled
    [    0.816958] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 81, base_baud = 0) is a PL011 rev2
    [    0.821412] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 53, base_baud = 31250000) is a 16550
    

    The above output interests me. It appears that mysgw.service (or mysensors/bin/mysgw) is not automatically starting. The ttyUSB0 port isn't there until I manually start the service using sudo ./bin/mysgw . My understanding is that these lines

    sudo systemctl daemon-reload
    sudo systemctl enable mysgw.service
    sudo systemctl start mysgw.service
    

    would make the service start automatically; is that not the case?

    As for my config string, I just used this one from the tutorial, minus the RF channel of 69, which seemed unnecessary, so I opted for the default of 76 and omitted it from the string:
    ./configure --my-gateway=serial --my-serial-is-pty --my-transport=rf24 --my-serial-groupname=tty

    I'm not sure how to monitor the traffic on the gateway, but this is the output now, which is failing, after following the above tutorial, and running sudo ./bin/mysgw:

    pi@OpenHabPi:/home/mysensors $ sudo ./bin/mysgw
    May 18 17:40:18 INFO  Starting gateway...
    May 18 17:40:18 INFO  Protocol version - 2.3.1
    May 18 17:40:18 DEBUG Serial port /dev/ttyUSB0 (115200 baud) created
    May 18 17:40:18 DEBUG MCO:BGN:INIT GW,CP=RNNGL---,REL=255,VER=2.3.1
    May 18 17:40:18 DEBUG TSF:LRT:OK
    May 18 17:40:18 DEBUG TSM:INIT
    May 18 17:40:18 DEBUG TSF:WUR:MS=0
    May 18 17:40:18 DEBUG !TSM:INIT:TSP FAIL
    May 18 17:40:18 DEBUG TSM:FAIL:CNT=1
    May 18 17:40:18 DEBUG TSM:FAIL:DIS
    May 18 17:40:18 DEBUG TSF:TDI:TSL
    May 18 17:40:28 DEBUG TSM:FAIL:RE-INIT
    May 18 17:40:28 DEBUG TSM:INIT
    May 18 17:40:28 DEBUG !TSM:INIT:TSP FAIL
    May 18 17:40:28 DEBUG TSM:FAIL:CNT=2
    May 18 17:40:28 DEBUG TSM:FAIL:DIS
    May 18 17:40:28 DEBUG TSF:TDI:TSL
    May 18 17:40:38 DEBUG TSM:FAIL:RE-INIT
    May 18 17:40:38 DEBUG TSM:INIT
    May 18 17:40:38 DEBUG !TSM:INIT:TSP FAIL
    May 18 17:40:38 DEBUG TSM:FAIL:CNT=3
    May 18 17:40:38 DEBUG TSM:FAIL:DIS
    May 18 17:40:38 DEBUG TSF:TDI:TSL
    May 18 17:40:48 DEBUG TSM:FAIL:RE-INIT
    May 18 17:40:48 DEBUG TSM:INIT
    May 18 17:40:48 DEBUG !TSM:INIT:TSP FAIL
    May 18 17:40:48 DEBUG TSM:FAIL:CNT=4
    May 18 17:40:48 DEBUG TSM:FAIL:DIS
    May 18 17:40:48 DEBUG TSF:TDI:TSL
    May 18 17:40:58 DEBUG TSM:FAIL:RE-INIT
    May 18 17:40:58 DEBUG TSM:INIT
    May 18 17:40:58 DEBUG !TSM:INIT:TSP FAIL
    May 18 17:40:58 DEBUG TSM:FAIL:CNT=5
    May 18 17:40:58 DEBUG TSM:FAIL:DIS
    May 18 17:40:58 DEBUG TSF:TDI:TSL
    May 18 17:41:08 DEBUG TSM:FAIL:RE-INIT
    May 18 17:41:08 DEBUG TSM:INIT
    May 18 17:41:08 DEBUG !TSM:INIT:TSP FAIL
    May 18 17:41:08 DEBUG TSM:FAIL:CNT=6
    May 18 17:41:08 DEBUG TSM:FAIL:DIS
    May 18 17:41:08 DEBUG TSF:TDI:TSL
    

    And here's the output from the DHT11 node:

    16 RF24:INIT
    23 RF24:INIT:PIN,CE=9,CS=10
    25 RF24:SBY
    26 RF24:WBR:REG=0,VAL=14
    33 RF24:WBR:REG=3,VAL=3
    35 RF24:WBR:REG=4,VAL=95
    37 RF24:WBR:REG=5,VAL=76
    39 RF24:WBR:REG=6,VAL=37
    43 RF24:WBR:REG=29,VAL=4
    45 RF24:RBR:REG=29,VAL=4
    47 RF24:RBR:REG=6,VAL=37
    49 RF24:RBR:REG=5,VAL=76
    51 RF24:WBR:REG=2,VAL=2
    53 RF24:WBR:REG=1,VAL=0
    56 RF24:WBR:REG=28,VAL=3
    58 RF24:FRX
    59 RF24:FTX
    60 RF24:WBR:REG=7,VAL=112
    62 RF24:WBR:REG=2,VAL=3
    65 RF24:WBR:REG=1,VAL=1
    67 RF24:STL
    68 RF24:WBR:REG=0,VAL=15
    70 RF24:WBR:REG=10,VAL=199
    72 RF24:SPL
    73 RF24:WBR:REG=0,VAL=14
    76 RF24:OWP:RCPT=255
    78 RF24:WBR:REG=10,VAL=255
    80 RF24:WBR:REG=16,VAL=255
    82 RF24:TXM:TO=255,LEN=7
    84 RF24:FTX
    1684 RF24:WBR:REG=7,VAL=48
    1686 RF24:STL
    1688 RF24:WBR:REG=0,VAL=15
    1690 RF24:WBR:REG=10,VAL=199
    1693 RF24:RBR:REG=23,VAL=1
    1695 RF24:RBR:REG=23,VAL=1
    1698 RF24:RBR:REG=23,VAL=1
    1700 RF24:RBR:REG=23,VAL=1
    1703 RF24:RBR:REG=23,VAL=1
    1705 RF24:RBR:REG=23,VAL=1
    1709 RF24:RBR:REG=23,VAL=1
    1711 RF24:RBR:REG=23,VAL=1
    1713 RF24:RBR:REG=23,VAL=1
    1716 RF24:RBR:REG=23,VAL=1
    1718 RF24:RBR:REG=23,VAL=1
    1721 RF24:RBR:REG=23,VAL=1
    1723 RF24:RBR:REG=23,VAL=1
    1726 RF24:RBR:REG=23,VAL=1
    1728 RF24:RBR:REG=23,VAL=1
    1731 RF24:RBR:REG=23,VAL=1
    1733 RF24:RBR:REG=23,VAL=1
    1735 RF24:RBR:REG=23,VAL=1
    1738 RF24:RBR:REG=23,VAL=1
    1740 RF24:RBR:REG=23,VAL=1
    1743 RF24:RBR:REG=23,VAL=1
    1745 RF24:RBR:REG=23,VAL=1
    1748 RF24:RBR:REG=23,VAL=1
    1751 RF24:RBR:REG=23,VAL=1
    1754 RF24:RBR:REG=23,VAL=1
    1756 RF24:RBR:REG=23,VAL=1
    1758 RF24:RBR:REG=23,VAL=1
    1761 RF24:RBR:REG=23,VAL=1
    1763 RF24:RBR:REG=23,VAL=1
    1766 RF24:RBR:REG=23,VAL=1
    1768 RF24:RBR:REG=23,VAL=1
    1771 RF24:RBR:REG=23,VAL=1
    1773 RF24:RBR:REG=23,VAL=1
    1776 RF24:RBR:REG=23,VAL=1
    1778 RF24:RBR:REG=23,VAL=1
    1781 RF24:RBR:REG=23,VAL=1
    1783 RF24:RBR:REG=23,VAL=1
    1785 RF24:RBR:REG=23,VAL=1
    1788 RF24:RBR:REG=23,VAL=1
    1790 RF24:RBR:REG=23,VAL=1
    1794 RF24:RBR:REG=23,VAL=1
    1796 RF24:RBR:REG=23,VAL=1
    1799 RF24:RBR:REG=23,VAL=1
    1801 RF24:RBR:REG=23,VAL=1
    1804 RF24:RBR:REG=23,VAL=1
    1806 RF24:RBR:REG=23,VAL=1
    1808 RF24:RBR:REG=23,VAL=1
    1811 RF24:RBR:REG=23,VAL=1
    1813 RF24:RBR:REG=23,VAL=1
    1816 RF24:RBR:REG=23,VAL=1
    1818 RF24:RBR:REG=23,VAL=1
    1821 RF24:RBR:REG=23,VAL=1
    1823 RF24:RBR:REG=23,VAL=1
    1826 RF24:RBR:REG=23,VAL=1
    1828 RF24:RBR:REG=23,VAL=1
    1830 RF24:RBR:REG=23,VAL=1
    1833 RF24:RBR:REG=23,VAL=1
    1836 RF24:RBR:REG=23,VAL=1
    1839 RF24:RBR:REG=23,VAL=1
    1841 RF24:RBR:REG=23,VAL=1
    1844 RF24:RBR:REG=23,VAL=1
    1846 RF24:RBR:REG=23,VAL=1
    1849 RF24:RBR:REG=23,VAL=1
    1851 RF24:RBR:REG=23,VAL=1
    1853 RF24:RBR:REG=23,VAL=1
    1856 RF24:RBR:REG=23,VAL=1
    1858 RF24:RBR:REG=23,VAL=1
    1861 RF24:RBR:REG=23,VAL=1
    1863 RF24:RBR:REG=23,VAL=1
    1866 RF24:RBR:REG=23,VAL=1
    1868 RF24:RBR:REG=23,VAL=1
    1871 RF24:RBR:REG=23,VAL=1
    1873 RF24:RBR:REG=23,VAL=1
    1875 RF24:RBR:REG=23,VAL=1
    1879 RF24:RBR:REG=23,VAL=1
    1881 RF24:RBR:REG=23,VAL=1
    1884 RF24:RBR:REG=23,VAL=1
    1886 RF24:RBR:REG=23,VAL=1
    1889 RF24:RBR:REG=23,VAL=1
    1891 RF24:RBR:REG=23,VAL=1
    1894 RF24:RBR:REG=23,VAL=1
    1896 RF24:RBR:REG=23,VAL=1
    1899 RF24:RBR:REG=23,VAL=1
    1901 RF24:RBR:REG=23,VAL=1
    1903 RF24:RBR:REG=23,VAL=1
    1906 RF24:RBR:REG=23,VAL=1
    1908 RF24:RBR:REG=23,VAL=1
    1911 RF24:RBR:REG=23,VAL=1
    1913 RF24:RBR:REG=23,VAL=1
    1916 RF24:RBR:REG=23,VAL=1
    1918 RF24:RBR:REG=23,VAL=1
    1922 RF24:RBR:REG=23,VAL=1
    1924 RF24:RBR:REG=23,VAL=1
    1926 RF24:RBR:REG=23,VAL=1
    1929 RF24:RBR:REG=23,VAL=1
    1931 RF24:RBR:REG=23,VAL=1
    1934 RF24:RBR:REG=23,VAL=1
    1936 RF24:RBR:REG=23,VAL=1
    1939 RF24:RBR:REG=23,VAL=1
    1941 RF24:RBR:REG=23,VAL=1
    1944 RF24:RBR:REG=23,VAL=1
    1946 RF24:RBR:REG=23,VAL=1
    1948 RF24:RBR:REG=23,VAL=1
    1951 RF24:RBR:REG=23,VAL=1
    1953 RF24:RBR:REG=23,VAL=1
    1956 RF24:RBR:REG=23,VAL=1
    1958 RF24:RBR:REG=23,VAL=1
    1961 RF24:RBR:REG=23,VAL=1
    1964 RF24:RBR:REG=23,VAL=1
    1967 RF24:RBR:REG=23,VAL=1
    1969 RF24:RBR:REG=23,VAL=1
    1971 RF24:RBR:REG=23,VAL=1
    1974 RF24:RBR:REG=23,VAL=1
    1976 RF24:RBR:REG=23,VAL=1
    1979 RF24:RBR:REG=23,VAL=1
    1981 RF24:RBR:REG=23,VAL=1
    1984 RF24:RBR:REG=23,VAL=1
    1986 RF24:RBR:REG=23,VAL=1
    1989 RF24:RBR:REG=23,VAL=1
    1991 RF24:RBR:REG=23,VAL=1
    1993 RF24:RBR:REG=23,VAL=1
    1996 RF24:RBR:REG=23,VAL=1
    1998 RF24:RBR:REG=23,VAL=1
    2001 RF24:RBR:REG=23,VAL=1
    2003 RF24:RBR:REG=23,VAL=1
    2007 RF24:RBR:REG=23,VAL=1
    2009 RF24:RBR:REG=23,VAL=1
    2012 RF24:RBR:REG=23,VAL=1
    2014 RF24:RBR:REG=23,VAL=1
    2016 RF24:RBR:REG=23,VAL=1
    2019 RF24:RBR:REG=23,VAL=1
    2021 RF24:RBR:REG=23,VAL=1
    2024 RF24:RBR:REG=23,VAL=1
    2026 RF24:RBR:REG=23,VAL=1
    2029 RF24:RBR:REG=23,VAL=1
    2031 RF24:RBR:REG=23,VAL=1
    2034 RF24:RBR:REG=23,VAL=1
    2036 RF24:RBR:REG=23,VAL=1
    2039 RF24:RBR:REG=23,VAL=1
    2041 RF24:RBR:REG=23,VAL=1
    2043 RF24:RBR:REG=23,VAL=1
    2046 RF24:RBR:REG=23,VAL=1
    2049 RF24:RBR:REG=23,VAL=1
    2052 RF24:RBR:REG=23,VAL=1
    2054 RF24:RBR:REG=23,VAL=1
    2057 RF24:RBR:REG=23,VAL=1
    2059 RF24:RBR:REG=23,VAL=1
    2062 RF24:RBR:REG=23,VAL=1
    2064 RF24:RBR:REG=23,VAL=1
    2066 RF24:RBR:REG=23,VAL=1
    2069 RF24:RBR:REG=23,VAL=1
    2071 RF24:RBR:REG=23,VAL=1
    2074 RF24:RBR:REG=23,VAL=1
    2076 RF24:RBR:REG=23,VAL=1
    2079 RF24:RBR:REG=23,VAL=1
    2081 RF24:RBR:REG=23,VAL=1
    2084 RF24:RBR:REG=23,VAL=1
    2086 RF24:RBR:REG=23,VAL=1
    2088 RF24:RBR:REG=23,VAL=1
    2092 RF24:RBR:REG=23,VAL=1
    2094 RF24:RBR:REG=23,VAL=1
    2097 RF24:RBR:REG=23,VAL=1
    2099 RF24:RBR:REG=23,VAL=1
    2102 RF24:RBR:REG=23,VAL=1
    2104 RF24:RBR:REG=23,VAL=1
    2107 RF24:RBR:REG=23,VAL=1
    2109 RF24:RBR:REG=23,VAL=1
    2111 RF24:RBR:REG=23,VAL=1
    2114 RF24:RBR:REG=23,VAL=1
    2116 RF24:RBR:REG=23,VAL=1
    2119 RF24:RBR:REG=23,VAL=1
    2121 RF24:RBR:REG=23,VAL=1
    2124 RF24:RBR:REG=23,VAL=1
    2126 RF24:RBR:REG=23,VAL=1
    2129 RF24:RBR:REG=23,VAL=1
    2131 RF24:RBR:REG=23,VAL=1
    2134 RF24:RBR:REG=23,VAL=1
    2137 RF24:RBR:REG=23,VAL=1
    2139 RF24:RBR:REG=23,VAL=1
    2142 RF24:RBR:REG=23,VAL=1
    2144 RF24:RBR:REG=23,VAL=1
    2147 RF24:RBR:REG=23,VAL=1
    2149 RF24:RBR:REG=23,VAL=1
    2152 RF24:RBR:REG=23,VAL=1
    2154 RF24:RBR:REG=23,VAL=1
    2157 RF24:RBR:REG=23,VAL=1
    2159 RF24:RBR:REG=23,VAL=1
    2161 RF24:RBR:REG=23,VAL=1
    2164 RF24:RBR:REG=23,VAL=1
    2166 RF24:RBR:REG=23,VAL=1
    2169 RF24:RBR:REG=23,VAL=1
    2171 RF24:RBR:REG=23,VAL=1
    2174 RF24:RBR:REG=23,VAL=1
    2177 RF24:RBR:REG=23,VAL=1
    2180 RF24:RBR:REG=23,VAL=1
    2182 RF24:RBR:REG=23,VAL=1
    2184 RF24:RBR:REG=23,VAL=1
    2187 RF24:RBR:REG=23,VAL=1
    2189 RF24:RBR:REG=23,VAL=1
    2192 RF24:RBR:REG=23,VAL=1
    2194 RF24:RBR:REG=23,VAL=1
    2197 RF24:RBR:REG=23,VAL=1
    2199 RF24:RBR:REG=23,VAL=1
    2202 RF24:RBR:REG=23,VAL=1
    2204 RF24:RBR:REG=23,VAL=1
    2206 RF24:RBR:REG=23,VAL=1
    2209 RF24:RBR:REG=23,VAL=1
    2211 RF24:RBR:REG=23,VAL=1
    2214 RF24:RBR:REG=23,VAL=1
    2216 RF24:RBR:REG=23,VAL=1
    2220 RF24:RBR:REG=23,VAL=1
    2222 RF24:RBR:REG=23,VAL=1
    2225 RF24:RBR:REG=23,VAL=1
    2227 RF24:RBR:REG=23,VAL=1
    2229 RF24:RBR:REG=23,VAL=1
    2232 RF24:RBR:REG=23,VAL=1
    2234 RF24:RBR:REG=23,VAL=1
    2237 RF24:RBR:REG=23,VAL=1
    2239 RF24:RBR:REG=23,VAL=1
    2242 RF24:RBR:REG=23,VAL=1
    2244 RF24:RBR:REG=23,VAL=1
    2247 RF24:RBR:REG=23,VAL=1
    2249 RF24:RBR:REG=23,VAL=1
    2251 RF24:RBR:REG=23,VAL=1
    2254 RF24:RBR:REG=23,VAL=1
    2256 RF24:RBR:REG=23,VAL=1
    2259 RF24:RBR:REG=23,VAL=1
    2262 RF24:RBR:REG=23,VAL=1
    2265 RF24:RBR:REG=23,VAL=1
    2267 RF24:RBR:REG=23,VAL=1
    2270 RF24:RBR:REG=23,VAL=1
    2272 RF24:RBR:REG=23,VAL=1
    2275 RF24:RBR:REG=23,VAL=1
    2277 RF24:RBR:REG=23,VAL=1
    2279 RF24:RBR:REG=23,VAL=1
    2282 RF24:RBR:REG=23,VAL=1
    2284 RF24:RBR:REG=23,VAL=1
    2287 RF24:RBR:REG=23,VAL=1
    2289 RF24:RBR:REG=23,VAL=1
    2292 RF24:RBR:REG=23,VAL=1
    2294 RF24:RBR:REG=23,VAL=1
    2297 RF24:RBR:REG=23,VAL=1
    2299 RF24:RBR:REG=23,VAL=1
    2301 RF24:RBR:REG=23,VAL=1
    2305 RF24:RBR:REG=23,VAL=1
    2307 RF24:RBR:REG=23,VAL=1
    2310 RF24:RBR:REG=23,VAL=1
    2312 RF24:RBR:REG=23,VAL=1
    2315 RF24:RBR:REG=23,VAL=1
    2317 RF24:RBR:REG=23,VAL=1
    2320 RF24:RBR:REG=23,VAL=1
    2322 RF24:RBR:REG=23,VAL=1
    2324 RF24:RBR:REG=23,VAL=1
    2327 RF24:RBR:REG=23,VAL=1
    2329 RF24:RBR:REG=23,VAL=1
    2332 RF24:RBR:REG=23,VAL=1
    2334 RF24:RBR:REG=23,VAL=1
    2337 RF24:RBR:REG=23,VAL=1
    2339 RF24:RBR:REG=23,VAL=1
    2342 RF24:RBR:REG=23,VAL=1
    2344 RF24:RBR:REG=23,VAL=1
    2347 RF24:RBR:REG=23,VAL=1
    2350 RF24:RBR:REG=23,VAL=1
    2352 RF24:RBR:REG=23,VAL=1
    2355 RF24:RBR:REG=23,VAL=1
    2357 RF24:RBR:REG=23,VAL=1
    2360 RF24:RBR:REG=23,VAL=1
    2362 RF24:RBR:REG=23,VAL=1
    2365 RF24:RBR:REG=23,VAL=1
    2367 RF24:RBR:REG=23,VAL=1
    2369 RF24:RBR:REG=23,VAL=1
    2372 RF24:RBR:REG=23,VAL=1
    2374 RF24:RBR:REG=23,VAL=1
    2377 RF24:RBR:REG=23,VAL=1
    2379 RF24:RBR:REG=23,VAL=1
    2382 RF24:RBR:REG=23,VAL=1
    2384 RF24:RBR:REG=23,VAL=1
    2387 RF24:RBR:REG=23,VAL=1
    2390 RF24:RBR:REG=23,VAL=1
    2393 RF24:RBR:REG=23,VAL=1
    2395 RF24:RBR:REG=23,VAL=1
    2397 RF24:RBR:REG=23,VAL=1
    2400 RF24:RBR:REG=23,VAL=1
    2402 RF24:RBR:REG=23,VAL=1
    2405 RF24:RBR:REG=23,VAL=1
    2407 RF24:RBR:REG=23,VAL=1
    2410 RF24:RBR:REG=23,VAL=1
    2412 RF24:RBR:REG=23,VAL=1
    2415 RF24:RBR:REG=23,VAL=1
    2417 RF24:RBR:REG=23,VAL=1
    2419 RF24:RBR:REG=23,VAL=1
    2422 RF24:RBR:REG=23,VAL=1
    2424 RF24:RBR:REG=23,VAL=1
    2427 RF24:RBR:REG=23,VAL=1
    2429 RF24:RBR:REG=23,VAL=1
    2433 RF24:RBR:REG=23,VAL=1
    2435 RF24:RBR:REG=23,VAL=1
    2438 RF24:RBR:REG=23,VAL=1
    2440 RF24:RBR:REG=23,VAL=1
    2442 RF24:RBR:REG=23,VAL=1
    2445 RF24:RBR:REG=23,VAL=1
    2447 RF24:RBR:REG=23,VAL=1
    2450 RF24:RBR:REG=23,VAL=1
    2452 RF24:RBR:REG=23,VAL=1
    2455 RF24:RBR:REG=23,VAL=1
    2457 RF24:RBR:REG=23,VAL=1
    2460 RF24:RBR:REG=23,VAL=1
    2462 RF24:RBR:REG=23,VAL=1
    2464 RF24:RBR:REG=23,VAL=1
    2467 RF24:RBR:REG=23,VAL=1
    2469 RF24:RBR:REG=23,VAL=1
    2472 RF24:RBR:REG=23,VAL=1
    2475 RF24:RBR:REG=23,VAL=1
    2478 RF24:RBR:REG=23,VAL=1
    2480 RF24:RBR:REG=23,VAL=1
    2483 RF24:RBR:REG=23,VAL=1
    2485 RF24:RBR:REG=23,VAL=1
    2487 RF24:RBR:REG=23,VAL=1
    2490 RF24:RBR:REG=23,VAL=1
    2492 RF24:RBR:REG=23,VAL=1
    2495 RF24:RBR:REG=23,VAL=1
    2497 RF24:RBR:REG=23,VAL=1
    2500 RF24:RBR:REG=23,VAL=1
    2502 RF24:RBR:REG=23,VAL=1
    2505 RF24:RBR:REG=23,VAL=1
    2507 RF24:RBR:REG=23,VAL=1
    2510 RF24:RBR:REG=23,VAL=1
    2512 RF24:RBR:REG=23,VAL=1
    2514 RF24:RBR:REG=23,VAL=1
    2518 RF24:RBR:REG=23,VAL=1
    2520 RF24:RBR:REG=23,VAL=1
    2523 RF24:RBR:REG=23,VAL=1
    2525 RF24:RBR:REG=23,VAL=1
    2528 RF24:RBR:REG=23,VAL=1
    2530 RF24:RBR:REG=23,VAL=1
    2533 RF24:RBR:REG=23,VAL=1
    2535 RF24:RBR:REG=23,VAL=1
    2537 RF24:RBR:REG=23,VAL=1
    2540 RF24:RBR:REG=23,VAL=1
    2542 RF24:RBR:REG=23,VAL=1
    2545 RF24:RBR:REG=23,VAL=1
    2547 RF24:RBR:REG=23,VAL=1
    2550 RF24:RBR:REG=23,VAL=1
    2552 RF24:RBR:REG=23,VAL=1
    2555 RF24:RBR:REG=23,VAL=1
    2557 RF24:RBR:REG=23,VAL=1
    2560 RF24:RBR:REG=23,VAL=1
    2563 RF24:RBR:REG=23,VAL=1
    2565 RF24:RBR:REG=23,VAL=1
    2568 RF24:RBR:REG=23,VAL=1
    2570 RF24:RBR:REG=23,VAL=1
    2573 RF24:RBR:REG=23,VAL=1
    2575 RF24:RBR:REG=23,VAL=1
    2578 RF24:RBR:REG=23,VAL=1
    2580 RF24:RBR:REG=23,VAL=1
    2582 RF24:RBR:REG=23,VAL=1
    2585 RF24:RBR:REG=23,VAL=1
    2587 RF24:RBR:REG=23,VAL=1
    2590 RF24:RBR:REG=23,VAL=1
    2592 RF24:RBR:REG=23,VAL=1
    2595 RF24:RBR:REG=23,VAL=1
    2597 RF24:RBR:REG=23,VAL=1
    2600 RF24:RBR:REG=23,VAL=1
    2603 RF24:RBR:REG=23,VAL=1
    2605 RF24:RBR:REG=23,VAL=1
    2608 RF24:RBR:REG=23,VAL=1
    2610 RF24:RBR:REG=23,VAL=1
    2613 RF24:RBR:REG=23,VAL=1
    2615 RF24:RBR:REG=23,VAL=1
    2618 RF24:RBR:REG=23,VAL=1
    2620 RF24:RBR:REG=23,VAL=1
    2623 RF24:RBR:REG=23,VAL=1
    2625 RF24:RBR:REG=23,VAL=1
    2627 RF24:RBR:REG=23,VAL=1
    2630 RF24:RBR:REG=23,VAL=1
    2632 RF24:RBR:REG=23,VAL=1
    2635 RF24:RBR:REG=23,VAL=1
    2637 RF24:RBR:REG=23,VAL=1
    2640 RF24:RBR:REG=23,VAL=1
    2642 RF24:RBR:REG=23,VAL=1
    2646 RF24:RBR:REG=23,VAL=1
    2648 RF24:RBR:REG=23,VAL=1
    2651 RF24:RBR:REG=23,VAL=1
    2653 RF24:RBR:REG=23,VAL=1
    2655 RF24:RBR:REG=23,VAL=1
    2658 RF24:RBR:REG=23,VAL=1
    2660 RF24:RBR:REG=23,VAL=1
    2663 RF24:RBR:REG=23,VAL=1
    2665 RF24:RBR:REG=23,VAL=1
    2668 RF24:RBR:REG=23,VAL=1
    2670 RF24:RBR:REG=23,VAL=1
    2673 RF24:RBR:REG=23,VAL=1
    2675 RF24:RBR:REG=23,VAL=1
    2677 RF24:RBR:REG=23,VAL=1
    2680 RF24:RBR:REG=23,VAL=1
    2682 RF24:RBR:REG=23,VAL=1
    2685 RF24:RBR:REG=23,VAL=1
    2688 RF24:RBR:REG=23,VAL=1
    2691 RF24:RBR:REG=23,VAL=1
    2693 RF24:RBR:REG=23,VAL=1
    2696 RF24:RBR:REG=23,VAL=1
    2698 RF24:RBR:REG=23,VAL=1
    2700 RF24:RBR:REG=23,VAL=1
    2703 RF24:RBR:REG=23,VAL=1
    2705 RF24:RBR:REG=23,VAL=1
    2708 RF24:RBR:REG=23,VAL=1
    2710 RF24:RBR:REG=23,VAL=1
    2713 RF24:RBR:REG=23,VAL=1
    2715 RF24:RBR:REG=23,VAL=1
    2718 RF24:RBR:REG=23,VAL=1
    2720 RF24:RBR:REG=23,VAL=1
    2722 RF24:RBR:REG=23,VAL=1
    2725 RF24:RBR:REG=23,VAL=1
    2727 RF24:RBR:REG=23,VAL=1
    2731 RF24:RBR:REG=23,VAL=1
    2733 RF24:RBR:REG=23,VAL=1
    2736 RF24:RBR:REG=23,VAL=1
    2738 RF24:RBR:REG=23,VAL=1
    2741 RF24:RBR:REG=23,VAL=1
    2743 RF24:RBR:REG=23,VAL=1
    

    I'm not sure what you mean by the gateway sketch, as I understand it, there isn't one for the RPi setup when you have the NRF2401 radio attached directly to the Raspberry Pi GPIO pins, unless you just mean the mysgw.cpp from /mysensors/examples_linux/

    Here is the sketch for the DHT11 node (arduino pro mini, 5v -> 3.3v dedicated regulator for the DHT and radio with capacitors installed):

    Is it simply not possible to have both gateway and Openhab live on the same RPi? Really at a loss here; very discouraging.



  • More info from logs:

    openhab> log:tail
    18:08:40.219 [INFO ] [bpanel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
    19:26:55.033 [INFO ] [rthome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
    19:26:56.968 [INFO ] [i.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.0.41:8080
    19:26:56.975 [INFO ] [i.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.0.41:8443
    19:26:58.438 [INFO ] [marthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
    19:26:58.572 [INFO ] [.ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
    19:26:59.304 [DEBUG] [org.openhab.binding.mysensors        ] - BundleEvent STARTING - org.openhab.binding.mysensors
    19:26:59.398 [DEBUG] [org.openhab.binding.mysensors        ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=392, service.bundleid=232, service.scope=bundle, component.name=org.openhab.binding.mysensors.factory.MySensorsHandlerFactory, component.id=252} - org.openhab.binding.mysensors
    19:26:59.412 [DEBUG] [org.openhab.binding.mysensors        ] - BundleEvent STARTED - org.openhab.binding.mysensors
    19:27:00.113 [DEBUG] [ensors.handler.MySensorsBridgeHandler] - Initialization of the MySensors bridge
    19:27:00.130 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-ser:e8bde86b' changed from UNINITIALIZED to INITIALIZING
    19:27:00.189 [DEBUG] [sensors.factory.MySensorsCacheFactory] - Cache file: given_ids.cached exist.
    19:27:00.193 [DEBUG] [sensors.factory.MySensorsCacheFactory] - Cache (given_ids) content: []
    19:27:00.219 [DEBUG] [ocol.serial.MySensorsSerialConnection] - Enabling connection watchdog
    19:27:00.226 [DEBUG] [ocol.serial.MySensorsSerialConnection] - Connecting to /dev/ttyUSB0 [baudRate:115200]
    19:27:00.239 [DEBUG] [org.openhab.binding.mysensors        ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=401, service.bundleid=232, service.scope=singleton} - org.openhab.binding.mysensors
    19:27:00.241 [DEBUG] [s.discovery.MySensorsDiscoveryService] - Starting MySensors discovery scan
    19:27:00.243 [DEBUG] [ensors.handler.MySensorsBridgeHandler] - Initialization of the MySensors bridge DONE!
    19:27:00.302 [DEBUG] [ocol.serial.MySensorsSerialConnection] - Serial port event listener started
    19:27:00.304 [DEBUG] [ocol.serial.MySensorsSerialConnection] - Successfully connected to serial port.
    19:27:00.317 [WARN ] [ocol.serial.MySensorsSerialConnection] - Skipping I_VERSION connection test, not recommended...
    19:27:00.343 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 255;3;0;14;Gateway startup complete.
    19:27:00.355 [DEBUG] [sensors.factory.MySensorsCacheFactory] - Writing on cache given_ids, content: []
    19:27:00.357 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-ser:e8bde86b' changed from INITIALIZING to ONLINE
    19:27:00.360 [INFO ] [ocol.serial.MySensorsSerialConnection] - Successfully connected to MySensors Bridge.
    19:27:00.368 [WARN ] [orsAbstractConnection$MySensorsReader] - Exception on reading from connection
    java.text.ParseException: class java.lang.NumberFormatException : For input string: "Gateway startup complete."
            at org.openhab.binding.mysensors.internal.protocol.message.MySensorsMessage.parse(MySensorsMessage.java:342) ~[232:org.openhab.binding.mysensors:2.4.0.201812040738]
            at org.openhab.binding.mysensors.internal.protocol.MySensorsAbstractConnection$MySensorsReader.run(MySensorsAbstractConnection.java:338) [232:org.openhab.binding.mysensors:2.4.0.201812040738]
            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
            at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
            at java.lang.Thread.run(Thread.java:748) [?:?]
    19:27:00.390 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;0;0;18;2.3.1
    19:27:00.447 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Presentation Message received
    19:27:00.456 [DEBUG] [sensors.factory.MySensorsCacheFactory] - Writing on cache given_ids, content: [0]
    19:27:00.459 [WARN ] [s.discovery.MySensorsDiscoveryService] - Cannot automatic discover thing node: 0, child: 255 please insert it manually
    19:30:00.341 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;0;3;0;2;
    19:30:00.358 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;2;2.3.1
    19:30:03.338 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Network sanity check: PASSED
    19:30:03.341 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Sending I_HEARTBEAT_REQUESTs
    19:30:03.344 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;255;3;0;18;
    19:30:03.357 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;22;4909969
    19:33:06.346 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;0;3;0;2;
    19:33:06.361 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;2;2.3.1
    19:33:09.345 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Network sanity check: PASSED
    19:33:09.348 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Sending I_HEARTBEAT_REQUESTs
    19:33:09.350 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;255;3;0;18;
    19:33:09.366 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;22;5095971
    19:36:12.351 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;0;3;0;2;
    19:36:12.363 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from eway received: 0;255;3;0;2;2.3.1
    19:36:15.351 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Network sanity check: PASSED
    19:36:15.354 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Sending I_HEARTBEAT_REQUESTs
    19:36:15.357 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;255;3;0;18;
    19:36:15.371 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;22;5281981
    

    I built a small breakout board for the radio and it appears to connect to the OH2 instance successfully with this pinout board.

    Even though the gateway appears to be recognized by OH2, the node still looks like this:

    16 MCO:BGN:INIT NODE,CP=RNNNA---,REL=255,VER=2.3.1
    26 TSM:INIT
    27 TSF:WUR:MS=0
    33 TSM:INIT:TSP OK
    35 TSF:SID:OK,ID=199
    37 TSM:FPAR
    1637 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    3645 !TSM:FPAR:NO REPLY
    3647 TSM:FPAR
    5246 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    7255 !TSM:FPAR:NO REPLY
    7257 TSM:FPAR
    8856 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    10864 !TSM:FPAR:NO REPLY
    10866 TSM:FPAR
    12466 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    14474 !TSM:FPAR:FAIL
    14475 TSM:FAIL:CNT=1
    14477 TSM:FAIL:DIS
    14479 TSF:TDI:TSL
    

  • Mod

    @iamtheghost said in Never been able to get MySensors to work:

    Both authentic, no "blobs", real chips.

    Still, they can be counterfeit nRF24L01+ (e.g. https://forum.mysensors.org/topic/1664/which-are-the-best-nrf24l01-modules)

    I don't feel like either of these are horrible soldering jobs.

    The top appears OK, the DHT pins look 'battle-tested' though 😉

    Followed this guide "to the T"

    That guide is already 2 years old; I'm not sure if it is correct. This is the official guide.

    May 18 17:40:48 DEBUG !TSM:INIT:TSP FAIL

    That is a clear indication of communication error between MySensors and the radio; the radio communication check by MySensors has failed.
    There's no use trying to continue with this error.

    I built a small breakout board for the radio and it appears to connect to the OH2 instance successfully with this pinout board.

    Not sure what you mean here...

    Even though the gateway appears to be recognized by OH2, the node still looks like this

    Yes, the gateway starts and can be connected to by OH2, but the gateway cannot communicate with the radio.
    There's no use looking deeper into the node, cause your gateway is faulty for some reason.

    Would you be able to build an Arduino serial gateway (e.g. based on Uno or Nano) and test if that gets the communication running? That way we could rule out defective radio(s).
    Beware to power the radio from 3.3V then.



  • @yveaux said in Never been able to get MySensors to work:

    That guide is already 2 years old; I'm not sure if it is correct. This is the official guide.

    That guide is the only complete tutorial I've found to getting MySensors 2.4 working with OpenHab 2.4 via the serial gateway. While the original post is 2 years old, it has been updated multiple times. I've followed the official guide as well, to the same result, however.

    Still, they can be counterfeit nRF24L01+ (e.g. https://forum.mysensors.org/topic/1664/which-are-the-best-nrf24l01-modules)

    Looking at my ICs through a magnifying lens, it appears that mine have the "hole" in the middle of the "+" symbol on the etching. They were purchased from Amazon, but I can't recall which supplier.

    Would you be able to build an Arduino serial gateway (e.g. based on Uno or Nano) and test if that gets the communication running?

    Yeah, I can throw one together.



  • @yveaux

    Okay, threw together an Arduino Nano serial gateway. It's currently plugged into the Pi via USB. Same port, ttyUSB0, and appears to be responding to sanity checks. Need to look at the gateway logs, now.


  • Mod

    @iamtheghost said in Never been able to get MySensors to work:

    Looking at my ICs through a magnifying lens, it appears that mine have the "hole" in the middle of the "+" symbol on the etching. They were purchased from Amazon, but I can't recall which supplier.

    We know now, that It is impossible to identify fakes from the outside (apart from the blob ones obviously).

    Okay, threw together an Arduino Nano serial gateway. It's currently plugged into the Pi via USB. Same port, ttyUSB0, and appears to be responding to sanity checks. Need to look at the gateway logs, now.

    Well, that sounds hopeful. Does the node find its parent now? Are the messages coming in correctly on the gateway?



  • If the proposed serial gateway wont work, then try something else, if you have a friend that also use home automation, maybe you can try to connect you gateway and sensor to his system, then you are away from your home, maybe something is disturbing your 2.4GHz communication


  • Mod

    @bjacobse IMHO wireless disturbance is quite unlikely to be the root cause here, as messages do come in to the gateway (they pass the radio's crc check, so they are almost certain valid messages).
    The gateway just reads them as all zeroes from the radio for some bizarre reason.



  • Is your power supply enough to supply the right current? Also play with the RF POWER when you build the gateway.



  • @iamtheghost I'm sorry I could not post any kind of solution, but just to say "Me too!".

    Two years and half of experimentations, different platform (ESP8266 / ESP-12) but same radio and same h/w for the controller, and in the end I had your exact same results.

    Same as you, I did everything I could to figure out the problem, including spending and "insane" amount of time (and money!) in sourcing the same hardware components from different sources.

    I did change the hardware (wires, components, microSD, cables, power sources, etc. etc. ) so many times that I can't even count; that poor raspberry of mine has been flashed over and over; same goes for the ESP-module, which I have also tried in every possible "flavour" (NodeMCU, Lolin, Amica, WeMos, etc. ). And in doing so I left quite a trail of "weird and unsolved" problems here in the forum.

    In the end, just like you have discovered, I could never make it work!
    I was captivated by the idea of having a "mesh sensors network" working around my building, especially because I have wide areas not covered by WiFi and I was intrigued (to say the least) by the possibilities promised by MySensors. But as you said, "It promises all the bells and whistles for cheap home automation, but despite my every effort, I cannot even read a simple DHT11". (*)

    (to be precise, in my case it was also a BME280; I switched to those AIO sensors after failing with DHT variants)

    I did never solve the issues, and I abandoned this platform when I reached the verge of my patience having exactly the same sketch with the same hardware (really, the same sensor, the same radio, the same wires, and two identical boards) working on one board and failing on another.

    After 2 years and a half I gave up on the idea of a "mesh network" and moved to another library (still free and still available to install on a raspberry to use as a controller, and with a beautiful UI)... wish I had done it sooner. In 4 days I fixed my whole network, having a plethora of sensors constantly reporting, never hanging up for any reason (I mean, I tried removing power in 60 seconds intervals for 5 minutes and in the end they all rebooted correctly with no errors) and with the bonus feature of outputting "eye friendly" data due to the different controller.

    Hence, I perfectly understand your situation and I know how it feels: the best suggestion I can give you is to "move on" and use a different library/architecture.



  • @neo-mod said in Never been able to get MySensors to work:

    @iamtheghost I'm sorry I could not post any kind of solution, but just to say "Me too!".

    Two years and half of experimentations, different platform (ESP8266 / ESP-12) but same radio and same h/w for the controller, and in the end I had your exact same results.

    Same as you, I did everything I could to figure out the problem, including spending and "insane" amount of time (and money!) in sourcing the same hardware components from different sources.

    I did change the hardware (wires, components, microSD, cables, power sources, etc. etc. ) so many times that I can't even count; that poor raspberry of mine has been flashed over and over; same goes for the ESP-module, which I have also tried in every possible "flavour" (NodeMCU, Lolin, Amica, WeMos, etc. ). And in doing so I left quite a trail of "weird and unsolved" problems here in the forum.

    In the end, just like you have discovered, I could never make it work!
    I was captivated by the idea of having a "mesh sensors network" working around my building, especially because I have wide areas not covered by WiFi and I was intrigued (to say the least) by the possibilities promised by MySensors. But as you said, "It promises all the bells and whistles for cheap home automation, but despite my every effort, I cannot even read a simple DHT11". (*)

    (to be precise, in my case it was also a BME280; I switched to those AIO sensors after failing with DHT variants)

    I did never solve the issues, and I abandoned this platform when I reached the verge of my patience having exactly the same sketch with the same hardware (really, the same sensor, the same radio, the same wires, and two identical boards) working on one board and failing on another.

    After 2 years and a half I gave up on the idea of a "mesh network" and moved to another library (still free and still available to install on a raspberry to use as a controller, and with a beautiful UI)... wish I had done it sooner. In 4 days I fixed my whole network, having a plethora of sensors constantly reporting, never hanging up for any reason (I mean, I tried removing power in 60 seconds intervals for 5 minutes and in the end they all rebooted correctly with no errors) and with the bonus feature of outputting "eye friendly" data due to the different controller.

    Hence, I perfectly understand your situation and I know how it feels: the best suggestion I can give you is to "move on" and use a different library/architecture.

    I knew I wasn't alone. I totally accept and encourage platforms that are geared towards EEs and programmers, and MySensors is definitely that. Even as a programmer by trade, it's still difficult.

    What library are you using now? I'm piqued.



  • @badisensors I'm using the 'official' 5v 2A transformer that came with the Pi kit when I bought it from Adafruit. Multimeter reads a flat 5v, no jumping around, and amperage/current draw seems to be normal.



  • Make a last try and change the RF POWER parameter when you build the gateway. If it is at high power set it to low power or the opposite. Did you try with other RF24 module?



  • Sorry, but you select most difficult way for build your sensor network.
    You spare one arduino like serial gateway or one Wemos like ethernet wifi gateway and two years hacking RPI gateway with no result.
    And you choose bad radio module too, I think. Instead of NRF24 use RFM69 and no more problems with distance in your home and mesh network function no needed.
    For all beginners I recommended step by step solution of problems, if something do not works.
    For example, first try simple communication between two modules using basic examples from RFM69 library for example.
    If it works, you have got certainty, that your hardware is OK ( radio properly connected to arduino ).
    Then you can load sketches for gateway and normal node to both modules and I bet, it will work.


  • Plugin Developer

    You can also check if messages come in to your Pi ok using minicom.

    For example:
    minicom -b 115200 -o -D /dev/ttyUSB0

    You would have to install minicom (sudo apt-get install minicom)
    You may have to change settings a bit so that it displays the data on newlines.



  • 2 years and keep trying without ask help??!!!
    I'm using lot of sensors since i'm registered on this forum and it works since first day.I only had problems with nrf24 chinese clones range,so a i changed all network to rfm69 and now i have an sensor 50m away from house and keep working every day.
    the only diference is that i use a serial gateway connected to raspberry pi. It's the arduino version with and rfm69 conected by usb.
    order some rfm69 from ebay and try again and order an arduino pro mini (1.x€) and an genuineftdi(clones won't work) or even an arduino nano with original ftdi chip and connect it by usb to the pi. I assure that it works.👍



  • At first I'm no expert of MySensors or openHAB.
    Perhaps I had luck but got the connection between MySensors and OH to work from
    the beginning with only minor problems. The system has now been working for almost 2 years and I did it this way.
    OH is installed on a RPi 3B, have a serial gateway on an Arduino Nano with nrf24L01 pa+lna the nodes (5 pcs) are built on Arduino pro mini.
    The nodes are 3 Door/Window sensors, one relay and one tempereture/humidity sensor.
    Since the gateway is placed in the basement and the nodes are on first floor one of the nodes is using nrf24L01 pa+lna and the other nrf24L01+.
    The nrf24L01+ are chines and I bought about 15 of them and tested them at a distance of 12m through 2 wooden walls and have to scrap 3 of them.
    The gateway and nodes have all standard sketches according to MySensors examples with minor changes. All nodes have fixed node_id.
    Installation:
    Downloaded "openHABianPi" SD card image file.
    Wrote the image to a SD card and put it in the RPi.
    Started the RPi and after some minutes OH was up and running.
    Complete insructions can be found at https://www.openhab.org/v2.4/docs/installation/openhabian.html.
    Connected the gateway to OH via a USB cable.
    Went to MySensors/Controller/openHAB and followed the "Install instructions" at https://github.com/tobof/openhab2-addons/wiki.
    Used Paper UI to configure the thing "MySensors serial gateway" and not .things file.
    Now the nodes (things) pop up in the Inbox. Don't remember if I had to restart the RPi, gateway and nodes.
    I hope this can help someone.



  • @iamtheghost I feel your pain brother. I am a newbie to MySensors and although got up and running relatively quickly with openHAB and an old Raspberry Pi 1 controller/gateway - I still spend days trying to sort out radio issues. At the moment it's replacing a standard nrf24L01 with the pa+lna version ... been at it for a couple of days without successful comms with gateway.

    Two years trying ... I salute you. Keep holding on to the fact that when it works it will be so satisfying 🙂



  • @iamtheghost Much as I admire those who got it all to work first time, the tenacity of those who have managed to get radio working against the unknown, and every sympathy for those who haven't, I really question the logic of the default MySensors recommendation with so many pirates and scammers flooding the market, and known 2.4GHz penetration problems.
    I have no doubt Nordic stand by their products, unfortunately it is their popularity which encouraged the pirates to flood the market such that even major suppliers have problems with verification.
    I can only suggest doing as I did with a router and a mobile to verify radio paths are solid, then you will know if the 2.4 devices should work, if not change frequency.
    My own decision to go go with 433MHz against 2.4GHz was based on this crude but effective first step, identifying blind spots. The standard RFM69 devices have not caused a single issue in 2 years, and as yet piracy is uncommon.



  • @zookazim be carefull with the nrf24 amplified boards.some times you just have less range because you incresed the signal power and starting have ecos and distortions on signals. I only has 1 amplified card and had poor range,just before change everyting to rfm69w ,not even need to be the hight power(hw )version to have more range than on 2.4 ghz cards


  • Plugin Developer

    I stopped using the amplified version and just used a normal version with an antenna. You can find them online. Works great.
    alt text

    https://www.aliexpress.com/item/32794109125.html



  • @tmaster Be careful not to compare apples and oranges, the frequency of the two devices react differently, higher frequencies tend to be more liable to attenuation and have shorter range.
    What is also often overlooked in the higher power versions of the 2.4 devices is the additional preamplifier stage which can make a difference at the reception extremes but overload in closer proximity...


  • Mod

    @alowhum said in Never been able to get MySensors to work:

    I stopped using the amplified version and just used a normal version with an antenna. You can find them online. Works great.

    The link actually does point to a pa+lna module (the BTE16-50), using a nRF24L01+ 'compatible' IC, the SI24R1.
    This would definately not be my module of preference...


  • Plugin Developer

    @Yveaux Ah, I didn't realise!

    it's working well though.



  • @iamtheghost sorry for the late reply.

    I moved to ThingsBoard which acts both as a controller (via the Rule Chain engine, a very powerfull yet very simple method to instantiate all kind of operations. For example: I'm fetching my sensors data every 5 minutes and uploading to wunderground and windy) and as a web gateway to access data with a nice UI.

    Sensors are still based on the "same old" NodeMCU board, and guess what: each variation of those boards (AMICA, Lolin, Lolin v3, etc.) now is working perfectly. I removed the radio module, since it won't be used anymore, and some of them are powered via battery shield (18650 LiPo with recharge port to be connected to a solar panel, for example).

    Here an example of one of my dashboards: you can also notice a ReedSwitch sensor and an Alarm Module that displays and Alarm each time the sensor reports "door open" and sends me an e-mail alert.
    alt text

    As for those stating that NodeMCU is a "wrong" choice: probably it is if one would like to use MySensors Library. But "per se" NodeMCU boards are extremely versatile, more than Arduino or WeMo which requires "stacking up" various modules/shields to obtain the same functionality offered by a NodeMCU in almost half the space.

    @kimot the radio module selection should be based upon the user-case scenario, at least as long as MySensors Library officially supports both NRF24 and RFM69. One case where you might want to stick with 2.4Ghz network is when your area is "heavily populated" by radio signals and interference from an airport less than 50km away in line-of-sight.

    @Tmaster I can assure you, at least in my case and I think that this has been the same for iamtheghost, I tried EVERY possible hardware variation out there. I spent months buying original components, both from resellers and producer.

    @iamtheghost said in Never been able to get MySensors to work:

    @neo-mod said in Never been able to get MySensors to work:

    @iamtheghost I'm sorry I could not post any kind of solution, but just to say "Me too!".

    Two years and half of experimentations, different platform (ESP8266 / ESP-12) but same radio and same h/w for the controller, and in the end I had your exact same results.

    Same as you, I did everything I could to figure out the problem, including spending and "insane" amount of time (and money!) in sourcing the same hardware components from different sources.

    I did change the hardware (wires, components, microSD, cables, power sources, etc. etc. ) so many times that I can't even count; that poor raspberry of mine has been flashed over and over; same goes for the ESP-module, which I have also tried in every possible "flavour" (NodeMCU, Lolin, Amica, WeMos, etc. ). And in doing so I left quite a trail of "weird and unsolved" problems here in the forum.

    In the end, just like you have discovered, I could never make it work!
    I was captivated by the idea of having a "mesh sensors network" working around my building, especially because I have wide areas not covered by WiFi and I was intrigued (to say the least) by the possibilities promised by MySensors. But as you said, "It promises all the bells and whistles for cheap home automation, but despite my every effort, I cannot even read a simple DHT11". (*)

    (to be precise, in my case it was also a BME280; I switched to those AIO sensors after failing with DHT variants)

    I did never solve the issues, and I abandoned this platform when I reached the verge of my patience having exactly the same sketch with the same hardware (really, the same sensor, the same radio, the same wires, and two identical boards) working on one board and failing on another.

    After 2 years and a half I gave up on the idea of a "mesh network" and moved to another library (still free and still available to install on a raspberry to use as a controller, and with a beautiful UI)... wish I had done it sooner. In 4 days I fixed my whole network, having a plethora of sensors constantly reporting, never hanging up for any reason (I mean, I tried removing power in 60 seconds intervals for 5 minutes and in the end they all rebooted correctly with no errors) and with the bonus feature of outputting "eye friendly" data due to the different controller.

    Hence, I perfectly understand your situation and I know how it feels: the best suggestion I can give you is to "move on" and use a different library/architecture.

    I knew I wasn't alone. I totally accept and encourage platforms that are geared towards EEs and programmers, and MySensors is definitely that. Even as a programmer by trade, it's still difficult.

    What library are you using now? I'm piqued.


 

208
Online

8.8k
Users

9.6k
Topics

100.4k
Posts