Ems-esp: Control both HC1 & HC2 at the same time in Home Assistant (MQTT)
I'm pretty new on this fora and starting to explore the possibilities of the EMS-ESP.
On top, I'm a Home Assistant (HA) user in order to control my home domotica.
I was very enthusiastic to read on the fora that it is possible to control the 2 heating circuits.
I'm using HC1 for radiators in the bedrooms & bathroom (level 1), HC2 as floor heating (level 0).
Is there a possibility to control both Heating Circuits at the same time with MQTT?
Meaning, having two thermostat control systems in the Home Assistant GUI.
Now you need to switch all the time between the Heating Circuits in order to read out the temperature and the heating settings.
Frederik-V
All 108 comments
Hi @Frederik-V, yes it's possible to extend the MQTT to support multiple Heating Circuits. Easiest is to have two sets of MQTT messages so you can add two climate components to HA.
It would need some additional code changes to fetch the thermostat values from the multiple HCs and store them. The difficulty is always testing these. Are you comfortable making code changes yourself to EMS-ESP ?
proddy
on 24 Jul 2019
Hi @proddy, unfortunately I do not have any experience to make code changes into the EMS-ESP.
On the other hand, support with testing of the changes and making some example's in HA, should be not an issue!
Just to complete my question, I'm using a Buderus RC35 thermostat.
Frederik-V
on 25 Jul 2019
Hi proddy,
I have a Buderus with 2 heat circuits and 2 separate thermostats an RC35 as main device and RMF20 for the first floor.
With version 1.8.x the gateway is randomly reading the of one of the thermostats. It doesn't take the Heat Circuit setting in account from the settings
As you can see in the screenshot the temperature is switching between the 2 locations
Hope you able to enhance the software that the HC setting is linked to a dedicated thermostat and will be able to read out both independently
Thanks in advance
lmdecroos
on 7 Sep 2019
This a bug, I'll add some extra functionality to read multiple heating circuits to the dev build
proddy
on 7 Sep 2019
@lmdecroos I'm adding supporting for multiple Heating Circuits. Adding additional thermostats will be more work. Can you answer these questions
- does EMS-ESP detect both your RC35 thermostats?
- do each of the thermostats report value for both the 2 heating circuits?
- can you do a 'log t' and send me some examples of telegrams 0x3E (HC1) and 0x48 (HC2) so I can build some test data. I don't have an RC35 so it'll be a lot of trial and error. be prepared to do a lot of testing!
proddy
on 7 Sep 2019
Hi proddy,
I have one RC35 and one RFM20 ( RC20 wireless)
The RC35 is used for programming the boiler settings and to control HC1 for heating on the ground floor
The RC20 is used to control HC2 for our heating on the fist floor.
They are both working independently .
When asking for "info” the gateway stays that i have an RC35
Thermostat stats:
Thermostat: RC35 (ProductID:86 Version:21.08)
When requesting an autodetect
Started scan on EMS bus for known devices
Boiler found: Nefit Topline Compact/Buderus GB162 (DeviceID:0x08 ProductID:115 Version:05.05)
Device found: BC10/RFM20 Receiver (DeviceID:0x09 ProductID:68 Version:02.03)
Device found: WM10 Switch Module (DeviceID:0x11 ProductID:71 Version:02.00)
The gateway recognise also the switch for the pumps to control both HC’s
I had a look at the telegram messages in the EMS gateway and the MQTT received by Domoticz and it seems that the EMS gateway receives the temperature details from both heat circuit and send them both to the MQTT host.
The EMS software doesn’t filter the message based on the selected HC in the EMS configuration. Therefore the actual temperature in the MQTT message is switching between both HC’s ( thermostats)
The MQTT messages includes the correct HC (thermostat_hc) as set in the EMS gateway, but send always as current temperature the temperature from last received telegram message.
I would assume that you have to build in a filter based on the selected HC to only send the temperature from the selected HC
Logs with HC1 selected:
System Logging set to Thermostat only
(03:49:30.725) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 12 07 14 2B 05 01 (CRC=A6) #data=8
(03:49:30.995) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 00 00 C5 00 00 00 00 00 00 00 00 11 05 04 (CRC=AD) #data=16
Publishing thermostat data via MQTT
(03:49:32.245) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 10 00 00 B4 00 00 00 00 00 00 00 00 11 05 04 (CRC=C8) #data=16
Publishing thermostat data via MQTT
(03:49:32.542) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 6E 11 00 00 C5 00 CB 00 CB 7D 00 7D 00 (CRC=D8) #data=13
(03:49:48.462) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 00 01 (CRC=0F) #data=3
(03:49:57.581) Thermostat -> Boiler, type 0x35, telegram: 10 08 35 00 11 01 (CRC=20) #data=2
(03:49:57.708) Thermostat -> 0x11, type 0x9D, telegram: 10 11 9D 00 00 (CRC=D7) #data=1
Publishing boiler data via MQTT
Publishing hot water and heating states via MQTT
Publishing thermostat data via MQTT
Requesting scheduled EMS device data
(03:50:01.243) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 00 00 C5 00 00 00 00 00 00 00 00 11 05 04 (CRC=C5) #data=16
Publishing thermostat data via MQTT
(03:50:01.556) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 1E 26 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 02 (CRC=43) #data=27
Publishing thermostat data via MQTT
(03:50:01.869) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 12 07 15 0E 05 01 (CRC=9D) #data=8
Publishing boiler data via MQTT
(03:50:06.364) Thermostat -> all, type 0xA2, telegram: 10 00 A2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=99) #data=14
(03:50:08.954) Thermostat -> Boiler, type 0x14, telegram: 10 88 14 00 03 (CRC=6E) #data=1
(03:50:08.967) Boiler -> Thermostat, type 0x14, telegram: 08 10 14 00 32 81 BA (CRC=30) #data=3
(03:50:17.710) Thermostat -> Boiler, type 0x1A, telegram: 10 08 1A 00 00 00 00 00 (CRC=91) #data=4
(03:50:31.225) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 12 07 15 2B 05 01 (CRC=AE) #data=8
(03:50:31.494) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 00 00 C5 00 00 00 00 00 00 00 00 11 05 04 (CRC=AD) #data=16
Publishing boiler data via MQTT
(03:50:32.744) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 10 00 00 B4 00 00 00 00 00 00 00 00 11 05 04 (CRC=C8) #data=16
Publishing thermostat data via MQTT
(03:50:33.039) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 6E 11 00 00 C5 00 CB 00 CB 7D 00 7D 00 (CRC=D8) #data=13
2019-09-07 18:22:11.643 (Buderus - System Pressure) Updating device from 1:'1' to have values 1:'1'.
2019-09-07 18:22:11.649 (Buderus) Current temp: 62.8
2019-09-07 18:22:11.649 (Buderus - Warmwater) Updating device from 1:'62.8' to have values 1:'62.8'.
2019-09-07 18:22:11.654 (Buderus) Current temp: 56.1
2019-09-07 18:22:11.654 (Buderus - Boiler) Updating device from 1:'56.1' to have values 1:'56.1'.
2019-09-07 18:22:11.659 (Buderus) Burner: off
2019-09-07 18:22:12.912 (Buderus) MQTT message: home/ems-esp/thermostat_data b'{"thermostat_hc":"1","thermostat_seltemp":0,"thermostat_currtemp":18,"thermostat_daytemp":19,"thermostat_nighttemp":15,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"night"}'
2019-09-07 18:22:12.912 (Buderus) Current temp: 18.0
2019-09-07 18:22:12.912 (Woonkamer) Updating device from 1:'19.7' to have values 1:'18.0'.
2019-09-07 18:22:12.918 (Buderus) Temp setting: 0
2019-09-07 18:22:12.918 (Buderus - Nefit) Updating device from 1:'0' to have values 1:'0'.
2019-09-07 18:22:19.335 (Buderus) Heartbeating...
2019-09-07 18:22:19.336 (Buderus) MqttClient::Ping
2019-09-07 18:22:29.305 (Buderus) Heartbeating...
2019-09-07 18:22:29.305 (Buderus) MqttClient::Ping
2019-09-07 18:22:39.322 (Buderus) Heartbeating...
2019-09-07 18:22:39.322 (Buderus) MqttClient::Ping
2019-09-07 18:22:42.178 (Buderus) MQTT message: home/ems-esp/boiler_data b'{"wWComfort":"Hot","wWSelTemp":58,"selFlowTemp":7,"selBurnPow":0,"curBurnPow":0,"pumpMod":0,"wWCurTmp":62.8,"wWCurFlow":0,"curFlowTemp":48.9,"retTemp":52.8,"sysPress":1,"boilTemp":56.1,"wWActivated":"on","burnGas":"off","heatPmp":"off","fanWork":"off","ignWork":"off","wWCirc":"off","wWHeat":"off","burnStarts":26051,"burnWorkMin":401798,"heatWorkMin":362810,"ServiceCode":"0H","ServiceCodeNumber":203}'
2019-09-07 18:22:42.178 (Buderus) System Pressure: 1
2019-09-07 18:22:42.179 (Buderus - System Pressure) Updating device from 1:'1' to have values 1:'1'.
2019-09-07 18:22:42.184 (Buderus) Current temp: 62.8
2019-09-07 18:22:42.184 (Buderus - Warmwater) Updating device from 1:'62.8' to have values 1:'62.8'.
2019-09-07 18:22:42.189 (Buderus) Current temp: 56.1
2019-09-07 18:22:42.189 (Buderus - Boiler) Updating device from 1:'56.1' to have values 1:'56.1'.
2019-09-07 18:22:42.194 (Buderus) Burner: off
2019-09-07 18:22:42.195 (Buderus) MQTT message: home/ems-esp/thermostat_data b'{"thermostat_hc":"1","thermostat_seltemp":0,"thermostat_currtemp":19.7,"thermostat_daytemp":19,"thermostat_nighttemp":15,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"night"}'
2019-09-07 18:22:42.195 (Buderus) Current temp: 19.7
2019-09-07 18:22:42.195 (Woonkamer) Updating device from 1:'18.0' to have values 1:'19.7'.
2019-09-07 18:22:42.200 (Buderus) Temp setting: 0
2019-09-07 18:22:42.200 (Buderus - Nefit) Updating device from 1:'0' to have values 1:'0'.
2019-09-07 18:22:45.312 (Buderus) MQTT message: home/ems-esp/boiler_data b'{"wWComfort":"Hot","wWSelTemp":58,"selFlowTemp":7,"selBurnPow":0,"curBurnPow":0,"pumpMod":0,"wWCurTmp":62.8,"wWCurFlow":0,"curFlowTemp":48.9,"retTemp":52.8,"sysPress":1,"boilTemp":55.9,"wWActivated":"on","burnGas":"off","heatPmp":"off","fanWork":"off","ignWork":"off","wWCirc":"off","wWHeat":"off","burnStarts":26051,"burnWorkMin":401798,"heatWorkMin":362810,"ServiceCode":"0H","ServiceCodeNumber":203}'
2019-09-07 18:22:45.312 (Buderus) System Pressure: 1
2019-09-07 18:22:45.312 (Buderus - System Pressure) Updating device from 1:'1' to have values 1:'1'.
2019-09-07 18:22:45.318 (Buderus) Current temp: 62.8
2019-09-07 18:22:45.318 (Buderus - Warmwater) Updating device from 1:'62.8' to have values 1:'62.8’.
logs with HC2 selected :
2019-09-07 18:43:20.681 (Buderus) MQTT message: home/ems-esp/thermostat_data b'{"thermostat_hc":"2","thermostat_seltemp":0,"thermostat_currtemp":19.7,"thermostat_daytemp":18,"thermostat_nighttemp":13.5,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"night"}'
2019-09-07 18:43:20.681 (Buderus) Current temp: 19.7
2019-09-07 18:43:20.681 (Woonkamer) Updating device from 1:'17.7' to have values 1:'19.7'.
2019-09-07 18:43:20.686 (Buderus) Temp setting: 0
2019-09-07 18:43:20.686 (Buderus - Nefit) Updating device from 1:'0' to have values 1:'0'.
2019-09-07 18:43:22.544 (Buderus) MQTT message: home/ems-esp/thermostat_data b'{"thermostat_hc":"2","thermostat_seltemp":0,"thermostat_currtemp":17.7,"thermostat_daytemp":18,"thermostat_nighttemp":13.5,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"night"}'
2019-09-07 18:43:22.545 (Buderus) Current temp: 17.7
2019-09-07 18:43:22.545 (Woonkamer) Updating device from 1:'19.7' to have values 1:'17.7'.
2019-09-07 18:43:22.550 (Buderus) Temp setting: 0
Please let me know if you need more or other logs
Hope this helps
Thanks in advance
On 7 Sep 2019, at 10:30, Paul notifications@github.com wrote:
@lmdecroos https://github.com/lmdecroos I'm adding supporting for multiple Heating Circuits. Adding additional thermostats will be more work. Can you answer these questions
does EMS-ESP detect both your RC35 thermostats?
do each of the thermostats report value for both the 2 heating circuits?
can you do a 'log t' and send me some examples of telegrams 0x3E (HC1) and 0x48 (HC2) so I can build some test data. I don't have an RC35 so it'll be a lot of trial and error. be prepared to do a lot of testing!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW445S4QJPUXCS75Q3DVLQINRBVA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6ETS6I#issuecomment-529086841, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW44ZJKHHCFUSAFTOS4P3QINRBVANCNFSM4IGOZDBQ.
lmdecroos
on 7 Sep 2019
I spent some time today to implement handling of multiple HCs independently. It's checked into the dev branch 1.9.1 so give it whirl. It's far from perfect and I still need to decide on the mqtt format for driving multiple heating circuits.
proddy
on 7 Sep 2019
I compiled the 1.9.1 dev branch and have unfortunately issues to get the gateway stable (similar as with the release version)
The connection to be EMS bus is unstable and crashes ( the led is flashing)
When using the 1.9.x version, every time I’m doing a telnet to the gateway the gateway start scanning the EMS bus
On 7 Sep 2019, at 20:42, Paul notifications@github.com wrote:
I spent some time today to implement handling of multiple HCs independently. It's checked into the dev branch 1.9.1 so give it whirl. It's far from perfect and I still need to decide on the mqtt format for driving multiple heating circuits.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW446RC25KDQQ6QA4FFGLQIPYYPA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6E7QGY#issuecomment-529135643, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW447IVH4DOTYCWWTBN73QIPYYPANCNFSM4IGOZDBQ.
lmdecroos
on 9 Sep 2019
@lmdecroos When EMS-ESP starts it will auto-detect all known devices, this only happens once and should take a few seconds. If the Tx is not working this will fail, but shouldn't repeat. You can try different tx_modes (1 is default, 2 is EMS+ and 3 is Junkers). I've seen others report back that 1.9 keeps crashing but I cannot reproduce and I have no example logs, stacks etc to help pinpoint the issue. Is it really crashing (i.e. resetting)? See https://github.com/proddy/EMS-ESP/wiki/Troubleshooting
proddy
on 10 Sep 2019
when using the default EMS protocol, the gateway crashes shortly and resets the serial value to on. the web UI seems to know that i have a RC35, but the console scans every time the EMS bus ( when starting a telnet session) and then crashes even before i’m try to change the log level
when using the EMS+ protocol, then the gateway is stable but reads only the boiler values, there is no information or update from the thermostat. in the web UI there is only info about the boiler. there is also no information about the thermostat in the temp & verbose logs
On 10 Sep 2019, at 04:14, Paul notifications@github.com wrote:
@lmdecroos https://github.com/lmdecroos When EMS-ESP starts it will auto-detect all known devices, this only happens once and should take a few seconds. If the Tx is not working this will fail, but shouldn't repeat. You can try different tx_modes (1 is default, 2 is EMS+ and 3 is Junkers). I've seen others report back that 1.9 keeps crashing but I cannot reproduce and I have no example logs, stacks etc to help pinpoint the issue. Is it really crashing (i.e. resetting)? See https://github.com/proddy/EMS-ESP/wiki/Troubleshooting https://github.com/proddy/EMS-ESP/wiki/Troubleshooting
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW444LKL46WDJO2IZ5QTLQI37ILA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6JSXHY#issuecomment-529738655, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW447UHYBDDLCLJU3BYDLQI37ILANCNFSM4IGOZDBQ.
lmdecroos
on 10 Sep 2019
@lmdecroos could you create a separate issue for this problem as this one is related to a feature request to support multiple heating circuits.
proddy
on 11 Sep 2019
Yes, I can create a separate issue. But the EMS communication issues are introduced with version 1.9.x
With version 1.8.3 my RC35 thermostat was recognised by using the ems protocol ( tx_mode 1)
With version 1.9.0 and 1.9.1b the ems protocol chraches the gateway :
System Logging set to None
System Logging set to Verbose
(00:00:05.704) Sending read of type 0x02 to 0x38, telegram: 0B B8 02 00 20 (CRC=25)
(00:00:06.476) Boiler -> all, type 0x34, telegram: 08 00 34 00 3D 02 72 02 72 21 00 00 03 00 00 98 A7 00 15 3C 00 80 00 (CRC=4A) #data=19
<--- UBAMonitorWWMessage(0x34)
(00:00:06.706) Boiler -> all, type 0x18, telegram: 08 00 18 00 3D 02 89 72 00 00 00 64 60 02 67 02 72 02 82 00 00 0D 30 41 01 31 00 01 00 (CRC=A4) #data=25
<--- UBAMonitorFast(0x18)
(00:00:06.949) Sending read of type 0x02 to 0x02, telegram: 0B 82 02 00 20 (CRC=EC)
(00:00:08.112) Boiler -> all, type 0x07, telegram: 08 00 07 00 03 03 00 00 00 00 00 00 00 00 00 00 00 (CRC=53) #data=13
(00:00:08.518) Sending read of type 0x02 to 0x08, telegram: 0B 88 02 00 20 (CRC=BC)
(00:00:08.558) Boiler -> me, type 0x02, telegram: 08 0B 02 00 73 05 05 00 00 00 00 00 00 00 (CRC=D7) #data=10
<--- Version(0x02)
Boiler found: Nefit Topline Compact/Buderus GB162 (DeviceID:0x08 ProductID:115 Version:05.05)
(00:00:08.636) Boiler -> all, type 0x07, telegram: 08 00 07 00 0B 03 00 00 00 00 00 00 00 00 00 00 00 (CRC=7F) #data=13
(00:00:08.892) Sending read of type 0x02 to 0x09, telegram: 0B 89 02 00 20 (CRC=B4)
(00:00:08.930) 0x09 -> me, type 0x02, telegram: 09 0B 02 00 44 02 03 (CRC=25) #data=3
<--- Version(0x02)
Device found: BC10/RFM20 Receiver (DeviceID:0x09 ProductID:68 Version:02.03)
(00:00:09.240) Sending read of type 0x02 to 0x10, telegram: 0B 90 02 00 20 (CRC=7C)
(00:00:09.279) 0x10 -> me, type 0x02, telegram: 10 0B 02 00 56 15 08 (CRC=5E) #data=3
<--- Version(0x02)
Thermostat found: RC35 (DeviceID:0x10 ProductID:86 Version:21.08)
- Setting Thermostat to RC35 (DeviceID:0x10 ProductID:86 Version:21.08)
Requesting type RC35StatusMessage_HC1(0x3E) from dest 0x10
Requesting type RC35Set_HC1(0x3D) from dest 0x10
Requesting type RC35StatusMessage_HC2(0x48) from dest 0x10
Requesting type RC35Set_HC2(0x47) from dest 0x10
Requesting type RC35StatusMessage_HC3(0x52) from dest 0x10
Requesting type RC35Set_HC2(0x51) from dest 0x10
Requesting type RC35StatusMessage_HC4(0x5C) from dest 0x10
Requesting type RC35Set_HC4(0x5B) from dest 0x10
Requesting type RCTime(0x06) from dest 0x10
(00:00:09.539) Sending read of type 0x02 to 0x11, telegram: 0B 91 02 00 20 (CRC=74)
(00:00:09.584) 0x11 -> me, type 0x02, telegram: 11 0B 02 00 47 02 00 (CRC=7C) #data=3
<--- Version(0x02)
Device found: WM10 Switch Module (DeviceID:0x11 ProductID:71 Version:02.00)
(00:00:09.813) Sending read of type 0x02 to 0x17, telegram: 0B 97 02 00 20 (CRC=44)
(00:00:10.417) Boiler -> all, type 0x18, telegram: 08 00 18 00 07 02 88 00 00 00 00 40 60 02 69 02 73 02 81 00 00 0A 30 48 00 CB 00 00 00 (CRC=25) #data=25
<--- UBAMonitorFast(0x18)
(00:00:10.677) 0x11 -> Boiler, type 0x1E, telegram: 11 08 1E 00 00 CD (CRC=AF) #data=2
(00:00:10.984) Sending read of type 0x02 to 0x18, telegram: 0B 98 02 00 20 (CRC=3C)
The gateway hangs every time on : Sending read of type 0x02 to 0x18, telegram: 0B 98 02 00 20 (CRC=3C) and reboots itself afterwards
When using the EMS+ protocol (tx_mode 2) the gateway works stable, but doesn’t recognise my RC35 thermostat
the EMS+ protocol recognises only my boiler ( same for version 1.8.3)
On 11 Sep 2019, at 05:23, Paul notifications@github.com wrote:
@lmdecroos https://github.com/lmdecroos could you create a separate issue for this problem as this one is related to a feature request to support multiple heating circuits.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW442WMIOGVNXOPH6GVKLQJBQEDA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6NEGFQ#issuecomment-530203414, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW44ZAX3MZ4BHTMWZBTVTQJBQEDANCNFSM4IGOZDBQ.
lmdecroos
on 11 Sep 2019
I’m now testing the 1.9.1b2 build and wondering how i can set and check the HC in the console.
I’m able to change the setting in the web UI, but when using the "set heating_circuit” command i get the error message "Invalid parameter for set command”
lmdecroos
on 12 Sep 2019
You don’t need to set the heating circuit anymore. It should detect readings on up to 4 HCs automatically. I forgot to remove it from the web interface.
proddy
on 13 Sep 2019
see also https://github.com/proddy/EMS-ESP/wiki/MQTT on how to use MQTT to control multiple heating circuits.
proddy
on 14 Sep 2019
Thanks for updating the MQTT wiki, but I'm still suffer to get my thermostat / HC recognised in version 1.9.x
With the standard EMS protocol, both my boiler and HC are recognised in version 1.8.3, but when using version 1.9.x the EMS gateway crashes at startup while polling the bus.
The gateway hangs every time on : Sending read of type 0x02 to 0x18, telegram: 0B 98 02 00 20 (CRC=3C) and reboots itself afterwards, see my entry from 11th September.
I tested this messages in version 1.8.3, and then the 18.3 EMS gateway crashes also.
Can you advise where I have to look in the source code for the initiation and startup process, so that I can troubleshoot by check the differences between both versions.
On 14 Sep 2019, at 16:41, Paul notifications@github.com wrote:
see also https://github.com/proddy/EMS-ESP/wiki/MQTT https://github.com/proddy/EMS-ESP/wiki/MQTT on how to use MQTT to control multiple heating circuits.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW444TEEQPDSTN4EDBU4DQJTZZNA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6W5B6A#issuecomment-531484920, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW447T7JESJOOX3ULDVWLQJTZZNANCNFSM4IGOZDBQ.
lmdecroos
on 14 Sep 2019
I‘d suggest ‚set log j‘ to get an idea where it happens...
Sent by mobile device
Am 14.09.2019 um 17:26 schrieb lmdecroos notifications@github.com:
Thanks for updating the MQTT wiki, but I'm still suffer to get my thermostat / HC recognised in version 1.9.x
With the standard EMS protocol, both my boiler and HC are recognised in version 1.8.3, but when using version 1.9.x the EMS gateway crashes at startup while polling the bus.
The gateway hangs every time on : Sending read of type 0x02 to 0x18, telegram: 0B 98 02 00 20 (CRC=3C) and reboots itself afterwards, see my entry from 11th September.
I tested this messages in version 1.8.3, and then the 18.3 EMS gateway crashes also.Can you advise where I have to look in the source code for the initiation and startup process, so that I can troubleshoot by check the differences between both versions.
On 14 Sep 2019, at 16:41, Paul notifications@github.com wrote:
see also https://github.com/proddy/EMS-ESP/wiki/MQTT https://github.com/proddy/EMS-ESP/wiki/MQTT on how to use MQTT to control multiple heating circuits.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW444TEEQPDSTN4EDBU4DQJTZZNA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6W5B6A#issuecomment-531484920, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW447T7JESJOOX3ULDVWLQJTZZNANCNFSM4IGOZDBQ.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
susisstrolch
on 14 Sep 2019
please find the jabber log until the crash :
(00:00:08.141) ems_parseTelegram: 00 01: 8B
(00:00:08.142) emsuart_tx_buffer: 00 01: 0B 82 02 00 20 EC
(00:00:08.158) ems_parseTelegram: 00 02: 0B 82 02 00 20 EC
(00:00:08.158) echo:telegram: 0B 82 02 00 20 (CRC=EC) #data=1
(00:00:08.390) ems_parseTelegram: 00 02: 90
(00:00:08.395) ems_parseTelegram: 00 02: 10
(00:00:08.415) ems_parseTelegram: 00 02: 89
(00:00:08.425) ems_parseTelegram: 00 02: 09
(00:00:08.440) ems_parseTelegram: 00 02: 8D
(00:00:08.465) ems_parseTelegram: 00 02: 89
(00:00:08.472) ems_parseTelegram: 00 02: 09
(00:00:08.490) ems_parseTelegram: 00 02: 8E
(00:00:08.515) ems_parseTelegram: 00 02: 91
(00:00:08.519) ems_parseTelegram: 00 02: 11
(00:00:08.540) ems_parseTelegram: 00 02: 89
(00:00:08.549) ems_parseTelegram: 00 02: 09
(00:00:08.565) ems_parseTelegram: 00 02: 99
(00:00:08.569) ems_parseTelegram: 00 02: 19
(00:00:08.590) ems_parseTelegram: 00 02: 8F
(00:00:08.615) ems_parseTelegram: 00 02: A1
(00:00:08.619) ems_parseTelegram: 00 02: 21
(00:00:08.639) ems_parseTelegram: 00 02: 92
(00:00:08.664) ems_parseTelegram: 00 02: 89
(00:00:08.672) ems_parseTelegram: 00 02: 09
(00:00:08.689) ems_parseTelegram: 00 02: 89
(00:00:08.698) ems_parseTelegram: 00 02: 09
(00:00:08.714) ems_parseTelegram: 00 02: 89
(00:00:08.724) ems_parseTelegram: 00 02: 09
(00:00:08.739) ems_parseTelegram: 00 02: 89
(00:00:08.749) ems_parseTelegram: 00 02: 09
(00:00:08.764) ems_parseTelegram: 00 02: 8B
(00:00:08.789) ems_parseTelegram: 00 02: 90
(00:00:08.794) ems_parseTelegram: 00 02: 10
(00:00:08.814) ems_parseTelegram: 00 02: 89
(00:00:08.821) ems_parseTelegram: 00 02: 09
(00:00:08.839) ems_parseTelegram: 00 02: 93
(00:00:08.864) ems_parseTelegram: 00 02: 89
(00:00:08.873) ems_parseTelegram: 00 02: 09
(00:00:08.888) ems_parseTelegram: 00 02: 94
(00:00:08.913) ems_parseTelegram: 00 02: 91
(00:00:08.918) ems_parseTelegram: 00 02: 11
(00:00:08.938) ems_parseTelegram: 00 02: 89
(00:00:08.945) ems_parseTelegram: 00 02: 09
(00:00:08.964) ems_parseTelegram: 00 02: 99
(00:00:08.968) ems_parseTelegram: 00 02: 19
(00:00:08.988) ems_parseTelegram: 00 02: 95
(00:00:09.013) ems_parseTelegram: 00 02: A1
(00:00:09.017) ems_parseTelegram: 00 02: 21
(00:00:09.038) ems_parseTelegram: 00 02: 96
(00:00:09.063) ems_parseTelegram: 00 02: 89
(00:00:09.073) ems_parseTelegram: 00 02: 09
(00:00:09.088) ems_parseTelegram: 00 02: 89
(00:00:09.094) ems_parseTelegram: 00 02: 09
(00:00:09.113) ems_parseTelegram: 00 02: 89
(00:00:09.120) ems_parseTelegram: 00 02: 09
(00:00:09.138) ems_parseTelegram: 00 02: 89
(00:00:09.145) ems_parseTelegram: 00 02: 09
(00:00:09.163) ems_parseTelegram: 00 02: 8B
(00:00:09.188) ems_parseTelegram: 00 02: 90
(00:00:09.192) ems_parseTelegram: 00 02: 10
(00:00:09.212) ems_parseTelegram: 00 02: 89
(00:00:09.222) ems_parseTelegram: 00 02: 09
(00:00:09.237) ems_parseTelegram: 00 02: 97
(00:00:09.262) ems_parseTelegram: 00 02: 89
(00:00:09.269) ems_parseTelegram: 00 02: 09
(00:00:09.287) ems_parseTelegram: 00 02: 9C
(00:00:09.312) ems_parseTelegram: 00 02: 91
(00:00:09.316) ems_parseTelegram: 00 02: 11
(00:00:09.337) ems_parseTelegram: 00 02: 89
(00:00:09.346) ems_parseTelegram: 00 02: 09
(00:00:09.362) ems_parseTelegram: 00 02: 99
(00:00:09.366) ems_parseTelegram: 00 02: 19
(00:00:09.387) ems_parseTelegram: 00 02: A4
(00:00:09.412) ems_parseTelegram: 00 02: A1
(00:00:09.416) ems_parseTelegram: 00 02: 21
(00:00:09.436) ems_parseTelegram: 00 02: AC
(00:00:09.461) ems_parseTelegram: 00 02: 89
(00:00:09.469) ems_parseTelegram: 00 02: 09
(00:00:09.486) ems_parseTelegram: 00 02: 89
(00:00:09.495) ems_parseTelegram: 00 02: 09
(00:00:09.511) ems_parseTelegram: 00 02: 89
(00:00:09.521) ems_parseTelegram: 00 02: 09
(00:00:09.536) ems_parseTelegram: 00 02: 89
(00:00:09.546) ems_parseTelegram: 00 02: 09
(00:00:09.561) ems_parseTelegram: 00 02: 8B
(00:00:09.586) ems_parseTelegram: 00 02: 90
(00:00:09.591) ems_parseTelegram: 00 02: 10
(00:00:09.629) ems_parseTelegram: 00 02: 08 00 07 00 03 03 02 02 00 00 00 00 00 00 00 00 00 FF
(00:00:09.630) Boiler -> all, type 0x07, telegram: 08 00 07 00 03 03 02 02 00 00 00 00 00 00 00 00 00 (CRC=FF) #data=13
(00:00:09.810) ems_parseTelegram: 00 01: B4
(00:00:09.835) ems_parseTelegram: 00 01: 89
(00:00:09.845) ems_parseTelegram: 00 01: 09
(00:00:09.860) ems_parseTelegram: 00 01: BC
(00:00:09.885) ems_parseTelegram: 00 01: 91
(00:00:09.889) ems_parseTelegram: 00 01: 11
(00:00:09.910) ems_parseTelegram: 00 01: 89
(00:00:09.917) ems_parseTelegram: 00 01: 09
(00:00:09.935) ems_parseTelegram: 00 01: 99
(00:00:09.939) ems_parseTelegram: 00 01: 19
(00:00:09.960) ems_parseTelegram: 00 01: C4
(00:00:09.985) ems_parseTelegram: 00 01: A1
(00:00:09.989) ems_parseTelegram: 00 01: 21
(00:00:10.009) ems_parseTelegram: 00 01: CC
(00:00:10.034) ems_parseTelegram: 00 01: 89
(00:00:10.040) ems_parseTelegram: 00 01: 09
(00:00:10.059) ems_parseTelegram: 00 01: 89
(00:00:10.066) ems_parseTelegram: 00 01: 09
(00:00:10.084) ems_parseTelegram: 00 01: 89
(00:00:10.092) ems_parseTelegram: 00 01: 09
(00:00:10.109) ems_parseTelegram: 00 01: 89
(00:00:10.117) ems_parseTelegram: 00 01: 09
(00:00:10.134) ems_parseTelegram: 00 01: 90
(00:00:10.139) ems_parseTelegram: 00 01: 10
(00:00:10.159) ems_parseTelegram: 00 01: 91
(00:00:10.163) ems_parseTelegram: 00 01: 11
(00:00:10.184) ems_parseTelegram: 00 01: 89
(00:00:10.189) ems_parseTelegram: 00 01: 09
(00:00:10.209) ems_parseTelegram: 00 01: D4
(00:00:10.234) ems_parseTelegram: 00 01: 89
(00:00:10.241) ems_parseTelegram: 00 01: 09
(00:00:10.258) ems_parseTelegram: 00 01: DC
(00:00:10.283) ems_parseTelegram: 00 01: 99
(00:00:10.288) ems_parseTelegram: 00 01: 19
(00:00:10.308) ems_parseTelegram: 00 01: 89
(00:00:10.318) ems_parseTelegram: 00 01: 09
(00:00:10.333) ems_parseTelegram: 00 01: A1
(00:00:10.338) ems_parseTelegram: 00 01: 21
(00:00:10.358) ems_parseTelegram: 00 01: E4
(00:00:10.383) ems_parseTelegram: 00 01: 89
(00:00:10.390) ems_parseTelegram: 00 01: 09
(00:00:10.408) ems_parseTelegram: 00 01: EC
(00:00:10.433) ems_parseTelegram: 00 01: 89
(00:00:10.441) ems_parseTelegram: 00 01: 09
(00:00:10.458) ems_parseTelegram: 00 01: 89
(00:00:10.467) ems_parseTelegram: 00 01: 09
(00:00:10.483) ems_parseTelegram: 00 01: 90
(00:00:10.487) ems_parseTelegram: 00 01: 10
(00:00:10.507) ems_parseTelegram: 00 01: 89
(00:00:10.514) ems_parseTelegram: 00 01: 09
(00:00:10.532) ems_parseTelegram: 00 01: 91
(00:00:10.537) ems_parseTelegram: 00 01: 11
(00:00:10.557) ems_parseTelegram: 00 01: 99
(00:00:10.562) ems_parseTelegram: 00 01: 19
(00:00:10.582) ems_parseTelegram: 00 01: 89
(00:00:10.591) ems_parseTelegram: 00 01: 09
(00:00:10.607) ems_parseTelegram: 00 01: 8A
(00:00:10.632) ems_parseTelegram: 00 01: 89
(00:00:10.642) ems_parseTelegram: 00 01: 09
(00:00:10.657) ems_parseTelegram: 00 01: 8B
(00:00:10.657) emsuart_tx_buffer: 00 01: 0B 88 02 00 20 BC
(00:00:10.672) ems_parseTelegram: 00 02: 0B 88 02 00 20 BC
(00:00:10.673) echo:telegram: 0B 88 02 00 20 (CRC=BC) #data=1
(00:00:10.697) ems_parseTelegram: 00 02: 08 0B 02 00 73 05 05 00 00 00 00 00 00 00 D7
(00:00:10.698) Boiler -> me, type 0x02, telegram: 08 0B 02 00 73 05 05 00 00 00 00 00 00 00 (CRC=D7) #data=10
Boiler found: Nefit Topline Compact/Buderus GB162 (DeviceID:0x08 ProductID:115 Version:05.05)
(00:00:10.699) emsuart_tx_buffer: 00 01: 0B
(00:00:10.704) ems_parseTelegram: 00 01: 0B
(00:00:10.707) ems_parseTelegram: 00 01: A1
(00:00:10.711) ems_parseTelegram: 00 01: 21
(00:00:10.750) ems_parseTelegram: 00 01: 08 00 07 00 0B 03 02 02 00 00 00 00 00 00 00 00 00 D3
(00:00:10.751) Boiler -> all, type 0x07, telegram: 08 00 07 00 0B 03 02 02 00 00 00 00 00 00 00 00 00 (CRC=D3) #data=13
(00:00:10.931) ems_parseTelegram: 00 01: 89
(00:00:10.940) ems_parseTelegram: 00 01: 09
(00:00:10.956) ems_parseTelegram: 00 01: 8C
(00:00:10.981) ems_parseTelegram: 00 01: 89
(00:00:10.987) ems_parseTelegram: 00 01: 09
(00:00:11.006) ems_parseTelegram: 00 01: 8D
(00:00:11.030) ems_parseTelegram: 00 01: 89
(00:00:11.038) ems_parseTelegram: 00 01: 09
(00:00:11.055) ems_parseTelegram: 00 01: 8B
(00:00:11.056) emsuart_tx_buffer: 00 01: 0B 89 02 00 20 B4
(00:00:11.071) ems_parseTelegram: 00 02: 0B 89 02 00 20 B4
(00:00:11.071) echo:telegram: 0B 89 02 00 20 (CRC=B4) #data=1
(00:00:11.094) ems_parseTelegram: 00 02: 09 0B 02 00 44 02 03 25
(00:00:11.095) 0x09 -> me, type 0x02, telegram: 09 0B 02 00 44 02 03 (CRC=25) #data=3
Device found: BC10/RFM20 Receiver (DeviceID:0x09 ProductID:68 Version:02.03)
(00:00:11.096) emsuart_tx_buffer: 00 01: 0B
(00:00:11.101) ems_parseTelegram: 00 01: 0B
(00:00:11.105) ems_parseTelegram: 00 01: 90
(00:00:11.110) ems_parseTelegram: 00 01: 10
(00:00:11.130) ems_parseTelegram: 00 01: 89
(00:00:11.136) ems_parseTelegram: 00 01: 09
(00:00:11.155) ems_parseTelegram: 00 01: 91
(00:00:11.160) ems_parseTelegram: 00 01: 11
(00:00:11.180) ems_parseTelegram: 00 01: 99
(00:00:11.185) ems_parseTelegram: 00 01: 19
(00:00:11.205) ems_parseTelegram: 00 01: 89
(00:00:11.213) ems_parseTelegram: 00 01: 09
(00:00:11.230) ems_parseTelegram: 00 01: 8E
(00:00:11.255) ems_parseTelegram: 00 01: 89
(00:00:11.264) ems_parseTelegram: 00 01: 09
(00:00:11.280) ems_parseTelegram: 00 01: 8F
(00:00:11.305) ems_parseTelegram: 00 01: A1
(00:00:11.309) ems_parseTelegram: 00 01: 21
(00:00:11.329) ems_parseTelegram: 00 01: 89
(00:00:11.336) ems_parseTelegram: 00 01: 09
(00:00:11.354) ems_parseTelegram: 00 01: 89
(00:00:11.362) ems_parseTelegram: 00 01: 09
(00:00:11.379) ems_parseTelegram: 00 01: 92
(00:00:11.404) ems_parseTelegram: 00 01: 89
(00:00:11.414) ems_parseTelegram: 00 01: 09
(00:00:11.429) ems_parseTelegram: 00 01: 93
(00:00:11.454) ems_parseTelegram: 00 01: 89
(00:00:11.460) ems_parseTelegram: 00 01: 09
(00:00:11.479) ems_parseTelegram: 00 01: 8B
(00:00:11.479) emsuart_tx_buffer: 00 01: 0B 90 02 00 20 7C
(00:00:11.494) ems_parseTelegram: 00 02: 0B 90 02 00 20 7C
(00:00:11.495) echo:telegram: 0B 90 02 00 20 (CRC=7C) #data=1
(00:00:11.540) ems_parseTelegram: 00 02: 10 0B 02 00 56 15 08 5E
(00:00:11.540) 0x10 -> me, type 0x02, telegram: 10 0B 02 00 56 15 08 (CRC=5E) #data=3
Thermostat found: RC35 (DeviceID:0x10 ProductID:86 Version:21.08)
- Setting Thermostat to RC35 (DeviceID:0x10 ProductID:86 Version:21.08)
(00:00:11.542) emsuart_tx_buffer: 00 01: 0B
(00:00:11.547) ems_parseTelegram: 00 01: 0B
(00:00:11.554) ems_parseTelegram: 00 01: 90
(00:00:11.558) ems_parseTelegram: 00 01: 10
(00:00:11.579) ems_parseTelegram: 00 01: 89
(00:00:11.589) ems_parseTelegram: 00 01: 09
(00:00:11.603) ems_parseTelegram: 00 01: 91
(00:00:11.608) ems_parseTelegram: 00 01: 11
(00:00:11.629) ems_parseTelegram: 00 01: 99
(00:00:11.633) ems_parseTelegram: 00 01: 19
(00:00:11.653) ems_parseTelegram: 00 01: 89
(00:00:11.660) ems_parseTelegram: 00 01: 09
(00:00:11.678) ems_parseTelegram: 00 01: 94
(00:00:11.703) ems_parseTelegram: 00 01: 89
(00:00:11.712) ems_parseTelegram: 00 01: 09
(00:00:11.728) ems_parseTelegram: 00 01: 95
(00:00:11.753) ems_parseTelegram: 00 01: A1
(00:00:11.757) ems_parseTelegram: 00 01: 21
(00:00:11.778) ems_parseTelegram: 00 01: 89
(00:00:11.784) ems_parseTelegram: 00 01: 09
(00:00:11.803) ems_parseTelegram: 00 01: 89
(00:00:11.810) ems_parseTelegram: 00 01: 09
(00:00:11.828) ems_parseTelegram: 00 01: 96
(00:00:11.852) ems_parseTelegram: 00 01: 89
(00:00:11.861) ems_parseTelegram: 00 01: 09
(00:00:11.877) ems_parseTelegram: 00 01: 97
(00:00:11.902) ems_parseTelegram: 00 01: 89
(00:00:11.913) ems_parseTelegram: 00 01: 09
(00:00:11.927) ems_parseTelegram: 00 01: 8B
(00:00:11.928) emsuart_tx_buffer: 00 01: 0B 91 02 00 20 74
(00:00:11.943) ems_parseTelegram: 00 02: 0B 91 02 00 20 74
(00:00:11.943) echo:telegram: 0B 91 02 00 20 (CRC=74) #data=1
(00:00:12.014) ems_parseTelegram: 00 02: 11 0B 02 00 47 02 00 7C
(00:00:12.014) 0x11 -> me, type 0x02, telegram: 11 0B 02 00 47 02 00 (CRC=7C) #data=3
Device found: WM10 Switch Module (DeviceID:0x11 ProductID:71 Version:02.00)
(00:00:12.016) emsuart_tx_buffer: 00 01: 0B
(00:00:12.021) ems_parseTelegram: 00 01: 0B
(00:00:12.027) ems_parseTelegram: 00 01: 90
(00:00:12.031) ems_parseTelegram: 00 01: 10
(00:00:12.052) ems_parseTelegram: 00 01: 89
(00:00:12.062) ems_parseTelegram: 00 01: 09
(00:00:12.077) ems_parseTelegram: 00 01: 91
(00:00:12.081) ems_parseTelegram: 00 01: 11
(00:00:12.102) ems_parseTelegram: 00 01: 99
(00:00:12.106) ems_parseTelegram: 00 01: 19
(00:00:12.126) ems_parseTelegram: 00 01: 89
(00:00:12.134) ems_parseTelegram: 00 01: 09
(00:00:12.151) ems_parseTelegram: 00 01: 98
(00:00:12.263) ems_parseTelegram: 00 01: 18 00 AF 00 83 00 09 00 00 B5
(00:00:12.264) 0x18 -> all, type 0xAF, telegram: 18 00 AF 00 83 00 09 00 00 (CRC=B5) #data=5
(00:00:12.451) ems_parseTelegram: 00 01: 18
(00:00:12.475) ems_parseTelegram: 00 01: 89
(00:00:12.484) ems_parseTelegram: 00 01: 09
(00:00:12.500) ems_parseTelegram: 00 01: A0
(00:00:12.525) ems_parseTelegram: 00 01: A1
(00:00:12.530) ems_parseTelegram: 00 01: 21
(00:00:12.568) ems_parseTelegram: 00 01: 08 00 07 00 0B 03 03 02 00 00 00 00 00 00 00 00 00 B7
(00:00:12.569) Boiler -> all, type 0x07, telegram: 08 00 07 00 0B 03 03 02 00 00 00 00 00 00 00 00 00 (CRC=B7) #data=13
(00:00:12.749) ems_parseTelegram: 00 01: 89
(00:00:12.756) ems_parseTelegram: 00 01: 09
(00:00:12.774) ems_parseTelegram: 00 01: A8
(00:00:12.799) ems_parseTelegram: 00 01: 89
(00:00:12.808) ems_parseTelegram: 00 01: 09
(00:00:12.824) ems_parseTelegram: 00 01: B0
(00:00:12.849) ems_parseTelegram: 00 01: 89
(00:00:12.859) ems_parseTelegram: 00 01: 09
(00:00:12.874) ems_parseTelegram: 00 01: 8B
(00:00:12.874) emsuart_tx_buffer: 00 01: 0B 97 02 00 20 44
(00:00:12.889) ems_parseTelegram: 00 02: 0B 97 02 00 20 44
(00:00:12.890) echo:telegram: 0B 97 02 00 20 (CRC=44) #data=1
(00:00:13.123) ems_parseTelegram: 00 02: 90
(00:00:13.127) ems_parseTelegram: 00 02: 10
(00:00:13.179) ems_parseTelegram: 00 02: 08 00 18 00 07 01 8A 00 00 00 00 00 60 01 1B 02 45 01 A7 00 00 0A 30 48 00 CB 00 00 00 22
(00:00:13.180) Boiler -> all, type 0x18, telegram: 08 00 18 00 07 01 8A 00 00 00 00 00 60 01 1B 02 45 01 A7 00 00 0A 30 48 00 CB 00 00 00 (CRC=22) #data=25
(00:00:13.372) ems_parseTelegram: 00 01: 91
(00:00:13.376) ems_parseTelegram: 00 01: 11
(00:00:13.397) ems_parseTelegram: 00 01: 98
(00:00:13.402) ems_parseTelegram: 00 01: 18
(00:00:13.447) ems_parseTelegram: 00 01: 08 00 34 00 3D 02 45 02 45 21 00 00 03 00 00 98 EC 00 15 49 00 80 00 D4
(00:00:13.448) Boiler -> all, type 0x34, telegram: 08 00 34 00 3D 02 45 02 45 21 00 00 03 00 00 98 EC 00 15 49 00 80 00 (CRC=D4) #data=19
(00:00:13.646) ems_parseTelegram: 00 01: B8
(00:00:13.671) ems_parseTelegram: 00 01: 89
(00:00:13.677) ems_parseTelegram: 00 01: 09
(00:00:13.696) ems_parseTelegram: 00 01: C0
(00:00:13.721) ems_parseTelegram: 00 01: 99
(00:00:13.725) ems_parseTelegram: 00 01: 19
(00:00:13.745) ems_parseTelegram: 00 01: 89
(00:00:13.754) ems_parseTelegram: 00 01: 09
(00:00:13.771) ems_parseTelegram: 00 01: A1
(00:00:13.775) ems_parseTelegram: 00 01: 21
(00:00:13.795) ems_parseTelegram: 00 01: C8
(00:00:13.820) ems_parseTelegram: 00 01: 89
(00:00:13.831) ems_parseTelegram: 00 01: 09
(00:00:13.845) ems_parseTelegram: 00 01: D0
(00:00:13.870) ems_parseTelegram: 00 01: 89
(00:00:13.877) ems_parseTelegram: 00 01: 09
(00:00:13.895) ems_parseTelegram: 00 01: 89
(00:00:13.903) ems_parseTelegram: 00 01: 09
(00:00:13.920) ems_parseTelegram: 00 01: 8B
(00:00:13.920) emsuart_tx_buffer: 00 01: 0B 98 02 00 20 3C
(00:00:13.935) ems_parseTelegram: 00 02: 0B 98 02 00 20 3C
(00:00:13.936) echo:telegram: 0B 98 02 00 20 (CRC=3C) #data=1
On 14 Sep 2019, at 18:11, susisstrolch notifications@github.com wrote:
I‘d suggest ‚set log j‘ to get an idea where it happens...
Sent by mobile device
Am 14.09.2019 um 17:26 schrieb lmdecroos notifications@github.com:
Thanks for updating the MQTT wiki, but I'm still suffer to get my thermostat / HC recognised in version 1.9.x
With the standard EMS protocol, both my boiler and HC are recognised in version 1.8.3, but when using version 1.9.x the EMS gateway crashes at startup while polling the bus.
The gateway hangs every time on : Sending read of type 0x02 to 0x18, telegram: 0B 98 02 00 20 (CRC=3C) and reboots itself afterwards, see my entry from 11th September.
I tested this messages in version 1.8.3, and then the 18.3 EMS gateway crashes also.Can you advise where I have to look in the source code for the initiation and startup process, so that I can troubleshoot by check the differences between both versions.
On 14 Sep 2019, at 16:41, Paul notifications@github.com wrote:
see also https://github.com/proddy/EMS-ESP/wiki/MQTT https://github.com/proddy/EMS-ESP/wiki/MQTT on how to use MQTT to control multiple heating circuits.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW444TEEQPDSTN4EDBU4DQJTZZNA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6W5B6A#issuecomment-531484920, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW447T7JESJOOX3ULDVWLQJTZZNANCNFSM4IGOZDBQ.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW4467UXAFMZZW4JAKGB3QJUEJ7A5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6W6YZI#issuecomment-531491941, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW442USL5RN4VPJNKPEGDQJUEJ7ANCNFSM4IGOZDBQ.
lmdecroos
on 14 Sep 2019
Please create a new GitHub issue for the reboot problems. From the log I see the devices are detected correctly so something else is causing the crash, either the MQTT or the Event Log.
proddy
on 15 Sep 2019
I have version 1.9.1b3.
I wanted to check if the RC35 temperature was in auto mode. (0.0C)
I see that it is no longer possible to switch heating circuits. By default, I see HC1 and want HC2 - how can I change it?
Additionally, I noticed that the web interface is very unstable (hangs)
majdzik84
on 17 Sep 2019
@majdzik84 all heating circuits should be detected and shown. What's strange is that you don't get any listed under the 'Thermostat stats' page?
The code picks up messages from telegram types 0x3E (HC1), 0x48 (HC2), 0x52 (HC3) and 0x5C (HC4)
I can't test when I make these changes and do my best to simulate what it would look like on the multitude of thermostat models so any test data would be helpful. Even better are code changes ;)
proddy
on 17 Sep 2019
below I am sending a log - maybe it will be helpful in something
log t
System Logging set to Thermostat only
Publishing boiler data via MQTT
Publishing hot water and heating states via MQTT
Requesting scheduled EMS device data
(04:06:02.034) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 00 7D 00 00 00 00 00 00 00 00 00 11 05 04 (CRC=ED) #data=16
(04:06:02.440) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2B 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=8F) #data=27
(04:06:02.908) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 00 00 E4 00 00 00 00 00 00 00 00 11 05 04 (CRC=45) #data=16
(04:06:03.315) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 13 15 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FD) #data=27
(04:06:03.784) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=B6) #data=16
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
(04:06:04.191) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1E) #data=27
(04:06:04.659) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
Publishing boiler data via MQTT
(04:06:05.066) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #data=27
Publishing boiler data via MQTT
(04:06:05.514) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 11 12 34 34 02 01 (CRC=43) #data=8
(04:06:05.905) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 10 00 00 00 E4 00 EA 00 EA 7D 00 7D 00 (CRC=24) #data=13
(04:06:10.376) Thermostat -> 0x08, type 0x1A, telegram: 10 08 1A 00 00 00 00 00 (CRC=91) #data=4
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
(04:06:21.002) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 00 03 (CRC=0D) #data=3
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
(04:06:28.869) Thermostat -> 0x08, type 0x14, telegram: 10 88 14 00 03 (CRC=6E) #data=1
(04:06:28.888) 0x08 -> Thermostat, type 0x14, telegram: 08 10 14 00 17 7A 48 (CRC=B9) #data=3
(04:06:31.121) Thermostat -> 0x08, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
(04:06:44.765) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 11 12 35 1F 02 01 (CRC=40) #data=8
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
(04:06:49.659) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 00 00 00 E4 00 00 00 00 00 00 00 00 11 05 04 (CRC=2D) #data=16
Publishing boiler data via MQTT
(04:06:54.159) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 00 7D 00 00 00 00 00 00 00 00 00 11 05 04 (CRC=85) #data=16
Requesting scheduled EMS device data
(04:07:00.657) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 00 7D 00 00 00 00 00 00 00 00 00 11 05 04 (CRC=ED) #data=16
(04:07:01.189) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2B 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=8F) #data=27
(04:07:02.033) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 00 00 E4 00 00 00 00 00 00 00 00 11 05 04 (CRC=45) #data=16
(04:07:02.440) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 13 15 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FD) #data=27
(04:07:02.783) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=B6) #data=16
(04:07:03.315) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1E) #data=27
(04:07:03.783) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
Publishing boiler data via MQTT
(04:07:04.190) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #data=27
Publishing boiler data via MQTT
(04:07:04.514) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 11 12 35 33 02 01 (CRC=57) #data=8
(04:07:06.154) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 10 00 00 00 E4 00 EA 00 EA 7D 00 7D 00 (CRC=24) #data=13
(04:07:10.500) Thermostat -> 0x08, type 0x1A, telegram: 10 08 1A 00 00 00 00 00 (CRC=91) #data=4
(04:07:21.126) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 00 03 (CRC=0D) #data=3
^C(04:07:31.621) Thermostat -> 0x08, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
(04:07:45.264) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 11 12 36 1F 02 01 (CRC=58) #data=8
(04:07:49.908) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 00 00 00 E4 00 00 00 00 00 00 00 00 11 05 04 (CRC=2D) #data=16
Publishing boiler data via MQTT
(04:07:54.408) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 00 7D 00 00 00 00 00 00 00 00 00 11 05 04 (CRC=85) #data=16
Publishing boiler data via MQTT
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
Publishing boiler data via MQTT
Publishing hot water and heating states via MQTT
Requesting scheduled EMS device data
(04:08:01.781) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 00 7D 00 00 00 00 00 00 00 00 00 11 05 04 (CRC=ED) #data=16
(04:08:02.189) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2B 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=8F) #data=27
(04:08:02.532) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 00 00 E4 00 00 00 00 00 00 00 00 11 05 04 (CRC=45) #data=16
(04:08:03.063) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 13 15 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FD) #data=27
(04:08:03.532) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=B6) #data=16
(04:08:03.939) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1E) #data=27
(04:08:04.282) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
Publishing boiler data via MQTT
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
(04:08:04.814) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #data=27
Publishing boiler data via MQTT
(04:08:05.138) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 11 12 36 33 02 01 (CRC=4F) #data=8
(04:08:06.528) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 10 00 00 00 E4 00 EA 00 EA 7D 00 7D 00 (CRC=24) #data=13
(04:08:10.624) Thermostat -> 0x08, type 0x1A, telegram: 10 08 1A 00 00 00 00 00 (CRC=91) #data=4
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
(04:08:21.500) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 00 03 (CRC=0D) #data=3
(04:08:29.243) Thermostat -> 0x08, type 0x14, telegram: 10 88 14 00 03 (CRC=6E) #data=1
(04:08:29.265) 0x08 -> Thermostat, type 0x14, telegram: 08 10 14 00 17 7A 4A (CRC=BB) #data=3
(04:08:29.406) Thermostat -> all, type 0xA2, telegram: 10 00 A2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=99) #data=14
(04:08:31.870) Thermostat -> 0x08, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
what I can see is
HC1 = 10 0B 3E 00 00 00 00 7D 00 00 00 00 00 00 00 00 00 11 05 04
HC2 = 10 00 48 00 00 00 00 00 E4 00 00 00 00 00 00 00 00 11 05 04
HC3 = 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00
HC4 = 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00
which tells me
HC1 has a setpoint of 0.0 and current temps is not defined
HC2 has a setpoint of 0.0 and a current temp is 22.8
HC3 and HC4 are both not used
Is this in line with what you expect?
proddy
on 17 Sep 2019
the thermostat controls the HC2 circuit (RC35) the current temperature is correct but the setpoint temp. should not show 0.0C. automatic mode was enabled and should be fixed in this version.
HC3 and HC4 - not used
majdzik84
on 17 Sep 2019
What should the setpoint show then for HC1,2,3 and 4? All the telegrams that come in are telling EMS-ESP that the value is 0.0? I can change the logic if you can help me understand what it should be in 'auto' mode. I don't have an RC35 to test unfortunately.
proddy
on 18 Sep 2019
Mode AUTO (day)
(06:35:05.227) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
Publishing boiler data via MQTT
(06:35:05.634) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #dat a=27
Publishing boiler data via MQTT
(06:35:05.957) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 0D 13 3A 34 03 01 (CRC=8A) #data=8
(06:35:06.473) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 0D 00 00 00 E C 00 F2 00 F1 7D 00 7D 00 (CRC=F8) #data=13
(06:35:12.562) Thermostat -> 0x08, type 0x14, telegram: 10 88 14 00 03 (CRC=6E) #data=1
(06:35:12.585) 0x08 -> Thermostat, type 0x14, telegram: 08 10 14 00 17 7E EA (CR C=13) #data=3
(06:35:31.194) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 0C 64 03 (CRC=E1) #data=3
(06:35:32.568) Thermostat -> 0x08, type 0x1A, telegram: 10 08 1A 00 2E 64 64 00 (CRC=B9) #data=4
(06:35:33.208) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 0D 13 3B 13 03 01 (CRC=B9) #data=8
(06:35:36.689) Thermostat -> 0x08, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
(06:35:37.852) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 02 39 7D 00 00 00 00 00 00 00 00 64 11 2E 00 (CRC=DA) #data=16
Publishing boiler data via MQTT
(06:35:42.102) Thermostat -> all, type 0x48, telegram: 10 00 48 00 04 02 15 00 EC 00 00 00 00 00 00 00 64 11 0C 00 (CRC=2D) #data=16
Publishing boiler data via MQTT
Publishing boiler data via MQTT
Publishing hot water and heating states via MQTT
Requesting scheduled EMS device data
(06:36:00.850) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 02 39 7D 00 00 00 00 00 00 00 00 64 11 2E 00 (CRC=B2) #data=16
(06:36:01.382) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2B 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=8F) #data=27
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
(06:36:01.726) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 02 15 00 EC 00 00 00 00 00 00 00 64 11 0C 00 (CRC=45) #data=16
(06:36:02.132) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 13 15 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FD) #data=27
(06:36:02.601) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=B6) #data=16
(06:36:03.008) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1E) #data=27
(06:36:03.476) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
Publishing boiler data via MQTT
(06:36:03.883) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #data=27
Publishing boiler data via MQTT
(06:36:04.331) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 0D 13 3B 32 03 01 (CRC=9A) #data=8
(06:36:06.847) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 0D 00 00 00 EC 00 F2 00 F2 7D 00 7D 00 (CRC=C8) #data=13
When I physically changed the temperature on the RC35 controller knob (from automatic DAY: 10.5 C to target 15C I get such telegrams. Perhaps now it will report setpoint temperature 15C. Can you check?
(06:45:01.250) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2B 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=8F) #data=27
(06:45:01.718) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 12 1E 00 EC 00 00 00 00 00 00 00 64 11 10 00 (CRC=41) #data=16
(06:45:02.126) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 13 15 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FD) #data=27
(06:45:02.468) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=B6) #data=16
(06:45:03.000) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1E) #data=27
(06:45:03.344) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
Publishing boiler data via MQTT
(06:45:03.750) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #data=27
Publishing boiler data via MQTT
** [DEBUG MODE] Warning, we missed the bus - Rx non-idle!
(06:45:04.201) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 0E 13 08 32 03 01 (CRC=7B) #data=8
(06:45:09.840) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 0D 00 00 00 EC 00 F2 00 F2 7D 00 7D 00 (CRC=C8) #data=13
(06:45:13.929) Thermostat -> 0x08, type 0x14, telegram: 10 88 14 00 03 (CRC=6E) #data=1
(06:45:13.948) 0x08 -> Thermostat, type 0x14, telegram: 08 10 14 00 17 7E F4 (CRC=0D) #data=3
(06:45:24.839) Thermostat -> all, type 0xA2, telegram: 10 00 A2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=99) #data=14
(06:45:33.311) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 10 64 03 (CRC=91) #data=3
(06:45:34.685) Thermostat -> 0x08, type 0x1A, telegram: 10 08 1A 00 2E 64 64 00 (CRC=B9) #data=4
(06:45:36.825) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 0E 13 09 17 03 01 (CRC=40) #data=8
(06:45:39.056) Thermostat -> 0x08, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
(06:45:41.344) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 02 39 7D 00 00 00 00 00 00 00 00 64 11 2E 00 (CRC=DA) #data=16
Publishing boiler data via MQTT
(06:45:45.844) Thermostat -> all, type 0x48, telegram: 10 00 48 00 04 12 1E 00 EC 00 00 00 00 00 00 00 64 11 10 00 (CRC=29) #data=16
If I think right, it looks like this for HC2
Standard auto mode (day) - set Day temp to 10,5C
(06:35:42.102) Thermostat -> all, type 0x48, telegram: 10 00 48 00 04 02 15 00 EC 00 00 00 00 00 00 00 64 11 0C 00 (CRC=2D) #data=16
Change of target temperature from 10.5 to 15C (the change will only apply until the switching point to Auto-night mode)
(06:39:02.098) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 12 1E 00 EC 00 00 00 00 00 00 00 64 11 10 00 (CRC=41) #data=16
I thought it could be like this:
When auto-day mode is on - setpoint temperature shows day temperature.
When auto-night mode is on, setpoint temperature shows night temperature.
When we change the temperature in auto-day or auto-night mode it does not permanently change the set day or nigt temperatures only temporarily until the next switching point.
This is how it looks on the thermostat.
When I have the day temp set to 10.5 C and in the auto mode I change to 15 C, it will be changed only until the evening when rc35 switch to the auto-night mode with the set temperature, e.g. 9C. The next morning, the Auto-day temperature will still be 10.5C instead of 15C
majdzik84
on 18 Sep 2019
how I read those values:
Setpoint temp = bytes 2, multiplied by 2
Current room temps = bytes 3 + 4, is multiplied by 10
Auto (day)
HC1 = 10 00 3E 00 04 02 39 7D 00 00 00 00 00 00 00 00 64 11 2E 00, setpoint=28.5 current=n/a
HC2 = 10 0B 48 00 04 02 15 00 EC 00 00 00 00 00 00 00 64 11 0C 00, setpoint=10.5, current=23.6
Manual, 15 C
HC1 = 10 00 3E 00 04 02 39 7D 00 00 00 00 00 00 00 00 64 11 2E 00, setpoint=28.5 current=n/a
HC2 = 10 0B 48 00 04 12 1E 00 EC 00 00 00 00 00 00 00 64 11 10 00, setpoint=15 current=23.6
It should display these.
proddy
on 18 Sep 2019
You wrote in an earlier post that it does not display by telegram. Since then, I have reset the stove and the gate. For now i can't check in telnet or webpanel if it displays correctly because thermostat stats nothing shows
majdzik84
on 18 Sep 2019
it should work. can you try again with the latest build? The web only shows HC1. I didn't implement multiple HCs in the web front end
proddy
on 18 Sep 2019
Version 1.9.1b4
Unfortunately the thermostat stats still show nothing
majdzik84
on 18 Sep 2019
strange. I'll do some more simulation and may send over a build that has more debugging in it.
proddy
on 18 Sep 2019
oops, was a bug. I forgot to set the Heating Circuit to be 'active'. Fixed now in dev, still called b4.
proddy
on 18 Sep 2019
Heating circuits have now appeared.
Note that current temperature is missing.
I only use two heating circuits (HC1, HC2)
The HC4 temperature is interesting.
The default circuit is HC1. How can I change to HC2 to be able to control correctly via Home assistant. Currently, when I try to change the mode it changes in HC1 and not in HC2
MQTT topic: thermostat HC1 mode value off
Setting thermostat mode to 0 for heating circuit
MQTT topic: thermostat HC1 mode value auto
Setting thermostat mode to 2 for heating circuit
looks like I need to make a few more fixes, it looks terrible!
to control a HC via Home Assistant look at https://github.com/proddy/EMS-ESP/wiki/home-assistant
proddy
on 18 Sep 2019
Good luck. Fingers crossed.
By the way Home assistant.
You have to change the 'manual' mode not supported by climate to 'heat'
majdzik84
on 18 Sep 2019
Probably the control with HA circuits does not fully work.
I have configured the HC2 heating circuit.
This is what I get in mqtt explore
majdzik84
on 18 Sep 2019
mine 1.9.1b4 has a similar output
Thermostat stats:
Thermostat: RC35 (ProductID:86 Version:21.08)
Thermostat time is 22:02:42 18/09/2019
Heating Circuit 1
Setpoint room temperature: ? C
Current room temperature: ? C
Day temperature: 19.0 C
Night temperature: 15.0 C
Vacation temperature: 17.0 C
Mode is set to night
Heating Circuit 2
Setpoint room temperature: ? C
Current room temperature: ? C
Day temperature: 18.0 C
Night temperature: 13.5 C
Vacation temperature: 17.0 C
Mode is set to night
Heating Circuit 3
Setpoint room temperature: ? C
Current room temperature: ? C
Day temperature: 19.0 C
Night temperature: 15.0 C
Vacation temperature: 17.0 C
Mode is set to night
Heating Circuit 4
Setpoint room temperature: 14724.0 C
Current room temperature: 1361.6 C
Day temperature: 19.0 C
Night temperature: 15.0 C
Vacation temperature: 17.0 C
Mode is set to night
It’s missing the current temperature..
(00:08:00.854) Thermostat -> Boiler, type 0x1A, telegram: 10 08 1A 00 00 00 00 00 (CRC=91) #data=4
(00:08:02.261) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 00 00 C6 00 00 00 00 00 00 00 00 00 05 04 (CRC=C0) #data=16
(00:08:02.919) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 1E 26 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 02 (CRC=43) #data=27
(00:08:03.637) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 00 00 B4 00 00 00 00 00 00 00 00 00 05 04 (CRC=9D) #data=16
(00:08:03.849) Thermostat -> 0x11, type 0x9D, telegram: 10 11 9D 00 00 (CRC=D7) #data=1
(00:08:04.918) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 01 1B 24 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 01 (CRC=BA) #data=27
(00:08:06.387) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=F2) #data=16
(00:08:07.043) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 1E 26 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=8A) #data=27
Publishing boiler data via MQTT
(00:08:07.762) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=84) #data=16
(00:08:07.993) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 16 12 09 2B 02 01 (CRC=89) #data=8
(00:08:08.918) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 1E 26 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=F8) #data=27
(00:08:09.492) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 16 12 09 2D 02 01 (CRC=36) #data=8
(00:08:26.355) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 00 01 (CRC=0F) #data=3
(00:08:27.762) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 00 00 C6 00 00 00 00 00 00 00 00 00 05 04 (CRC=A8) #data=16
(00:08:30.849) Thermostat -> Boiler, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
(00:08:47.388) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 00 00 00 B4 00 00 00 00 00 00 00 00 00 05 04 (CRC=F5) #data=16
(00:08:47.632) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 6E 00 00 00 C6 00 CC 00 CC 7D 00 7D 00 (CRC=BE) #data=13
Requesting scheduled EMS device data
(00:09:00.978) Thermostat -> Boiler, type 0x1A, telegram: 10 08 1A 00 00 00 00 00 (CRC=91) #data=4
(00:09:02.510) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 00 00 C6 00 00 00 00 00 00 00 00 00 05 04 (CRC=C0) #data=16
(00:09:02.917) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 1E 26 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 02 (CRC=43) #data=27
Publishing boiler data via MQTT
(00:09:03.635) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 00 00 B4 00 00 00 00 00 00 00 00 00 05 04 (CRC=9D) #data=16
(00:09:04.417) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 01 1B 24 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 01 (CRC=BA) #data=27
(00:09:04.473) Thermostat -> 0x11, type 0x9D, telegram: 10 11 9D 00 00 (CRC=D7) #data=1
(00:09:05.761) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=F2) #data=16
(00:09:06.792) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 1E 26 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=8A) #data=27
Publishing boiler data via MQTT
(00:09:07.386) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=84) #data=16
(00:09:08.042) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 1E 26 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=F8) #data=27
(00:09:08.242) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 16 12 0A 2B 02 01 (CRC=91) #data=8
(00:09:08.867) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 16 12 0A 2C 02 01 (CRC=2A) #data=8
(00:09:20.346) Thermostat -> Boiler, type 0x14, telegram: 10 88 14 00 03 (CRC=6E) #data=1
(00:09:20.379) Boiler -> Thermostat, type 0x14, telegram: 08 10 14 00 32 C0 79 (CRC=71) #data=3
(00:09:26.479) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 00 01 (CRC=0F) #data=3
(00:09:28.136) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 00 00 C6 00 00 00 00 00 00 00 00 00 05 04 (CRC=A8) #data=16
(00:09:31.223) Thermostat -> Boiler, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
(00:09:48.136) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 00 00 00 B4 00 00 00 00 00 00 00 00 00 05 04 (CRC=F5) #data=16
(00:09:48.381) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 6E 00 00 00 C6 00 CC
On 18 Sep 2019, at 20:51, majdzik84 notifications@github.com wrote:
Heating circuits have now appeared.
Note that current temperature is missing.I only use two heating circuits (HC1, HC2)
The HC4 temperature is interesting.
https://user-images.githubusercontent.com/31352476/65176780-c2653a00-da55-11e9-8234-0cb27a94b876.png
The default circuit is HC1. How can I change to HC2 to be able to control correctly via Home assistant. Currently, when I try to change the mode it changes in HC1 and not in HC2MQTT topic: thermostat HC1 mode value off
Setting thermostat mode to 0 for heating circuit
MQTT topic: thermostat HC1 mode value auto
Setting thermostat mode to 2 for heating circuit
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW44YRSGMMUEXE2HBI2LTQKJ2BTA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7BCP4Y#issuecomment-532817907, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW4443UJTSTEMXBWB7QHTQKJ2BTANCNFSM4IGOZDBQ.
lmdecroos
on 18 Sep 2019
Think I fixed the temp values that but will double check before committing to the dev branch.
proddy
on 19 Sep 2019
can you try the 1.9.1b5?
proddy
on 19 Sep 2019
current temperature is still missing
I also see that the thermostat_data topic is missing in mqtt
(00:14:23.734) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 04 00 00 00 F5 00 FB 00 FB 7D 00 7D 00 (CRC=D7) #data=13
(00:14:35.323) Thermostat -> Boiler, type 0x14, telegram: 10 88 14 00 03 (CRC=6E) #data=1
(00:14:35.353) Boiler -> Thermostat, type 0x14, telegram: 08 10 14 00 17 86 F9 (CRC=E9) #data=3
(00:14:39.594) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 00 15 04 0F 05 01 (CRC=FD) #data=8
** Warning, we missed the bus - Rx non-idle!
(00:14:40.325) Thermostat -> Boiler, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
(00:14:41.580) Thermostat -> Boiler, type 0x1A, telegram: 10 08 1A 00 2C 64 64 00 (CRC=A9) #data=4
(00:14:41.955) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 64 03 (CRC=C5) #data=3
** Warning, we missed the bus - Rx non-idle!
(00:14:55.738) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 2D 7D 00 00 00 00 00 00 00 00 64 00 2C 00 (CRC=9A) #data=16
(00:14:55.989) Thermostat -> all, type 0x48, telegram: 10 00 48 00 44 00 13 00 F5 00 00 00 00 00 00 00 00 00 05 00 (CRC=77) #data=16
Publishing boiler data via MQTT
Requesting scheduled EMS device data
(00:15:01.986) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 2D 7D 00 00 00 00 00 00 00 00 64 00 2C 00 (CRC=F2) #data=16
(00:15:02.143) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 00 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=BD) #data=27
(00:15:02.862) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 44 00 13 00 F5 00 00 00 00 00 00 00 00 00 05 00 (CRC=1F) #data=16
(00:15:03.519) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 13 15 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FD) #data=27
(00:15:03.987) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=F2) #data=16
** Warning, we missed the bus - Rx non-idle!
(00:15:04.393) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1E) #data=27
(00:15:04.862) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=84) #data=16
(00:15:05.269) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #data=27
(00:15:05.717) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 00 15 04 29 05 01 (CRC=C2) #data=8
(00:15:09.324) Thermostat -> 0x09, type 0x29, telegram: 10 89 29 00 01 (CRC=90) #data=1
(00:15:09.344) 0x09 -> Thermostat, type 0x29, telegram: 09 10 29 00 7B (CRC=CF) #data=1
** Warning, we missed the bus - Rx non-idle!
(00:15:24.233) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 04 00 00 00 F5 00 FB 00 FB 7D 00 7D 00 (CRC=D7) #data=13
** Warning, we missed the bus - Rx non-idle!
(00:15:39.843) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 00 15 05 0F 05 01 (CRC=F5) #data=8
(00:15:40.575) Thermostat -> Boiler, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
(00:15:41.704) Thermostat -> Boiler, type 0x1A, telegram: 10 08 1A 00 2C 64 64 00 (CRC=A9) #data=4
(00:15:42.205) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 64 03 (CRC=C5) #data=3
(00:15:55.987) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 2D 7D 00 00 00 00 00 00 00 00 64 00 2C 00 (CRC=9A) #data=16
(00:15:56.238) Thermostat -> all, type 0x48, telegram: 10 00 48 00 44 00 13 00 F5 00 00 00 00 00 00 00 00 00 05 00 (CRC=77) #data=16
Publishing boiler data via MQTT
Publishing boiler data via MQTT
Publishing hot water and heating states via MQTT
Requesting scheduled EMS device data
(00:16:00.861) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 2D 7D 00 00 00 00 00 00 00 00 64 00 2C 00 (CRC=F2) #data=16
(00:16:01.393) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 00 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=BD) #data=27
(00:16:01.861) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 44 00 13 00 F5 00 00 00 00 00 00 00 00 00 05 00 (CRC=1F) #data=16
(00:16:02.268) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 13 15 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FD) #data=27
(00:16:03.111) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=F2) #data=16
(00:16:03.519) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1E) #data=27
(00:16:03.986) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=84) #data=16
(00:16:04.393) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #data=27
(00:16:04.842) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 00 15 05 28 05 01 (CRC=CE) #data=8
Publishing boiler data via MQTT
** Warning, we missed the bus - Rx non-idle!
(00:16:24.482) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 04 00 00 00 F5 00 FB 00 FB 7D 00 7D 00 (CRC=D7) #data=13
(00:16:34.731) Thermostat -> all, type 0xA2, telegram: 10 00 A2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=99) #data=14
(00:16:35.446) Thermostat -> Boiler, type 0x14, telegram: 10 88 14 00 03 (CRC=6E) #data=1
(00:16:35.458) Boiler -> Thermostat, type 0x14, telegram: 08 10 14 00 17 86 FB (CRC=EB) #data=3
(00:16:40.092) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 00 15 06 0F 05 01 (CRC=ED) #data=8
(00:16:40.698) Thermostat -> Boiler, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
(00:16:41.953) Thermostat -> Boiler, type 0x1A, telegram: 10 08 1A 00 2C 64 64 00 (CRC=A9) #data=4
(00:16:42.704) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 64 03 (CRC=C5) #data=3
** Warning, we missed the bus - Rx non-idle!
(00:16:56.361) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 2D 7D 00 00 00 00 00 00 00 00 64 00 2C 00 (CRC=9A) #data=16
(00:16:56.612) Thermostat -> all, type 0x48, telegram: 10 00 48 00 44 00 13 00 F5 00 00 00 00 00 00 00 00 00 05 00 (CRC=77) #data=16
Publishing boiler data via MQTT
** Warning, we missed the bus - Rx non-idle!
Requesting scheduled EMS device data
(00:17:02.110) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 2D 7D 00 00 00 00 00 00 00 00 64 00 2C 00 (CRC=F2) #data=16
(00:17:02.516) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 00 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=BD) #data=27
(00:17:03.235) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 44 00 13 00 F5 00 00 00 00 00 00 00 00 00 05 00 (CRC=1F) #data=16
(00:17:03.642) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 13 15 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FD) #data=27
(00:17:04.110) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=F2) #data=16
(00:17:04.517) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1E) #data=27
(00:17:04.985) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=84) #data=16
(00:17:05.392) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #data=27
(00:17:05.841) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 00 15 06 29 05 01 (CRC=D2) #data=8
** Warning, we missed the bus - Rx non-idle!
(00:17:24.856) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 04 00 00 00 F5 00 FB 00 FB 7D 00 7D 00 (CRC=D7) #data=13
(00:17:40.341) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 09 00 15 07 0F 05 01 (CRC=E5) #data=8
(00:17:40.823) Thermostat -> Boiler, type 0x35, telegram: 10 08 35 00 01 01 (CRC=00) #data=2
(00:17:42.702) Thermostat -> Boiler, type 0x1A, telegram: 10 08 1A 00 2C 64 64 00 (CRC=A9) #data=4
(00:17:42.830) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 64 03 (CRC=C5) #data=3
(00:17:56.735) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 00 00 2D 7D 00 00 00 00 00 00 00 00 64 00 2C 00 (CRC=9A) #data=16
(00:17:56.986) Thermostat -> all, type 0x48, telegram: 10 00 48 00 44 00 13 00 F5 00 00 00 00 00 00 00 00 00 05 00 (CRC=77) #data=16
Publishing boiler data via MQTT
Publishing boiler data via MQTT
Publishing hot water and heating states via MQTT
Requesting scheduled EMS device data
(00:18:00.609) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 00 00 2D 7D 00 00 00 00 00 00 00 00 64 00 2C 00 (CRC=F2) #data=16
(00:18:01.017) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 00 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=BD) #data=27
(00:18:01.484) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 44 00 13 00 F5 00 00 00 00 00 00 00 00 00 05 00 (CRC=1F) #data=16
(00:18:01.891) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 13 15 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FD) #data=27
(00:18:02.734) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=F2) #data=16
(00:18:03.141) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1E) #data=27
(00:18:03.485) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=84) #data=16
(00:18:04.025) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 13 15 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6C) #data=27
(00:18:04.465) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 09 00 15 07 27 05 01 (CRC=E2) #data=8
I also noticed that the auto temperature correction only works for auto-night. In auto-day shows 0.0 C
majdzik84
on 23 Sep 2019
I'm constantly making small changes. Is this with the latest dev build?
proddy
on 24 Sep 2019
I tested on the version 1.9.1b6.
When trying to install version 1.9.1b7 I have an error
Linking .pio\build\debug\EMS-ESP-1.9.1b7
c:/users/piotrek/.platformio/packages/toolchain-xtensa/bin/../lib/gcc/xtensa-lx106-elf/4.8.2/../../../../xtensa-lx106-elf/bin/ld.exe: cannot open linker script file local.eagle.app.v6.common.ld: No such file or directory
collect2.exe: error: ld returned 1 exit status
*** [.pio\build\debug\EMS-ESP-1.9.1b7] Error 1
majdzik84
on 24 Sep 2019
the error was introduced yesterday when I made a change to the python script that renames the firmware filename - apparently, all the dots didn't go well with Linux. You should be able to build again.
The warning with OneWire you can ignore - it's not my library.
proddy
on 24 Sep 2019
After uploading version 1.9.1b7, the temperatures I wrote about earlier appeared correctly.
After some time, again in Auto-Day mode is (setpoint temp) 0.0C.
I tried to upload the firmware again, reset the stove, but still shows 0.0C
Current room temperature shows correctly
majdzik84
on 24 Sep 2019
can you send the telegrams when in this auto-day mode from types 3E and 48 so I can see what is coming in. You can use the thermostat read command
proddy
on 24 Sep 2019
Today it seems to be working properly. Yesterday evening I changed the setpoint temperature manually on RC35 and the switching took place on the auto-day showing the correct temperature.
I will watch if the problem occurs. Sorry for the confusion. I don't know what caused 0.0C values
majdzik84
on 24 Sep 2019
unfortunately the bug has reappeared.
This time in NIGHT mode
**
(00:58:10.354) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=63) #data=16
(00:58:11.354) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 10 00 E9 00 00 00 00 00 00 00 00 11 05 00 (CRC=24) #data=16
(00:58:33.605) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 00 10 00 E9 00 00 00 00 00 00 00 00 11 05 00 (CRC=4C) #data=16
(00:58:28.480) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=0B) #data=16
(00:59:28.729) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=0B) #data=16
(01:01:29.478) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=0B) #data=16
(01:01:34.353) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 00 10 00 E9 00 00 00 00 00 00 00 00 11 05 00 (CRC=4C) #data=16
After switching to DAY mode, setpoint temp shows temperature day.
Return to night mode does not change - the day temperature is still shown
(01:11:11.218) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=63) #data=16
(01:11:11.749) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=40) #data=27
(01:11:12.218) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 10 00 E8 00 00 00 00 00 00 00 00 11 05 00 (CRC=EC) #data=16
(01:11:12.625) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 10 16 26 0A 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=12) #data=27
(01:11:33.343) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=0B) #data=16
Publishing boiler data via MQTT
(01:11:37.719) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 00 10 00 E8 00 00 00 00 00 00 00 00 11 05 00 (CRC=84) #data=16
(01:12:12.092) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=63) #data=16
(01:12:13.092) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 10 00 E8 00 00 00 00 00 00 00 00 11 05 00 (CRC=EC) #data=16
AUTO-DAY
(02:14:53.164) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=0B) #data=16
(02:14:58.414) Thermostat -> all, type 0x48, telegram: 10 00 48 00 04 03 00 00 EB 00 00 00 00 00 00 00 00 11 05 00 (CRC=FF) #data=16
(02:15:53.663) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=0B) #data=16
(02:15:58.789) Thermostat -> all, type 0x48, telegram: 10 00 48 00 04 03 00 00 EB 00 00 00 00 00 00 00 00 11 05 00 (CRC=FF) #data=16
(02:16:10.162) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=63) #data=16
(02:16:10.912) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 EB 00 00 00 00 00 00 00 00 11 05 00 (CRC=97) #data=16
Ok - I have the data so I'll see what is happening.
proddy
on 25 Sep 2019
I see the problem - not sure how to fix it. Deciphering the telegrams is hard as some of the data is dependent on the state its in. I'll do a new build for you to test. If you get on gitter we can debug real time.
proddy
on 27 Sep 2019
OK
majdzik84
on 27 Sep 2019
I added some thoughts to the wiki here. Once I know how to decipher these telegrams I can implement it correctly. Could you help?
proddy
on 27 Sep 2019
I think I found what is wrong. I'll work on a test build
proddy
on 27 Sep 2019
Great . I was preparing psychologically to decipher the telegrams :)
majdzik84
on 27 Sep 2019
my thinking is that I use the 3E monitor telegram for only reading the current room temperature from the thermostat. And use the 3D working mode telegram for bringing back the setpoint temps for night, day and holiday modes.
I'm just not sure about what happens when you manually override and set a temp. You'll need to try the latest build and show me some 3E/3D messages on HC1 so I can see.
proddy
on 27 Sep 2019
After uploading the latest compilation I can no longer see setpoint temperature.
I see "Program is set to summer mode.
I use HC2
(00:12:06.749) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 03 00 7D 0 0 00 00 00 00 00 00 00 00 11 05 00 (CRC=0B) #data=16
(00:14:09.996) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=63) #data=16
(00:14:10.904) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=40) #data=27
(00:14:11.371) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 E4 00 00 00 00 00 00 00 00 11 05 00 (CRC=CB) #data=16
(00:14:09.996) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=63) #data=16
(00:14:10.904) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=40) #data=27
(00:14:11.371) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 E4 00 00 00 00 00 00 00 00 11 05 00 (CRC=CB) #data=16
After setting the temperature manually no rc35 to 14C
(00:02:01.808) Thermostat -> all, type 0x48, telegram: 10 00 48 00 04 13 1C 00 E4 00 00 00 00 00 00 00 64 11 0F 00 (CRC=01) #data=16
(00:02:02.305) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=63) #data=16
(00:02:02.463) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=40) #data=27
(00:03:52.305) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=0B) #data=16
(00:01:02.598) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=63) #data=16
Publishing boiler data via MQTT
(00:01:02.879) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=40) #data=27
(00:01:03.473) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 13 1C 00 E5 00 00 00 00 00 00 00 64 11 0F 00 (CRC=A1) #data=16
yes I extended to add the mode to summer, holiday etc. No idea if it works since I don't own a RC35 - does that make sense? Is program the correct naming for it?
As for the setpoint, I found no reliable way to determine this, and then thought since there are already 3 setpoint defined (day, night, vacation) just use them. Does this make sense too?
proddy
on 27 Sep 2019
can you tell me what the values for setpoint and current room temps should be for HC1 and HC2? Its hard to figure out your exact environment. What do you expect to see?
proddy
on 27 Sep 2019
It seems to me that the summer / winter operation mode will not work in this situation.
What I would like to get is for sure the Setpoint temperature value for Home Assistant to display it on the thermostat.
I'm only interested in the HC2 circuit because it supports the floor installation. HC1 supports standard heaters where I adjust the thermostatic heads.
On RC35 you can set the temperature:
Day, Night and in automatic mode it switches by itself.
The setpoint temperature at a given moment is Day or Night.
When we change the temperature in automatic mode (regardless of whether auto-day or auto-night) it only changes in setpoint temperature (not in day-temp / night-temp).
When switching to the next time of the auto mode (i.e. from auto-day to auto-night or vice versa), the time set by us is deleted and the day or night temperature is displayed.
Example - my HC2:
Standard Auto-DAY
Setpoint room temperature: 20 C
Current room temperature: 22 C
Day temperature: 20 C
Night temperature: 15 C
When I change the temperature value to 25 C i get
Setpoint room temperature: 25 C
Current room temperature: 22 C
Day temperature: 20 C
Night temperature: 15 C
Setpoint temperature will be valid until the next switching point to auto-night
Standard Auto-NIGHT
Setpoint room temperature: 15 C
Current room temperature: 22 C
Day temperature: 20 C
Night temperature: 15 C
the pre-set temperature of 25C is deleted (it does not permanently change any set value such as day-temp, night-temp)
majdzik84
on 27 Sep 2019
its still a puzzle to me.
Some of the telegrams you posted still confuse me, for example
Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 which basically says HC1 has a setpoint temp of 0.0C and no room temp available
and
Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 E4 00 00 00 00 00 00 00 00 11 05 00 which says HC2 has a setpoint temp of 0.0 C and a room temp of 22.8 C
it's baffling me! Anyway I reverted the last changes and made it so it only responds to broadcasts. I'm away this weekend so will continue next week. If you have any smart thoughts do let me know :-)
proddy
on 28 Sep 2019
I don't think you should look at my HC1. It is not controlled by RC35 only by thermostats on the radiator (only the heating curve is set).So it is not surprising that you cannot see the current temperature.
I'm just thinking. Are the values at the set temperature correct, even 0.0C in automatic mode?
Look:
- In the DAY manual mode we get the Setpoint temperature value, which is the set temperature for the day
In the manual mode NIGHT we get the Setpoint temperature value, which is the set temperature for the night
In AUTO mode, we get 0.0 C (because the auto mode simply switches day and night temperatures) and the Setpoint temperature parameter will change only when a different temperature is specified than in the (auto-day / auto-night) mode.
We have 3 variables at the moment.
- Day temp.
- Night temp.
- Auto temp. (let's take that name)
0x48, telegram: 10 00 48 00 04 13 1C 00 E4 00 00 00 00 00 00 00 64 11 0F 00 (CRC=01) #data=16
Does this telegram contain setpoint temperature 14C?
Could it be possible to make dependencies in the auto mode, e.g.
If setpoint temp. = 0.0C show temperature day or night.
If setpoint temp > 0.0C show auto temp.
In this case, the setpoint temperature would always have a value. In the home assistant on the thermostat the set temperature would be visible.
majdzik84
on 28 Sep 2019
AUTO -DAY
(00:03:14.981) Thermostat -> all, type 0x48, telegram: 10 00 48 00 04 03 00 00 EC 0 0 00 00 00 00 00 00 00 11 05 00 (CRC=B5) #data=16
(00:04:11.355) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 EC 00 00 00 00 00 00 00 00 11 05 00 (CRC=DD) #data=16
(00:06:10.259) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=40) #data=27
After setting the temperature manually no rc35 to 14C -
(00:08:12.601) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 13 1C 00 EC 00 00 00 00 00 00 00 64 11 0F 00 (CRC=7F) #data=16
(00:08:12.007) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2D 39 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=40) #data=27
yup, there it is again in Day-mode with:
10 0B 48 00 04 03 00 00 EC 00 00 00 00 00 00 00 00 11 05 00
the 7th byte after the 03 is the setpoint which is 0 again. I need to figure the logic on when to ignore it and it must have something to the bit masks in the first 2 bytes (04 03). Unfortunately there is very little documentation on this so it'll be trial and error.
proddy
on 30 Sep 2019
something like look at bit 5 of the 6th bit and if its set then read the value. So 04 03 is bad and 04 13 is good. Thing is I need some more examples of x3E/x48 messages from people with an RC35 to verify this.
proddy
on 30 Sep 2019
@lmdecroos , @davidw3591, @Frederik-V, @majo551, @lobocobra
Hi guys! is there a chance for little help?
majdzik84
on 30 Sep 2019
@proddy : yes, no problem I’m happy to help. As I’m traveling a lot these days I have limited availibilty these weeks. I should be able to do some tests from Friday onwards
Sent from my iPhone
On 30 Sep 2019, at 23:21, majdzik84 notifications@github.com wrote:
@lmdecroos , @davidw3591, @Frederik-V, @majo551, @lobocobra
Hi guys! is there a chance for little help?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
lmdecroos
on 1 Oct 2019
@proddy
I have compiled the daily build and all seems to work ok for me
[APP] EMS-ESP version: 1.9.1b11
[APP] MyESP version: 1.2.6
[APP] Build timestamp: 2019-10-04 12:22:39
Thermostat: RC35 (ProductID:86 Version:21.08)
Thermostat time is 12:47:47 04/10/2019
Heating Circuit 1
Current room temperature: 18.3 C
Setpoint room temperature: 15.0 C
Day temperature: 19.0 C
Night temperature: 15.0 C
Vacation temperature: 17.0 C
Mode is set to auto
Heating Circuit 2
Current room temperature: 17.0 C
Setpoint room temperature: 13.5 C
Day temperature: 18.0 C
Night temperature: 13.5 C
Vacation temperature: 17.0 C
Mode is set to night
(00:10:12.351) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 00 1E 00 B7 00 00 00 00 00 00 00 00 00 21 00 (CRC=E2) #data=16
(00:10:13.008) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 1E 26 22 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 02 (CRC=BE) #data=27
(00:10:13.602) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 1B 00 A9 00 00 00 00 00 00 02 00 11 27 00 (CRC=B5) #data=16
(00:10:14.258) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 01 1B 24 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 01 (CRC=BA) #data=27
(00:10:14.851) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=B6) #data=16
(00:10:15.758) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 1E 26 22 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=77) #data=27
(00:10:16.351) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
(00:10:17.008) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 1E 26 22 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=05) #data=27
(00:10:17.582) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 0A 0C 04 26 31 04 01 (CRC=F9) #data=8
(00:10:18.847) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 6E 11 00 00 B7 00 BD 00 BD 7D 00 7D 00 (CRC=ED) #data=13
(00:10:27.438) Thermostat -> 0x11, type 0x9D, telegram: 10 11 9D 00 00 (CRC=D7) #data=1
(00:10:31.472) Thermostat -> all, type 0xA2, telegram: 10 00 A2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (CRC=99) #data=14
(00:10:34.937) Thermostat -> Boiler, type 0x14, telegram: 10 88 14 00 03 (CRC=6E) #data=1
(00:10:34.959) Boiler -> Thermostat, type 0x14, telegram: 08 10 14 00 33 18 61 (CRC=C4) #data=3
(00:10:35.583) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 0A 0C 04 27 07 04 01 (CRC=8E) #data=8
(00:10:45.226) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 00 1E 00 B7 00 00 00 00 00 00 00 00 00 05 00 (CRC=C2) #data=16
(00:10:50.069) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 27 64 01 (CRC=4F) #data=3
(00:10:52.064) Thermostat -> Boiler, type 0x35, telegram: 10 08 35 00 11 01 (CRC=20) #data=2
(00:10:53.693) Thermostat -> Boiler, type 0x1A, telegram: 10 08 1A 00 00 00 00 00 (CRC=91) #data=4
(00:10:57.602) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 00 1B 00 AA 00 00 00 00 00 00 02 00 11 27 00 (CRC=9C) #data=16
(00:11:12.975) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 00 1E 00 B7 00 00 00 00 00 00 00 00 00 05 00 (CRC=AA) #data=16
(00:11:13.632) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 1E 26 22 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 02 (CRC=BE) #data=27
(00:11:14.225) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 1B 00 AA 00 00 00 00 00 00 02 00 11 27 00 (CRC=F4) #data=16
(00:11:14.882) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 01 1B 24 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 01 (CRC=BA) #data=27
(00:11:15.601) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=B6) #data=16
(00:11:16.257) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 1E 26 22 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=77) #data=27
(00:11:16.850) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
(00:11:17.507) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 1E 26 22 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=05) #data=27
(00:11:18.081) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 0A 0C 04 27 31 04 01 (CRC=F1) #data=8
(00:11:19.596) Thermostat -> all, type 0xA3, telegram: 10 00 A3 00 6E 11 00 00 B7 00 BD 00 BD 7D 00 7D 00 (CRC=ED) #data=13
(00:11:27.812) Thermostat -> 0x11, type 0x9D, telegram: 10 11 9D 00 00 (CRC=D7) #data=1
(00:11:36.331) Thermostat -> all, type 0x06, telegram: 10 00 06 00 13 0A 0C 04 28 07 04 01 (CRC=F6) #data=8
(00:11:45.725) Thermostat -> all, type 0x3E, telegram: 10 00 3E 00 04 00 1E 00 B7 00 00 00 00 00 00 00 00 00 05 00 (CRC=C2) #data=16
(00:11:50.568) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 27 64 01 (CRC=4F) #data=3
(00:11:51.943) Thermostat -> 0x21, type 0xAC, telegram: 10 21 AC 00 05 00 01 (CRC=0F) #data=3
(00:11:52.688) Thermostat -> Boiler, type 0x35, telegram: 10 08 35 00 11 01 (CRC=20) #data=2
(00:11:53.942) Thermostat -> Boiler, type 0x1A, telegram: 10 08 1A 00 00 00 00 00 (CRC=91) #data=4
(00:11:57.850) Thermostat -> all, type 0x48, telegram: 10 00 48 00 00 00 1B 00 AA 00 00 00 00 00 00 02 00 11 05 00 (CRC=D8) #data=16
(00:12:10.973) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 00 1E 00 B7 00 00 00 00 00 00 00 00 00 05 00 (CRC=AA) #data=16
(00:12:11.380) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 1E 26 22 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 02 (CRC=BE) #data=27
(00:12:11.974) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 00 00 1B 00 AA 00 00 00 00 00 00 02 00 11 05 00 (CRC=B0) #data=16
(00:12:12.631) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 01 1B 24 22 00 28 00 00 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 02 01 (CRC=BA) #data=27
(00:12:13.224) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=B6) #data=16
(00:12:13.881) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 1E 26 22 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=77) #data=27
(00:12:14.474) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
(00:12:15.256) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 1E 26 22 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=05) #data=27
(00:12:15.829) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 0A 0C 04 28 2F 04 01 (CRC=F1) #data=8
My RC35 is controlling HC1 and my RC20F is controlling HC2
Previously i was running :
[APP] EMS-ESP version: 1.9.1b8
[APP] MyESP version: 1.2.4
[APP] Build timestamp: 2019-09-26 22:38:44
and all values where also showing ok
During summer I turn the heating temperature on my boiler to zero, so the my heating is off ( this is also the message i get on my RC35 thermostat)
When my heating is off, then the set point temperature is always 0 (zero)
Hope this helps otherwise let me know which tests and logs you need
On 1 Oct 2019, at 02:58, Luk-Marie Decroos lmd@telenet.be wrote:
@proddy : yes, no problem I’m happy to help. As I’m traveling a lot these days I have limited availibilty these weeks. I should be able to do some tests from Friday onwards
Sent from my iPhone
On 30 Sep 2019, at 23:21, majdzik84 <[email protected] notifications@github.com> wrote:
@lmdecroos https://github.com/lmdecroos , @davidw3591 https://github.com/davidw3591, @Frederik-V https://github.com/Frederik-V, @majo551 https://github.com/majo551, @lobocobra https://github.com/lobocobra
Hi guys! is there a chance for little help?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW4455INKO4V7BBUU7ZOTQMJUVVA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD77ERDA#issuecomment-536758412, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW44424HPRX3SF3ECVGLLQMJUVVANCNFSM4IGOZDBQ.
lmdecroos
on 4 Oct 2019
thanks @lmdecroos for providing this - that was really useful. I think the current implementation hopefully works in all situations now. Let's see...
proddy
on 4 Oct 2019
@proddy you're welcome
As all the data in the gateway of my both HC’s are now correct, the next stap is to get both HC in domoticz :)
Until now i was using the nefit v0.0.1 plugin and today I discovered the new "ems-esp-domoticz-plugin” plugin from bbqkees
The plug-in is only monitoring and passing the data of the first HC, with a small change I’m able to pass the data from my second HC
lmd@pi01:~/Downloads/ems-esp-domoticz-plugin $ diff plugin.py plugin.py.org
287c287
< self.topics = list(["home/ems-esp/thermostat_data2", "home/ems-esp/boiler_data", "home/ems-esp/STATE"])
self.topics = list(["home/ems-esp/thermostat_data", "home/ems-esp/boiler_data", "home/ems-esp/STATE”])
I will probably able to customise the script to monitor two HC’s , but as I’m not a programmer it would not very nice looking
Are there plans to update the plugin to pass that data from all available HC’s in the gateway to the Domoticz ?
On 4 Oct 2019, at 13:18, Proddy notifications@github.com wrote:
thanks @lmdecroos https://github.com/lmdecroos for providing this - that was really useful. I think the current implementation hopefully works in all situations now. Let's see...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW442RNKLXGPZQQ4OIXYDQM4RB3A5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEALKX3Q#issuecomment-538356718, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW443LFEFQPYPVNK2H5ETQM4RB3ANCNFSM4IGOZDBQ.
lmdecroos
on 4 Oct 2019
I don't use Domoticz personally and not supporting it. bbqkees and a few others do. If you upgrade the script please do a PR.
proddy
on 5 Oct 2019
@proddy
Can you advise what that logic behind the MQTT subscriptions?
I have 2 HC’s and the gateway publishes 2 topics “thermostat_data” and “thermostat_data2” , I would expect that my first HC has topic name”thermostat_data1”. Or are you stil using topic “thermostat_data” for backwards compatibility ?
Also the payloads naming are the same between both topics. I would expect unique topics for every HC as in the "MQTT subscriptions" list
MQTT publish log:
Topic:thermostat_data Payload:{"thermostat_hc":"1","thermostat_seltemp":19,"thermostat_currtemp":19.1,"thermostat_daytemp":19,"thermostat_nighttemp":15,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":32,"thermostat_mode":"auto"}
Topic:thermostat_data2 Payload:{"thermostat_hc":"2","thermostat_seltemp":13.5,"thermostat_currtemp":16.3,"thermostat_daytemp":18,"thermostat_nighttemp":13.5,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"night"}
Topic:start Payload:start
Topic:shower_timer Payload:0
Topic:shower_alert Payload:0
Topic:boiler_data Payload:{"wWComfort":"Hot","wWSelTemp":56,"selFlowTemp":32,"selBurnPow":100,"curBurnPow":0,"pumpMod":0,"wWCurTmp":57.9,"wWCurFlow":0,"curFlowTemp":31.1,"retTemp":28.5,"sysPress":1,"boilTemp":30,"wWActivated":"on","burnGas":"off","heatPmp":"off","fanWork":"off","ignWork":"off","wWCirc":"off","wWHeat":"off","burnStarts":26163,"burnWorkMin":402742,"heatWorkMin":363359,"ServiceCode":"0Y","ServiceCodeNumber":204}
Topic:tapwater_active Payload:0
Topic:heating_active Payload:0
MQTT subscriptions:
Topic:home/ems-esp/thermostat_cmd_temp
Topic:home/ems-esp/thermostat_cmd_mode
Topic:home/ems-esp/thermostat_daytemp
Topic:home/ems-esp/thermostat_nighttemp
Topic:home/ems-esp/thermostat_holidayttemp
Topic:home/ems-esp/thermostat_cmd_temp1
Topic:home/ems-esp/thermostat_cmd_mode1
Topic:home/ems-esp/thermostat_daytemp1
Topic:home/ems-esp/thermostat_nighttemp1
Topic:home/ems-esp/thermostat_holidayttemp1
Topic:home/ems-esp/thermostat_cmd_temp2
Topic:home/ems-esp/thermostat_cmd_mode2
Topic:home/ems-esp/thermostat_daytemp2
Topic:home/ems-esp/thermostat_nighttemp2
Topic:home/ems-esp/thermostat_holidayttemp2
Topic:home/ems-esp/thermostat_cmd_temp3
Topic:home/ems-esp/thermostat_cmd_mode3
Topic:home/ems-esp/thermostat_daytemp3
Topic:home/ems-esp/thermostat_nighttemp3
Topic:home/ems-esp/thermostat_holidayttemp3
Topic:home/ems-esp/thermostat_cmd_temp4
Topic:home/ems-esp/thermostat_cmd_mode4
Topic:home/ems-esp/thermostat_daytemp4
Topic:home/ems-esp/thermostat_nighttemp4
Topic:home/ems-esp/thermostat_holidayttemp4
On 5 Oct 2019, at 14:13, Proddy notifications@github.com wrote:
I don't use Domoticz personally and not supporting it. bbqkees and a few others do. If you upgrade the script please do a PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW44YZ6T34Q62DEIONRV3QNCAIFA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEANRBMA#issuecomment-538644656, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW4453SXUZAQIJXUQSI73QNCAIFANCNFSM4IGOZDBQ.
lmdecroos
on 6 Oct 2019
yes I left the topic “thermostat_data” in for backwards compatibility, but what you just shown makes me think I got it wrong. If there is a single HC its just “thermostat_data” and if there are multiple it should be “thermostat_dataX”. I'll check the code again.
proddy
on 6 Oct 2019
made a change in b3
proddy
on 6 Oct 2019
with b3 I have :
Topic:thermostat_data1 Payload:{"thermostat_seltemp":15,"thermostat_currtemp":19.1,"thermostat_daytemp":19,"thermostat_nighttemp":15,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"auto"}
Topic:thermostat_data2 Payload:{"thermostat_seltemp":13.5,"thermostat_currtemp":16.9,"thermostat_daytemp":18,"thermostat_nighttemp":13.5,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"night”}
is this the aim or should the subscriptions also be unique ?
On 6 Oct 2019, at 21:31, Proddy notifications@github.com wrote:
made a change in b3
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW446UAPMYZHP5UWZPB2DQNI4HLA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOSAZY#issuecomment-538779751, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW445HPBY5MNMD46JOPKTQNI4HLANCNFSM4IGOZDBQ.
lmdecroos
on 7 Oct 2019
subscriptions also unique too.
proddy
on 7 Oct 2019
The topics are now correct for both HC’s but the subscriptions are not unique
Topic:thermostat_data1 Payload:{"thermostat_seltemp":15,"thermostat_currtemp":19.2,"thermostat_daytemp":19,"thermostat_nighttemp":15,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"auto"}
Topic:thermostat_data2 Payload:{"thermostat_seltemp":13.5,"thermostat_currtemp":16.3,"thermostat_daytemp":18,"thermostat_nighttemp":13.5,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"night"}
testing with :
[APP] EMS-ESP version: 1.9.2b4
[APP] MyESP version: 1.2.9
[APP] Build timestamp: 2019-10-10 21:48:59
On 7 Oct 2019, at 10:48, Proddy notifications@github.com wrote:
Closed #162 https://github.com/proddy/EMS-ESP/issues/162.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW444HYVNJLCT3TO62JU3QNLZVVA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUBSVITI#event-2690995277, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDW446AOHRLKLSXRIH6MUDQNLZVVANCNFSM4IGOZDBQ.
lmdecroos
on 10 Oct 2019
Subscription is on topics, and they are unique right? Anyway I’m changing
all of this to reduce the number of topics this weekend
On Thu, 10 Oct 2019 at 22:05, lmdecroos notifications@github.com wrote:
The topics are now correct for both HC’s but the subscriptions are not
uniqueTopic:thermostat_data1
Payload:{"thermostat_seltemp":15,"thermostat_currtemp":19.2,"thermostat_daytemp":19,"thermostat_nighttemp":15,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"auto"}
Topic:thermostat_data2
Payload:{"thermostat_seltemp":13.5,"thermostat_currtemp":16.3,"thermostat_daytemp":18,"thermostat_nighttemp":13.5,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"night"}testing with :
[APP] EMS-ESP version: 1.9.2b4
[APP] MyESP version: 1.2.9
[APP] Build timestamp: 2019-10-10 21:48:59On 7 Oct 2019, at 10:48, Proddy notifications@github.com wrote:
Closed #162 https://github.com/proddy/EMS-ESP/issues/162.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <
https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW444HYVNJLCT3TO62JU3QNLZVVA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUBSVITI#event-2690995277>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/ANDW446AOHRLKLSXRIH6MUDQNLZVVANCNFSM4IGOZDBQ
.—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=AAJMO6CUMX5UG5NGN6ZE7QTQN6DHJA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA5WKYI#issuecomment-540763489,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJMO6FNPBN5ULEZO4WA5DLQN6DHJANCNFSM4IGOZDBQ
.
proddy
on 10 Oct 2019
HC1 is missing, only HC2 is part pf the MQTT messages
[APP] EMS-ESP version: 1.9.2b6
[APP] MyESP version: 1.2.10
[APP] Build timestamp: 2019-10-13 16:36:27
MQTT publish log:
Topic:start Payload:start
Topic:boiler_data Payload:{"wWComfort":"Hot","wWSelTemp":56,"wWDesiredTemp":70,"selFlowTemp":7,"selBurnPow":0,"curBurnPow":0,"pumpMod":0,"wWCircPump":0,"wWCurTmp":54.3,"wWCurFlow":0,"curFlowTemp":29.4,"retTemp":30.8,"switchTemp":19.8,"sysPress":1,"boilTemp":31.2,"wWActivated":"on","burnGas":"off","flameCurr":0,"heatPmp":"off","fanWork":"off","ignWork":"off","wWCirc":"off","heating_temp":76,"pump_mod_max":91,"pump_mod_min":30,"wWHeat":"off","wWStarts":5505,"wWWorkM":39490,"UBAuptime":3361837,"burnStarts":26230,"burnWorkMin":403582,"heatWorkMin":364092,"ServiceCode":"0H","ServiceCodeNumber":203}
Topic:tapwater_active Payload:0
Topic:heating_active Payload:0
Topic:shower_data Payload:{"timer":"0","alert":"0","duration":"n/a"}
Topic:thermostat_data Payload:{"hc2":{"seltemp":13.5,"currtemp":19.5,"daytemp":18,"nighttemp":13.5,"holidayttemp":17,"heating
On 10 Oct 2019, at 23:30, Proddy notifications@github.com wrote:
Subscription is on topics, and they are unique right? Anyway I’m changing
all of this to reduce the number of topics this weekendOn Thu, 10 Oct 2019 at 22:05, lmdecroos notifications@github.com wrote:
The topics are now correct for both HC’s but the subscriptions are not
uniqueTopic:thermostat_data1
Payload:{"thermostat_seltemp":15,"thermostat_currtemp":19.2,"thermostat_daytemp":19,"thermostat_nighttemp":15,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"auto"}
Topic:thermostat_data2
Payload:{"thermostat_seltemp":13.5,"thermostat_currtemp":16.3,"thermostat_daytemp":18,"thermostat_nighttemp":13.5,"thermostat_holidayttemp":17,"thermostat_heatingtype":1,"thermostat_circuitcalctemp":5,"thermostat_mode":"night"}testing with :
[APP] EMS-ESP version: 1.9.2b4
[APP] MyESP version: 1.2.9
[APP] Build timestamp: 2019-10-10 21:48:59On 7 Oct 2019, at 10:48, Proddy notifications@github.com wrote:
Closed #162 https://github.com/proddy/EMS-ESP/issues/162.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <
https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW444HYVNJLCT3TO62JU3QNLZVVA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUBSVITI#event-2690995277>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/ANDW446AOHRLKLSXRIH6MUDQNLZVVANCNFSM4IGOZDBQ
.—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=AAJMO6CUMX5UG5NGN6ZE7QTQN6DHJA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA5WKYI#issuecomment-540763489,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJMO6FNPBN5ULEZO4WA5DLQN6DHJANCNFSM4IGOZDBQ
.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW44YMTA3TAXE6CEIT64TQN6NIDA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA6BIMA#issuecomment-540808240, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANDW447F56SHQPEFBFQVKOTQN6NIDANCNFSM4IGOZDBQ.
lmdecroos
on 13 Oct 2019
oops. try b7 ?
proddy
on 13 Oct 2019
no change, only HC2 is published
have the EMS gateway and MQTT explorer running for 5 minutes
On 13 Oct 2019, at 17:30, Proddy notifications@github.com wrote:
oops. try b7 ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW4444VJEAUYKURO4Q4ZTQOM5H3A5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBCYXCQ#issuecomment-541428618, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANDW44YVGDOOXPCVZF3RK6TQOM5H3ANCNFSM4IGOZDBQ.
lmdecroos
on 13 Oct 2019
Checked the MQTT explorer values and it seems it sending both at the same time and only the last one save is saved
{"hc2":{"seltemp":13.5,"currtemp":19.6,"daytemp":18,"nighttemp":13.5,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"night”}}
{"hc1":{"seltemp":19,"currtemp":20.3,"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"auto”}}
On 13 Oct 2019, at 17:49, Luk-Marie Decroos lmd@telenet.be wrote:
no change, only HC2 is published
have the EMS gateway and MQTT explorer running for 5 minutesOn 13 Oct 2019, at 17:30, Proddy <[email protected] notifications@github.com> wrote:
oops. try b7 ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW4444VJEAUYKURO4Q4ZTQOM5H3A5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBCYXCQ#issuecomment-541428618, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANDW44YVGDOOXPCVZF3RK6TQOM5H3ANCNFSM4IGOZDBQ.
lmdecroos
on 13 Oct 2019
think I fixed it. still calling in b7
proddy
on 13 Oct 2019
[MQTT] Error publishing to home/ems-esp/thermostat_data with payload {"hc1":{"seltemp":19,"currtemp":20.3,"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"auto"},"hc2":{"seltemp":13.5,"currtemp":19.7,"daytemp":18,"nighttemp":13.5,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"night"}}, error 0
a syntax error ??
On 13 Oct 2019, at 18:13, Proddy notifications@github.com wrote:
think I fixed it. still calling in b7
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW447N6GZYIPC6JUZVNXTQONCLDA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBCZSZY#issuecomment-541432167, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANDW444DVG5JJMETPPDUUG3QONCLDANCNFSM4IGOZDBQ.
lmdecroos
on 13 Oct 2019
yes I'm seeing those too, its kinda random and I think they've always been there but I've suppressed the warnings. I'm also looking into this. The MQTT is still sent.
proddy
on 13 Oct 2019
It seems as long the subtopics are not complete between HC1 and HC2, the data fro HC2 comes through
once the EMS gateway has all values ( subtopics) for both HC’s that only the value of HC1 is taken in account
the first 3 messages after a restart ( and filtered on HC2)
{"hc1":{"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"mode":"auto"},"hc2":{"daytemp":18,"nighttemp":13.5,"holidayttemp":17,"heatingtype":1,"mode":"night"}}
{"hc1":{"seltemp":19,"currtemp":20.8,"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"auto"},"hc2":{"daytemp":18,"nighttemp":13.5,"holidayttemp":17,"heatingtype":1,"mode":"night"}}
{"hc1":{"seltemp":19,"currtemp":20.8,"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"auto"},"hc2":{"seltemp":13.5,"currtemp":19.6,"daytemp":18,"nighttemp":13.5,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"night"}}
on the next update all values are published, but only the values from HC1 are coming through
On 13 Oct 2019, at 18:50, Proddy notifications@github.com wrote:
yes I'm seeing those too, its kinda random and I think they've always been there but I've suppressed the warnings. I'm also looking into this. The MQTT is still sent.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW445AKG22E247RQLEVO3QONGVHA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBC2KDY#issuecomment-541435151, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANDW44YKJIVZZVR5FCPREULQONGVHANCNFSM4IGOZDBQ.
lmdecroos
on 13 Oct 2019
sorry, not sure I understand. What is happening and what is the expected behaviour ?
proddy
on 13 Oct 2019
When looking at MQTT explorer, after an EMS gateway reboot the MQTT messages contains {"hc1":{“day…. and ,"hc2":{“dayt ….
But once all values for HC1 and HC2 are published, the MQTT receiver seems to be confused as it received 2 times the values ( one for HC1 another for HC2) and it takes only the one for HC1 in account
it seems that the MQTT message can’t handle 2 times the values in the same topic
On 13 Oct 2019, at 21:02, Proddy notifications@github.com wrote:
sorry, not sure I understand. What is happening and what is the expected behaviour ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW442EBGHPVMMRYYWL2ODQONWE3A5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBC5KYQ#issuecomment-541447522, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANDW44ZZSQMY25ASG2MQAZTQONWE3ANCNFSM4IGOZDBQ.
lmdecroos
on 13 Oct 2019
still confused, sorry! Is the payload on the thermostat_data correct? If so its up to the MQTT receiver on how to interpret the data. I'm using Home Assistant and with templates it is working.
proddy
on 13 Oct 2019
Yes, payload thermostat data in the EMS gateway seems to be correct ( at least it contains all details for both HC’s) , but the MQTT explorer is not able to interpreet it correct.
it’s understand only the values for HC1, it ignores the values for HC2
Only on the first (3) messages after a reboot, when it the EMS is still missing some data, the values of HC2 are in the message received / interpreted by MQTT explorer
message 1 :
{"hc1":{"seltemp":19,"currtemp":20.8,"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"auto”}}
message 2 :
{"hc1":{"seltemp":19,"currtemp":20.8,"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"auto"},"hc2":{"daytemp":18,"nighttemp":13.5,"holidayttemp":17,"heatingtype":1,"mode":"night”}}
message 3 :
{"hc1":{"seltemp":19,"currtemp":20.8,"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"auto"},"hc2":{"seltemp":13.5,"currtemp":19.6,"daytemp":18,"nighttemp":13.5,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"night"}}
message 4 and later
{"hc1":{"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"mode":"auto”}}
so from message 4 onwards all the details of HC2 are missing on the MQTT receiver side
On 13 Oct 2019, at 21:28, Proddy notifications@github.com wrote:
thermostat_data correct
lmdecroos
on 13 Oct 2019
ahh, found the error. very silly of me. I'll do a commit soon.
proddy
on 13 Oct 2019
well done, seems to be fixed
{"hc1":{"seltemp":19,"currtemp":21,"daytemp":19,"nighttemp":15,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"auto"},"hc2":{"seltemp":13.5,"currtemp":19.9,"daytemp":18,"nighttemp":13.5,"holidayttemp":17,"heatingtype":1,"circuitcalctemp":5,"mode":"night”}}
I will contact bbqkees and ask him to update his plugin
On 13 Oct 2019, at 21:59, Proddy notifications@github.com wrote:
ahh, found the error. very silly of me. I'll do a commit soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW44562MYGPYVDZ3J7623QON4ZHA5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBC6VRY#issuecomment-541452999, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANDW444DTJTPVJNWLLESRCTQON4ZHANCNFSM4IGOZDBQ.
lmdecroos
on 14 Oct 2019
ok closing this issue for now.
proddy
on 14 Oct 2019
1.9.2b9
I noticed that setpoint temperature again does not give the correct value in auto-day, auto-night mode.
Example: When changing from OFF (night) mode to auto mode it still shows off-night temperature instead of auto-day.
Should now show 22C (auto-day)
> (00:59:10.206) Thermostat -> me, type 0x3E, telegram: 10 0B 3E 00 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00 (CRC=63) #data=16
> (00:59:10.488) Thermostat -> me, type 0x3D, telegram: 10 0B 3D 00 01 2A 2C 26 00 28 00 02 00 05 05 2D 01 01 04 3C 06 39 01 00 3C FF 0D 05 05 03 00 (CRC=3E) #data=27
> Publishing external sensor data via MQTT
> (00:59:11.081) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 EF 00 00 00 00 00 00 00 00 11 05 00 (CRC=9C) #data=16
> (00:59:11.613) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 28 2C 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FF) #data=27
> Publishing external sensor data via MQTT
> (00:59:11.957) Thermostat -> me, type 0x52, telegram: 10 0B 52 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=B6) #data=16
> (00:59:12.363) Thermostat -> me, type 0x51, telegram: 10 0B 51 00 00 28 2C 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=1C) #data=27
> (00:59:13.332) Thermostat -> me, type 0x5C, telegram: 10 0B 5C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 (CRC=C0) #data=16
> (00:59:14.113) Thermostat -> me, type 0x5B, telegram: 10 0B 5B 00 00 28 2C 26 00 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 11 05 05 03 02 (CRC=6E) #data=27
> (00:59:14.562) Thermostat -> me, type 0x06, telegram: 10 0B 06 00 13 0A 0D 10 1A 24 02 01 (CRC=21) #data=8
oh no, this again. Did it ever work? The logic is just too difficult to figure out as 1) I don't own an RC35 and 2) I never really understood what auto-day and auto-night really means.
Do you think you could take a look at code and with your example telegrams do a PR ? Otherwise we'll just be going back and forth for weeks and I don't have the time.
proddy
on 16 Oct 2019
unfortunately I am not a programmer. I don't know how to do PR :(
A few versions ago (i thing 1.9.1b11 ) I have the impression that in automatic mode it just jumped between day-temp and night-temp.
RC35 has something like a temporary temperature - but I let it go.
So it's day-temp and night-temp - automatic mode just switches these temperatures (auto-day - shows day temp) and in the evening auto-night (shows nighttemp)
EDIT:
I checked in 1.9.1 stable - unfortunately it is the same - sometimes everything is ok, sometimes not. In this case, we are waiting for someone smart who has rc35 :)
majdzik84
on 16 Oct 2019
I can do the programming, I just need someone to create the rules.
The logic now is in ems.cpp function _process_RC35StatusMessage() and goes:
- look for telegrams with type 3E (HC1) and 48 (HC2)
- ignore whole telegram is 15th byte of the data block is 0
- set the setpoint temperature using the 3rd byte of that data block (value is *2), but ignore if value is 0
In your examples the data blocks look like
For 0x3E (HC1): 04 03 00 7D 00 00 00 00 00 00 00 00 00 11 05 00
For 0x48 (HC2): 04 03 00 00 EF 00 00 00 00 00 00 00 00 11 05 00
can you help define what it should be?
proddy
on 16 Oct 2019
Probably, before I get the ideas of bytes, etc. it will pass a little :)
In the meantime, I was able to intercept telegrams after RC35 changed auto-day mode to auto-night.
Maybe it will be helpful to correctly determine the switch point between day and night mode (in auto mode)
Auto-night - RC35
(00:29:12.276) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 01 00 00 EE 00 00 00 00 00 00 00 00 00 05 00 (CRC=3C) #data=16
Auto-day - RC35
(00:34:10.506) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 F1 00 00 00 00 00 00 00 00 11 05 00 (CRC=24) #data=16
Auto-Day- (change in HA)
(00:24:13.139) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 EF 00 00 00 00 00 00 00 00 11 05 00 (CRC=9C) #data=16
Auto-day (change in HA from night mode) < incorrect setpoint (its still night temp)
(00:49:11.492) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 F0 00 00 00 00 00 00 00 00 11 05 00 (CRC=EC) #data=16
Auto-day (change in HA from day mode (heat))
(00:54:11.988) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 03 00 00 F0 00 00 00 00 00 00 00 00 11 17 00 (CRC=C8) #data=16
Auto-night(change in HA from day mode(heat)) < incorrect setpoint (its still day temp)
(01:26:11.460) Thermostat -> me, type 0x48, telegram: 10 0B 48 00 04 01 00 00 F3 00 00 00 00 00 00 01 00 00 17 00 (CRC=F1) #data=16
majdzik84
on 16 Oct 2019
In all those examples, the setpoint temperature is 0.0C. I've highlighted them below:
Auto-night - RC35
telegram: 10 0B 48 00 04 01 00 00 EE 00 00 00 00 00 00 00 00 00 05 00
Auto-day - RC35
telegram: 10 0B 48 00 04 03 00 00 F1 00 00 00 00 00 00 00 00 11 05 00
Auto-Day- (change in HA)
telegram: 10 0B 48 00 04 03 00 00 EF 00 00 00 00 00 00 00 00 11 05 00
Auto-day (change in HA from night mode) < incorrect setpoint (its still night temp)
telegram: 10 0B 48 00 04 03 00 00 F0 00 00 00 00 00 00 00 00 11 05 00
Auto-day (change in HA from day mode (heat))
telegram: 10 0B 48 00 04 03 00 00 F0 00 00 00 00 00 00 00 00 11 17 00
Auto-night(change in HA from day mode(heat)) < incorrect setpoint (its still day temp)
telegram: 10 0B 48 00 04 01 00 00 F3 00 00 00 00 00 00 01 00 00 17 00
But there's another byte we could read adjacent to the setpoint. I'm not sure what it is. I've listed the values below. Can you see if this matches anything you're seeing?
Auto-night - RC35
telegram: 10 0B 48 00 04 01 00 00 EE 00 00 00 00 00 00 00 00 00 05 00 (value 23.8)
Auto-day - RC35
telegram: 10 0B 48 00 04 03 00 00 F1 00 00 00 00 00 00 00 00 11 05 00 (value 24,1)
Auto-Day- (change in HA)
telegram: 10 0B 48 00 04 03 00 00 EF 00 00 00 00 00 00 00 00 11 05 00 (value 23,9)
Auto-day (change in HA from night mode) < incorrect setpoint (its still night temp)
telegram: 10 0B 48 00 04 03 00 00 F0 00 00 00 00 00 00 00 00 11 05 00 (value 24)
Auto-day (change in HA from day mode (heat))
telegram: 10 0B 48 00 04 03 00 00 F0 00 00 00 00 00 00 00 00 11 17 00 (value 24)
Auto-night(change in HA from day mode(heat)) < incorrect setpoint (its still day temp)
telegram: 10 0B 48 00 04 01 00 00 F3 00 00 00 00 00 00 01 00 00 17 00 (value 24,3)
proddy
on 16 Oct 2019
Yes.I think it's current room temperature
majdzik84
on 16 Oct 2019
From each of the examples I need to know what the expected setpoint values should be, so I can hunt them down in the telegrams.
proddy
on 16 Oct 2019
I did a few tests with 1.9.1 release and 1.9.2b10 and all temperatures are correct.
when using 1.9.1 it takes up to 2 minutes before the change in mode ( day/ night/ auto) are reflected.
when using 1.9.2b10 it takes up to 5 minutes or more
even after 20 minutes i have only :
Thermostat stats:
Thermostat: RC20F (ProductID:93 Version:02.00)
Thermostat time is 18:05:59 16/10/2019
Heating Circuit 1
Current room temperature: 19.6 C
Setpoint room temperature: 19.0 C
Heating Circuit 2
Current room temperature: 18.3 C
Setpoint room temperature: 13.5 C
Mode is set to night
On 16 Oct 2019, at 17:37, majdzik84 notifications@github.com wrote:
Yes.I think it's current room temperature
https://user-images.githubusercontent.com/31352476/66934937-8c5aac00-f03b-11e9-91f9-50f3b1d7a915.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/162?email_source=notifications&email_token=ANDW44Z6V4WJKOMZUL7IV33QO4YJ5A5CNFSM4IGOZDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBM6ISA#issuecomment-542762056, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANDW447P2LB2ZJHQPZNGM2TQO4YJ5ANCNFSM4IGOZDBQ.
lmdecroos
on 16 Oct 2019
Of course, the temperatures work correctly.
- In night mode it is ok
- In day mode it is ok.
- How to manually set the knob on RC35 the set temperature in auto mode is also ok.
This is the so-called temporary temperature, which is displayed only until the next switching point (that's why the telegram shows 0.0C because it was not set).
After thinking, I think that it is easier to control the thermostat, e.g. in Home assistant by simply setting the day or night temperature because the auto mode switches them on at the appropriate times.
I think Proddy once inserted a dependency.
If in auto mode set temperature = 0.0C show day temp or night temp (depending on rc35 is in auto-day or auto-night mode).
The problem is that if the night mode 20C switched to auto mode (which is currently in daytime auto mode) then the temperature does not change to 22C (day temp) but remains at 20C.
Is it possible to read the current status of the automatic mode (whether it is auto-day or auto-night) and depending on it display the correct temperature (in setpoint temperature in auto mode) - of course, as I wrote earlier only when the value setpoint temperature (temporary) is equal to 0.0C.
I hope this clarifies things a little.
majdzik84
on 16 Oct 2019
I don't know what it is caused by, but I noticed that there are times when all switches work properly but it also happens that the temperatures are not updated.
Since last night at my switch again correctly.
majdzik84
on 17 Oct 2019
I should be able to find the auto-day and auto-night modes. They must be in 0x3D (HC1) or 0x47 (HC2) if you could send along some examples.
proddy
on 18 Oct 2019
Auto-Day (temp. day 22C)
(03:01:03.793) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 28 2C 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FF) #data=27
Auto-Night (temp. night 20C)
(03:04:02.057) Thermostat -> me, type 0x47, telegram: 10 0B 47 00 03 28 2C 26 0A 28 00 02 00 05 05 2D 01 01 04 4B 05 4B 01 00 3C FF 0D 05 05 02 02 (CRC=FF) #data=27
majdzik84
on 19 Oct 2019
lol, they're identical so its not in that telegram!
proddy
on 19 Oct 2019
yes, they are identical - to be sure I checked 2 times
majdzik84
on 19 Oct 2019
closing.
proddy
on 13 Nov 2019
Related issues
jorritsmit
·
12Comments
realthk
·
16Comments
Oderik
·
26Comments
Chuckame
·
10Comments
mtvw
·
13Comments