FYI - After installing the Homekit Controller after this weeks 2.4.2.119 update, 2 Sensi thermostats were added without any issues. there is just one small issue ..
when using the set cooling point command button ....
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: HomeKitThermostat.setCoolingSetpoint() is applicable for argument types: (java.math.BigDecimal) values: [80] (method setCoolingSetpoint) , the infamous BigDecimal error when entering a cooling temperature value. the other command buttons (auto etc) seem to be working OK. i tried entering the value as 80 and 80.0.. both gave the error.
There is a fix in the HomeKit Thermostat driver that should be in the next release (and are currently in beta) that looks like it should address this problem.
Is this a thing? 
thanks for the update, BigDecimal is a thing but not on the hubitat end... Since I use webCore and I write many of my own drivers, the initial test phase seems to always bring out a few BigDecimal errors especially when using driver commands etc in webCore. easy to remedy but always can be a gotcha.
another minor issue has surfaced, the set thermostat mode command button issues the following error..
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: HomeKitThermostat.setThermostatMode() is applicable for argument types: (java.lang.String) values: [off] (method setThermostatMode).. this occurs on all of the available selections. the individual commands , auto, cool, off all work well. this was found when a webcore piston turns off the AC if the door or window was open longer than 2 minutes. i used the set thermostat mode to functionality and the error resulted.
Should be fixed in 2.4.2.125, released today.
1 Like
wonderful, it it now setting to auto using the set thermostat mode. but another issue arises, 2025-06-30 01:34:22.717 PM
debug
modes is auto, temperature is 80.0
dev:7722025-06-30 01:33:56.902 PM
debug
modes is auto, temperature is 80.0
dev:7722025-06-30 01:33:48.602 PM
warn
debug logging is: false
the debug is not respecting the set to false, so maybe a log.debug vs logDebug and more problematic is it wants to update often. the timestamps are at the 22 seconds and 56 seconds after every minute... not sure if this is a function when the cooling is on etc, here in Arizona , it is 106 currently and even with the AC set to 80, it runs ,
1 Like
Looks like a missed debug statement. Will fix in the next build.
1 Like
how often are the device update log settings? is there a reason for them to be every 30 seconds on average?
Those events are device push updates, not log setting updates.
1 Like
the polling of some kind is the root cause.. it is evident in the debug log updating every 30 seconds on average (34 sec and 26 sec) every minute. it is a WiFi device. so does this suggest that the app or the device is the root cause? that was the basic question at hand. the chatty nature of 30 second updates and having no ability to set this interval (whether or not it is a device issue or an app issue) is a no go for me, I have disabled the devices for now. the original log i sent showed a log update, mode is auto, temp is 80.0. every 30 seconds on average(this is not the actual temperature, it is a setting). these are static values! Yet they get polled every 30 seconds on average.
1 Like
