I have some contact sensors that used to work great.
But, for some reason after eWeLink CUBE 2.0.0 update, all them stopped updating states on Node RED, although they work normally on iHost.
I can’t remember what options it had before as State, but now it shows only Battery state and I suspect the lack of a “contact” state (opened/closed) causes the component to be useless when used with a contact sensor.
As a matter of fact, a temperature sensor I have shows all possible states as expected:
I’ve also discovered that Homebridge with eWeLink CUBE plugin (homebridge-plugin-ewelink-cube) isn’t receiving contact sensor states either.
It’s log has:
[6/25/2024, 4:14:07 PM] [homebridge-plugin-ewelink-cube] This plugin generated a warning from the characteristic 'Contact Sensor State': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
It’s working fine in iHost, right?
We’ve checked.
The result is this device used new capability which is not supported by node-red plugin yet.
We’ll support it in next version of node-red-contrib-ewelink-cube.
I was starting to do some NR with a couple of spare contact sensors when in the debug noticed that some do not report ‘detect’ – it is not even a capability – but not every sensor suffers the same!
The sensors report correctly in the ihost dashboard.
Oh, so these unfortunate people are F-ed for two months, basically. That’s not something responsible business would do.
Out of sheer curiosity then: how can people bring back the old firmware and run it as a temporary solution, till a new firmware is pushed out?
Seriously guys, telling people that their smart home is out of order for 1/6th of a year on top of all problems the CUBE has been giving so far is ludicrous.