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

eWeLink CUBE
63

I’ve been ranting about this since April. Most of the ihost users from back then are long gone. As of today, my ihost is worse than it was back then. There are no new features and broken support for Sonoff’s own devices in Node-RED, which was itself a workaround for their crappy, unreliable scenes editor. There is no way to bring back version 1.14 because Suika and Ward couldn’t be arsed to help us. No sense of duty, nothing.

I’m done. All I do now is give them a bad reputation wherever I can and warn people not to touch anything Sonoff as a token of “appreciation” for their support for us stuck with their crap. Well deserved.

64

Maybe I’m the only one left, but somehow don’t think so. Very pleased with it running Node-red and although there have been issues they have been resolved.
Agree with @Unnamedi so won’t repeat his post.
Sorry it’s not working for you. Suppose it must more than anything else a HA problem but that’s a rabbit hole I personally don’t want to go down.

65

I am platform/solution agnostic; I couldn’t care less about who, what, or how something accomplishes the tasks I need in the most efficient way. I would run an army of chinese rats to automate tasks in my home if that were the case, so let’s take HA out of the picture, shall we?

The objective truth is that ITEAD has not introduced any new features for the past few months. This is black and white, undebatable. Nothing. Nada.

Maybe I’m the only one left, but somehow don’t think so.

My word against yours, I suppose. There were posts on leaving/selling ihosts, everyone can seach on their own.

It’s “not working” for many people. Look it up. It’s me who is, let’s call it “most vocal”

Where is @SuiKa where is @ward to tell us how to make 04-P, 05-P, 06-P work?
From top of my head @ociepa.ekotox @el404 probalbly, @miguelangelanguloalmela @sintoxx have been waiting for a month too. John, walk us through how to make these things work. Simple, isn’t it? You are the man to tell us that:

there have been issues they have been resolved.

Im all ears, John.
Cheers…

EDIT: Oh, months end is approaching @ward @SuiKa are we going to get a timely firmware update this time round? Not dreaming about anything new or groundbreaking. Just patches fixing the damn thing. No “storms” please. Just mend this thing after the last one.

1 Like
66

I totally disagree that every FW release has to have new features implemented.

Again you are reporting and saying that 06P.
Again I have no problem with 06P.

I think if equipment is bad for you. You should not buy and recommend it. Don’t advertise on the product support forum itself that it’s not good and that it doesn’t.

I am a long-time iHost user.
I believe again that there have been and there are numerous flaws in the product this and a fact.
As I said, many problems have been solved.

The problem with 06P and 04P should be studied and corrected, I believe it will never be at the speed we want, but I believe it will be corrected.

As I have no problems with 06P and I cannot make the mistakes that are informing you I cannot help in this regard.

@ward @SuiKa

They can help

67

They promised it in the product card.
It’s been so long, and they’re just breaking what worked - the network was breaking in V1.14.0.
Homebridge/Node red in V2.0.0.

Here is a list of their planned updates.

321
3211000×1233 160 KB

123
1231000×802 149 KB

Matter Hub? There will never be a Meter Hub, because the chip is 32 bit.
Edge AI? It’s funny after all these bugs…

1 Like
68

Metter Hub is possible at 32Bit until several Matter Hubs work at 32Bit.

Well, well of all these items on the list taking HUB Matter all are in Beta state not?

AI is possible by the NPU that exists in the product.

Again they kind of promise updates every 2 months or something until the last update it was monthly.

Yes really from version 1.14 to version 2.0 there were some breaks to some items and some things.
But as I said with the update of the node-red and Homebridge some of these breaks have been corrected.

Of all these things the more they promised to have the one that I would say there is no plug-in or sketch would be the Zigbee plug-in.

That’s if you don’t take Zigbee2Cube into account.

So if you look at the Matter specification it doesn’t limit hubs to anything 64bit.

The Matter Hubs that already exist on the market work with 32bit chip.

Yes I know that 32Bits is dead some applications will no longer run on 32bits and etc…
Really for the application of iHost I do not see it as something dead due to chip technology.
I understand that the 32bit chip was put in to cheapen the manufacturing process and etc… But it’s not something that’s already dead.

About the use of NPU this chip is fully possible to use. I have an NVR that uses the same chip it can identify objects and people easily. logic that it cannot be used for more complicated things.

More like I said and everything about how it’s going to be. I believe that many things that were promised must have been delayed and so on… because there is usually a delay in these maps.

But again I believe that almost everything exists in the beta version taking away the HUB Matter part.

I agree to be upset about the break that existed from 1.14 to 2.0 and the whole story that existed about that which would be an update with big changes and etc…

These changes existed underneath everything that users see so much and that there were breaks in functionality.

I agree to be upset about that.
Because in the Update Log they could very well inform the possible existing errors.
And that they would be concerted in the next version and so on.
I agree with that chatiation about it.

More to the point of saying that these features do not exist or that they will not exist because of x or y is very boring.

Because there really are people who like the product and are wanting to help its development and etc…
Much of Matter is behind and due to the company itself that controls Matter. And apart from a new protocol that is still constantly evolving, each manufacturer has its own particulars.

69

Our discussion moved away from the main topic of the conversation.

The fact is that sensors do not report detection status to node-red and homebridge. @SuiKa confirmed this and they will fix it in the August update.
So all we can do is wait.

2 Likes
70

What you cannot do is make users wait a month to fix your error, it is detrimental to the user and shows little seriousness of the company. When these errors are made you have to fix them within a few days so that the damage you could cause to the user is minimized.

1 Like
71

We have a new CUBE update, has anyone installed it?

Firmware Upgrade
V2.1.0
New Features:

  • Initial support for OTA updates for Zigbee devices.
  • Added support for Sonoff Smart Water Valve.（If already added, remove and re-add the Sonoff Smart Valve after upgrading.）
  • Support multiple tile sizes for switches/plugs and sensors displayed on CAST.
  • CAST now adds dynamic UI display based on device features, including:
    • Turn On/Off
    • Brightness
    • Color
    • ColorTemp
    • Percentage Control
    • Detection
    • Temperature
    • Humidity
    • Illumination
    • Smoke
    • Contact
    • Motion
    • Leakage
    • Press Action
    • Battery Level
    Optimizations:
    -Enhanced iHost Zigbee2CUBE device features, adding support for:
    • Illuminantion (illuminance_lux)
    • Pressure (barometric-pressure)
    • Gas (gas)
    • PM2.5 (particulate matter 2.5)
    • Voc_index (Volatile Organic Compound Index)
  • Pairing Zigbee devices is now faster.
  • Optimized Open API
    Bug Fixes:
  • Fixed a bug potentially preventing Zigbee2CUBE-added switches/plugs from syncing to Matter Bridge.
  • Resolved the page lag issue caused by overwhelming device reports.
  • Fixed an issue where some devices won’t display default device images.
1 Like
72

Yes, nothing has changed. In homebridge, SNZB-04P still does not show the status.

Log:
[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).

2 Likes
73

Remove the sensor and add it again. Maybe that will help. I haven’t checked yet because I don’t have the new update.

74

Why not use it via the Matter Bridge directly in HomeKit?
I believe this sensor would be compatible with the Matter Bridge.

75

Got a strike on another post, an empty one this time, LOL. Checked forum to see whats what, checked ihost, a new firmware has landed. Installed. Reset NODE RED for good measure aaaaannnddd… this update did f*** all to 04-P, 05-P, 06-P conundrum in my case. I guess it’s a nothingburger for me. Maybe there are some important improvements I dont notice at the moment. Judging by the changelog, they were working for post month and the FW arrived on time. So thats always a plus. Will check in upcoming days.

EDIT: CAST feature disregards my virtual master switch created in the NODE RED and shows it as a plug. :grimacing: :man_facepalming:

76

hmmm…nothing change…

77

because you need to have a matter hub for this, there is no matter hub on ihost

78

I no longer have the strength and patience…what’s happening? When will everything just work without any “new features”?

79

In case you’re saying you don’t have an Apple TV Or a Siri that is compatible with matter?
Because iHost is a Matter Bridge.

I say this because I use it with Google Alexa and Samatthings.
I find it an easier way.
It’s a shame you’re having mistakes.
I’m waiting for a sensor like this to arrive to do this test to see if I have the same result. Because so far with 06P I have had no problem.

80

I have another voice assistant device, but it doesn’t matter. I use IHost as a local device, which is how it should be. To repeat this stupid problem, it is enough to connect snzb-06p/04p to IHost and send it to homebridge via the “eWeLink CUBE” plugin.

81

@SuiKa @ward did you manage to locate the cause of the problem?

82

Well, I really don’t know why the 06P isn’t working, it’s working normally and doesn’t lose the configuration!

I uploaded a Homebridge server for testing and it’s working normally as you can see!

1
11263×401 37.1 KB

2
21271×412 36.7 KB

3
3792×636 22.9 KB