-
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
Dual state RF door sensors problem #807
Comments
Show your yaml config |
|
Oh. In new version it works only if you setup turn on signal in ewelink app as sensor, not as button :( |
I don't understand. How can i do that ? In ewelink, on rf bridge, when i press Add, i have: 1 button, 2, 3, 4 button, Curtain and Alarm. What shoud I do ? |
alarm |
Hi, In my case in the eWelink APP the alarm option doesn't have dual state, only single. |
The button also has no dual state... |
So, in that case, we can't use dual sensors anymore. |
So you are stating we have to add an alarm device for the open state and another for the closed, instead of using a two button device as before. This really sucks, as the bridge only allows 16 devices. Before if I had 16 two button remotes, I now need 32 alarms, and would need a second bridge. |
So you can use 16 four button remotes if you want? |
I have never tried the four buttons, but I currently have 24 dual state sensors configured as 24 two button remotes, across two rf bridges. (So 48 buttons.) This had been working up until the update. (They still are all in the ewelink app, and show up in hass, but now as individual switches instead of a two state sensor. My YAML is pretty much the same as above. |
Latest master-version has new features:
|
Also updated docs. All changes will be in next release |
Thank you! |
I Confirm it now works as before. Thanks a lot |
After V3 update, the Rf Bridge - door sensors does not work anymore. It used to work as they have 2 states - open/close. So i used the old payload off function. Now i only see 2 entities as button (door_open / door_closed).
The text was updated successfully, but these errors were encountered: