Home Assistant

@electrik Thanks. That will do I think. Now hopefully this will work :)

Thanks again for the advice. I added persistence_file: '/config/mysensors.json' to my configuration.yaml file after deleting mysensors.pickle and things seemed to work much better as I didn't get the initial error. However I did get these errors instead: 2020-03-24 19:45:34 INFO (MainThread) [homeassistant.setup] Setting up mysensors 2020-03-24 19:45:34 WARNING (SyncWorker_3) [mysensors.persistence] File does not exist or is not readable: /config/mysensors.json 2020-03-24 19:45:34 WARNING (SyncWorker_3) [mysensors.persistence] Trying backup file: /config/mysensors.json.bak 2020-03-24 19:45:34 WARNING (SyncWorker_3) [mysensors.persistence] File does not exist or is not readable: /config/mysensors.json.bak 2020-03-24 19:45:34 WARNING (SyncWorker_3) [mysensors.persistence] Failed to load sensors from file: /config/mysensors.json 2020-03-24 19:45:34 DEBUG (SyncWorker_10) [mysensors.persistence] Saving sensors to persistence file /config/mysensors.json 2020-03-24 19:45:44 DEBUG (SyncWorker_2) [mysensors.persistence] Saving sensors to persistence file /config/mysensors.json And also I still can't get past the original point in the communications but perhaps that is now linked to the file permissions above: 2020-03-24 19:45:34 INFO (MainThread) [mysensors] Connected to Serial<id=0xb272eab0, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=0, xonxoff=False, rtscts=False, dsrdtr=False) 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;9;0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:5 TSM:INIT 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:7 TSF:WUR:MS=0 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:15 TSM:INIT:TSP OK 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:18 TSM:INIT:GW MODE 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:21 TSM:READY:ID=0,PAR=0,DIS=0 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:24 MCO:REG:NOT NEEDED 2020-03-24 19:45:35 INFO (MainThread) [mysensors.handler] n:0 c:255 t:3 s:14 p:Gateway startup complete. 2020-03-24 19:45:35 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Node update: node 0 child 255 2020-03-24 19:45:35 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Node update: node 0 child 255 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:28 MCO:BGN:INIT OK,TSP=1 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:36 TSM:READY:NWD REQ 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:41 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: 2020-03-24 19:45:35 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:52 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=1,l=1,sg=0,ft=0,st=OK:0

Thank you so much @BearWithBeard for this, it's really helpful. I decided to try using a serial gateway and have had more success. The sensor is connecting and getting an ID from the controller. Although the gateway drops out when i reboot my Pi and I have to unplug, reconnect and restart HA! Not the end of the world, and certainly better than no connection, but a bit annoying. I'd like to use an Ethernet gateway if I can so I'll try your suggestion of static ID's and see what happens. I like the idea of organising things as you suggest, so may well end up doing that anyway. I'll try the static route to the gateway too if still no luck - very useful info. I'm using Uno's at the minute while I test/set it up and am powering them via USB from a laptop (sensor) and an NUC (Gateway). Although my serial gateway is connected via USB to the Pi running HA. No capacitors at this point either. They are within a few metres of each other so don't think range is the problem. Will amend my HA Config as you suggest, again useful info. Only other thing I didn't mention is I'm using a 5100 shield breakout board on the gateway rather than the board in the tutorial, not sure if this affects power or is relevant! Again, thank you, really appreciate your advice! I was completely stuck so really nice to have options now.

Hello, is someone find a way to send a I_PRESENT or I_REBOOT command using HA? or an other workaround to force node presentation when the persistant file is desactivated? (usefull after a HA reboot for instance)

OK I found the reason. I had to disable MY_RADIO_RF24 and MY_RF24_PA_LEVEL so I commented out line 44 and 51 and it worked. Sketch code: /** * 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-2019 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. * ******************************* * * DESCRIPTION * The ArduinoGateway prints data received from sensors on the serial link. * The gateway accepts input on serial which will be sent out on radio network. * * The GW code is designed for Arduino Nano 328p / 16MHz * * Wire connections (OPTIONAL): * - Inclusion button should be connected between digital pin 3 and GND * - RX/TX/ERR leds need to be connected between +5V (anode) and digital pin 6/5/4 with resistor 270-330R in a series * * LEDs (OPTIONAL): * - To use the feature, uncomment any of the MY_DEFAULT_xx_LED_PINs * - RX (green) - blink fast on radio message received. In inclusion mode will blink fast only on presentation received * - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly * - ERR (red) - fast blink on error during transmission error or receive crc error * */ // Enable debug prints to serial monitor #define MY_DEBUG // Enable and select radio type attached //#define MY_RADIO_RF24 //#define MY_RADIO_NRF5_ESB //#define MY_RADIO_RFM69 //#define MY_RADIO_RFM95 // Set LOW transmit power level as default, if you have an amplified NRF-module and // power your radio separately with a good regulator you can turn up PA level. //#define MY_RF24_PA_LEVEL RF24_PA_LOW // Enable serial gateway #define MY_GATEWAY_SERIAL // Define a lower baud rate for Arduinos running on 8 MHz (Arduino Pro Mini 3.3V & SenseBender) //#if F_CPU == 8000000L #define MY_BAUD_RATE 38400 //#define MY_BAUD_RATE 115200 //#endif // Enable inclusion mode #define MY_INCLUSION_MODE_FEATURE // Enable Inclusion mode button on gateway //#define MY_INCLUSION_BUTTON_FEATURE // Inverses behavior of inclusion button (if using external pullup) //#define MY_INCLUSION_BUTTON_EXTERNAL_PULLUP // 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 // Set blinking period #define MY_DEFAULT_LED_BLINK_PERIOD 300 // Inverses the behavior of leds //#define MY_WITH_LEDS_BLINKING_INVERSE // Flash leds on rx/tx/err // Uncomment to override default HW configurations //#define MY_DEFAULT_ERR_LED_PIN 4 // Error led pin //#define MY_DEFAULT_RX_LED_PIN 6 // Receive led pin //#define MY_DEFAULT_TX_LED_PIN 5 // the PCB, on board LED #include <MySensors.h> uint32_t SLEEP_TIME = 120000; // Sleep time between reports (in milliseconds) #define DIGITAL_INPUT_SENSOR 3 // The digital input you attached your motion sensor. (Only 2 and 3 generates interrupt!) #define CHILD_ID 1 // Id of the sensor child // Initialize motion message MyMessage msg(CHILD_ID, V_TRIPPED); void setup() { // Setup locally attached sensors pinMode(DIGITAL_INPUT_SENSOR, INPUT); // sets the motion sensor digital pin as input } void presentation() { // Present locally attached sensors // Send the sketch version information to the gateway and Controller sendSketchInfo("Motion Sensor", "1.0"); // Register all sensors to gw (they will be created as child devices) present(CHILD_ID, S_MOTION); } void loop() { // Send locally attached sensor data here // Read digital motion value bool tripped = digitalRead(DIGITAL_INPUT_SENSOR) == HIGH; Serial.println(tripped); send(msg.set(tripped?"1":"0")); // Send tripped value to gw // Sleep until interrupt comes in on motion sensor. Send update every two minute. sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, SLEEP_TIME); } I've also changed some lines in my configuration.yml mysensors: gateways: - device: '/dev/ttyUSB0' persistence_file: 'mysensors/mysensors.json' baud_rate: 38400 persistence: true version: '2.3.2' And the motion sensor showed up as Motion Sensor

Here I am again, I had a second node running and tried to make it battery powered but it doesn't seem to work on battery only. Anyway along the process of finding out what the problem is I encountered two other problems: I'm getting a ERROR accept: Bad file descriptor in mysgw, only 1 instance seems to be running though: Any suggestions on this? PID TTY STAT TIME COMMAND 1 ? Ss 0:05 /sbin/init 2 ? S 0:00 [kthreadd] 3 ? I< 0:00 [rcu_gp] 4 ? I< 0:00 [rcu_par_gp] 8 ? I< 0:00 [mm_percpu_wq] 9 ? S 0:00 [ksoftirqd/0] 10 ? I 0:05 [rcu_sched] 11 ? I 0:00 [rcu_bh] 12 ? S 0:00 [migration/0] 13 ? S 0:00 [cpuhp/0] 14 ? S 0:00 [cpuhp/1] 15 ? S 0:00 [migration/1] 16 ? S 0:00 [ksoftirqd/1] 17 ? I 0:00 [kworker/1:0-mm_percpu_wq] 19 ? S 0:00 [cpuhp/2] 20 ? S 0:00 [migration/2] 21 ? S 0:00 [ksoftirqd/2] 23 ? I< 0:00 [kworker/2:0H-kblockd] 24 ? S 0:00 [cpuhp/3] 25 ? S 0:00 [migration/3] 26 ? S 0:00 [ksoftirqd/3] 29 ? S 0:00 [kdevtmpfs] 30 ? I< 0:00 [netns] 33 ? I 0:00 [kworker/2:1-mm_percpu_wq] 34 ? S 0:00 [khungtaskd] 35 ? S 0:00 [oom_reaper] 36 ? I< 0:00 [writeback] 37 ? S 0:00 [kcompactd0] 38 ? I< 0:00 [crypto] 39 ? I< 0:00 [kblockd] 40 ? S 0:00 [watchdogd] 42 ? I< 0:00 [rpciod] 43 ? I< 0:00 [kworker/u9:0-hci0] 44 ? I< 0:00 [xprtiod] 47 ? S 0:00 [kswapd0] 48 ? I< 0:00 [nfsiod] 59 ? I< 0:00 [kthrotld] 60 ? I< 0:00 [iscsi_eh] 61 ? I< 0:00 [dwc_otg] 62 ? I< 0:00 [DWC Notificatio] 63 ? S< 0:04 [vchiq-slot/0] 64 ? S< 0:01 [vchiq-recy/0] 65 ? S< 0:00 [vchiq-sync/0] 66 ? S 0:00 [vchiq-keep/0] 67 ? S< 0:00 [SMIO] 69 ? S 0:00 [irq/86-mmc1] 71 ? I< 0:00 [mmc_complete] 74 ? I< 0:01 [kworker/0:1H-mmc_complete] 75 ? I< 0:00 [kworker/1:1H-kblockd] 76 ? S 0:00 [jbd2/mmcblk0p2-] 77 ? I< 0:00 [ext4-rsv-conver] 79 ? I< 0:00 [ipv6_addrconf] 96 ? I< 0:00 [kworker/3:2H-kblockd] 101 ? S 0:00 [irq/166-usb-001] 114 ? Ss 0:01 /lib/systemd/systemd-journald 144 ? Ss 0:01 /lib/systemd/systemd-udevd 159 ? S< 0:00 [SMIO] 181 ? I< 0:00 [mmal-vchiq] 183 ? I< 0:00 [mmal-vchiq] 185 ? I< 0:00 [mmal-vchiq] 198 ? I< 0:00 [cfg80211] 202 ? I< 0:00 [brcmf_wq/mmc1:0] 203 ? S 0:00 [brcmf_wdog/mmc1] 247 ? Ssl 0:00 /lib/systemd/systemd-timesyncd 290 ? Ss 0:55 /usr/local/bin/mysgw -q 295 ? Ss 0:00 /usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket /run/thd.socket --user nobody --deviceglob /dev/input/ev 297 ? Ss 0:00 /usr/sbin/cron -f 298 ? Ss 0:01 avahi-daemon: running [raspberrypi.local] 299 ? Ss 0:01 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only 303 ? Ssl 0:00 /usr/sbin/rsyslogd -n -iNONE 311 ? Ss 0:00 /lib/systemd/systemd-logind 315 ? SNs 0:00 /usr/sbin/alsactl -E HOME=/run/alsa -s -n 19 -c rdaemon 319 ? Ss 0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant 344 ? SLsl 0:00 /usr/sbin/rngd -r /dev/hwrng 356 ? S 0:00 avahi-daemon: chroot helper 395 ? I 0:00 [kworker/2:3-mm_percpu_wq] 456 ? Ss 0:00 /sbin/dhcpcd -q -w 461 ? Ss 0:01 /usr/sbin/nmbd --foreground --no-process-group 463 ? Ssl 0:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal 466 ? Ssl 0:02 /usr/bin/containerd 467 ? Ssl 0:11 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock 468 tty1 Ss+ 0:00 /sbin/agetty -o -p -- \u --noclear tty1 linux 469 ? Ss 0:00 /usr/sbin/sshd -D 479 ? S 0:00 /usr/bin/hciattach /dev/serial1 bcm43xx 3000000 flow - b8:27:eb:d7:7e:1b 481 ? I< 0:00 [kworker/u9:2-hci0] 483 ? Ss 0:00 /usr/lib/bluetooth/bluetoothd 489 ? Ss 0:00 sshd: pi [priv] 511 ? Ss 0:01 /lib/systemd/systemd --user 514 ? S 0:00 (sd-pam) 525 ? Ss 0:00 /usr/sbin/smbd --foreground --no-process-group 536 ? R 0:03 sshd: pi@pts/0 539 pts/0 Ss 0:01 -bash 542 ? S 0:00 /usr/sbin/smbd --foreground --no-process-group 543 ? S 0:00 /usr/sbin/smbd --foreground --no-process-group 552 ? S 0:00 /usr/sbin/smbd --foreground --no-process-group 794 ? Ss 0:00 /bin/sh /usr/sbin/hassio-supervisor 821 ? Sl 0:01 docker start --attach hassio_supervisor 873 ? Sl 0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/af8bfda572398f9806ba54d 890 ? Ss 0:00 s6-svscan -t0 /var/run/s6/services 1045 ? S 0:00 s6-supervise s6-fdholderd 1192 ? Ss 0:00 udevd --daemon 1267 ? S 0:00 s6-supervise supervisor 1271 ? Ssl 0:17 python3 -m supervisor 1354 ? S 0:00 socat UDP-RECVFROM:53,fork UDP-SENDTO:172.30.32.3:53 1398 ? Sl 0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/21403e3385d0ce05418df7e 1409 ? Sl 0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/2b6193b6744b35b8d848671 1433 ? Ssl 0:01 coredns -conf /config/corefile 1437 ? Ss 0:00 s6-svscan -t0 /var/run/s6/services 1625 ? S 0:00 s6-supervise s6-fdholderd 1919 ? Ss 0:00 udevd --daemon 1951 ? S 0:00 s6-supervise bridge 1952 ? S 0:00 s6-supervise pulseaudio 1955 ? Ss 0:00 socat UNIX-LISTEN:/data/external/pulse.sock,fork,unlink-early,mode=777 UNIX-CONNECT:/data/internal/pulse.sock 1956 ? S<sl 0:05 pulseaudio --system -vvv 2004 ? Sl 0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/00ef0f54f7a780be3af62a1 2019 ? Ssl 2:07 /usr/local/bin/python3 -m homeassistant --config /config 2036 ? Ss 0:01 udevd --daemon 2353 ? Sl 0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/9ca754987ee52a3a48c5290 2369 ? Ss 0:00 /sbin/docker-init -- /init /run.sh 2462 ? S 0:00 s6-svscan -t0 /var/run/s6/services 2487 ? S 0:00 foreground if /etc/s6/init/init-stage2-redirfd foreground if if s6-echo -n -- [s6-init] 2488 ? S 0:00 s6-supervise s6-fdholderd 2499 ? S 0:00 foreground s6-setsid -gq -- with-contenv backtick -D 0 -n S6_LOGGING printcontenv S6_LOGGING importas S 2632 ? S 0:02 /usr/local/bin/python /usr/local/bin/hass-configurator /etc/configurator.conf 2677 ? S 0:02 /usr/sbin/smbd --foreground --no-process-group 2837 ? I< 0:00 [kworker/1:2H] 2854 pts/0 T 0:00 sudo nano mysensors.conf 2859 pts/0 T 0:00 nano mysensors.conf 2903 ? I 0:00 [kworker/u8:2-events_unbound] 2937 ? I< 0:00 [kworker/3:0H] 2939 ? I 0:00 [kworker/3:2-mm_percpu_wq] 2968 ? I 0:00 [kworker/1:2-events] 3008 ? I 0:00 [kworker/u8:0-events_unbound] 3021 ? I< 0:00 [kworker/0:2H] 3022 ? I 0:00 [kworker/0:0-events] 3036 ? I 0:00 [kworker/3:0-events] 3037 ? I< 0:00 [kworker/2:2H] 3043 ? I 0:00 [kworker/0:1-events_power_efficient] 3068 ? I 0:00 [kworker/u8:1-events_unbound] 3070 ? I 0:00 [kworker/2:0-mm_percpu_wq] 3071 ? I< 0:00 [kworker/3:1H-kblockd] 3074 ? I< 0:00 [kworker/0:0H] 3075 ? I 0:00 [kworker/3:1-events] 3076 pts/0 R+ 0:00 ps -ax

@BearWithBeard said in 2nd sensor in sketch not showing up in HA: send(msg2.set(sensorValueA1)); Yes, that was it!! Thank you!!

Did you solve your problem? I had a similar problem, but using an Ethernet gateway, until I discovered that my sketch was not using the 2.x API, contrary to the gateway. This is also the case for the BinarySwitchSleepSensor you mention. You might want to try with a sketch based on the last one on this page (using the 'initialValueSent' variable): https://www.home-assistant.io/integrations/sensor.mysensors/#mysensors-2x-example-sketch After updating to the 2.x API, my sensor showed up in the entities list of Home Asisstant (v0.106.6, HassOS 3.12, on Raspberry Pi 3) and I could create a UI card for it. (For some reason the entity is read-only in Hass.)

Hello, yes. https://www.home-assistant.io/integrations/mysensors#nodes using nodes Configuration Variable nodes: 100: name: 'MyName' Cheers.

Ha!! That worked! That is so cool! I am going to be automating watering of my garden based on individual plant needs and can easily do that now! Thank you!

Late reply but, adding the version to my configuration file solved the problem just like you suggested. So this topic is now solved using two methods. Very nice!

I recently read that if you use multiple USB gateway then you can't have duplicate of child is. Maybe this is a clue

@macieiks This is triggered by the HA, as the log suggests: 2020-02-19 08:18:39 DEBUG (MainThread) [mysensors] Sending 0;255;3;0;2; 2020-02-19 08:18:39 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;2;2.3.2 2020-02-19 08:18:49 DEBUG (MainThread) [mysensors] Sending 0;255;3;0;2; 2020-02-19 08:18:49 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;2;2.3.2 Please check with the HA ppl

@Joost great news! always a good feeling when you find a solution to a pesky problem :)

I have added a sollution to V_VAR problem in both my rain and power pulse meter (check these threads). As said above, Homeassistant will not give an answer to these requests if there are no value in the mysensors json file. Either add this in the hardware code or as I did, request a couple of times to make sure you get the value if there is one. Count these requests and set a upper limit, like five or ten reuqest. Once your each this limit, send the value 0 to HA and this will be updated in the json file and start from there.

@skywatch it's not me trying to compare, it happens in the mysensors library when receiving messages. It seems that mysensors is badly implemented in the home assistant, in domoticz it works very well

@Michał-Szura I had problems with relay and HA too. The best solution was to save the state of the relay in the EEPROM and to recall the value after a defined amount of time and send it to HA in loop(). This way you do not have to restart the relay node everytime you restart HA.

@sebex unless you have hass.io you should be able to SSH into the rpi

I never used HAAS but have you looked at this page for how to set initial state? Then you can just send that to the controller. https://www.mysensors.org/build/relay