Hello,
first of all, I really appreciate the work you’ve put into EnOcean to MQTT Slim, the UI is great and it’s very nice to use!
I’m not very deep into EnOcean internals, so maybe I’m missing something obvious.
I noticed an issue when using one EnOcean sender ID for multiple actuators (for example: light + roller shutter).
Even if I configure different devices in Slim with different names/IDs, both actuators react at the same time.
In Dolphin View this only works correctly when different RORG: RPS Data bytes (channels, e.g. 0x10, 0x30, 0x70) are used, then the actuators know which function is meant.
My question is:
Does EnOcean to MQTT Slim support separating devices by RPS Data / channel?
If it’s not supported right now:
– Is there a planned way to add this?
– Or is there a workaround you would recommend?
MQTT broker is already installed and working.
Thanks a lot for your work and your time!
Hello,
first of all, I really appreciate the work you’ve put into EnOcean to MQTT Slim, the UI is great and it’s very nice to use!
I’m not very deep into EnOcean internals, so maybe I’m missing something obvious.
I noticed an issue when using one EnOcean sender ID for multiple actuators (for example: light + roller shutter).
Even if I configure different devices in Slim with different names/IDs, both actuators react at the same time.
In Dolphin View this only works correctly when different RORG: RPS Data bytes (channels, e.g. 0x10, 0x30, 0x70) are used, then the actuators know which function is meant.
My question is:
Does EnOcean to MQTT Slim support separating devices by RPS Data / channel?
If it’s not supported right now:
– Is there a planned way to add this?
– Or is there a workaround you would recommend?
MQTT broker is already installed and working.
Thanks a lot for your work and your time!