Also something similar is going on with buttons - capability there, but no state.
It might be worth checking all types?
1 Like
Lol guys. Donât bother⌠
Here is another user with the same problem, a serious company would have the update the next day, at most 2 days. You cannot do this to the detriment of the user, now I have decorative sensors and the home automation does not work at home. Who pays for that, I know who!! My wallet.
Did you try press the button?
The press capability didnât show on state may because you didnât control it.
Thats very interesting - you are correct, no press means no data.
I will have to think abut this a bit - I feel another topic coming on!
Can I ask what the âidentifyâ capability is? I have seen this on a couple of sensor types, but it is something that is not reported in the status section.
Identify means some sensors needs confirmation to do sth.
The thing they do diff from sensor to sensor.
Thanks for censoring my posts, Sonoff/ewelink/itead whoever.
Yes, CUBE is t.o.f.u-d.r.e.g software and your approach to fixing issues YOU created is disrespectful.
Dear Ewelink/SONOFF Team,
I am writing to highlight an ongoing issue with the API Sensor State in the Ewelink iHost devices, which is causing significant problems for me and many other users. It appears that similar issues are affecting other users as well.
These devices are essential for automating many homes and applications, making it especially frustrating when such issues arise without a satisfactory solution.
We urgently need a statement and resolution from the company. The continued lack of a solution is severely impacting our daily use and eroding confidence in the reliability of your products.
I look forward to a prompt response and appropriate action to address this problem.
Thank you for your attention.
Best regards,
2 Likes
You have updated the ihost firmware - the rest of the plugins are broken. You have released the device - the software does not work. Whatâs happening? Why donât you update the entire ecosystem together?
IHost in the previous firmware, the network was broken.
Node Red also doesnât work because of the eWeLink CUBE plugin.
Homebridge also doesnât work because of the eWeLink CUBE plugin.
Thx for your feedback. We feel sorry for any trouble caused by the issue.
I have forwarded your message to CUBE team for possible solutions.
Hey
Thx for the message.
We understand that the recent update has caused some frustration. This update included significant changes to the backend, and we recognize that it may take extra effort to ensure everything operates smoothly beyond the standard update routine.
Please note that some features are still listed as in the Copilot stage, which means they might have issues, including some unexpected ones. Given that CUBE is an open system, we do not restrict the use of devices based on brand or platform, which can occasionally lead to compatibility issues.
Our team is closely monitoring the issues reported here and via support tickets. We are diligently working on solutions, and some of the identified issues will be fixed soon.
Thank you for your patience and understanding as we improve our system.
Hi
Thanks for the info. I have a feeling that might be useful - not sure where or when at the moment 
Can I just add another node red âoopsâ. The water leak detectors only have battery and rssi as capability and status.
Thanks
@SuiKa
there is a new update (node-red-contrib-ewelink-cube v1.2.3).
In iHost cube 2.0.0 the sensor still doesnât show any movement in node-red.
LOL, good thing ITEAD/Sonoff isnât an antivirus software vendor with access to the Windows kernel, because we would be back to the Stone Age by now.
Though I often wake up with a horrible, dreadful feeling that the safety of the Chinese nuclear stockpile is managed by software of the same quality, it makes me instantly grateful for living another day.
Relax people 
#tofusoftwareforthewin
Apart from the fact that Cube 2.0 ruined Node RED automations for a suite of Sonoffâs SNZBs (03, 04, 06 etcâŚ)
It was meant to bring a Storm and boy, oh boy, did it deliver.
Ward, all it takes is to say this:
WE take full responsibility for a f* up WE caused. Itâs out fault, we are to blame and no one else. Fixing this mess is our priority, we dropped everything else to fix the issue ASAP. Sorry.
⌠and back it up by hard work or at least give people some temporary solution, to bring back broken functionalities.
I presume itâs problem within eWeLink CUBE itself, maybe in its exposed API used by other plugins (ie. homebridge and node-red eWeLink plugins).
For that reason, both plugins (and possible others) donât receive the correct information from CUBE and therefore canât work properly.
Maybe if the source code was opened somehow we could try to do some further investigation.
Anyway, all we can do for now is wait for a proper fix from the team.
probably you are right. The problem only affects sensors that were added to ihost after the 2.0 update. sensors added before the update work normally.
My sensors that had been added before the update also had trouble working, but in version 1.2.3 my problem was solved.
Sometimes the problem of you need the upgrade combo to update the Pluguin and iHost.
In the last email I received from the support, I said that I would be released at the end of that month.
We have 6 days left of the month. You can release tomorrow or I donât really know.
Update 2.0 must have broken the API into parts, which must be fixed at 2.0.1 (I donât know the number of the version) to get back up and running.
But since day 1 I had an error I sent a feedback log and that was a conversation that lasted almost the whole month via ticket for my error to be corrected.
Yes, I can confirm that sensors added before v2.0.0 also donât work anymore on this version.
In fact, all my contact sensors were added before the update.