Hello,
I just deployed a VM, Docker Compose and all the shebang… and I wanted to test Gladys to offer a slightly more polished dashboard than my personal devs with node-red/dashboard-ui to my mother-in-law (that said, it works nonetheless)
And I thought, great, we can hook into preexisting Z2M (zigbee2mqtt)
However, between her house, mine, the office, two datacenters, my car over LTE (yes yes I’m nuts), I have several brokers bridged together, which host 4 different Z2M on… 4 different topics none of which is ‹ zigbee2mqtt/# › which is hardcoded in server/services/zigbee2mqtt/lib/constants.js, rather ‹ z2mtln/# › ‹ z2mdc2/# › ‹ z2msixf/# › ‹ z2mdijon/# › etc… that lets me, without breaking my head, gather stats in one place
And bam, it doesn’t work at all.
Mosquitto is flexible, and we could do topic transformation and maybe fiddle with the acl/bridge so this « fake » topic doesn’t leak onto the other brokers, but that’s much less simple and maintainable.
Could we configure the base topic used? I thought I came across a few threads that ended in a dead end, but is this something that could be brought back to the table?
Thanks
JaXX./.
