Sensative strips confuse wakeup with status change?

[marcwau 30]

In moving all my devices from HC2 to HC3 last week, the Sensative Guard strips have given me nothing but headaches.

Apart from not being to able to include most of them, I discovered another issue with the strips that did include.

Once every day, if you believe the HC3, the windows change their status from closed to open. In reality, they remained closed all day.

The consequence is that the scenes that use the strips to close or open the heat controllers, turn off the heat in those rooms once every day.

 

My gut feeling is that the wakeup of the strips is interpreted by the HC3 as a status change, because it happens once every 24 hours (the wakeup time).

 

Also, according to the HC3, the strips never wake up. I changed a parameter of the strips (LED indication upon status change), but it was never confirmed, the HC3 is still waiting for wakeup (the dot keeps spinning) ever since the change, several days ago. This happens on all the strips. It could also be explained by seeing confusing a wakeup with a status change.

 

In the 5 years that these strips were on my HC2, all of the above never happened.

Edited November 20, 2021 by marcwau

[RH_Dreambox 189]

@marcwau

Use the round magnet to wake up the device.
Repeat the movement with the magnet three times within 10 sec. as stated in the manual.

[marcwau 30]

@RH_Dreambox

I have tried that a million times. No reaction from the HC3.

I also tried hard and soft reconfigure, exclusion-reset-inclusion of the strip, ... every possible likely and unlikely remedy.

Nothing helps.

[RH_Dreambox 189]

@marcwau

Yes that sensor is a bit awkward, but it's just trying again.
First perform a factory reset of the sensor (Reset).
Start the inclusion in the HC3 and then wake up the sensor with the round magnet and check that there is a long flash.
When you wake up the sensor, it is important that you can see all three flashes and then a long flash.

[marcwau 30]

@RH_Dreambox

I had tried all your suggestions before. I have 155 devices and have had the HC2 (and the 23 strips) for 5 years and they worked perfectly. Last week, I made the switch from HC2 to HC3 (not transferring, but a clean install) and did most of the powered devices first, to have a good mesh. I then added battery powered devices, and that is where it started going wrong, especially with the strips.

I had done 5 strips in the early stages of the rebuild, and those are the ones that did get included, but that show the behaviour that this thread is about - flipping status every 24hrs instead of being seen as waking up.

 

But the other 18 strips I can not include, they never configure (see other thread). Whatever I try (including what you describe), they are added as "unconfigured" and reconfiguration afterwards does not work. According to A. Socha, during inclusion, because of the large number of devices, the discovery of neighbours takes too long for the strip to stay awake. So it goes in sleep mode before the inclusion is finished. Waking it up afterwards does not seem to work, and I think that is because the HC3 does not register the wakeup of the strip, for some reason. Even if the strip is very close to the HC3.

 

And it's not just the strips. I have similar wakeup problems with other battery powered devices (HC3 not seeing the periodic wakeup). Especially older v1 devices (Minimote, Keyfob, Recessed door sensor....).

 

I am really starting to doubt whether the switch from a perfectly stable HC2 setup to the HC3 was a good idea.

There is a lot to like about the HC3 and the web client is great (not the Yubii app), but it clearly is not as stable as the HC2. See also the thread about the "Serious problem detected" message.

 

Someone suggested to put the problem (battery powered) devices on a HC3L acting as slave to the HC3. But when I read the horror stories of master/slave problems, I am not sure whether that is a good idea.

Also, if there are only battery powered devices on the slave, I doubt whether its mesh is good enough... 

Edited November 20, 2021 by marcwau

[RH_Dreambox 189]

I also experienced that the HC2 was quite stable before I bought an HC3.
What attracted me to HC3 were the promised protocols 433 MHz, 868 MHz and ZigBee.
Now, almost two years after its launch, it is still not possible to use any of these protocols.
It's a shame and I and many other users have been fooled by Fibaro.

 

But what I was trying to help you with was my own experience with HC3 and these Strips.
Maybe there was a bug in an update that is causing your problems?

[marcwau 30]

The weird behaviour of the Sensative Guard strips on HC3 is not limited to flipping the state for no reason.

 

Yesterday, I changed the parameters of a number of strips to see whether that would make a difference.

Especially parameter 1, which determines the notification type; I changed it from 1 (default - "notification report") to 0 ("binary report").

I woke up the strips and the HC3 confirmed that the new parameter settings were stored.

 

Today, when the state of the window flipped from closed to open without any cause, the parameter setting (according to the HC3) was back at 1 instead of 0.

So the window sensor not only changes to a wrong state, but its parameters are changed also when this happens.