HC2->HC3 - unsolved issues

[marcwau 30]

Because my HC2 setup is approx. 5 years old with over 150 devices, I decided NOT to use the transfer procedure, but to do a clean install of all 155 devices in moving from HC2 to HC3 (v5.090).

In retrospect, I'm not sure that was the right decision; it took me 4 full days, with many retries of exlusion (HC2), and many retries of inclusion (HC3)... especially for the older devices.

But all in all the result is quite OK and most devices are behaving correctly.

 

A few issues remain:

 

1. I have over 20 Sensative Guard strips, and they have been performing flawlessly for 5 years on the HC2. They were used in scenes that turn the FGT heat controllers in the room to "off" when the window is opened, and to "return" to the heating schedule when the window is closed again - and it was much more reliable than the "open window detection" of the FGT.

Excluding the Sensative strips from the HC2 went relatively smoothly, but including them in the HC3 was a nightmare; I tried and re-tried endlessly and gave up on many of them. And when inclusion did work, the device sometimes ended up unconfigured, and reconfiguration never happens (waiting endlessly for wakeup). Waking the strips up manually is not recognised by the HC3.

Still, a minority of strips were included without problems, I don't know why.

Most of those now lead their own life. Without any apparent reason (the window remains closed), the HC3 suddenly shows the window as "open", which makes the related scene turn the heat controller off. This happens once a day, as far as I can tell, but at different times.

 

2. I also have 5 Aeotec Multisensor 6 v1.11 and I cannot change the parameters in the HC3. When I change a value and press save, it appears to work, but the value is NOT changed. That is very annoying, because the humidity sensor sends too many reports. And I want to turn the LED off (with an extra parameter), but it's not registered in the device either.

 

3. With the HC3 comes the Yubii app, and as far as I am concerned, the app should be re-built from scratch by a team that knows what (good) UI/UX design is. There is so much wrong with it... and so much you can mess up if you are not careful (like accidently setting the light level for all the dimmers in your house). And you need strong reading glasses.

And the whole idea of "learning" the order in which devices/rooms/... are displayed was tried in some old Android version long before the Yubii app was created, and Google quickly abandoned the concept because everyone hated it. And... And... And... 

 

Any advice on getting the Sensative strips work as they should is highly appreciated.

Edited November 17, 2021 by marcwau

[m.roszak 765]

Ad1 Have you been adding them at the beginning or when there was a lot of devices already in the system?
During Sensative strips integration we have noticed that those tends to fell asleep during configuration (during protocol mandatory neighbors list request) - if that is the case and those falls asleep during configuration it will be extremely difficult to configure them properly and there is nothing we can do about it.
During inclusion protocol sends potential neighbors list to the including node and we do not have any possibility to change this one.

Ad2 We have an issue in the backlog planned for one of future releases to check (and fix) why in some versions of Multisensor 6 parameters settings does not work correctly for some specific settings.
In preliminary research we found out that some parameters have different payload sizes in different revisions of the product - we need to prepare different parameters templates for different device versions.

Ad3 Full re-desing of the app is not planned at the moment but there are some things in the backlog for the app to be more reliable, faster with some additional UX changes. 
Can't give any timeline but I assure you that we focusing on it.

[Sjakie 156]

Ad1>>>use HC2 as slave and add your Sensative strips

              same for AEOTEC

Ad3>>>VERRY ANOYING!!!!!!!!!!!!!!

              if I come home I cant relay on the app if house is armed yes/no. The app ist showing realtime/real the state of the devices!!!!

              I hope it will have some priority by Fibaro its important. And you know what its a result of an update because  it was working well.!!!!

 

Ad4>>>I will move shortly to another house perhaps also to another sytem??My wife ist able to interact with that bl..... Yubi app to see if see can come in da house without notifing the rest of the people in the street.

 

Ticket is made but what will that say?

 

regards,

//Sjakie

 

[marcwau 30]

@m.roszak Ad1 - but why was it not an issue with HC2? I included those 20 strips as some of the last devices at the time, so with already over 100 devices in the HC2. I never had these problems then.

When you are saying: "there is nothing we can do about it", do you mean that I have to buy 20 new door/windows sensors, while the strips were working fine on the HC2 until a few days ago? And they are the only invisibly mounted door/window sensors - the only (big) advantage they have.

 

And what about the random switching of the status of the strips that I was able to include? Any idea what could cause that? 

 

Also, if I try to reconfigure an included but unconfigured strip, the HC3 is waiting for it to wakeup for ever; no matter how often I try to wake it up manually, or let the days go by, the HC3 does not respond.

One strip was actually one of the first devices I included and it did configure. But then I changed a parameter, and it still shows the spinning dot, many days later. So again, even the wakeup of a correctly configured strip is not acted on.
It's not just the strips; I have a similar problem with some other battery powered devices (minimote, keyfob, duwi...). A wakeup of the devices does not seem to trigger the HC3 to respond and start e.g. a reconfiguration, a parameter change or an association.

 

All this at least gives the impression that something is wrong in the timing and handling of (several/all?) battery powered devices (and their wakeup).

 

@Sjakie Ad1 - I really don't intend to keep the HC2 after the migration, so that is not an option. The fact that the strips worked fine before means that there has to be a technical solution to treat them the same way in the HC3 as in the HC2, no? But only Fibaro can fix that... 

Edited November 17, 2021 by marcwau

[SmartHomeEddy 1,006]

You are not the only one with problems with configuring Sensative Guard strips.
 

Search the forum for: Sensative Guard 

And you will find a lot of problems with the strips. 
 

 

Edited November 17, 2021 by SmartHomeEddy

[marcwau 30]

@m.roszakRegarding the second point about the Aeotec multisensor 6: if I uncheck the "use template" and try to adjust the parameters by number, I cannot save any change I try to make.

So I change a parameter, but the Save button is not enabled.

This happens for any device with a template, including Fibaro templates.

Easy to reproduce: uncheck the template, and whatever parameter you change, the Save button will not allow you to store these changes. 

Seems to me like a bug...

[m.roszak 765]

We are aware of the issue with unchecking "use template" for devices which has it.

When there is no template available it works ok - one of next versions will resolve this.