-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Bridge notifications doesn't publish state 0 on local broker when loosing internet #2467
Comments
I ran another test using the IP-address, 5.196.95.208 and now the state changes as expected. |
I have other results. |
See also #1488 that this is probably a dupe of. |
Actually #1488 is the post I'm referring to in the first sentence of the first post, and also pointing out the differences. |
It may be related, but this is not the same. As I see this bug is present since: So there are two possible solutions:
I prefer the first, since that way we get the notification sooner. I could make the fix, but first i want to hear what the developers say about this. @ralight |
I second that solution 1 is preferred. |
Please give the |
I tried compiling the
|
@BubuOT Sorry about that, it's fixed now. |
Tested again now and this seems to fix the problem for us. Thanks for fixing this! (after it was broken 7 years ago I think? :)) |
Hi,
I have seen som reports with similar behaviour when having notification_local_only true, but in my case I have notifications turned on both locally and remote.
When shutting down remote bridge the bridge state 0 is published on local broker, but if I instead break the internet connection the bridge will never publish state 0!
The remote broker will always detect lost connection with bridge and publish state 0.
How to reproduce his:
Set up a local broker and a bridge to for example test.mosquitto.org:1883 and notifications = true.
Verify bridge-state-topic to have value 1.
Disconnect your internet-connection (disconnect WiFi or equivalent)
Expected result is bridge state 0, but is still 1.
Noticed behaviour when this occur:
bridge will restart repeatedly, after timeouts, connecting to local broker and will log an error saying that the remote host is unknown, probably caused by no internet connection.
The text was updated successfully, but these errors were encountered: