more BusID's

[stmb-100]

Is it possible to add further BUS-IDs for terminals.
My gateway (Premium II base board) has the address Terminal 0x0A.
ServiceKey 0x0B and Modem 0x0D is occupied
TimeModule 0x0F and AlarmModule 0x12 remain.
I would like to attach a second gateway (EMS interface board V3) to the bus for testing. Can I also attach this to the address 0x0F or 0x12?

[proddy]

I'd say just try 0xF and 0x12 and see what happends. To be safe enable the "Enable read-only mode (blocks all outgoing EMS Tx Write commands)" option to ensure your 2nd gateway board is only in 'listen' mode.

[proddy]

We can add more BUS IDs but these are only I was able to find from the internet. There may be more out there...

[MichaelDvP]

Id 0x12 is working, but not good to use, this is address of error module and the thermostat is permanently trying to read the version info.
We can add 0x0E this is for converters/gateways. 0x48 should work, but is often occupied by KM200, 0x49..0x67 are unknown, maybe working for emsesp.

[MichaelDvP]

I've tested with ids 0x48 to 0x4F: 0x48 to 0x4D are working good, no unwanted communication like 0x12.
0x4E and 0x4F not working, the master does not echo to TX, but i have ems1.0, maybe ems+ handles these ids.

[MichaelDvP]

I've tested the 0x12 error module as ems-esp id. I think we should remove it as id-setting. The thermostat is using every free bustime to ask for the version. The original module have a analog input and controls boiler flowtemp, i think the thermostat will stop controlling the flowtemp if the module is registered with version.
Communication of EM10 errormodule is in #575.
Log from my test:

2022-10-12 09:14:58.423 TRACE 2462: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:14:58.672 TRACE 2463: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:14:58.927 TRACE 2464: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:14:59.263 TRACE 2465: [emsesp] Boiler(0x08) -B-> All(0x00), UBAMonitorFast(0x18), data: 34 01 AA 64 00 01 01 00 00 01 D9 7D 00 80 00 00 00 FF 30 59 00 00 FF 00 00 83 00
2022-10-12 09:14:59.272 DEBUG 2466: [mqtt] Publishing topic ems/boiler/curflowtemp (#468, retain=0, retry=1, size=4, pid=1)
2022-10-12 09:14:59.543 TRACE 2467: [emsesp] Boiler(0x08) -B-> All(0x00), UBAMonitorFast(0x18), data: 00 00 00 00 00 15 37 34 00 00 (offset 27)
2022-10-12 09:14:59.943 TRACE 2468: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:00.172 TRACE 2469: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:00.672 TRACE 2470: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:00.922 TRACE 2471: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:01.259 TRACE 2472: [emsesp] Boiler(0x08) -B-> All(0x00), UBAMonitorFast(0x18), data: 34 01 A9 64 00 01 01 00 00 01 D9 7D 00 80 00 00 00 FF 30 59 00 00 FF 00 00 83 00
2022-10-12 09:15:01.314 DEBUG 2473: [mqtt] Publishing topic ems/boiler/curflowtemp (#469, retain=0, retry=1, size=4, pid=1)
2022-10-12 09:15:01.540 TRACE 2474: [emsesp] Boiler(0x08) -B-> All(0x00), UBAMonitorFast(0x18), data: 00 00 00 00 00 15 E9 34 00 00 (offset 27)
2022-10-12 09:15:01.923 TRACE 2475: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:02.172 TRACE 2476: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:02.422 TRACE 2477: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:02.798 TRACE 2478: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:03.047 TRACE 2479: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:03.297 TRACE 2480: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:03.802 TRACE 2481: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:04.048 TRACE 2482: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:04.343 TRACE 2483: [emsesp] Boiler(0x08) -B-> All(0x00), UBADevices(0x07), data: 03 05 00 02 00 01 00 00 00 00 00 00 00 00 00
2022-10-12 09:15:04.797 TRACE 2484: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:05.053 TRACE 2485: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:05.354 TRACE 2486: [emsesp] Boiler(0x08) -B-> All(0x00), UBAMonitorFast(0x18), data: 34 01 A8 64 00 01 01 00 00 01 D9 7D 00 80 00 00 00 FF 30 59 00 00 FF 00 00 83 00
2022-10-12 09:15:05.374 DEBUG 2487: [mqtt] Publishing topic ems/boiler/curflowtemp (#470, retain=0, retry=1, size=4, pid=1)
2022-10-12 09:15:05.633 TRACE 2488: [emsesp] Boiler(0x08) -B-> All(0x00), UBAMonitorFast(0x18), data: 00 00 00 00 00 17 53 34 00 00 (offset 27)
2022-10-12 09:15:06.047 TRACE 2489: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:06.297 TRACE 2490: [emsesp] Thermostat(0x10) -R-> Me(0x12), Version(0x02), length: 0x03
2022-10-12 09:15:06.551 TRACE 2491: [emsesp] Boiler(0x08) -B-> All(0x00), UBAMonitorFast(0x18), data: 34 01 A7 64 00 01 01 00 00 01 D9 7D 00 80 00 01 CB FF 30 43 00 00 FF 00 10 83 00

Sometimes people like to control the flowtemp, but thermostat overwrites it. It could be a solution for this to use 0x12 as ems-esp id and answer to the version request. Then we can send flowtemp command to the boiler and thermostat does not overwrite, But this is a very special function and should be protected against accidental use.

[proddy]

Ok, so remove 0x12 and add 0x48 -> 0x4D ? I think we can just do this easily in the web code and change console.cpp for the command

[MichaelDvP]

0x12 could be fine for overriing a thermostat and setting the flowtemp, but we need to reply to version request for this. I think remove for now, but keep the option in mind.
Converter 0x0E works good, add it.
Gateway 0x48 is mostly KM200, works good
0x49-0x4D how to call it in UI, only number or Gateway 2...

[proddy]

hmm, we need a name. Either Gateway, Special or Custom ?