Hi I am having a problem with my C7 shutting down that I seem to have narrowed down to a scheduled rule which sends a HTTP post to my personal server (local to my network).
I use the http post rule as a heatbeart that runs every 15 mins which sends a simple JSON containing a simple text message identifying the hubs IP address.
When the rule is enabled the hub will partially freeze usually within 24 hours and the logs show that the hub mesh to my other hub is down (network related) and I have to reset the hub to get it working again.
If I disable the rule then the hub seems to work without any issues......
Is sending a periodic http post every 15 mins really too much for the hub too handle?
I have read in some other posts that there is possibly more detailed logs that support have access too that may help point me in the right direction. Any idea if this is true?
You are asking for a lot of data every 15 minutes. If the requested data is not available, this might freeze your hub.
You might find it less problematic to report exceptions only. For example, rather than reporting the pond pump wattage every 15 minutes, only issue a report if the power is above or below a specific range.
@rwclements228 sorry i don't think i have explained myself very well. The power reporting shown in the log is not being transmitted that's just some of my devices reporting internally to the hub. However I have changed the power change level on some of the devices to reduce some of the overhead.
The HTTP post that seems to be causing an issue runs every 15 mins contains the following json body {id:hub20} which is processed by my server so I know the hubitat is functioning. Surely this shouldn't be enough to cause an issue?
I have to think there is some other problem. For a long time I sent HTTP strings to activate cameras and there could be quite a few of those (triggered by motion sensors) in a short period of time. Never had a problem with that.
1 Like
