V4.0.0

[alphons]

I have issues with rules not working after upgrade to v4.0.2. Schedules seems to work.

[alphons]

I have 3 door sensors that needed the fix to make them work in 4.0.1
After Upgrade to 4.0.2 they fail to work again.
The Settings for acceptUnsecureSet and acceptUnsecureSet have reverted to their old settings.

Can it be made permanent ?





3 steps taken to fix it.
1. In Rules, IF Rule does not show a device. Reselected the sensor, which was available in the list.
2. Set acceptUnsecureSet to 0 (had reverted back to Nul)
3. Set mapBasicSetToSpecificReport to True. (had reverted back to False)

Seems like this solved my problems with the rules to.

[micky1500]

Wait up to one hour after changing it to let the Z-Wave data to save or save it explicitly shutting down Z-Way gracefully.

The updates were a month apart. Lots of Hours !
I rarely do a graceful shutdown of my Raspberry.
Just upgrade and restart.
Do I need to do a graceful shutdown?

[PoltoS]

Some changes are saved instantly (like the completed interview, changes of apps settings in Smart Home,...) Some are not (like device status changes - or direct altering of internal engine settings lie acceptUnsecureSet and others). This is to prevent Z-Way from killing the SD card (this happened a lot in the past). In addition, we save Z-Wave engine settings every hour to have a more or less fresh state. If it was lots of hours, they had to be saved by hourly savings.