forum

I have encountered a strange behavior running razberry:
My scheduled scenes are not being executed anymore if I reboot my raspberry pi.

The scheduled scenes still show up as active even though they don't work.
If I disable the scheduled scene and activate it again everything works fine: The scheduled scenes are being called again.

Is this the supposed behavior?

No, it isn't. What version are you using?

Can suggest to run debugger, but I believe it is a question of dependencies on Cron module. Scheduled Scene relies on it. Please check in the log that Cron is executed first

I am using version 2.1.1.

How do I run the debugger?

Could you please tell me where to find the logs you need?

Thank you very much,

jrn

jrn wrote:I am using version 2.1.1.

How do I run the debugger?

First thread under RaZberry forum index (viewtopic.php?f=3422&t=20387)

Could you please tell me where to find the logs you need?

/var/log/z-way-server.log

Thank you pz1 for the links you provided.

Here is part of the log file output:

[2015-11-12 20:15:58.347] [D] [zway] Worker thread exit point
[2015-11-12 20:15:58.347] [D] [zway] Worker thread successfully finished
[2015-11-12 20:15:58.347] [zway] Saving configuration data to config/zddx/e1678686-DevicesData.xml
[2015-11-12 20:16:07.342] [core] Executing script: /*** Z-Way Home Automation Engine main executable ***************************** ...
[2015-11-12 20:16:07.346] [core] Executing script: // Comon utilities and functions ...
[2015-11-12 20:16:07.356] [core] Executing script: // This script transforms old formats to new ...
[2015-11-12 20:16:07.467] [core] Executing script: /*! ...
[2015-11-12 20:16:07.518] [core] Executing script: // Underscore.js 1.7.0 ...
[2015-11-12 20:16:07.560] [core] Executing script: /*** Z-Way HA Virtual Device base class *************************************** ...
[2015-11-12 20:16:07.567] [core] Executing script: /*** Z-Way DevicesCollection class ************************************ ...
[2015-11-12 20:16:07.605] [core] Executing script: /*** Z-Way HA Controller class module ***************************************** ...
[2015-11-12 20:16:07.613] [core] Executing script: /*** Automation Webserver Auth Controller ************************************* ...
[2015-11-12 20:16:07.616] [I] [core] Executing script: /*** Z-Way HA Automation module base class ************************************ ...
[2015-11-12 20:16:07.619] [I] [core] Executing script: ...
[2015-11-12 20:16:07.628] [I] [core] Executing script: /*** Main Automation storage module ***************************************** ...
[2015-11-12 20:16:07.642] [I] [core] Executing script: /*** Main Automation webserver module ***************************************** ...
[2015-11-12 20:16:07.645] [I] [core] Executing script: // Make this testable by pulling in underscore from the parent module ...
[2015-11-12 20:16:07.650] [I] [core] Executing script: /*** Main Automation storage module ***************************************** ...
[2015-11-12 20:16:07.665] [I] [core] --- Loading ZAutomation classes
[2015-11-12 20:16:07.858] [I] [core] Starting ZWay Automation webserver
[2015-11-12 20:16:07.951] [I] [core] Loading modules...
[2015-11-12 20:16:07.960] [I] [core] Loading module Cron from modules/Cron
[2015-11-12 20:16:07.963] [I] [core] Executing script: /*** Cron ZAutomation module ************************************************** ...
[2015-11-12 20:16:07.982] [I] [core] Instantiating module 2 from class Cron
[2015-11-12 20:16:07.984] [I] [core] --- Starting module System Clock (CRON)
[2015-11-12 20:16:08.005] [I] [core] Loading module BatteryPolling from modules/BatteryPolling
[2015-11-12 20:16:08.067] [I] [core] Executing script: /*** BatteryPolling Z-Way HA module ******************************************* ...
[and much more...]

Is this the part you needed? So it looks like CRON is started in the beginning right? :)

You can just provide us an example of your config and we try to reproduce it

Absolutely. What's the best way to get my current config? What info/files do you need?

I've had this problem as well. Seems to be related to the naming of the scene, or the contents of the scene.
After a reboot, some of the devices revert to their generic names (same as when first included), and those scenes no longer works. I have had to remove a scene, remake it and re-edit the scheduled scene to get it to work again.
Basic stuff, still broken after all this time.

toomuo wrote: After a reboot, some of the devices revert to their generic names (same as when first included)

This happens to me too, a lot! It seems to me that there may be an issue with z-way not persisting such configuration changes when they are made in the expert ui, thus on a reboot they are lost.

My work-around:

Go to "Network" > "Control" on expert ui and create a backup

If you tail the log at the same time, you will notice that this actions triggers config write to disk.

Make sure you do this after _every_ configuration change you make. As well as ensuring your configuration is saved properly, it also means that you always have an up to date backup of your configuration (file is downloaded when you create the backup)