I have this sensor model SNZB-03P, but in node red it doesn’t let me select detection, I can only select all, battery and RSSI. And I can’t create the scene. Does anyone know why it could be?
In this other sensor that I have, it does allow me the option to detect
All the best.
This is a problem with ewelink cube 2.0 and node-red ewelink cube add-on. They are supposed to fix node-red ewelink cube add-on in August. All newly added sensors to ihost cube 2.0 behave this way.
So we have to wait until August. What a shame they can’t do this with users. I buy sensors that I won’t be able to use until they are updated. I’m sorry but I feel cheated with users. You can’t sell equipment and have the software like this. If I pay it’s to be able to use it, not to have it as decoration.
In this case, the sensor works normally.
What is not working is the node-red complement.
To make automation within the iHost automation platform the sensor is working properly.
The sensor must also function properly via the Matter Bridge.
I’m not having trouble using the Matter Bridge with these sensors.
I even put them in the Node-Red via Matter without any problem.
there is a new update (node-red-contrib-ewelink-cube v1.2.3)
In host cube 2.0.0 the sensor still doesn’t show any movement in node-red.
How did you place sensors in Node-Red via Matter?
I don’t use matter, in node red I use the event state node, I select the ihost to search for the sensors, etc. that I have in the home automation center, and I select the action I require, be it detect, lamp module status, etc. …
And I have already updated the nodes in version 1.2.3
The sensors, before the ihost update to 2.0.0, worked correctly. After the update, any sensor that I introduce does not have the option to select detection
As you can see in the images, one of the sensors were there before the update and has the detection option, and the ones that incorporated new ones do not.
do you have SNZB-04P ?
A recent update should get these sensors to work, but you need an extra switch node for now.
There would be a revised version to optimize this usage, releasing along with the next version of CUBE.
I don’t have a SNZB-04P sensor, the door sensors I have are SNZB-04.
The new update has arrived and I still have the same problem. I can’t program in node red, since the detect option doesn’t appear. Now, how do I make my home automation work? Do I spend money to have useless devices?.
So you can’t receive the true or false status?
I’m using it like this and so far it’s working correctly.
However, I can’t retrieve the status of whether the door is open or closed!
There really is a bug in this regard.
And when we use different sensors from different brands, sometimes the sensor status is different.
In some I have the contact status, in others I have detected.
There are still other cases where the status node is bringing contact information to the sensor.
The funny thing is that I have about 4 more of these sensors and 2 of them do not have the contact option.
However, when using ALL, I receive the status of true or false.
It would be a good idea for @ward to check this out.
Another version of node-red-contrib-ewelink-cube is on the way.
And it will fix all your problem.
It’s not a workaround but a proper version for our new open api protocol.
So it still needs some time.
Might be release in the end of the month or early next month.
I’m glad to hear that a new version will be made available.
I’d be happy to help with testing if needed.
I noticed that in one of my labs Matter started to become unstable and was not representing the statuses correctly.
At a certain point in HA, which is already using Matter 1.3, I can’t seem to put the matter bridge there anymore due to naming errors, I believe.
I can’t say for sure because I’m not a DEV.
I still have the same problem and I have updated the ihost and node red to the new version, there is no way to get a signal about the status of the sensor. It is a shame how little serious users are after 1 month of problems.
As the Dev himself said, the solution would be ready by the end of the month or the beginning of the next.
I understand that it is an annoying problem.
However, it is only affecting Node-Red and Homebridge.
The Matter bridge continues to work normally.
Sorry about that.
Do you mean you still can’t receive sensor status after selected “All” in event-state node?
Using this node option.
Depending on the device it may not bring status information
For example, this is a motion sensor that does not display the movement status in this node.
This is probably what is causing the problem.
Using input node the movement information exists.
We only did a workaround in event-state node.
So get-device node still can’t get any new capability.
