Closed jhselby closed 2 years ago
In my case, this happens if my heat setting is lower than 10 degrees, as the cooling lowest setting is 10. I use my thermostat for heat only, so this can be noted as a bug in this sense.
I’m confused — Heat set to 10 degrees? I’m a dumb America who uses freedom units, but 10 degrees Celsius seems too cold for a heat swerving.
— jhs
On Nov 26, 2021, at 2:50 PM, thabandit007 @.***> wrote:
In my case, this happens if my heat setting is lower than 10 degrees, as the cooling lowest setting is 10. I use my thermostat for heat only, so this can be noted as a bug in this sense.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
What is even odder is that I have the thermostat tell Homebridge what the limits are and override homebridge
If you can run the plugin with the debug option set to true, and capture the thermostat details, we should be able to figure this out.
My debug has been set to true. How do I send you my logs? Running homebridge on MacOS, and I don't know where the logs are.
On Mon, Nov 29, 2021 at 10:30 AM Northern Man @.***> wrote:
What is even odder is that I have the thermostat tell Homebridge what the limits are and override homebridge
If you can run the plugin with the debug option set to true, and capture the thermostat details, we should be able to figure this out.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-tcc/issues/106#issuecomment-981745398, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUN2LDS6BQLPPHOVJQAI3ETUOOMCRANCNFSM46O3YA7Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
-- Joe Selby @.***
Just attach the logs to this issue, just remove any login or personal information. Just the portion with the thermostat details, it should be a JSON type entry.
The log location is determined by how your starting homebridge. If your starting from the command line they are in the console.
I’m confused — Heat set to 10 degrees? I’m a dumb America who uses freedom units, but 10 degrees Celsius seems too cold for a heat swerving. — jhs … On Nov 26, 2021, at 2:50 PM, thabandit007 @.***> wrote: In my case, this happens if my heat setting is lower than 10 degrees, as the cooling lowest setting is 10. I use my thermostat for heat only, so this can be noted as a bug in this sense. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Yea sorry, should have mentioed that I am using this on a garage heater, it is set on scheudle from 12 degres in the morning to 8 at night, therefore I get the warning as you noted when the temperate (heat setting) is set to below 10 (cooling threshold).
What is even odder is that I have the thermostat tell Homebridge what the limits are and override homebridge
If you can run the plugin with the debug option set to true, and capture the thermostat details, we should be able to figure this out.
In my case the device.TargetTemperatureCoolMinValue is always 10, which is the lowest cool setting as per the thermostat, however I have cooling disabled, I am getting warnings still due to this value being higher than my target (heat) temp.
[Thermostat] Current Heating Cooling State 0 Target Heating Cooling State 0 Current Temperature 7° Target Temperature 8° Temperature Display Units 0 Cooling Threshold Temperature 10° Heating Threshold Temperature 8° Manufacturer TCC Model Manhattan Name GARAGE log.txt
Unfortunately that didn't have enough information to troubleshoot it further. So I added additional debug logging to collect more details on the Cooling Threshold setting. If you update to the latest version and run it again with debug enabled it should log something like this shortly after startup. This logs the value returned by the thermostat and the setting inside Homebridge.
tcc TccAccessory() {
ThermostatID: XXXXXX,
Name: 'XXXXX',
Model: 'Communicating Focus PRO Retail',
OutsideTemperature: 128,
CurrentTemperature: 17.5,
TargetTemperature: 10,
HeatingThresholdTemperature: 10,
CoolingThresholdTemperature: 28,
CurrentHeatingCoolingState: 0,
TargetHeatingCoolingState: 1,
TargetHeatingCoolingStateValidValues: [ 0, 1, 2 ],
TargetTemperatureHeatMinValue: 4.5,
TargetTemperatureHeatMaxValue: 32,
TargetTemperatureCoolMinValue: 10,
TargetTemperatureCoolMaxValue: 37,
OutsideHumidity: 128,
InsideHumidity: 128,
device: {
ThermostatID: XXXXXX,
MacID: 'XXXXX',
DomainID: 44449,
Instance: 0,
DeviceName: 'THERMOSTAT',
UserDefinedDeviceName: 'XXXXX',
Upgrading: false,
ThermostatsAlerts: { ThermostatsAlert: [Object] },
UI: {
Created: '2021-11-30T07:08:18',
ThermostatLocked: false,
OutdoorTemp: 128,
DispTemperature: 17.5,
HeatSetpoint: 10,
CoolSetpoint: 28,
DisplayedUnits: 'C',
StatusHeat: 2,
StatusCool: 2,
HoldUntilCapable: true,
ScheduleCapable: true,
VacationHold: 0,
DualSetpointStatus: false,
HeatNextPeriod: 30,
CoolNextPeriod: 30,
HeatLowerSetptLimit: 4.5,
HeatUpperSetptLimit: 32,
CoolLowerSetptLimit: 10,
CoolUpperSetptLimit: 37,
SchedHeatSp: 17,
SchedCoolSp: 28,
SystemSwitchPosition: 1,
CanSetSwitchAuto: false,
CanSetSwitchCool: true,
CanSetSwitchOff: true,
CanSetSwitchHeat: true,
CanSetSwitchEmergencyHeat: false,
CanSetSwitchSouthernAway: false,
Deadband: 0,
OutdoorHumidity: 128,
IndoorHumidity: 128,
Commercial: false,
SystemSwitchChangeSource: [Object],
HeatSetpointChangeSource: [Object],
CoolSetpointChangeSource: [Object]
},
Fan: {
CanControl: false,
Position: 'Auto',
CanSetAuto: true,
CanSetCirculate: false,
CanFollowSchedule: false,
CanSetOn: true,
IsFanRunning: false
},
Humidification: {
CanControlHumidification: false,
CanControlDehumidification: false,
HumidificationSetPoint: 0,
HumidificationUpperLimit: 0,
HumidificationLowerLimit: 0,
HumidificationMode: 'Off',
DehumidificationSetPoint: 0,
DehumidificationUpperLimit: 0,
DehumidificationLowerLimit: 0,
DehumidificationMode: 'Off',
Deadband: 255
},
EquipmentStatus: 'Off',
CanControlSchedule: false,
WillSupportSchedule: false,
ModelTypeID: 9,
ModelTypeName: 'Communicating Focus PRO Retail'
}
} +0ms
[Thermostat] Existing TCC accessory (deviceID=6918822) Wasaga
tcc Heating Threshold {
format: 'float',
perms: [ 'ev', 'pr', 'pw' ],
unit: 'celsius',
minValue: 4.5,
maxValue: 32,
minStep: 0.1
} +1ms
tcc Cooling Threshold {
format: 'float',
perms: [ 'ev', 'pr', 'pw' ],
unit: 'celsius',
minValue: 10,
maxValue: 37,
minStep: 0.1
} +0ms
See attached. new 1.txt
Thanks for that bit, I made some minor tweaks that should resolve that issue. I couldn't recreate the issue, so I'm not sure if this is resolved.
Seems to be fixed, I have not seen any warnings since the update. Thank you for that.
Glad to hear hear
Tks
[6/10/2021, 12:21:59 PM] [homebridge-tcc] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 4.4 exceeded minimum of 10. See https://git.io/JtMGR for more info.