Shelly Plug US not being discovered -- even if manually entered

The plug is fully functional, using hte shelly app, and it is on the same network - can ping it from my HA box. What I found in hte logs is that there is a 404 beging returned by the Plug when the integration is issuing the status call. Talked to Shelly support, and they indicate that for this device the status call has been depricated and the new calls are: http://deviceip/rpc/Shelly.GetStatus, http://deviceip/rpc/Shelly.GetConfig
Am I missing someting in the configuration that will allow me to integrate these plugs, or is this a bug?

I have four Shelly Plug US running fine and happy to help.

I have not seen that 404 error. Which log file are you seeing the error (Home Assistant Core?). Can you provide the full error message?

I’m going to assume that you have read the Shelly Integration docs. The Plug is a Generation 2 device. NOTE: I did not need to configure outbound websocket configuration since the plug is not a battery powered device.

If you can ping the plug from your local network, you should be able to access the Shelly Plug configuration page by going directly to the Plug IP address from your HA box (or any browser on the same network).

I would check for firmware updates and check the network settings on the plug.

Thanks for jumping in. Yes, I have been to the devices setup page directly, and I know it’s a gen 2, and the firmware is updated to the latest (at least that is what it says :slight_smile: )
Firmware version: 0.11.4

Firmware build ID: 20221024-141933/0.11.4-ga1906a2

Web build ID: 1.5.5-8e98823

I’ve got over 30 Shelly devices on my network, all working fine, and a mix of 1, 2.5, 1L, rgb, and now the plugs. Only the plugs are showing the problem.
Among all of the good devices, I see both of my plugs like this:
2022-12-03 18:12:28.148 WARNING (S4H-Poll status) [pyShelly] Error, 404 Not Found http://192.168.99.175/status
2022-12-03 18:12:28.153 WARNING (S4H-Poll status) [pyShelly] Error, 404 Not Found http://192.168.99.133/status

Any help is gladly appreciated. Let me know if there is more info I can provide.
Thanks,
Paul

Might want to edit configuration.yaml to set logging to debug for pyshelly to get more info than head over to github and log an issue there.

Yeah, figured that was the next step, but wanted to run it up the pole here first. Oddly, that logging is debug level. That’s all that shows up for those devices.
Thanks again.

I noticed that there are two debug lines I use under the logger to capture shelly debug information:

homeassistant.components.shelly: debug
aioshelly: debug

Mark - thanks for all your help… I figured it out, and it was all my fault… was using the older Haas integration. Just finished going through the pain of migrating everything over to the core support, and it’s working perfectly.

Appreciate your help!!!
Thanks,
Paul