Page 1 of 1

Profile change after restart

Posted: Mon Mar 30, 2020 11:35 am
by morten
I'm using my home automation (Openhab) to control active profiles in BI. I use various profiles depending on the situation: No one at home daytime, only children at home during night, etc. I have the home automation system change profile e.g. when my or my wifes mobilephone connects to the WIFI (i.e. when profile in BI was set to e.g. "Parents Away, daytime"). I use the MQTT connection and http-API in BI for this inter-system communication.

One problem with this setup is when BI for whatever reason is restarted. Not a big problem when I'm doing the restarting, but I've also seen restarts initiated by BI itself (Can be seen in the log). Profile is then set to profile 1 (which I for example am not using in any of the scenarious controlled by the home automation system). This then stays the profile until a condition is met to iniate a change of profile (e.g. sundown) by the automation system. This can take many hours if I'm unlucky.

To solve this problem I'm monitoring the MQTT-topic "BlueIris/app". The payload "running" is sent when BI has been (re-)started. I then put a delay of 20 seconds to allow full startup, and then I have my home automation software tell BI to activate the profile that was active before the restart.

This works fine for me, but I would appreciate any comments on how there might be better/simpler/more reliable solutions out there.

Re: Profile change after restart

Posted: Mon Mar 30, 2020 3:58 pm
by TimG
Hi morten,

It sounds like you have it sorted there; the only thing is, why is BI rebooting ? I don't think mine reboots itself at all, there are no reboots in the log.

Do you allow BI to automatically update ?

Re: Profile change after restart

Posted: Mon Mar 30, 2020 4:16 pm
by morten
Hi Tim.

No automatic update. It's been a couple of weeks since the last time, so I can not find the message in the log. It was something like "Restarted after unexpected shutdown". I never did find out what caused it. It might have been due to the fact that I had configured storage space on my NAS, and the windows service did not have write access to it. I have removed that now, so this might have been what caused it. Not sure.