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
Gen2 Devices
Shelly firmware version
Different, e.g. latest
Protocol
MQTT
The problem
Hello everyone, First of all, I would like to thank you for your work! Unfortunately, I don't really find the time to program in my free time besides work. Respect :).
So, that brings us to my problem. I use the IOBroker in a not necessarily everyday setup. I run the IOB in a K3s cluster behind a reverse proxy (Traefik).
All Gen1 devices work perfectly via MQTT and Http. The MQTT communication also works for the Gen2 devices, but the HTTP requests do not.
In my opinion, this is because the “hostname” is initialized with the internal IP from K3s (see log), but then no longer updated with the real IP via MQTT. This host name is used for the request, as far as I know. The mechanism for “updating” the IP is done via a question and answer from the adapter and Shelly. '/rpc' -method MQTTShelly.GetDeviceInfo see Request: Line 435
Response: Line 542
This is also sent, see log. However, the response is not received (not subscribed?) The rest, so if an answer came, it looks right to me again in the code (i.e. structure of the Json message, etc.)
I also tested it without an adapter, just with an MqttBroker, and a response was received there. That's why I would exclude the Shellys as problem.
Next step in my analysis. I ran the IOBroker in a single Docker container, without Kubernetes, proxies, etc. I saw the same behavior there, i.e. the message/response was never received. However, the Shellies work here because the “hostname” IP initial was of course initialized with the correct IP.
Hello,
i think that is the same problem as in #1052
As temp fix i have to edit the value of "hostname" in iob, but gets overwritten after reboot/reconnect.
I'm sure that
Shelly device
Gen2 Devices
Shelly firmware version
Different, e.g. latest
Protocol
MQTT
The problem
Hello everyone, First of all, I would like to thank you for your work! Unfortunately, I don't really find the time to program in my free time besides work. Respect :).
So, that brings us to my problem. I use the IOBroker in a not necessarily everyday setup. I run the IOB in a K3s cluster behind a reverse proxy (Traefik).
All Gen1 devices work perfectly via MQTT and Http. The MQTT communication also works for the Gen2 devices, but the HTTP requests do not.
In my opinion, this is because the “hostname” is initialized with the internal IP from K3s (see log), but then no longer updated with the real IP via MQTT. This host name is used for the request, as far as I know. The mechanism for “updating” the IP is done via a question and answer from the adapter and Shelly. '/rpc' -method MQTTShelly.GetDeviceInfo see Request: Line 435
Response: Line 542
This is also sent, see log. However, the response is not received (not subscribed?) The rest, so if an answer came, it looks right to me again in the code (i.e. structure of the Json message, etc.)
I also tested it without an adapter, just with an MqttBroker, and a response was received there. That's why I would exclude the Shellys as problem.
Next step in my analysis. I ran the IOBroker in a single Docker container, without Kubernetes, proxies, etc. I saw the same behavior there, i.e. the message/response was never received. However, the Shellies work here because the “hostname” IP initial was of course initialized with the correct IP.
iobroker.current.log (in debug mode!)
Version of nodejs
v20.18.0
Version of ioBroker js-controller
6.0.11
Version of adapter
8.4.0
The text was updated successfully, but these errors were encountered: