iHost update

Already sent via Ihost, Feedback. Check, ticket with ID211160

1 Like

Any news ?

No news for all devices for now. I guess there was a holiday lull or some such thing. Either way, nothing shocking is likely to happen :grin:

Hey,

Sorry for the late reply.

I think SONOFF staff has taken over your ticket and responded last month.

Just routine between updates/versions. :wink:

The problem is still not resolved. I would like to know if the problem will be solved in the next update?

Hi, bajanich.
Sorry for the delay.
I can’t quite understand the problem.
Do you mean two sensor’s operation mixed?
Can you specify the problem more?

I have already described the problem earlier here and via email (ticket with ID211160).
The sensor is triggered, and this is visible in the Ihost log, but some triggers do not turn off or turn on the sonoff mini. There was no such problem when using Sonoff bridge. Of all the smart home equipment, the sonoff bridge was changed to ihost.

Example: I open and close a door with an open/close sensor. In the event log of the open/close sensor in ihost, I see these actions. But after a random number of such openings/closings, the sonoff mini r2 relay stops responding and nothing happens. after 10-15 seconds everything works again. During the day I can enter a room and the light will turn on, but after I leave it does not turn off. Or I may walk into a room and the light won’t turn on, but after waiting 10-15 seconds if I open the door again the light will turn on. When I used the sonoff bridge, I did not observe such problems, even if I stood and specifically opened/closed the doors, the response was 100%. This problem also occurs with the motion sensor, but less frequently. I replaced the relays and sensors with new ones (those that I had not used before), but the problem also exists with the new sensors and relays, which means that the problem is not with them. Why ihost behaves this way is unclear to me.

What kind of sensors? What are they?

SNZB-04 and SNZB-03 which have not been used before. spare. to rule out a problem in the sensor itself

When I still had iHost, I used both of these sensors. Also other Zigbee sensors, in these PIR sensors from IKEA. I didn’t notice any problems. A poor consolation for you but I think that iHost has little to do with your problems. In the sense that they stem from something else.
When it comes to PIR sensors, you have to remember the cooldown grace period. This has nothing to do with iHost.

The main question is why did this start happening after I changed the sonoff bridge to ihost? However, all other devices remained the same. There is a problem on ihost, but there is no problem on Sonoff bridge.

One more question.
An open/close sensor to trigger a Sonoff miniR2 to act is base on smart scene, right?
Can you take a screenshot of your scene?

Any news on when my problem will be solved?

Can you still reproduce the problem the newest version (v2.2.0)?

Yes, after updating to version 2.2.0 - the problem remained

Are you trigger the scene within 10 seconds?
If you trigger the scene with interval more than 2 seconds, is the problem still presist?

Example: I open and close a door with an open/close sensor. In the event log of the open/close sensor in ihost, I see these actions. But after a random number of such openings/closings, the sonoff mini r2 relay stops responding and nothing happens. after 10-15 seconds everything works again. During the day I can enter a room and the light will turn on, but after I leave it does not turn off. Or I may walk into a room and the light won’t turn on, but after waiting 10-15 seconds if I open the door again the light will turn on. When I used the sonoff bridge, I did not observe such problems, even if I stood and specifically opened/closed the doors, the response was 100%. This problem also occurs with the motion sensor, but less frequently. I replaced the relays and sensors with new ones (those that I had not used before), but the problem also exists with the new sensors and relays, which means that the problem is not with them. Why ihost behaves this way is unclear to me.