Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it

[gohan]

what radio are you using? Also you can update to the stable 2.2

[Richard van der Plas]

its a nrf24 PA, ill try to update to stable 2.2
and maybey add another 4.7u, i saw in a previous post you have 2 on them

[Richard van der Plas]

This post is deleted!

[gohan]

@richard-van-der-plas are you using a 3.3v voltage regulator from the 5V pins?

[Richard van der Plas]

yes, we had that discussion in another post already, seems to be running now, except 1 node gives me a headache (the newly created 3.3v arduino as discussed earlier)

[Richard van der Plas]

the arduino side:

53 TSF:MSG:SEND,8-8-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2062 !TSM:FPAR:NO REPLY
2064 TSM:FPAR
2101 TSF:MSG:SEND,8-8-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4108 !TSM:FPAR:NO REPLY
4110 TSM:FPAR
4147 TSF:MSG:SEND,8-8-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6154 !TSM:FPAR:NO REPLY
6156 TSM:FPAR
6193 TSF:MSG:SEND,8-8-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8200 !TSM:FPAR:FAIL
8202 TSM:FAIL:CNT=1
8204 TSM:FAIL:PDT

the gateway side:

TSF:MSG:READ,8-8-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
TSF:MSG:BC
TSF:MSG:FPAR REQ,ID=8
TSF:PNG:SEND,TO=0
TSF:CKU:OK
TSF:MSG:GWL OK
!TSF:MSG:SEND,0-0-8-8,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
TSF:MSG:READ,4-4-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
TSF:MSG:PINGED,ID=4,HP=1
TSF:MSG:SEND,0-0-4-4,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
TSF:MSG:READ,3-3-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
TSF:MSG:PINGED,ID=3,HP=1
TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
TSF:MSG:READ,8-8-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
TSF:MSG:BC
TSF:MSG:FPAR REQ,ID=8
TSF:CKU:OK,FCTRL
TSF:MSG:GWL OK

[gohan]

The node is not receiving the reply from the gateway. Try moving it closer to gateway, or use the lower TX power settings

[Richard van der Plas]

@gohan weird distance is 3 meters in clear air , it was working :(
is has do do something with power and capacitors, connected a 3.3u one, and using a 2xaaa power supply with a DCDC stepup to 3.3 volt as in the manuals.
what capacitors would you advice ?

[gohan]

Try with fully charged alkaline batteries without the booster and see if it works better.

[Richard van der Plas]

@gohan looks alot better indeed, powered the radio directly from the AAA batteries, and seems to work now, next step is why my voltage reading of the battery is way off :)

[gohan]

Try using a ceramic cap on the booster output. I used 10uF without issues. As an alternative get the LiFePO4 batteries, get rid of booster and use vcc library to read battery voltage

[Richard van der Plas]

@gohan Small update, still weird things, everything works after a reboot, but after a short time, when toggling a switch in HA, nothing is send through the gateway?
receives though work fine..

snippet of the log, where the first sends are working, but then dead the send commands.

Feb  6 22:01:53 raspberrypi mysgw: TSF:MSG:READ,3-3-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
Feb  6 22:01:53 raspberrypi mysgw: TSF:MSG:PINGED,ID=3,HP=1
Feb  6 22:01:53 raspberrypi mysgw: TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
Feb  6 22:01:55 raspberrypi mysgw: TSF:MSG:READ,5-3-0,s=255,c=3,t=24,pt=1,l=1,sg=0:2
Feb  6 22:01:55 raspberrypi mysgw: TSF:MSG:PINGED,ID=5,HP=2
Feb  6 22:01:55 raspberrypi mysgw: TSF:MSG:SEND,0-0-3-5,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
Feb  6 22:02:02 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:02:02 raspberrypi mysgw: GWT:RFC:C=0,MSG=5;2;1;0;2;0
Feb  6 22:02:02 raspberrypi mysgw: TSF:MSG:SEND,0-0-3-5,s=2,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:0
Feb  6 22:02:02 raspberrypi mysgw: TSF:MSG:READ,5-3-0,s=2,c=1,t=2,pt=1,l=1,sg=0:0
Feb  6 22:02:10 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:1
Feb  6 22:02:12 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:02:18 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:0
Feb  6 22:02:22 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:02:32 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:02:35 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:1
Feb  6 22:02:42 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:02:46 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:0
Feb  6 22:02:52 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:02:54 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:1
Feb  6 22:03:02 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:03:03 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:0
Feb  6 22:03:06 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:1
Feb  6 22:03:12 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:03:21 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:0
Feb  6 22:03:22 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:03:25 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:1
Feb  6 22:03:32 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:03:32 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:0
Feb  6 22:03:38 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:1
Feb  6 22:03:42 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:03:45 raspberrypi mysgw: TSF:MSG:READ,5-3-0,s=1,c=1,t=0,pt=7,l=5,sg=0:-3.06
Feb  6 22:03:45 raspberrypi mysgw: TSF:MSG:READ,5-3-0,s=0,c=1,t=16,pt=1,l=1,sg=0:0
Feb  6 22:03:52 raspberrypi mysgw: GWT:RFC:C=0,MSG=0;255;3;0;2;
Feb  6 22:03:53 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:0
Feb  6 22:03:57 raspberrypi mysgw: TSF:MSG:READ,2-2-0,s=2,c=1,t=16,pt=0,l=1,sg=0:1
Feb  6 22:03:58 raspberrypi mysgw: TSF:MSG:READ,3-3-0,s=3,c=1,t=0,pt=7,l=5,sg=0:1.0

[gohan]

Are you sure it's not a controller problem? Try using something else like mycontroller or myscontroller and send something to the gateway

[Richard van der Plas]

@gohan is there a light weigth application to test this? or do i have to install a complete suite ?
wouldt be handy if there's just a way to do a SEND command on the gateway

[gohan]

With myscontroller it is just a windows app where you can send anything you want to the gateway. Mycontroller it is just a Java program where you just launch the start script and configure a few simple parameters, nothing fancy but it is useful to have for multiple purposes.

[Richard van der Plas]

@gohan said in Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it:

myscontroller

yes Mycontroller works as expected :), the issue lies in HA

[Richard van der Plas]

@gohan what i see is that the mysensors.json isnt updated with values of the different sensors on the node ?
log shows:

child_id 3 already exists in children of node 11, cannot add child
3:26 PM /srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py (WARNING)
child_id 2 already exists in children of node 11, cannot add child
3:26 PM /srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py (WARNING)
child_id 1 already exists in children of node 11, cannot add child
3:26 PM /srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py (WARNING)
Node 11 is unknown
3:25 PM /srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py (WARNING)

Small update, using the 2.1 library issues are not there so much

[gohan]

I moved it to the home assistant section. Let's hope somebody could help you out, I'm not HA expert

[Richard van der Plas]

@gohan ty

[Sergio Rius]

@gohan said in Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it:

I moved it to the home assistant section. Let's hope somebody could help you out, I'm not HA expert

Don't know if that is caused by the controller, by I'm having the same issue months ago but with domoticz.
When that happens, I've found that manually restarting the mys GW service makes it work again.