I have some strange issues with my ESP8266 Wifi gateway and NRF24L01 connection.
All goes well for a day or so or sometimes 3, but than the WiFi communication stops, rebooting my WiFi access point solves the problem.
It shouldn't be a DHCP issue, because that is handled through the firewall, so it must be something else. Problem is i cannot see what goes wrong, because i don't have a log anywhere on the device?
What could be the best steps to solve or find the issue ?
Richard van der Plas
Posts
-
💬 Building a WiFi Gateway using ESP8266 -
💬 Building a WiFi Gateway using ESP8266seems to work again indeed, had to flash something empty first.
-
💬 Building a WiFi Gateway using ESP8266HI there, i have been using this code a while, but had to made some changes in my wifi connection info (because it seems that my Domotica controller couldnt command the gateway), but after a failed flash, i have managed to flash it again correctly, but it doesnt seem to connect to the gateway anymore, how can i check this? it wouldnt respond on a ping and i see no wifi connection in de serial log?
-
MySensor nodes powering on with Dusk / Dawn Garden lights issue@nca78 said in MySensor nodes powering on with Dusk / Dawn Garden lights issue:
before()
so i need to create like :void before(); { delay(2500); } -
MySensor nodes powering on with Dusk / Dawn Garden lights issueI have converted some of my garden lights (not the pond lights because of the water ;) ) to Mysensor lights with NeoPixels with different nice settings (color alarm etc). Thing is these are powerd by the 12V power lines running through the garden. This 12V system turns on @ dusk for a few hours (because they power the analog lights also). This results in 6-8 nodes booting at the same time, thus flooding the gatway with messages (presentation, getting the last state & color etc).
The last i can fix by creating a few second wait different for all nodes, but i cannot find a option to delay the presentation and the whole bootup part of the nRF24L01 radio part.
i found #define MY_TRANSPORT_WAIT_READY_MS but is this really working?
i tested with the line:#define MY_TRANSPORT_WAIT_READY_MS 5000but didn't seem to delay / wait?
-
New Light is not shown in HASSissue seems the version number, which in 2.2 is a text string (Major releas bladiebla) that messes with the json file somehow
-
New Light is not shown in HASSafter uploading the code to a 5th node of the same code, the node is not seen in HASS,
Debug log shows the first set section of the code is working:Mar 24 16:59:22 raspberrypi mysgw: GWT:RFC:C=1,MSG=14;255;3;0;6;M Mar 24 16:59:22 raspberrypi mysgw: TSF:MSG:SEND,0-0-14-14,s=255,c=3,t=6,pt=0,l=1,sg=0,ft=0,st=OK:M Mar 24 16:59:22 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=255,c=3,t=11,pt=0,l=8,sg=0:TuinLamp Mar 24 16:59:22 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.5 Mar 24 16:59:23 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=1,c=0,t=27,pt=0,l=0,sg=0: Mar 24 16:59:24 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=2,c=0,t=4,pt=0,l=0,sg=0: Mar 24 16:59:26 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=3,c=0,t=3,pt=0,l=0,sg=0: Mar 24 16:59:28 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2 Mar 24 16:59:28 raspberrypi mysgw: TSF:MSG:SEND,0-0-14-14,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1 Mar 24 16:59:29 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=3,c=1,t=2,pt=2,l=2,sg=0:0 Mar 24 16:59:30 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=2,c=1,t=2,pt=2,l=2,sg=0:0 Mar 24 16:59:30 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=2,c=1,t=3,pt=2,l=2,sg=0:0 Mar 24 16:59:30 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=1,c=1,t=41,pt=0,l=8,sg=0:00000000 Mar 24 16:59:30 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=1,c=1,t=2,pt=2,l=2,sg=0:0 Mar 24 16:59:30 raspberrypi mysgw: TSF:MSG:READ,14-14-0,s=1,c=1,t=3,pt=2,l=2,sg=0:0Home assistant log shows:
Mar 24 17:07:22 raspberrypi hass[449]: #033[33m2018-03-24 17:07:22 WARNING (Thread-23) [mysensors] child_id 1 already exists in children of node 14, cannot add child#033[0m Mar 24 17:07:23 raspberrypi hass[449]: #033[33m2018-03-24 17:07:23 WARNING (Thread-23) [mysensors] child_id 2 already exists in children of node 14, cannot add child#033[0m Mar 24 17:07:24 raspberrypi hass[449]: #033[33m2018-03-24 17:07:24 WARNING (Thread-23) [mysensors] child_id 3 already exists in children of node 14, cannot add child#033[0m Mar 24 17:09:03 raspberrypi hass[449]: Exception in thread Thread-23: Mar 24 17:09:03 raspberrypi hass[449]: Traceback (most recent call last): Mar 24 17:09:03 raspberrypi hass[449]: File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner Mar 24 17:09:03 raspberrypi hass[449]: self.run() Mar 24 17:09:03 raspberrypi hass[449]: File "/srv/homeassistant/lib/python3.5/site-packages/mysensors/gateway_tcp.py", line 180, in run Mar 24 17:09:03 raspberrypi hass[449]: response = self.handle_queue() Mar 24 17:09:03 raspberrypi hass[449]: File "/srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py", line 374, in handle_queue Mar 24 17:09:03 raspberrypi hass[449]: reply = func(*args, **kwargs) Mar 24 17:09:03 raspberrypi hass[449]: File "/srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py", line 202, in logic Mar 24 17:09:03 raspberrypi hass[449]: ret = self._handle_set(msg) Mar 24 17:09:03 raspberrypi hass[449]: File "/srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py", line 101, in _handle_set Mar 24 17:09:03 raspberrypi hass[449]: msg.child_id, msg.sub_type, msg.payload) Mar 24 17:09:03 raspberrypi hass[449]: File "/srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py", line 519, in set_child_value Mar 24 17:09:03 raspberrypi hass[449]: msg.validate(self.protocol_version) Mar 24 17:09:03 raspberrypi hass[449]: File "/srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py", line 634, in validate Mar 24 17:09:03 raspberrypi hass[449]: const = get_const(protocol_version) Mar 24 17:09:03 raspberrypi hass[449]: File "/srv/homeassistant/lib/python3.5/site-packages/mysensors/__init__.py", line 32, in get_const Mar 24 17:09:03 raspberrypi hass[449]: if parse_ver('1.5') <= parse_ver(version) < parse_ver('2.0'): Mar 24 17:09:03 raspberrypi hass[449]: File "/usr/lib/python3.5/distutils/version.py", line 52, in __lt__ Mar 24 17:09:03 raspberrypi hass[449]: c = self._cmp(other) Mar 24 17:09:03 raspberrypi hass[449]: File "/usr/lib/python3.5/distutils/version.py", line 337, in _cmp Mar 24 17:09:03 raspberrypi hass[449]: if self.version < other.version: Mar 24 17:09:03 raspberrypi hass[449]: TypeError: unorderable types: str() < int()and the mysensors.json file has node 14 in its list, but HASS wont show it in the states list or the made groups.yaml ?
the other nodes didn't have that issue. -
💬 Building a Raspberry Pi GatewayWas pointed here from another post, having serious issues with high CPU utilization op the gateway, is there any workaround and the moment?
top:
asks: 157 total, 2 running, 155 sleeping, 0 stopped, 0 zombie %Cpu(s): 2.5 us, 23.0 sy, 0.0 ni, 74.3 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 949580 total, 448732 free, 146912 used, 353936 buff/cache KiB Swap: 102396 total, 102396 free, 0 used. 737656 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 337 root 20 0 20492 1060 932 R 100.0 0.1 28:54.55 mysgw 3947 pi 20 0 8248 3324 2736 R 1.6 0.4 0:00.82 top 447 homeass+ 20 0 340112 63684 9916 S 1.0 6.7 3:28.71 hass 7 root 20 0 0 0 0 S 0.3 0.0 0:04.18 rcu_sched 767 root 20 0 126572 8628 6544 S 0.3 0.9 0:00.95 piplight-daemonPRETTY_NAME="Raspbian GNU/Linux 9 (stretch)" NAME="Raspbian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" Linux raspberrypi 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/LinuxRebooting the pi sometimes helps, sometimes freezes the pi
seeing nothing strange in the mysensors log what so ever
running MySensors Version 2.2.0
and Home Assistant Version 0.64.0
Anyone can point me in the direction where to troubleshoot this further ?
its not a high traffic gateway (around 10 sensors connected of which 5 updating every 15 minutes) -
latest version 2.2.0 shows strange version in presentation@nick-willis mine is turned around, 2.1.1 nodes give the version 2.2.x gives the text row messing up mysensors
-
latest version 2.2.0 shows strange version in presentation@mfalkvidd the mysensors.json file
-
Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it@gohan ty
-
Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it@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
-
Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it@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
-
Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it@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 -
Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it@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 -
latest version 2.2.0 shows strange version in presentationHi all, just updated my libary to 2.2.0, and seeing the following strange things in my presentation:
"sketch_version":"1.6", "protocol_version":"2 /*!< Major release vers", "type":17, "sensor_id":11, "sketch_name":"TuinLamp_11",where as the previous library clearly shows the proto version:
"10":{ "sketch_version":"1.5", "protocol_version":"2.1.1", "type":17, "sensor_id":10, "sketch_name":"TuinLamp",Is this normal, or not?
-
Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it@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 :)
-
Suddenly communication between gw & nodes stopped , rebooting pi sometimes solves it@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 ?