You need to find out if its really Cron (I dont believe it)
Switch something every Minute or to a Time every Day.
Use a Lamp or connect a LED to a GPIO, something like that
Try this first.
-
Pimatic cron doesnt work until i login to web panel
-
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
i found a workaround that is really odd.
i inserted a cronjob command that requests 127.0.0.1 every minute.
* * * * * curl 127.0.0.1 > /dev/null 2>&1
And everything is fine now. (i had deep suspects about the sleeping of raspbian os, and struggled with that. but nothing changed, then i found this workaround. )
-
Any news on this? I think this is a really serious issue. I now also noticed this when I wanted to use an
every 30 minutes
trigger to take timelapse photos and was wondering why it only took photos for some time.I think the solution above is just a very dirty workaround.
@sweetpi any ideas? The plugin should normally not be dependant on the web front-end at all? I can’t imagine where this comes from.
-
It looks like requesting the values of the attributes of the devices used in the rule does hang until the webfrontend does request them.
@macitemre could you post the full rule that is not working and all devices or device classes used in this rule?
-
Here it is the condition
every 30 minutes
the action is only shellexecute.Any other ideas how to work around this as long as we don’t have a fix?
-
Hi all, I have exactly the same problem, a cron job is only executed after a login into the web panel
cron installed:
"plugins": [ { "plugin": "cron" }, "rules": [ { "id": "poort-open-maandag", "name": "Poort open maandag", "rule": "when it is Monday 12:15 then switch poort on", "active": true, "logging": true },
and this is from the event log:
I logged in at 12:28 to see is ‘poort’ was open, it opened on the login
The ‘poort’ device:{ "plugin": "gpio", "active": true },
( node.js module onoff is installed )
"devices": [ { "gpio": 17, "id": "poort", "name": "Poort", "class": "GpioSwitch" }
A relais is connected to gpio 17, manually is everything working correctly.
When I copy an existing rule and change the time en stay logged in to see if it is executed, the rule is working.
The rasp is a fresh install of (headless) raspbian, on an older rasp on other location is everything working correctly.Help needed!
-
Just added
* * * * * curl 127.0.0.1:9000 > /dev/null 2>&1
to crontab to test if that helps.
( Pimatic port = 9000 )Rule:
{ "id": "poort-open-woensdag", "name": "poort open woensdag", "rule": "when it is Wednesday 14:00 then switch poort on", "active": true, "logging": true }
This solution is working for me, Pimatic in some kind of sleep mode?
-
Same problem for me.
Pimatic 0.9.38 installed in /home/user/pimatic-home/ on Raspberry PI 2I am using this plugins:
- cron 0.8.8
- johnny-five 0.9.1
- mobile-frontend 0.9.11
- shell-execute 0.9.8
- sunrise 0.8.7
My time rules only start if my pimatic url is open in a browser.
If my rule starts at 6 o’clock nothing happens.
If i open at 7 o’clock my pimatic url then all rules from 6 o’clock starts…I will use the dirty workarround with crontab.
But i prefere a solution inside pimatic in the future.Sorry for my bad english.
-
Same kind of problem here
Curious about a “real” solution!