Unknown devices on Buderus system #142
Comments
|
It looks we first need to
|
|
Agree, first is to add the boiler 0x08 and then log on the bus to see the commiunication with 0x70. |
|
Wao... 1 boiler and 2 unknown devices:
MC400 is an ESP device, a manual in english is here: https://www.libble.eu/buderus-mc-400/online-manual-877928/ But the data: Is possibile from the MC 400:
The log:
PS: firmware update did not work on MAC (firefox, safari), work on Windows... (crome) |
|
Can you give some more information about your system. How it is connected to the ems-bus? @proddy I think the MC400 is product-id 210, but recognizes itself as boiler id 0x08, the two boilers are now 0x70 and 0x74 (because of possible MC400 cascading). |
|
I asked someone else with a MC400 and 3 boilers to provide some details about his system. Hope he joins this discussion. |
Here is my setup : 3 boilers in cascade via cascade controller Bosch MC 400 with EMS, EMS+ and EMS2 Bosch GC7000IW 42KW -> Via BUS1 on MC400 Bosch MC 400 cascade controller via EMS bus 3 x Bosch MM100, (2 not mixing) and (1 mixed group) hc1 -> MM100 -> NOT mixed -> controlled via MD contact by LOXONE mini server output hc1= Jacuzzi heating circuit As to my understanding, the boilers can not be visible from the EMS bus side or the EMS-ESP since the boilers are connected to BUS1, BUS2, BUS3 and are controlled by the MC 400? I want to control the MM100 hc3 flow temperature and pump status via the LOXONE mini-server virtual outputs using REST API. Since there is no way to control the MM100 directly, this should be achieved by controlling the CW 400, I suppose? At this moment reading the parameters in LOXONE via virtual inputs works fine, however writing does not work, hence the "Allow WEB API to write" is activated. Also cmd=info does not work when passing the id as hc1, hc2 or hc3? Does anyone have some examples or ideas?
|
|
As far as i see: @DLX2550 I think with your MB_Lan you see the boiler values. Can you update to the new dev to see the MC400 as boiler and check if there are values missing. I think the MC400 will collect the boiler information from ems1,.. and shows all data on the ems. |
|
0x70 , 0x74, 0x78 show the details of the MM100 hc1, hc2 and hc3 @MichaelDvP this is a premium II gateway and I could not find a way to update higher than 2.2 , I have ordered the new S32 gateway today.
|
|
@DLX2550 latest dev builds for the ESP8266 (v2) are here: https://github.com/proddy/EMS-ESP/releases/tag/esp8266_dev |
|
MC 400:
BUS1 --> Boiler 1 The switch position on MC400: 2 The ems-esp was bus-powered, now is USB powered. Log from BUS1 and/or BUS2 later |
|
Nice, a bit more power and the crc-errors are all gone. Setup is mailnly like @DLX2550 and helps to understand the system. It will take some time to read the log, but on first look the thermostat reads mainy some E4 values direct from boilers, but the cascade publishes them to all. Than reading the cascade will give all information. Maybe i've missed something, but i've added the cascaded boilers without values to device-list. Adding new values will blow esp8266 memory, if we find more than a few values in the cacaded moodules, this will only got to esp32-v3-version, sorry. |
|
My EMS-ESP is updated to the latest dev now. Now the cascade shows up as boiler. Writing to the thermostat via REST API now also works. Still, need to figure out how to write the target flow temperature value of hc3 and start the pump of hc3? Any suggestions? Thanks.
|
If hc3 is controlled by CW400, the thermostat sets the flowtemp and send it to mixer. You should see this as setpoint in mixer id 0x22. If you change the temp via "device=thermostat cmd=temp id=3 data=xx" the setpoint of flowtemp will follow. |
|
Wired to BUS1:
:) And the log: |
|
@csubakk |
|
With new firmware:
Thank You @MichaelDvP! I needed the 2 selected sensor data, my problem is resolved. Boilers are without data, but that isn't a problem for me. @DLX2550 yes, BUS 1-4 are for boilers, but they are ESP buses... |
|
@DLX2550 Yes, but EMS1,.. are sperarated ems-buses and we can read on them. On this bus the MC400 has device_id 0x18, playing the role of a single thermostat, and the boiler is device_id 0x08. @csubakk Yes, thats what i expected, i'll push here. |
|
What i see in the log from the 0x70, 0x74 devices:
@DLX2550 If you have received the esp32 and agree to make some tests, we can try add some values to the individual boilers. @csubakk and @DLX2550 What does the system system-status shows for free heap? With the number of devices you have, i may be low. |
|
I will notify you once I receive the ESP32.
|
|
|
@MichaelDvP nice addition. |
|
|
@MichaelDvP |
The system is: Buderus Logamax Plus GB172i-42i (2 pieces), Buderus MM100 modules (2 pc), Buderus MC 400 module (1 pc) and Buderus RC310 Thermostat (1 pc).
I can read or write informations from the Thermostat and read info from MM100 modules.
My problem: I cannot see all informations, EMS-ESP does not recognize all devices
The system info result is:
{
"System": {
"version": "2.2.0",
"uptime": "000+00:07:48.999",
"freemem": 45,
"fragmem": 22
},
"Settings": {
"enabled": "on",
"publish_time_boiler": 10,
"publish_time_thermostat": 10,
"publish_time_solar": 10,
"publish_time_mixer": 10,
"publish_time_other": 10,
"publish_time_sensor": 10,
"mqtt_format": 3,
"mqtt_qos": 0,
"mqtt_retain": "off",
"tx_mode": 1,
"ems_bus_id": 11,
"master_thermostat": 0,
"rx_gpio": 13,
"tx_gpio": 15,
"dallas_gpio": 14,
"dallas_parasite": "off",
"led_gpio": 2,
"hide_led": "off",
"api_enabled": "off",
"bool_format": 1,
"analog_enabled": "off"
},
"Status": {
"bus": "connected",
"bus protocol": "Buderus",
"#telegrams received": 878,
"#read requests sent": 103,
"#write requests sent": 3,
"#incomplete telegrams": 51,
"#tx fails": 3,
"rx line quality": 100,
"tx line quality": 100,
"#MQTT publish fails": 0,
"#dallas sensors": 0
},
"Devices": [
{
"type": "Thermostat",
"name": "RC300/RC310/Moduline 3000/1010H/CW400/Sense II (DeviceID:0x10, ProductID:158, Version:18.05)",
"handlers": "0xA3 0x06 0xA2 0x12 0x2A5 0x2B9 0x2AF 0x29B 0x2A6 0x2BA 0x2B0 0x29C 0x2A7 0x2BB 0x2B1 0x29D 0x2A8 0x2BC 0x2B2 0x29E 0x2F5 0x31B 0x31D 0x31E 0x23A 0x267 0x240"
},
{
"type": "Mixer",
"name": "MM100 (DeviceID:0x20, ProductID:160, Version:24.05)",
"handlers": "0x2D7"
},
{
"type": "Mixer",
"name": "MM100 (DeviceID:0x28, ProductID:160, Version:24.05)",
"handlers": "0x331"
},
{
"type": "Unknown",
"name": "unknown (DeviceID:0x08, ProductID:210, Version:02.05)",
"handlers": ""
},
{
"type": "Unknown",
"name": "GBx72/Trendline/Cerapur/Greenstar Si/27i (DeviceID:0x70, ProductID:123, Version:07.00)",
"handlers": ""
},
{}
]
}
The text was updated successfully, but these errors were encountered: