Various enhancements

[ebaauw]

• Ignore faulty -100°C temperature in the regular and Xioami special attribute report for lumi.weather, see Aqara temp sensor reports -100 degrees #1748.
• Add ne operator for rule conditions, see Rule operator ne #1874.
• Initial support for iCasa remote, see https://www.icasa.io/afstandsbediening. Still work in progress.

[manup]

Cool thanks, good stuff, the remote looks interesting.

[ebaauw]

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]

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?

[Thomas-Vos]

Add ne operator for rule conditions, see #1874

Is there any place where details like this are documented? It is quite difficult to just guess the API differences between Hue and deCONZ without documentation.