Sensative Strips Guard 500 doesn't report Open/Close state after updating to v7.0.0-rc.8

[dirkg173]

Hi Marcel,

After updating to v7.0.0-rc.8 the Strips Guard 500 from Sensative doesn’t work anymore. No more open/close is reported.

What I already tried and does not fix the problem!

• App restart

• Homey restart

• Homey PTP

• Maintenance (reset tamper alarm, within the app)

• New pairing doesn’t help also, this was reported by another user.

However, a Strip Comfort 500 continues to report the temperature.

Diagnostic code: d05e7237-d31a-4beb-80eb-7600b028ce79

Thx in advance!

Best regards, Dirk

[mruiter]

Change in setting advanced . The setting for alarm from report to binary switch and it should work again

Did it here with 10 strips

Verstuurd vanaf mijn iPhone

Op 29 mei 2021 om 10:38 heeft dirkg173 @.***> het volgende geschreven:

 Hi Marcel,

After updating to v7.0.0-rc.8 the Strips Guard 500 from Sensative doesn’t work anymore. No more open/close is reported.

What I already tried and does not fix the problem!

App restart

Homey restart

Homey PTP

Maintenance (reset tamper alarm, within the app)

New pairing doesn’t help also, this was reported by another user.

However, a Strip Comfort 500 continues to report the temperature.

Diagnostic code: d05e7237-d31a-4beb-80eb-7600b028ce79

Thx in advance!

Best regards, Dirk

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[dirkg173]

Tried it with one strip and it works.

Thx very much! You're great! 👍🏼

@Thorarin, I'm not closing the issue yet on purpose because the inclusion routine probably needs to be adjusted. I hope that is ok. Otherwise just close it.

[Thorarin]

So far I've not been able to reproduce this issue. It's working fine with notification command class.

Did you pair the Guard 500 using v7.0.0-rc.8 or was it already paired?

[dirkg173]

My Guard Strips were paired before Homey FW upgrade. But an other user paired a Guard Strip after Homey FW upgrade and had the same problems.

This is the thread in the forum (only German language, sorry): https://community.athom.com/t/sensative-lauft-nach-homey-update-nicht-mehr/47898

And @mruiter had also the same problems.

[dudz40]

I have changed a device to Binary Sensor as well. Still no open/close events. Also noticed that all my strips report unreachable in Zwave tool under Homey developer tools. At v7.0.0-rc.8 as well.

[dirkg173]

@dudz40, did you wake up the strips before saving the changed settings? In Developer -> Tools -> Z-Wave you can test the strips if they really unreachable. Click on the 3 dots at the end and then on Test. For this, however, the strips must also be woken up first.

Btw, this information is from Slack (31.05.21, 13:35 o'clock):

Tjalling Tolle is software developer at Athom.

[dudz40]

@dudz40, did you wake up the strips before saving the changed settings? In Developer -> Tools -> Z-Wave you can test the strips if they really unreachable. Click on the 3 dots at the end and then on Test. For this, however, the strips must also be woken up first.

Btw, this information is from Slack (31.05.21, 13:35 o'clock):

Tjalling Tolle is software developer at Athom.

Yes, just did a manual wake up and clicked the test...

NEO/Fibaro and others are functioning correctly after the update, just Sensitive is doing this.

[dirkg173]

The strip ID3 "Deur Fitness" has definitely NO connection to Homey. So this strip is definitely unreachable. Did you tried it also with the ID4 "Deur Wijnkelder"? Do you have any repeater/actors in use? If not, it might be a problem of the range.

Btw, to wake up the strips is a little bit tricky.

[dudz40]

I know ;-) about the tricky part, tested it with a number of strips ( I have more than 10, but this was never an issue, the strips are in use a couple of years). Other strips that use intermediates in the mesh have the same issue. PS do not know if there is a difference between the first gen strips and 500 type. I am owning the first gen.

[dirkg173]

NEO/Fibaro and others are functioning correctly after the update, just Sensitive is doing this.

I know, I have also NEO and Fibaro in use and they work without any problems. And there is definitely a bug in the FW v7.0.0-rc.8 as Tjalling Tolle has mentioned. Actually, the only way to get the strips work again is to switch the "Notification type" from "Notification" to "Binary Sensor". If there are more bugs within the v7.0.0-rc.8 I don't know. So my suggestion is to contact Athom.

The 500 strips are the first gen. I mentioned it because Sensative published new strips "Strips Guard 700". The number refers to the Z-Wave chip that is used.

[mruiter]

Then just do a reboot since zwave core seems to have problem

Verstuurd vanaf mijn iPhone

Op 31 mei 2021 om 14:53 heeft Martin Verbeek @.***> het volgende geschreven:

 @dudz40, did you wake up the strips before saving the changed settings? In Developer -> Tools -> Z-Wave you can test the strips if they really unreachable. Click on the 3 dots at the end and then on Test. For this, however, the strips must also be woken up first.

Btw, this information is from Slack (31.05.21, 13:35 o'clock):

Tjalling Tolle is software developer at Athom.

Yes, just did a manual wake up and clicked the test...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[mruiter]

Even beter do a pull the plug

Verstuurd vanaf mijn iPhone

Op 31 mei 2021 om 15:09 heeft Martin Verbeek @.***> het volgende geschreven:

 I know ;-) about the tricky part, tested it with a number of strips ( I have more than 10, but this was never an issue, the strips are in use a couple of years). Other strips that use intermediates in the mesh have the same issue. PS do not know if there is a difference between the first gen strips and 500 type. I am owning the first gen.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[mruiter]

Yeh but zwave core on the experimental suffers from several race conditions . Also have gen 1 and 2 all available on multiple homeys so it isn’t te app .

But when they come available I guess you will have to change from report to binary on the gen 1,s

Verstuurd vanaf mijn iPhone

Op 31 mei 2021 om 15:51 heeft Marco Ruiter @.***> het volgende geschreven:

Then just do a reboot since zwave core seems to have problem

Verstuurd vanaf mijn iPhone

Op 31 mei 2021 om 14:53 heeft Martin Verbeek @.***> het volgende geschreven:

 @dudz40, did you wake up the strips before saving the changed settings? In Developer -> Tools -> Z-Wave you can test the strips if they really unreachable. Click on the 3 dots at the end and then on Test. For this, however, the strips must also be woken up first.

Btw, this information is from Slack (31.05.21, 13:35 o'clock):

Tjalling Tolle is software developer at Athom.

Yes, just did a manual wake up and clicked the test...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.