I turned my daily service restart rule back on:
Ok thanks,
I am still trying to figure out how to install the rule. I was able to get the driver installed.
However, when I try to configure the rule and select Actuator I don't see Home Kit Service Restart listed.
I have tried everything.
But disabled gives the best results.. lol
Did you actually install the device from GitHub? It’s a driver and you can call it whatever you like. Once it’s installed, then RM can use it.
Yes, I installed the driver code from GitHub. It looks like it should be working based off the screenshot but its still not showing up in the menu,
That is Step 1.
Step 2 would be to use that Driver to create a Device. Only once a device is created, will it show up so Rule Machine can use it.
2 Likes
Ok thanks! So I have to create a virtual switch to the command that rule to run? After that Driver Code is installed.
I tried doing that and I am still not able to select device in the variables list.
I tried running the device and it doesnt seem to be working. I am not sure where I went wrong.. I am guessing I am doing something wrong when setting up the virtual device.
You need to add an action that invokes the device you added.
Someone posted the steps on how to setup an actuator action.
I had the same issue as everyone here. I was able to get it working again using the device driver and the rule.
The only thing I don't understand is scheduling. Should I use device preferences to define frequency or set it via rule trigger?
Also, not sure why the firmware update did not fix the issue for me. Maybe the firmware update can't resolve an existing disconnect issue, but it prevents it from happening again once the connection is reestablished.
For what it's worth, I'm using a C8 running v2.3.9.166, connected via ethernet
I use RM to restart the service everyday while we all still asleep (4:30am):
When you say "restart service" you're referring to what exactly? Triggering the action associated with the rule?
I can't make sense of the Restart Interval in the device prefs. I'm trying to avoid invoking a process that creates child processes, seems like a memory leak waiting to happen. I guess I just don't know enough about how the actuator logic works.
My rule tells the driver to restart the HomeKit service at 4:30am.
The actuator is just enabling the driver functions to be triggered outside of itself by eg RM.
That’s it. I just like to use RM to schedule tasks so I can go to a single location to find them.
I had a temperature device I was using that would return negative values. That was causing the homekit connection to go unresponsive. As soon as I removed that device, no more issues with "no response" EVERY SINGLE DAY. lol. Running good again for two months now.
I have a C7 in the house and a C8 hub in the barn. Only the house was going unresponsive, which the temperature device was connected too.
I would suggest as a test to remove the tempurature reporting devices and see if that solves your issues. It was hard to catch the negative value, but it was crashing it.
1 Like
Negative temperature values are not the problem as I have freezer temperature readings below zero.
Maybe something way outside the normal temperature range but not -4 or so.
1 Like
Completely agree. That shouldn't throw it off and should be within reason.
My application was a esp8266 with a Ds18b20 sensor for my pool.
I just started watching the readings coming back to HE, then noticed the negative readings coming in. It would only happen for a blip (maybe a blop, lol) It seemed like the device would drop, send a default negative value, then HomeKit would go unresponsive for all eight devices on that hub.
Not sure if it was the negative value or a default "out of range" error. I would assume there are a lot of users using HE to monitor freezers and fridges.
I have a lot of buttons that report temperature to Homekit, but never had an issue with those devices. They are all positive values though.
