FredericMa
commented
3 years ago Yes, indeed, I don't see those. So never missed them until now that I know 😄 This is the output of the show command:
Boiler: HT3 (DeviceID:0x08, ProductID:95, Version:23.04)
Hot tap water: off
Central heating: off
Warm Water activated: on
Warm Water charging type: 3-way valve
Warm Water circulation pump available: off
Warm Water circulation pump freq: 1x3min
Warm Water circulation active: off
Warm Water comfort setting: Hot
Warm Water disinfection temperature: 75°C
Warm Water selected temperature: 50°C
Warm Water set temperature: 50°C
Warm Water current temperature (intern): 64.7°C
Warm Water current temperature (extern): 64.7°C
Warm Water current tap water flow: 0.0l/min
Warm Water # starts: 802
Warm Water active time: 12 days 11 hours 32 minutes
Warm Water charging: off
Warm Water disinfecting: off
Selected flow temperature: 0°C
Current flow temperature: 29.5°C
Gas: off
Boiler pump: off
Fan: off
Ignition: off
Burner selected max power: 100%
Burner current power: 0%
System service code: (0)
Heating temperature setting on the boiler: 66°C
Boiler circuit pump modulation max power: 100%
Boiler circuit pump modulation min power: 10%
Boiler circuit pump delay time: 3min
Boiler temp hysteresis on: -5°C
Boiler temp hysteresis off: 0°C
Boiler burner min period: 3min
Boiler burner min power: 0%
Boiler burner max power: 100%
Outside temperature: 25.7°C
Pump modulation: 0%
Burner # starts: 104927
Total burner operating time: 364 days 11 hours 56 minutes
Total heat operating time: 352 days 0 hours 23 minutes
Thermostat: Junkers FW200 (DeviceID:0x10 ProductID:106, Version:12.14)
Clock: 10:40:13 17/08/2020
Heating Circuit 1:
Current room temperature: 23.7°C
Setpoint room temperature: 15.0°C
Mode: manual
Mode Type: nofrost
Heating Circuit 2:
Current room temperature: 23.7°C
Setpoint room temperature: 16.0°C
Mode: manual
Mode Type: nofrost
Mixing Module: Junkers IPM (DeviceID:0x21 ProductID:102, Version:20.08)
Heating Circuit: 2
Current flow temperature: 28.2°C
Setpoint flow temperature: 0°C
Current pump modulation: 0%
Current valve status: 0
Mixing Module: Junkers IPM (DeviceID:0x20 ProductID:102, Version:20.08)
Heating Circuit: 1
Current pump modulation: 0%
Solar Module: Junkers ISM1 (DeviceID:0x30 ProductID:101, Version:23.04)
Collector temperature (TS1): 38.2°C
Bottom temperature (TS2): 62.5°C
Solar Pump (PS1) active: off
Pump working time: 202 days 9 hours 0 minutes
Tank Heated: off
Collector shutdown: off
Energy last hour: 0.0WhAnd this is the output of the thermostat_data publish:
{"hc1":{"seltemp":15,"currtemp":23.7,"mode":"manual","modetype":"nofrost"},"hc2":{"seltemp":16,"currtemp":23.7,"mode":"manual","modetype":"nofrost"}}
proddy
MichaelDvP
The MQTT commands inherited from v1.9 and the new Console commands are not always in sync. The code needs some refactoring and simplification. This will also help reduce the memory hog when running mqtt, telnet, and web at the same time on an ESP8266.
Specification
1) sending commands to EMS-ESP is done by a single topic called
cmd. The payload determines the device/sub-system and the action. An additional id field can be used to set the heating circuit. For example:cmdpayload={"target":"boiler", "cmd":"flowtemp", "data":55}cmdpayload={"target":"thermostat", "cmd":"mode", "data":"auto"}cmdpayload={"target":"thermostat", "cmd":"mode", "id":2, "data":"auto"}cmdpayload={"target":"system", "cmd":"fetch"}cmdpayload={"target":"system", "cmd":"gpio", "id":1, "data":"on"}2) The exception to the above is for Home Assistant's default climate component. Here the subscribed topic will behomeassistant/climate/ems-esp/hc<num>/<cmd_temp|cmd_mode>. At some point, we should have our own component installed via HACS. 3) Console commands will be derived from the MQTT commands and accessible viaset <cmd> <data> [hc]in the associated context. For example:This will simplify the code significantly. When using a console command it will just invoke the MQTT function effectively simulating an incoming MQTT request. It will mean each command function will take now a char * and be responsible for deciphering the values from the payload string. For example the
setcomfort()function will no longer an int values 1, 2 or 3 but "hot", "eco", "intelligent".4) The WebUI will be used for configuring EMS-ESP. The console will have a few
setcommands for debugging mainly such as setting the wifi credentials or changing the UART tx mode