Device stops working - new interview required

[CudaNet]

Thanks pz1 for opening the issue on Git. Now we need a 2.2.6 that addresses the loss of z-wave control ASAP. Allow me to write the release notes.

Code: Select all

2.2.6 Corrects issue with having to re-interview specific z-wave devices.

[000]

Thanks pz1 for opening the issue on Git. Now we need a 2.2.6 that addresses the loss of z-wave control ASAP. Allow me to write the release notes.

Code: Select all

2.2.6 Corrects issue with having to re-interview specific z-wave devices.

CudaNet, I do an upgrade, but the actual version is 2,2,5, is already public the 2,2,6?

Thank you!!

[pz1]

I don't expect a 2.2.6. They seem to be working on 2.3.0 now. It is not advisable to try any of the present 2.3 release candidates. A lot of code is still changing as far as I can see.

[CudaNet]

Greatness ? Looks as if 2.3.0 is now official with release notes. Can anyone confirm that this release alleviates the issue (as defined within this thread) ? Much appreciate any feedback.

[PoltoS]

v2.3.0 is out!

[roha]

I've just upgraded. Fingers crossed.

[roha]

Upgrade done - this time without issues.

the good: my fibaro motion sensors still work.

the bad: nothing seem changed regarding the interview problem

[jarnold]

Still getting the problem after using the ExpertUI and returning to the Razberry main menue. The device I have worked on is lost.

[PoltoS]

Can you give more info about the issue?

[roha]

So, after using 2.3.0 for some time now, I have to say that it is indeed a lot more stable regarding this issue. It was not necessary for me to do the often interviews again.
Once thing I do notice is that the status of the actors often are not updated properly. This caused me some issues as I had the "Don't send On command, if device is already turned On, similarly for Off" flag enabled in a lot scenes. Since I have disabled the flag it became a lot more reliable. So, thanks a lot for that!

Cheers,

Robert