[Updated] Presence Central

All of my apps started because I wanted HE to do something for myself
I released them when I realised other people wanted the same thing :slight_smile:

After lots of extra feature requests, most of the apps are much larger and have many more features than I use but hey! if it helps :slight_smile:

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 ?

25 mins before sunset! :slight_smile:

Most (if not all) of my apps have the same restrictions pages...


1 Like

Well there is is. Silly me thanks

1 Like

So i setup a day to evening trigger in modes plus

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.

any idea why it wouldn't have triggered?

thank you

Yep! (maybe!) :slight_smile:

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.


1 Like

Ok cool. Yeah the presence sensor definitely changed after it was configured and before the sunset (4 hours prior ). Will enable logging and monitor

Thank you

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?


there you go . thanks for your help

Ok.. that is a problem...
This is the schedule from one of mine...

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

1 Like

I would delete the child app and create a new one, then check for these settings.

I am also surprised to see a schedule for 'resetMsg'
This does not exist in Modes Plus!

Ha just my luck. I moved everything over from ST today. Felt cleansing actually! But lots to fix still. Will re do the app. Thank you.

Should I see something similar on presence central?

If you put similar restrictions then yes

1 Like

I re did the mode child apps and still same result. Going to delete app completely and re do code from your hub to ensure its right.

Re tried it - updated the code to ensure it was fresh (but didn't remove cobra app)

and getting same result

could this be to do with my location not been US?

Update: I think i checked the settings too soon. it has this now on evening check rule (day to evening mode at sunset):

and for asleep to day which looks lke it's ready to go at 6am per the settings

thanks for your help!

yeah still no luck after that i thought it would be working. Didn't go to evening mode tonight :frowning:

is this gone? link broken...

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.