-
Notifications
You must be signed in to change notification settings - Fork 403
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
RFbridge doesnt update alarm sensor when disconnected from Internet (local) #1379
Comments
There's nothing in the logs that would be helpful. This a problem between the bridge and the server. This is more a development suggestion sorry |
Without device and any debug info I can't do anything |
I can see local updates in your logs. You don't have them when there's no internet?
|
With no internet, pushing a button works in both homeassistant and ewelink app. But sensor status doesn't update also in both ewelink and homeassistant. I can see the orange light on the bridge flash when I trigger the window alarm (open or close) but it doesnt update the 'last triggered' or current status in ewwelink or homeassistant |
Yes. Same TS will be skipped. I don't know if it safe to remove this check. Then another check would have to be made for local+cloud messages. SonoffLAN/custom_components/sonoff/remote.py Lines 128 to 130 in 08070c3
|
I don't know how to fix this on the component side. Disabling the date check doesn't seem to be safe. You can also see that the message counter on the device side doesn't increase. |
Pulling the WAN cable out the router while everything else is connected, the RF bridge continue to work normally for 2-3 minutes. Then it misbehaves |
RFbridge 2, firmware 3.5.2. integration (in Local or Auto). with Internet access for the bridge denied from the router, the buttons keep working but the window sensor doesn't update. I found that the bridge bridge connects to this IP (13.56.143.44) even with pihole block, and it stays online in the ewelink app. Interestingly, if I allow internet access then pull the WAN cord out after the bridge initialized, the sensors keep working.
I am thinking that the bridge uses the connection to 13.56.143.44 to pull the clock time because the sensor triggers need "last triggered" which needs the clock on the bridge to be correct. What if we spoof this IP address and redirect it to a local NTP server? It wouldn't be this easy because this IP is not only n NTP but is also the connection to ewelink. But if anyone can figure how supply the time clock to sonoff devices without ewelink, that would be awesome... potentially solve all issues with sensors not working in local mode.
The text was updated successfully, but these errors were encountered: