I’m Openhabian 2.5.7 build 175 on an RPi4 and have found an issue where when using the iOS Home app, devices will periodically display a “No response” message. This happens a few times a day. I have a script running as an hourly OH cron task with this content:
if the cron task is run when the devices are in the “No Response” state, communication is not restored. But, if I run the script manually from the command line, or execute the command from within Karaf the communication is restored. I’ve also used bundle:refresh in the script, but the results are the same.
I’m at a loss as to how to keep Homekit working as it should. Any ideas?
But as this is bit inefficient, with a little help from the community, I re-wrote the script as the above, but I think my “older” version may have actually worked better, but I’ll try it again and see what happens.
The cronjob is being executed under the same user that is being used on command line ?
Scripts that are being executed under cron have a limited environment.
You need to make sure that related environment variables that are required are explicitly set.
E.g. I would use an abosolute path to the openhab-cli executable.
You also can make sure that ( if you have not done yet ) STDOUT is redirected to a logfile.
Redirect to STDERR to the same or to another file to have a look at the output in case of an error.
As long as the executable ( openhab-cli ) is not found you will find that in the logfile then.
E.g. you can use
>> /tmp/mylogfile 2>&1
right after the call to your script file in the cron entry to redirect the output to a logfile placed in the temp directory. >> will make sure that output is appended to the end of the file. 2>&1 will redirect STDERR to STDOUT. This makes sure that STDERR is written to the same logfile.
and there are more examples.
While the above examples use ssh key-pairs for authentication your script uses password.
So the above examples can be used for the OH cron part. Just adapt it to continue to use password instead of keys.
the log message says an update about item state was sent to subscribed iOS device. typically an iOS device subscribes to all changes
you have several lines for the same item which typically means that there are several iOS devices paired with openHAB (according to log files > 7 device).
do you have more that many iOS devices with home app connected to openHAB?
if you have less than 7 device then one device is subscribed several times. that could lead to the issue with non-responsive items in home app.
do you see something like “Added subscription to …” in the log?
do you see them only after a restart or later?
could it be that your wifi connection is sometimes unstable and devices get disconnected?
maybe too many subscription is result of often binding restarts.
can you restart openhab and pay attention how many “Publishing change for” you get for the same number. it must 1 or 2 depending on number of connected devices.
do you have this issue since beginning or only after an upgrade / config change or new homekit device?
this is strange. without logs it will be difficult to troubleshoot. it could be anything - starting from wrong configuration, bug in the binding and to out of memory issues.
not sure how to fix logging issue. only the standard things
check disk space to ensure the disk/sd card is not full
check access rights to /var/log/openhab2/ and /var/log/openhab2/openhab.log. if unsure allow all the full access to them, e.g. chmod o+rw /var/log/openhab2/openhab.log