Matthias Kleine

I cannot find documentation for the Shelly UNI offset. Just for the Shelly 1 / Shelly 1 PM ext sensors (as you mentioned in the issue). EDIT: Found it: https://shelly-api-docs.shelly.cloud/gen1/#shelly-uni-settings

@aschmidt74 Can you test if the Shelly UNI provides the following URLs? - ``/settings/ext_temperature/0`` - ``/settings/ext_temperature/1`` - ``/settings/ext_temperature/2`` - ``/settings/ext_temperature/3`` - ``/settings/ext_temperature/4`` (I don't know why there are 5 states...

Thanks! Do you know how to use the browsers developer console? Can you change the offset in the web ui of the Shelly device and send me the HTTP-Request?

- Open the website of the Shelly device - Open the developer tools (which browser do you use?) - Go to the "Network tab" - Clear the list - Change...

Is it a normal Shelly 1 with a different firmware?! Or was does "customized" mean?

> not sure if they also changed hardware. The question is, if we can handle that Shelly device as a normal Shelly 1 (with all features) or if the device...

Can you provide the full log (in debug mode) and/or the complete message above? I need a device type which should be part of the log message.

``online`` means (at the moment), that the device is reachable via TCP (ping). There are plans to use the MQTT connection state for online indication. But I have no time...

"There are no requirements regarding whether you should return a URI that is on the same local network as the device with Alexa or a remote URI accessible from anywhere...

Documentation tells me to remove the room in that case: https://github.com/ioBroker/ioBroker.iot/blob/5d8f8fc61cd25c68997c438e9981c68aa36c5102/README.md?plain=1#L103 Like this: But the result is still strange: