Skip to content
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

Thermostat hc1 with Homeassistant: changing values (Operation, Target Temperature) doesn't work #110

Closed
NFis opened this issue Sep 14, 2021 · 8 comments
Labels
bug Something isn't working

Comments

@NFis
Copy link

NFis commented Sep 14, 2021

I just changed to EMS32 (thanks!), Sw v3.2.1, using Homeassistant (with mqq discovery) as a frontend to change values in Thermostat hc1.
My Config:
(1) Boiler: Topline/GB162 (DeviceID:0x08, ProductID:115, Version:05.05)
(2) Controller: BC10/RFM20 (DeviceID:0x09, ProductID:68, Version:02.03)
(3) Thermostat: RC35 (DeviceID:0x10, ProductID:86, Version:01.16) ** master device **
(4) Thermostat: RC20RF (DeviceID:0x18, ProductID:93, Version:02.00)
Homassistant 2021.9.4
Before changing to v3 I deleted all mqtt topics in my broker and deleted all EMS-devices in HA.

Thermostat hc1 is autodected bei HA and added as climate.thermostat_hc1. I can see the correct values for actual temp, mode, target temp. But when I change i. e. the mode or the target temperature in HA it will not work.
In mqtt Explorer I see a topic ems-esp/thermostat_hc1 with payload corresponding to the selction in HA (auto, heat, off, temperature, one of those).

Changing mode, the log shows:
WARNING: [thermostat] Set mode: Heating Circuit 1 not found or activated
ERROR: [mqtt] MQTT error: invalid payload heat for this topic thermostat_hc1

Changing target temperature, the log shows:
WARNING: [thermostat] Set temperature: Heating Circuit 1 not found or activated for device ID 0x18

It looks like the values cannot be adressed to my devices. How can I fix that? In v2 everything worked fine.

@NFis NFis added the question Question about something label Sep 14, 2021
@proddy
Copy link
Contributor

proddy commented Sep 14, 2021

horray! Welcome to V3.

At first glance, it looks like when setting the temperature it's sending the command to the RC20RF (ID 0x18) and not the RC35 thermostat. Which is odd since the RC35 is defined as the "Master Device" in EMS-ESP. Let's fix that first and see what else is not working.

@NFis
Copy link
Author

NFis commented Sep 14, 2021

ok, looking at RC20RF is a good hint. I made some tests:
I disconnected the RC20RF from the bus, restarted EMS-ESP gateway (RC20RF is not in the list of EMS devices), and now Thermostat hc1 is working! But current temperature remains at the last value received from RC20RF.
Then I reconnected the RC20RF to the bus (EMS-ESP detects it later on), Thermostat hc1 is still working, current temperatur is valid and comes from the RC20RF.

@MichaelDvP
Copy link
Contributor

I think it's only these lines in v2 missing in v3. Then the subscription of thermostat_ha_cmd is overwritten by second thermostat.

@proddy
Copy link
Contributor

proddy commented Sep 18, 2021

I've added the lines. @NFis can you test with the latest dev build? https://github.com/emsesp/EMS-ESP32/releases/tag/latest

@proddy proddy added bug Something isn't working and removed question Question about something labels Sep 18, 2021
@NFis
Copy link
Author

NFis commented Sep 18, 2021 via email

@NFis
Copy link
Author

NFis commented Sep 19, 2021

I have just tried version v3.2.2b5 / 28bf7c3 (after deleting all mqtt topics in my broker and all ems devices in homeassistant) and it works perfectly. Thank you very much!

@proddy
Copy link
Contributor

proddy commented Sep 19, 2021

great, all thanks to Michael. Can I close this issue?

@NFis
Copy link
Author

NFis commented Sep 20, 2021

Yes, the issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants