-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLIMATE entity not being configured on Home Assistant discovery #315
Comments
The HA climate entity will only be created when there is a valid current temperature, setpoint temperature and mode. These are the HVAC requirements within HA. Can you use MQTTExplorer and post here the values of the and of course your settings |
see also #299 |
Settings as in http://ems-esp.local/api/system/settings (and mentioned in https://emsesp.github.io/docs/#/Support?id=support. I wanted to see if you had ha enabled and the prefix matches, but from the screenshot above it looks ok. It's strange the climate is missing. I can't reproduce or find anything in the code that would cause it. You could turn log level to ADD which will show you all the MQTT publishes and ctrl-F search for 'climate'. Or even easier if you have a syslog service running. |
Not sure how set log level to ADD but log level ALL for a few minutes produced the following. esp/boiler_data No mention of climate ems-esp:$ log ADD { { |
I think the best way forward is if I create a special debug version for you with some extra trace information to help pinpoint why it's failing |
Sure, OK. Let me know when it's ready. |
@proddy Just loaded v3.4.0b0 and Climate entity HA configuration has returned. 😁 |
wonderful! To be honest, I have no idea why. I refactored some of the code but this is still a mystery why it didn't work. If you had multiple thermostats or heating circuits then I could probably think of a reason or two, but you only had hc1 |
Bug description
ems-esp is only sending HA discovery config data for 6 thermostat SENSORS. It is not sending HA discovery config data for a CLIMATE entity. .
Steps to reproduce
Ran HA discovery.. Examined result.
Expected behavior
A CLIMATE entity discovery config should be published.
Screenshots
![image](https://user-images.githubusercontent.com/71522772/150651829-5ae0dc96-a631-401c-8114-734b9501a794.png)
Device information
{
"System": {
"version": "3.4.0a16",
"uptime": "001+04:16:27.506",
"uptime (seconds)": 101787,
"freemem": 120,
"reset reason": "Software reset CPU / Software reset CPU",
"Temperature sensors": 0
},
"Status": {
"bus status": "connected",
"bus protocol": "HT3",
"telegrams received": 47863,
"read requests sent": 5157,
"write requests sent": 47,
"incomplete telegrams": 3,
"tx fails": 1,
"rx line quality": 100,
"tx line quality": 100,
"MQTT": "connected",
"MQTT publishes": 35557,
"MQTT publish fails": 0,
"Temperature sensors": 0,
"Temperature sensor reads": 0,
"Temperature sensor fails": 0,
"Analog sensors": 0,
"API calls": 3,
"API fails": 0
},
"Devices": [
{
"type": "Boiler",
"name": "Condens 2500/Logamax/Logomatic/Cerapur Top/Greenstar/Generic HT3 (DeviceID:0x08, ProductID:95, Version:12.10)",
"handlers": "0x10 0x11 0xC2 0x14 0x15 0x1C 0x18 0x19 0x1A 0x35 0x16 0x33 0x34 0x26 0x2A"
},
{
"type": "Thermostat",
"name": "Worcester CRF200S (DeviceID:0x18, ProductID:216, Version:01.03)",
"handlers": "0xA3 0x06 0xA2 0x12 0x2A5 0x2A6 0x2A7 0x2A8"
},
{
"type": "Controller",
"name": "HT3 (DeviceID:0x09, ProductID:95, Version:12.10)"
}
]
}
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: