Skip to content
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

Various enhancements #1978

Merged
merged 12 commits into from Oct 21, 2019

Conversation

@ebaauw
Copy link
Contributor

ebaauw commented Oct 18, 2019

  • Ignore faulty -100°C temperature in the regular and Xioami special attribute report for lumi.weather, see #1748.
  • Add ne operator for rule conditions, see #1874.
  • Initial support for iCasa remote, see https://www.icasa.io/afstandsbediening. Still work in progress.
ebaauw added 12 commits Sep 27, 2019
See #1898
Setup binding for client clusters for innr RC 110.  See #653.
Setup binding for client clusters for innr RC 110.  See #635.
work in progress
See #1874.
See #1748.
Ignore faulty temperature of -100°C for `lumi.weather`.  See #1978.
@manup manup merged commit c525d2d into dresden-elektronik:master Oct 21, 2019
@manup

This comment has been minimized.

Copy link
Member

manup commented Oct 21, 2019

Cool thanks, good stuff, the remote looks interesting.

@ebaauw

This comment has been minimized.

Copy link
Contributor Author

ebaauw commented Oct 21, 2019

It feels very nice, but I'm running into a number of challenges supporting it in full.

The (unnumbered) On/Off buttons send commands to all four groups, corresponding to the numbered (1-4) On/Off buttons. Same for the S1 and S2 buttons. When using the default groups, it sends the commands from the last endpoint used for the numbered On/Off buttons, causing the REST API plugin to see new group assignments. When I bind the endpoints to groups manually, the commands are sent from the appropriate endpoint. However, I haven't yet been able to make the REST API create these bindings, since it already sees the default groups.

@manup

This comment has been minimized.

Copy link
Member

manup commented Oct 21, 2019

However, I haven't yet been able to make the REST API create these bindings, since it already sees the default groups.

Yes tricky perhaps a read-only group/button setup for which the bindings are created while sensor search is active will work.

  • When remote joins and modelid is detected:
  • Create a todo list of bindings which are to be created, which is processed one at a time
  • The bindings target new dynamically created groups
  • During active sensor search, no default Groups are created based on received commands

A "binding todo list" might be useful in general.

Does this make sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.