You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed an issue where if I yank the power cable from the receiver and plug it back in, Home Assistant stops communicating with the receiver until I restart the plugin.
It is something I am able to easily reproduce if there is a certain set of diagnostics or logs that would be helpful in tracking down what is happening.
The text was updated successfully, but these errors were encountered:
The PR mentioned above might help, as it includes a commit which does address reconnection.
I've recently created a new project - Anthem Proxy - which might also indirectly help. It's a proxy that sits in front of an Anthem device and addresses two concerns, the first of which probably doesn't affect you if you are already successfully using Home Assistant but the second of which might.
Firstly, an Anthem device won't respond to discovery requests from hosts not on the same subnet. By running the proxy on a multihomed host you can allow devices on other subnets to be discovered by, eg, the official Anthem app.
Secondly, an Anthem device will only retain one TCP connection at a time, so if you connect with, eg, Home Assistant, and later connect with, eg, the official app, the first connection will be silently dropped. The proxy accepts connections from multiple clients, writes commands sent by any of them to the target device, and writes status messages received back from the device to all connected clients.
The proxy will reconnect to the target device if its connection is closed, so if you put it in front of your real device and point Home Assistant at the proxy, you might (or might not, who knows) avoid the issue mentioned here.
I've noticed an issue where if I yank the power cable from the receiver and plug it back in, Home Assistant stops communicating with the receiver until I restart the plugin.
It is something I am able to easily reproduce if there is a certain set of diagnostics or logs that would be helpful in tracking down what is happening.
The text was updated successfully, but these errors were encountered: