Hey,
Thx for the feedback. I have forwarded your information to the CUBE team and see if there’s anything we can do.
Could you please also send me a system log?
Thanks again for your time
Hello,
I gave it a try again, since iHost has been upgraded to v2.1.1, and I saw two upgrades of node-red-contrib-ewelink-cube too (now version 1.2.4) but still the same :
-
iHost sees a motion detector
-
It gets temp and humidity details
-
but I don’t get even the motion detector part in node-red
Worse, I have a few SNZB-03 as well, one got disconected and since I re-paired it it shows the same behaviour : no “detect” state is available from node-red :-/
In iHost previous version before v2.0.0, there’s no motion state, only detect state.
And after iHost version v2.0.0, all the newly paired PIR sensor, motion replaces detect.
But node-red-contrib-ewelink-cube haven’t catch up for now.
It still needs some time.
So we made a temporary workaround.
In node-red-contrib-ewelink-cube to version 1.2.4, with “All” option selected, you should be able to receive the state in event-state node .
There you’ll have your motion state.
We’ll release a new version to completely fix the problem in the end of the month or early next month.
Hello, understood, I managed to adapt my flows with the SNZB-03 or PIR313 and it works fine (by adapt I mean “All” option + replacing “detect”/“detected” by “motion” like explained in [Node-RED] Contact sensor event-state node missing states - #88 by wojtek). A bit buggy since my code doesn’t handle rssi and lqi payloads, but it’s not a big problem since I’ll be able to filter later.
My experience of multi sensors is that you are best buying a sensor for each component. The trigger is usually just one of them and then the others update at regular intervals or when the first activated. For example, I have door sensors/light which are only good for triggering when the door opens. Luminosity is lacking I think in the eWeLink system though, unless they’ve recently added it.
That’s a good point; many all-in-one sensors have such issues.
It’s already being discussed as our capability of Zigbee/Matter grows, but there isn’t much to share at the moment.
It would be useful. I have loads of automations that involve knowing if it is dark or light. I currently have a Tuya compatible luminosity sensor connected to Home Assistant using Zigbee2MQTT and whether it is light/dark saved as a Boolean “helper” and transmitted to the iHost using MQTT, but it would be a lot easier if it connected directly.
If you don’t think Sonoff wish to create a sensor I can try reconnect this one and send the iHost logs. I probably tried ages ago but that was with the old iHost firmware.
What is the sensor model?
Is that a real device or a virtual one? If it is virtual which settings and default settings JavaScript did you use?