Thermostat icon Stays blue indicating it "On" but its?

[chuck1]

One of my Dashboards for Thermostats has a thermostat icon that has a tendency to stay blue indicating the Unit is running even though its not running. See screensnip showing i have the unit in off setting but icon is stuck in blue. This thermostat is a centralite pearl thermostat that still works very good for me.. just this little hiccup so far... It seems like this clears itself up after a day or so. It's not a deal killer or anything i am just looking for input on where to look into fixing this. Any help would be greatly appreciated. Thanks

[arnb]

I reported the same issue a few days ago with virtual thermostats.

Dashboard Thermostat Anomaly

While controlling my home's mini-split system with my Dew Point app, the dashboard virtual thermostat devices sometimes show odd results, such as this case where the mode is Off, but the device appears to be cooling. (The physical mini-splits are off) I've also had it where Mode=cool, with the runningMode= idle. My Dew Point app changes the device mode, but does not adjust the runningMode. In this case it changed from cool to off. BTW DewPoint AC control rocks! [image] tagging @bravenel @…

[joelspc]

Have a look at this thread about a custom driver from Denise (I know it's about adding the "Hold" function). When I was using the Pearl's (since replaced by Zen's) at my home I had the same issue. Her driver fixed that issue for me. You will need to user her code to create a new "User" driver in the Developers section of the HE interface. Hope this works for you. -Joel

Centralite Pearl Thermostat

This is a collection of several thermostat drivers from ST, I wanted to be able to support the Hold button on the thermostat. The Generic ZigBee Thermostat driver in Hubitat may eventually support everything that this driver does. Fixes/Improvements welcome! /* * Centralite Pearl Thermostat */ metadata { definition (name: "CentraLite Pearl Thermostat", namespace: "hubitat", author: "dagrider") { capability "Actuator" capability "Temperature Measurement" capability…

[arnb]

@chuck1

It seems like this clears itself up after a day or so. It's not a deal killer or anything i am just looking for input on where to look into fixing this.

The following code is from my personal Dew Point app that runs a second after the thermostats are changed by the app.

//	Purpose fix weird anomalies likely from Virtual Thermostat mistakenly resetting or failing to set thermostatOperatingState
void anomalyKiller()
	{
	if (settings.logDebugs) log.debug 'anomalyKiller entered'
	controlStats.each
		{
		if (it.currentThermostatMode == 'off' && it.currentThermostatOperatingState == 'cooling')
			{
			if (settings.logDebugs) log.debug "anomaly dry with cooling found for ${it.name}"
			it.setThermostatOperatingState('idle') 			//if this does not work issue the off()
//			it.off()
			}
		else
		if (it.currentThermostatMode == 'cool' && it.currentThermostatOperatingState == 'idle' &&
			it.currentCoolingSetpoint < (it.currentTemperature-it.currentHysteresis))
			{
			if (settings.logDebugs) log.debug "anomaly cool with idle found for ${it.name} Cool Pt: ${it.currentCoolingSetpoint} Temperatue: ${it.currentTemperature} Hysteresis: ${it.currentHysteresis}"
			it.setThermostatOperatingState('cooling') 		//if this does not work issue the cool()
//			it.cool()
			}
		}
	}

[Sebastien]

Could it be blue because it says it is cooling (even though it is set to off…)?

[arnb]

@Sebastien

Could it be blue because it says it is cooling

Yes, and red when thermostatOperatingState = heating