Hi,
I have several devices (R78 and R103) connected to openhab/mqtt via wifi.
Some of them stops responding after working for days/weeks, reason totally unknown.
What happens if the wifi router is rebooted ?
In the code I only see a retry on a MQTT connection when it fails to connect but what if the wifi link is/was down ?
Will it try to establish a wifi connection again ?
Is there a way to do an automatically reboot every xx hours?
-ben
espeasy stops responding
Moderators: grovkillen, Stuntteam, TD-er
Re: espeasy stops responding
Good question, I also need this info, +1
-----------
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.
Re: espeasy stops responding
Ben,
Not sure if you have seen Scargill's home automation controller, but he sends out a heartbeat from a RasPi every minute to esp's, if esp stops getting this, it will first reboot mqtt, there after reboot and reconnect wifi. He has published this as a node-red node as well to control, neat solution to same problem.
http://tech.scargill.net/home-control-2016/
----------
"Whatever controls these boards must now send topic toesp command {heartbeat} every minute. All the boards will see this - and all will pre-set a counter in themselves - which if allowed to drop to zero will re-initialise the MQTT code. In the event that boards lose the WIFI for some time, they may reset their WIFI - then reset the MQTT code. Reset is used only as a last resort and the software can handle up to two SSIDs in case you happen to have two access points. If one fails it will try the other."
----------
Not sure if you have seen Scargill's home automation controller, but he sends out a heartbeat from a RasPi every minute to esp's, if esp stops getting this, it will first reboot mqtt, there after reboot and reconnect wifi. He has published this as a node-red node as well to control, neat solution to same problem.
http://tech.scargill.net/home-control-2016/
----------
"Whatever controls these boards must now send topic toesp command {heartbeat} every minute. All the boards will see this - and all will pre-set a counter in themselves - which if allowed to drop to zero will re-initialise the MQTT code. In the event that boards lose the WIFI for some time, they may reset their WIFI - then reset the MQTT code. Reset is used only as a last resort and the software can handle up to two SSIDs in case you happen to have two access points. If one fails it will try the other."
----------
-----------
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.
-
- Normal user
- Posts: 44
- Joined: 31 Jan 2016, 21:05
Re: espeasy stops responding
Hi
Very nicely done, looks impressive.
I did 'standardize' on espeasy due to the wide range of supported interfaces.
I really like the idea of having a heartbeat function over MQTT controlled by (example) OPENHAB.
This should not be difficult to implement and I hope this will be done in the future.
For me a selectable heartbeat would be fine, something between 1 en 10 minutes would be great.
-ben
Very nicely done, looks impressive.
I did 'standardize' on espeasy due to the wide range of supported interfaces.
I really like the idea of having a heartbeat function over MQTT controlled by (example) OPENHAB.
This should not be difficult to implement and I hope this will be done in the future.
For me a selectable heartbeat would be fine, something between 1 en 10 minutes would be great.
-ben
Who is online
Users browsing this forum: No registered users and 29 guests