My device appears in iobroker Objects tab as:
shelly.0.shellyplus1pm#3c610572ace0#1
This name is not usable in the iobroker mqtt adapter (which exposes iobroker objects/states as mqtt topics)
because the mqtt syntax does use '#' as a wildcard,
so it is impossible to subscribe to the topic 'shelly/0/shellyplus1pm#3c610572ace0#1' to get the states forwarded as mqtt messages.
Version of nodejs
16.17
Version of ioBroker js-controller
6.2.22
Version of Adapter
6.0.0
Operating system running ioBroker
Docker on raspberry pi 4 with 64 bit Debian bullseye
Checklist of files to include below
[X] iobroker.current.log (Please share the logs in debug mode)
[ ] Contents of the JavaScript browser console (always include in cases of issues with the user interface)
Shelly device
Shelly plus 1 PM
Protocol (CoAP / MQTT)
mqtt
The problem
My device appears in iobroker Objects tab as:
shelly.0.shellyplus1pm#3c610572ace0#1
This name is not usable in the iobroker mqtt adapter (which exposes iobroker objects/states as mqtt topics) because the mqtt syntax does use '#' as a wildcard, so it is impossible to subscribe to the topic 'shelly/0/shellyplus1pm#3c610572ace0#1' to get the states forwarded as mqtt messages.
Version of nodejs
16.17
Version of ioBroker js-controller
6.2.22
Version of Adapter
6.0.0
Operating system running ioBroker
Docker on raspberry pi 4 with 64 bit Debian bullseye
Checklist of files to include below
Additional information & file uploads
Adapter mqtt 4.0.7
iobroker.2022-09-20.log