Range Extender Shellys Endless MQTT Prefix warning

[dekatWin]

I'm sure that

• [X] This issue is still present in the current beta version of this adapter
• [X] There is no other (open) issue with the same topic (used the search)
• [X] This issue is not described in the adapter documentation / FAQ

Shelly device

All Gen2

Protocol (CoAP / MQTT)

MQTT

IoBroker Log:

2023-05-28 15:54:00.981 | warn | [Mqtt.topicPrefix] 192.0.0.112 (shellyplus1pm / shellyplus1pm-12345678910A / shellyplus1pm#12345678910A#1): Configured mqtt topic prefix "Outdoor_AP" and actual topic prefix "Outdoor_BluGateway" do not match. Please check configuration

My setup:

I have a Shelly Plus1PM set up as a range extender AP and another Shelly connected to it, both have different MQTT prefixes in their settings. 1. Shelly MQTT Prefix: "Outdoor_AP" 2. Shelly MQTT Prefix: "Outdoor_BluGateway"

My problem:

The Shelly adapter writes endless warnings in my log that something is wrong with the set prefixes, but it is absolutely correct, 2 devices on one IP, 2 MQTT prefixes. Please remove this warning if possible, it is just spamming at the moment.

The Shelly adapter is great, I thought my setup with a range extender would go wrong, but both shellys were correctly detected and created. Great job, thanks for always improving it!

Version of Adapter

6.4.1

[klein0r]

Mhhh, I've never tested that. Thanks for reporting

[c1328]

Same effect here and I have the concern that this is responsible for another effect I have: one of two Shellies behind the range extender goes offline after a while (object becomes yellow). If that happened the Shelly is not able to be controlled by ioBroker anymore. A reboot of the Shelly and restart of adapter solves the problem for some hours, sometimes for the whole day.

[helbgd]

I have the same problem, is there a solution for that already?

[klein0r]

@helbgd nope, since the adapter is not designed for 1:n devices per connection. Just 1:1

[joeflower]

Is there solution in future? I hope so... or perhaps simply take out this debug text ? Have unfortunately the same Issue.

[klein0r]

Is there solution in future?

If someone will rewrite the complete adapter: yes. It's a lot of work because nobody expected that the same client connection must handle multiple devices.

[tappas197112]

Not sure if this issue is still relevant / existing but I found a solution.

You have to change the MQTT prefix of the shelly, which is connected to the range extender, to the same MQTT prefix as from the range extender.

[klein0r]

You have to change the MQTT prefix of the shelly, which is connected to the range extender, to the same MQTT prefix as from the range extender.

Bad idea.

[tappas197112]

I can't decide whether it's a bad idea. I can only report that this has been working for me without any problems for about three weeks. The only limitation is that some namings are referenced to the shelly which is the extender.

An alternative would be to use the “original” MQTT adapter, which I also tested. Naming is not an issue there. However, this makes processing the data points significantly more complex...