Shelly 2PM cover mode MQTT Topics missing

[ChrisPrefect]

Shelly device

2PM plus in cover mode

Protocol (CoAP / MQTT)

MQTT

The problem

After updating the firmware today, I am missing the "cover" subtopic.

https://imgur.com/4p95ZEa

Firmware version: 0.11.4
Firmware build ID: 20221024-142414/0.11.4-ga1906a2

This happens on three 2PM plus devices.

Version of nodejs

v14.19.3

Version of ioBroker js-controller

v6.2.23

Version of Adapter

v6.2.4

Operating system running ioBroker

debian virtualbox

Checklist of files to include below

• 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)

Additional information & file uploads

iobroker.2022-11-05.log.txt

[ChrisPrefect]

Update: I copied the device_id string from a 1PM device, so it had a 1 in the string instead of a 2. After changing the device_id string to shellyplus2pm-xxxxx the cover subtopic appeared again.

How is the device_id string handled? Why is this important? Why can't it be anything arbitrary like "shelly_cover_office"?

[klein0r]

As documented, you must not change the client id. That identifier is used to identify the device type.

https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/en/protocol-mqtt.md#generation-2-devices-plus-and-pro

[ChrisPrefect]

OK it's fixed. I was searching for two hours for an explanation for this. Didn't even find the manual, only a lot of 404 links to github. There is no link to a manual in the adapter config. Maybe it would be helpful to add it there? This new field "device_id" is really confusing and error-prone and leads to very strange errors when it is not set exactly correctly. If you changed it because you thought it is an MQTT topic, it is really hard to fix it again. Is there no other way to detect the correct device type?
Thanks!

[klein0r]

@ChrisPrefect Feel free to contribute: ioBroker/ioBroker.admin#1600 , ioBroker/ioBroker.admin#1293 or ioBroker/ioBroker.docs#379

[klein0r]

Didn't even find the manual

[ChrisPrefect]

Yes, I searched for the manual and the github page, but it did not show up. I only found some dead links. I have not been to this github page before. There is no link to it from the adapter. OK the open issues are a good start, thanks.