You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is still present in the current beta version of this adapter
There is no other (open) issue with the same topic (use the search!)
This issue is not described in the adapter documentation / FAQ (read the docs!)
Shelly device
No response
Shelly firmware version
No response
Protocol
MQTT
The problem
If a Shelly is connected via the range extender function of another Shelly (Wi-Fi AP), then the "ChannelName" (Relay) can not be set in the adapter. It is always overwritten with the "ChannelName" of the host (Shelly with Ragenextender).
Maybe it's because the Shelly has the same IP address in the network as the host (just with a different port). Could this perhaps be fixed? So that the “ChannelName” can be set independently of the IP address?
iobroker.current.log (in debug mode!)
No response
Version of nodejs
18.19.0
Version of ioBroker js-controller
5.0.17
Version of adapter
6.6.1
The text was updated successfully, but these errors were encountered:
A pity. So far everything has been running smoothly for me with the range extender, except that due to this bug the channel name is the same for all Shellys in the adapter.
I'm sure that
Shelly device
No response
Shelly firmware version
No response
Protocol
MQTT
The problem
If a Shelly is connected via the range extender function of another Shelly (Wi-Fi AP), then the "ChannelName" (Relay) can not be set in the adapter. It is always overwritten with the "ChannelName" of the host (Shelly with Ragenextender).
Maybe it's because the Shelly has the same IP address in the network as the host (just with a different port). Could this perhaps be fixed? So that the “ChannelName” can be set independently of the IP address?
iobroker.current.log (in debug mode!)
No response
Version of nodejs
18.19.0
Version of ioBroker js-controller
5.0.17
Version of adapter
6.6.1
The text was updated successfully, but these errors were encountered: