-
-
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
Summer mode on heat Circuit #108
Comments
Looks like sumermode and summertemp is set to zero and is not writable. Do you have a outdoor sensor attached? You do not have a summermode if in roomtemperature-controlled state. |
I can control the summer mode on the heat pump. I can change between, "summer, vinter and auto" and I also uses this to turn off the circuit. And yes i have a outdoor sensor attached! |
Ok, if the heatpump manages the summermode, this is a unknown setting, and the thermostat does not responde. |
Ok, here you have the requested files. |
Yes, it's from thermostat these telegrams:
If For settings and info i've meant the two nice buttons if you go to |
you are fast :-) And I think you are right about circuit 1 & 3 I tried to change the summer temp to 19 from 17 and back to 19 Here you have the result of the read command: |
Ok, the summertemp is in the same telegram in offset 1 The read command should be You have thermostat product-ID 158, that's sad because others have the same product-ID but summermode working, we have to check for the extra telegram and take the right value. Hopefully the 0x471 is empty if 0x2AF have valid summermode. @proddy I think best way is to set the new telegram to fetch and check the @sfbia2m There are some unknown telegrams from heatpump, not changing while logging:
The |
Ok, I have looked in the control to find a temperature around that and now the telegram returns 33.5 "Rx: 88 00 FF 00 03 A0 0E 10 01 4F A5" but I can't find any value with that in the control. I will try to follow this telegrams to see if I can find anything to pare it with! |
Thanks for the complete telegram, it's a bit longer, but i have no idea what the bytes 2-7 represents. We stay with summermode/summertemp in bytes 0, 1. It would be fine it someone with thermostat productID:158 and working summermode can also check that this change does not affect him. |
Super Thanks a lot! It is working perfectly :-) I will try to follow some of the other telegrams you mentioned to see if it gives any sens compared to the control. |
@MichaelDvP But I have to check if values for summertemp are really changed in RC310. Since I am not at home this has to wait until Sunday. BTW: the thermostat is sending every 60 secs 3 telegrams to the km200 gateway with type 473 (no data) 10 48 FF 05 03 73 00 |
@tp1de Thank you for testing. If 0x471, ff are empty the code works as before with telegrams 0x2AF, ff. The 0x473 to km200 is strange, i think you do not have hc3? Is it the same for 0x471, 0x472? Emsesp will read only one time for the existing hc (you have only hc1 and hc2 right?), and after emty answer not again. @proddy Please merge. |
0x471 and 0x472 are the same empty telegrams.... and yes I have only hc1 and hc2 |
this should be fixed now. |
Hi
I have a Bosch Compress7000 AW heat pump with 3 heat circuit, and non of them is showing the right state of Set summer mode or summer mode. If I try to change the value from the webinterface nothing is happing. I have checked the log and I can see something is happening.
000+00:45:27.194 INFO 5539: [command] Calling thermostat command 'hc3/summersetmode', value winter, id is default
000+00:45:27.194 INFO 5540: [thermostat] Setting summer mode to winter for heating circuit 3
000+00:45:27.276 DEBUG 5541: [telegram] Sending write Tx [#170], telegram: 8B 10 FF 07 01 B1 02
000+00:45:27.296 TRACE 5542: [telegram] Rx: 8B 10 FF 07 01 B1 02 F9
000+00:45:27.300 DEBUG 5543: [emsesp] Last Tx write successful
000+00:45:27.300 DEBUG 5544: [telegram] Sending post validate read, type ID 0x2B1 to dest 0x10
000+00:45:27.600 DEBUG 5545: [telegram] Sending read Tx [#171], telegram: 8B 90 FF 00 20 01 B1
000+00:45:27.621 TRACE 5546: [telegram] Rx: 8B 90 FF 00 20 01 B1 06
000+00:45:27.661 DEBUG 5547: [emsesp] Last Tx read successful
000+00:45:27.661 TRACE 5548: [telegram] Rx: 90 0B FF 00 01 B1 00 28 00 00 3C 24 00 00 1E 1E 00 E4
The text was updated successfully, but these errors were encountered: