Page 1 of 2

Device stops working - new interview required

Posted: 21 Nov 2016 22:34
by roha
Hi,

I have the problem that most of my devices (switches, dimmer, thermostat) stop working after a few days in action. They still report the status and are shown as active but they do not react to any state changing commands from my razberry again.

As soon as I force a new interview the device works again. I haven't been able to find a pattern yet. Some devices stop working after a few days, some after a few hours. It's quite annoying because you can't rely on it.

Does anyone has seen this before - and know how to fix?

Thanks,

Robert

Re: Device stops working - new interview required

Posted: 22 Nov 2016 11:56
by Z-Wave Support
Hello,

which Z.Way Version is installed on your RPi?
What do you use, a UZB or a Razberry?

Best regards
Z-Wave Support Team

Re: Device stops working - new interview required

Posted: 22 Nov 2016 12:35
by roha
Hi,

I'm using a Razberry. I'm on the latest 2.2.3 firmware - but I've seen this behaviour also on earlier versions.
Version details
Version details
Bildschirmfoto 2016-11-22 um 10.31.39.png (121.64 KiB) Viewed 11312 times
Thanks for your help,

Robert

Re: Device stops working - new interview required

Posted: 23 Nov 2016 10:18
by Z-Wave Support
Hello,

the newest version is 2.2.5. Please save a backup in SmartHome UI and Expert UI and update your System.

regards
Z-Wave-Support

Re: Device stops working - new interview required

Posted: 23 Nov 2016 14:14
by roha
Hi,

I tried the upgrade to 2.2.5 but all my Fibaro Motion sensors stop working. So I had to roll back. Is this a known issue?

Thanks,

Robert

Re: Device stops working - new interview required

Posted: 24 Nov 2016 10:32
by Z-Wave Support
Hello,

deactivate all your Apps and investigate that problem further.

ragards
Z-Wave Support

Re: Device stops working - new interview required

Posted: 01 Dec 2016 08:54
by CudaNet
I have the exact same problem with Leviton dimmer/scene capable switches. Works for a day or days - sometimes hours and then stops responding to actions (e.g. on/off etc.). The device will indicate active and even reflect a state change if I toggle the Leviton switch. Re-interview and it works again (temporarily). I even sent a switch back for a replacement to have it happen again.

Raspberry Pi3
2.2.3
Razberry2 (latest board with longer range antenna).

I'm seriously disappointed as this is unreliable and therefore quickly becomes a useless product. Support wants us to upgrade but the issues change from 1 -2 problems to a host of new problems. Then they release 2.2.5 with zero release notes. I honestly get tired of trying to figure out why something isn't working and support is simply non-existent. Rather than introduce new features, focus on maintenance builds until we reach a stable state.
roha wrote:Hi,

I have the problem that most of my devices (switches, dimmer, thermostat) stop working after a few days in action. They still report the status and are shown as active but they do not react to any state changing commands from my razberry again.

As soon as I force a new interview the device works again. I haven't been able to find a pattern yet. Some devices stop working after a few days, some after a few hours. It's quite annoying because you can't rely on it.

Does anyone has seen this before - and know how to fix?

Thanks,

Robert

Re: Device stops working - new interview required

Posted: 01 Dec 2016 16:00
by pz1
Then they release 2.2.5 with zero release notes.
I can understand your frustration, and that of others facing the same.

In my role of moderator I raised Issue #120 on github.

Re: Device stops working - new interview required

Posted: 01 Dec 2016 16:51
by Vovven
I can confirm that I experience the same type of problem as described above for switches.
I've upgraded to 2.2.5, still same type of problem.

Re: Device stops working - new interview required

Posted: 02 Dec 2016 12:47
by pz1
pz1 wrote:
Then they release 2.2.5 with zero release notes.
I can understand your frustration, and that of others facing the same.

In my role of moderator I raised Issue #120 on github.
@PoltoS, thanks for updating release notes for v2.2.5