Device XXX generates excessive hub load - how do I reset the count?

I'm using the iota watt driver found elsewhere on this site.
The device has been out of Wifi range for a couple of months on and off, and it seems that the Habitat is counting the 10 second timeout for the HTTP access as hub load.

Now the device is back on the network, I'd like to get it back working in Habitat, but since the historical hub load is over 90%, it's not letting the driver even parse the reply, httpget is just throwing this exception. com.hubitat.app.exception.LimitExceededException


Iotawatt	622,421,011	92.7	54.364

I'm going to try to rewrite the driver to use an async http get to avoid this, but is there anyway to start afresh with this load count.

Code snippet is

    def params = [
        uri: "http://${deviceIP}/status?inputs=yes&outputs=yes",
        contentType: "application/json",
        requestContentType: "application/json",
        timeout: 10
    ]
    
    if (deviceIP) {
        try{
            log.debug "Sending to IoTaWatt = ${params}"

            httpGet(params){response ->

That would be correct behavior as CPU load is the number of processes which are being executed by CPU or waiting to be executed by CPU. As to how to reset the number might try rebooting the hub.

Just an FYI - @rlithgow1 reported this issue to me in the main IoTaWatt thread. I have spent a few hours tonight rearchitecting the IoTaWatt driver to use an asynch http call versus a synchronous call. I should have something for users to try tomorrow if my testing goes well tonight.

1 Like

Awesome. I missed the other thread completely.
When I got the iotawatt back on the net for a short while (rainy weather reducing RF reflections giving a better connection I guess), I saw the RSSI was way too low, so I'll be rearranging my APs.

1/08/23 15:31:36 WiFi connected. SSID=16103, IP=192.168.2.151, channel=11, RSSI -87db

1 Like

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