Phantom rules/apps

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
cdogg76
Posts: 23
Joined: 28 Sep 2014 23:13

Phantom rules/apps

Post by cdogg76 » 05 Feb 2019 03:41

Hello,

I have a couple Schedule app configurations to turn lights on/off at specified times that have become phantoms. Basically, I reconfigured those apps to change the times, but they are still running at previous times (and also at the newly configured time).

Where is this data stored in the file system on a Razberry setup? Or, is there some way to rebuild the rules (hopefully without me having to reenter all of my configurations)?

Thanks!

fez
Posts: 85
Joined: 20 Jul 2015 23:03

Re: Phantom rules/apps

Post by fez » 06 Feb 2019 13:03

It looks like the registered Cron events were not properly removed by the schedule app you were using.
Try report a bug by the app developer, whoever that night be.

piet66
Posts: 45
Joined: 04 Feb 2017 17:00

Re: Phantom rules/apps

Post by piet66 » 06 Feb 2019 22:18

And do a restart of zway server to remove the old cron tasks.
-
Raspberry Pi 3 Model B Rev 1.2
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
Raspbian GNU/Linux 8
Z-Way version v2.3.7 from 2018-03-23 09:28:53 +0300 (build b1902d4433d1337bd488834db3347fa7ef8f8a33)

cdogg76
Posts: 23
Joined: 28 Sep 2014 23:13

Re: Phantom rules/apps

Post by cdogg76 » 07 Feb 2019 02:38

Thanks for the suggestions. It's the Schedule app that, I thought, came with the base install. I'm not sure how to submit a bug report to that.

Are these crons actually system crons i.e., via crontab, or are you referring to a proprietary scheduling system within the app? I don't see any actual crons from crontab for my scheduled items. Is there some way I can access those directly?

I'll try rebooting to see if that clears them. I can't remember if I've rebooted since I changed the schedules.

Thanks!

cdogg76
Posts: 23
Joined: 28 Sep 2014 23:13

Re: Phantom rules/apps

Post by cdogg76 » 07 Feb 2019 03:25

Unfortunately, the reboot didn't help.

piet66
Posts: 45
Joined: 04 Feb 2017 17:00

Re: Phantom rules/apps

Post by piet66 » 07 Feb 2019 11:35

cdogg76 wrote:
07 Feb 2019 03:25
Unfortunately, the reboot didn't help.
So it's caused by different reason than supposed.

zway cron jobs are different from Linux cron tasks. You can find them in storage/configjson.
Or via http://....ip...:8083/ZAutomation/api/v1/instances
-
Raspberry Pi 3 Model B Rev 1.2
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
Raspbian GNU/Linux 8
Z-Way version v2.3.7 from 2018-03-23 09:28:53 +0300 (build b1902d4433d1337bd488834db3347fa7ef8f8a33)

cdogg76
Posts: 23
Joined: 28 Sep 2014 23:13

Re: Phantom rules/apps

Post by cdogg76 » 09 Feb 2019 03:17

Hello,

Thanks for the pointers. The file is automation/storage/configjson-... appended with a long string of what appears to be hex numbers. I'm assuming that's it.

But given the hex numbers in the filename, it makes me think this is a generated file. Is that correct? Is this what the z-way UI actually writes to for storage of schedules, or does it write to a db elsewhere, and this file gets generated from that and is what z-way actually executes? That is, is it possible that this file (configjson) might get corrupted, and I can do something to get it regenerated from the actual configurations?

Thanks!

piet66
Posts: 45
Joined: 04 Feb 2017 17:00

Re: Phantom rules/apps

Post by piet66 » 09 Feb 2019 12:17

Yes, that's the right file. config.json is an abbreviation for it. You can have a look in it to see if it's corrupted. It's not very likely.

You can do following:
1. http://<ip>:8083/ZAutomation/api/v1/instances/<your instance number> to get the stored configuration of your module instance.
Have a look in it to see whether it is what you have entered.
2. http://<ip>:8083/ZAutomation/api/v1/instances/2 to get the currently active cron jobs.
Search for the cron jobs your instance has created at runtime. Normally the cron task id has the instance number at end.
Look if the cron jobs are created correctly.

If both are correct it's not a cron problem. Perhaps other instance is running at that times? You can check all active cron jobs.

Another try: remove and recreate your instance.
-
Raspberry Pi 3 Model B Rev 1.2
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
Raspbian GNU/Linux 8
Z-Way version v2.3.7 from 2018-03-23 09:28:53 +0300 (build b1902d4433d1337bd488834db3347fa7ef8f8a33)

Post Reply