New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watchdog heartbeat timeout #8
Comments
I forgot to say I'm using your example.yaml and Esphome v2021.12.1 |
I haven't seen this issue before. My setup is running 10 days++ without issues. I will try to provide some ideas to isolate the cause:
|
Thanks for replying syssi.
One question: have you tried your setup with the latest ESPhome version (like in my case)? |
If your network is switched you can only see broadcasts if you use a third host to sniff traffic. You have to make sure to capture the traffic at the network card of your HA instance (using I've updated my setup vom |
Update: I flashed the bridge with the custom tasmota firmware from thehelpfulidiot, and seems to be working flawlessly. I will keep you updated if the actual setup will continue working. |
You are right. I can see multiple reconnects using
I've flashed the device using esphome |
The log message at the esphome node are the same on
|
Could it be possible that the ESPhome directories need to be cleaned before downgrading the files? Otherwise it doesn't have much sense since previously it was working |
May be my HA core instance is closing the connection intentionally. I will try to monitor the HA core log as next step. |
At the
I will capture some traffic to get a better understanding who drops the connection. |
@dartanidi Do you use ZHA or Z2M now? |
I'm using ZHA, btw with the tasmota custom firmware it's working perfectly, no errors are reported in the log. I still suspect there is an issue within the |
I assume you are on the right track. Let's see! :-) |
|
Exactly what was happening to me, see first post |
In short: I'm able to reproduce the issue now. ;-) I captured some traffic. It looks like the connection is terminated by the watchdog because of no(?) serial/ezsp traffic. https://github.com/zigpy/bellows/blob/dev/bellows/zigbee/application.py#L44-L50 |
Quick update: It looks like if you downgrade esphome to |
Hi, Thanks |
It's pretty easy to install an old esphome version if you have access to a linux host. Do you need some instructions? |
If you are so kind to provide to me it wold be great!! Thanks!!!! |
Yes. Just pick a linux machine, make sure the python package manager
It's possible the path to the esphome CLI command isn't part of your
This should return
You could upgrade the esphome install later on to the most recent version:
But keep in mind to downgrade the version again if you want to update/improve your gateway configuration. |
Thank you so much!! It worked!! Now i have to remember to not "Update All" on the esphome dashboard :D |
Did you flash your ZigBee module ever? It's independent from the ESPHome version. The ZigBee module is equipped with the last flashed firmware. |
Yes, i followed the entire guide and the coordinator was working but poorly with EspHome |
Could you create a new issue first? We should avoid off-topic questions here. |
It looks like the issue is gone. This user don't have trouble with a recent esphome version: https://community.home-assistant.io/t/zb-gw03-ewelink-ethernet-zigbee-gateway-now-hacked-with-tasmota-and-esphome-so-can-be-used-via-mqtt-or-as-a-remote-zigbee-lan-adapter-with-home-assistants-zha-integration-or-zigbee2mqtt/341223/59 |
@syssi |
Cool! I will update the project as soon as possible. I would be happy about a pull request too! |
There is no no need, your yaml files are working out of the box since the component works exactly as the previous version. |
@syssi first of all thank you for making this Esphome firmware possible for the zb-gw03.
I moved from a Sonoff Zbbridge where I had sometime some connection stability problems looking for a more reliable solution.
Unfortunately this seems totaly unstable, with bellows reporting a lot of watchdog heartbeat timeouts in the log.
It eventually stops working with HA reporting errors like this:
which I read are tipical in the ZB to WiFi bridges.
So it looks like a connection problem, but HA PC and the bridge are connected via the same switch, and the bridge is never reported to be unavailable.
Toggling the Zigbee Reset switch solves the issue, but this problems occurs say every hour or two.
Any clue?
Thanks for your help.
The text was updated successfully, but these errors were encountered: