If you go this route, then I would look at 'hubConnect' a brilliant app which connects devices from one hub to be able to be controlled by another hub.
I have it on all of my 5 hubs (4 production, 1 dev/test hub) and it works really well.
Ok thanks. Oke other question sorry. For mode plus restricting after sunset. I'd like it to be -25 so it's just before sunset - but doesnt look like it can take that ?
sunset was at 5:37pm here (melbourne AU) and it's now 6:11pm and the mode hasn't triggered.
the presence sensor (which is controlled by rule engine to update to present not present based on all to keep things simple) was on at the time it should have run.
the time is correct on my hub and sunset is correct.
One thing that usually happens is that the app doesn't know the status of the presence sensor
If the presence sensor didn't change since configuring the app then the app doesn't know whether the sensor is present or not.
As with apps that use switches etc to restrict then it needs to be 'toggled' once before the app knows it's status
If you had turned on the logging before the event you would probably have seen the error.
It's always best when installing a new driver or app to enable the logging for a while to confirm everything works ok.
When you enable logging.. have the logs open in another browser window.
It should tell you the settings configured and also when it thinks it needs to trigger next. (As you save it)
Also, if you go back into the app after config/save and click the 'gear' icon in the top right-hand corner of the app, then scroll to the bottom of the new page, you should see a 'schedule' section..
I'd be interested to see what is there if you could screenshot it for me please?
It shows 'Astrocheck' (which checks every day for sunset/rise times just after midnight)
And the scheduled 'sunsethandler' which actually allows/prohibits the app at that time
I'm not sure what is happening and why yours didn't work as I'm using the same version