Open StinkendeHobbit opened 11 months ago
Thanks. Indeed it appears that Gen 2 shelly devices have changed authentication methods. For the time being I have noted in Moonraker's documentation that only Gen 1 devices support authentication and relabeled this as an feature request. Hopefully an interested developer will add support for Gen 2 devices.
In the meantime, it should be possible to get the switch working over MQTT. Alternatively, it is likely that Home Assistant supports Gen 2 shelly.
i found a workaround to use shelly plug S to turn printer on off simply use the http type
#Shelly Plug
[power printer]
type: http
on_url:http://192.168.1.45/relay/0?turn=on
off_url:http://192.168.1.45/relay/0?turn=off
status_url:http://192.168.1.45/rpc/Switch.GetStatus?id=0
request_template:
response_template:
Thanks. This is the purpose of the generic http implementation...it should support nearly any switch.
That said, I suspect there is an error in your configuration. The request_template
is likely not necessary, as it seems that all parameters are provided in the query string. The response_template
is required, it needs process the response received from the device and evaluate to "on" or "off".
What happened
moonraker failes authenication with shelly plug plus s. https://www.shelly.com/en/products/shop/shelly-plus-plug-s
This results in the following log:
Client
Mainsail
Browser
Chrome
How to reproduce
Additional information
I have had a the simmular issue with OctoPrint PSU control pluging. I managed to solve it with the following thread. https://github.com/edekeijzer/OctoPrint-PSUControl-Shelly/issues/16
The issue seems to be related to the authentication method used by the plugin. As the new plug use a different method (HTTPDigestAuth). The provided solution has the following changes to handle this change in authentication method.