-
Notifications
You must be signed in to change notification settings - Fork 420
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
Sonoff Dw2 Wifi - State update issue. After a few seconds close or open it shows unavaliable until it open or close again #232
Comments
This is the nature of the beast. It's trying to save power. The DW2 is horrible. I replaced all mine with the new ZigBee ones |
Is it possible to create an object that saves the last state (on or off) of the sensor, ignoring the "Unavaliable" state? |
Yes, this is possible in HA, but it still doesn't solve the slow response times of the switches. I've seen them take up to 1-2hrs to register a change sometimes. Hopeless things. Seriously, cut your losses and get the SNZB-04 and the ZBBridge instead. |
Mine is working fine with dw2, you can get last state from database ignoring the unavaiable and unknow
|
then you can create a binary using the data that you collet binary_sensor:
|
Thanks! Will try it soon. I bought 10 of those and i thought i was stuck, since sonoff now requires a paid service for IFTTT (and IFTTT went pay-to-actually-use-it) and that was what make me search for alternatives, thats how i started Home assistant stuff |
Maybe your router can't handle 10 extra wifi devices |
2 of them are for my house and 8 for my bussiness, No problem so far |
Sorry if this is obvious, but how do i use the database? I've created the binary sensor and wited the SQL int configuration, but it appears always closed, it is not actualizing the state |
Hi. My 4 DW2 WiFi sensors work fine. I think the power saving issue was solved in latest firmware upgrade. Only problem is that they show as unavailable after home assistant start or restart. They work fine after triggering them once (open or close) after HA has loaded. |
Can you send debug log? I'm interesting in init setup lines for this sensor |
Init, open and close (removed api key):
|
The cloud tells the device is offline. eWeLink guys should fix it. |
The "unavailable issues" are all Sonoff service-related (other than the "unavailable" after a restart. The DW2 is not like the other Sonoff devices which can be controlled by your LAN (LAN control) ... the DW2 has no LAN control option at all - it needs to speak to the Sonoff backend to report open, closed etc. This also means that if your internet is down, these won't work. So frustrating because they are great devices - in principle. |
Better to use battery devices on Zigbee or Bluetooth protocols. |
Yeah - I'm beginning to see that. Mine are actually working very well right now. They need to enable LAN control/reporting on them then their serviceability will increase. |
Sonoff Dw2 Wifi - State update issue. After a few seconds close or open it shows unavaliable until it open or close again, but after that it goes unavaliable again (because the device enters in sleep mode) It shoud shows lastOnlineState
The text was updated successfully, but these errors were encountered: