[Node-RED] Contact sensor event-state node missing states

eWeLink CUBE
43

They don’t. I had the Tofu, I mean CUBE 2.0, with the latest Node RED and the latest eWeLink palette (version 1.2.2, I believe). It worked for some time until it stopped for no apparent reason. Two SNZB-06-P sensors stopped reporting present/not-present states in Node RED, causing the automations to fail.

I had paired the Sonoff presence sensors with the iHost before updating CUBE 2.0.

And it gets worse. Every time I reset the iHost, I need to REMOVE both presence sensors and add/pair them again; otherwise, they don’t report at all. :man_facepalming:

They messed up this firmware so badly it’s beyond embarrassing. If I were responsible for this mess, I’d probably feel suicidal.

EDIT: They’ll fix one thing in the next update, ruin two things, take several months to fix it and repeat the cycle. Break the vicious cycle and leave the CUBE malarkey. Seriously, there are better, far better alternatives. Do yourself a favour. My HA works like a clockwork and pairs to absolutely everything.

44

Pallet has updated to 1.2.3.
My temperature sensors are all working normal on ihost and node-red etc…

It may be that the FW of your sensor is not updated. have you checked if it is in the last version available?
Since iHost has no FW update it may be that in update 2.0 it was written above the newest FW of its sensor.

But I don’t have these sensors that you’re talking about I only have 1 old Zigbee temperature sonoff sensor that’s working normal.

The other sensors are from TUYA and everyone is working normal including Sonoff’s door sensors I have the first version of them Zigbee are working along with other door and window sensors TUYA.

All Tuya Zigbee sensors that are connected on ihost are working properly with Pallet version 1.2.3 and all of Sonoff’s old Zigbee sensors are also working properly.

It really must be something with the specific model of your sensor.

1 Like
45

HA itself is what else has updates that break integrations or change things.

I think it’s kind of unfair to compare the development of the two. There is a large community that is always making corrections and moving on to them to implement in the source code.

You can see that the CUBE team is smaller.

HA and for a slightly different audience than iHost’s public.

Usually updates always break things. the only mistake of the CUBE team is not to provide this information of what will be broken and what will not be broken.

So I believe it’s a process that everyone can grow together.

As I said earlier all my mistakes that were caused with version 2.0 were corrected with plug updates after a long investigation and help from both sides.

1 Like
46

back to the topic of the post.
the error only appears in motion and opening sensors added to ihost after updating to v2.0.
(SNZB-03, SNZB-03P, SNZB-06P, SNZB-04, SNZB-04P)

1 Like
47

all my 06P have a total of 4 are working properly. but all are in the FW version 1.0.6.

What is the version of your FW?

48

All are operating normally on Cube 2.0.

The only problem I had in Nodred was with Tuya sensors but it was arranged in the version of Pallet 1.2.3.

49

Wrote 1.2.2 but I meant 1.2.3, updated today. Appart from that everything is up-to-date. Still, doesnt work. My 06-P properties card has two entries: ALL and RSSI. When switched to ALL it provides JSON with id, RSSI, and brightness level.
I does not update presence state.

The FW is 1.0.6.
Node RED 4.0.2
Both report Link Quality Indicator at the moment, which isn’t always the case. (in the main UI thing, not the Node RED)

See, that’s the case, it’s pleasant summer evening and I’m troubleshooting most basic stuff, because some blithering :grimacing: :no_mouth: :face_with_symbols_over_mouth: didn’t hire testers to thoroughly test his software before launching. Why am I even doing this?!
Untitled design

1 Like
50

If you can, remove the sensor from ihost and add it again. if the error does not occur, it is some kind of magic.

51

Never expected that ihost could rival HA in terms of features, all I wanted was a reliable , simple, tweakable, local home automation.

Usually updates always break things.

LOL, no. Hell, no.

HA and for a slightly different audience than iHost’s public.

True.

So I believe it’s a process that everyone can grow together.

No. I have life and won’t waste my time on being unpaid beta tester. Not my mission in life. Sorry.

help from both sides.

Judging by the past performance of the company in areas of FW for ihost I can safely assume that ihost is just an unwanted pain in the ass for itead. Complete abandoment of the project is just around the corner, mark my words.

1 Like
52

Well, I just got a new 06P and put it on iHost. Where the network brings everything correctly [Processing: 17219558608825677982938976268471.jpg…] ()

I really couldn’t replicate the error.
I’ll see if it gets bad or loses the setup or doesn’t break free from the status.

17219559665518386880653692432054
172195596655183868806536924320541560×4000 918 KB

53

17219562067603779095043157206061
172195620676037790950431572060611560×4000 707 KB

54

Cool. I hear you.
Same configuration, same software, same FW, unplugged, flushed, reset, paired/unpaired.

Still. Doesn’t work.
EDIT: I asked them for some temporary solution and some tutorial on how to implement it two weeks ago but they don’t give a fuck. All is well as far as they are concerned. Abysmal levels of incompetence.

1 Like
55

As I said, I have this new one, as well as others that work correctly!

Even with the bug when the internet connection is lost and things get a little crazy, they were working correctly.

I ordered more of these sensors since my house is big, I want to see how they will behave!

I’m sad about your situation!

But I believe it should be investigated!

But as I said before, it is working normally via node network and etc… all the statuses are fine, so far all the automations are working correctly. I’m really surprised so far with this new one, I haven’t had any false positives and it always detects me when I’m present!

56

No worries.

My house is newly built, and it’s fully wired for Loxone. I didn’t originally go this way, as Loxone seems over-the-top, expensive, and plagued by some serious anti-user policies.

I like Sonoff’s SNZB P-series. They’re well thought-out, fairly cheap, and usable devices, but my God, the iHost is a lump of stinking crap. I’m using Home Assistant now, and it’s more than adequate. No one wanted my iHost, and it’s with me because I want to prove to myself that it will never mature beyond what it is now. The hardware is meh (32-bit, crap radios), but CUBE… CUBE is abysmal. If it was Japanese, the whole dev team would have committed seppuku out of sheer shame. Oh, and the dev team can’t stand harsh criticism, they censor my posts right away. China :no_mouth:

57

I have to disagree!

I agree that iHost is lacking.

32Bit may be a limit for more advanced users!

For example, my house is large and most of it runs Sonoff products and a part of it runs Tuya ZigBee!

Everything works on iHost without any problems and without any headaches.

That’s right, I have 4 air conditioners, 1 refrigerator, about 5 TVs, several lights and switches, several motion sensors, and so on.

I have everything connected to iHost and everything works beautifully via integrations that already existed and I haven’t had any headaches!

As I said in previous reports, I did have problems with iHost. Get in touch and we investigated my case and with that it was solved and everything is working normally.

I’ve used and have HA installed, it’s great and perfect, it works and does everything too.

However, for my scenario, iHost was a perfect fit. I just need automations to work, I don’t need a dashboard or anything else. They are simple automations that make the house work by themselves.

Some automations are done in nodered due to the limitation of automations in iHost, but as I said, this doesn’t make me mad at the product. Because I know it’s a new product on the market and they’re still trying to figure out how it should work!

From what I’m seeing, they’re committed to making it work with third-party devices. So much so that I have several and several Tuya sensors connected to it.

iHost is not an object to compete with HA, it’s not a replacement for it, nor is it a palliative.

iHost is more of a companion for those who have a house based on Alexas and Google Homes. Where all the complexity of having a Hardware that does billions of things doesn’t exist.

I think it is a smart Zigbee HUB that runs local automations. It is not smarter than that.

I would be much angrier if it were 64-bit and did what it does today! I believe that in the future, if there is an iHost 2 or a new version of the product, it will have other defects, but again, if the idea is a Zigbee HUB that supports all brands, etc., I don’t see why it should have so much firepower.

One day, HA in the Docker version will have Matter implemented in the code.

The iHost will be able to replace some types of HA installations.

I am not defending anyone here.

However, I believe that we have to respect everyone.

I believe that there should be demands for more transparent changes, etc.

But we should not attack anyone.

I don’t think that HA and iHost are on the same level or in the same category of devices!

As I said, iHost is a Zigbee HUB that can be used for more things. It fulfills this role very well.

At least for me, it has been doing everything it needs to do.

If it becomes a Matter HUB, it will also be perfect.

If it becomes a complete Matter bridge, it will also be perfect.

If I can put my cameras and record on it, it will also be perfect.

If I can put HA and run basic things, it will be perfect!

Apart from the Matter part, these other things would be a bonus!

Just being able to buy a product and pair my Zigbee devices to it without having to do much makes me happy!

It’s something that I can leave almost in the center of my house, it’s simple, beautiful and doesn’t take up much space, it doesn’t make much noise.

As I said, the product’s proposal is to be a partner of Alexa and Google Home and other Assistants like Samsung, etc.

1 Like
58

My situation is similar. NodeRed detects nothing but RSI and Battery… NR and Cube Pallete updated to the latest version, Cube on 2.0, unlinked and paired again but nothing works. My Cube firmware is original.

ID dispositivo
00124b002fa0a8c4

Fabricante
eWeLink

Model
DS01

Version
0.5

59

I have such devices.

Funny are they not bringing the status?
Could you confirm that homebridge does not also have the status?

60

I confirm) In the homebridge does not also have the status.
the device is SNZB-04P.
homebridge log:
‘Contact Sensor State’: characteristic value expected valid finite number and received “NaN” (number).

61

If I am not mistaken the correction for 04P will come out with the FW of CUBE.

From 04P I’m still waiting to arrive so I can see how it will work.

@ward

Could you report on 04P?

62

Yes, as i understand it, there is no difference, devices - contact sensor or motion sensor - not work correctly in homebridge or node red.
I created a post about it, they are aware of it.

He also wrote on github.