Shelly PM1 Mini Gen3

Configuration
22

Hi!

Can someone confirm that Home Assistant 2024.1 works with the Shelly Plus PM Mini (“shellypmmini”)?

I have updated HA (it was mentioned that support was added in 2024.1), but I can’t see that I’m able to add this device even after update. The device is also updated to latest firmware.

I have about 15 other Shelly devices (older devices) without any problems, but this one does not show up at all.
It is configured for my home WiFi network, and I have no problems browsing the UI of the device, but it is not detected by HA.

Any ideas?

Cheers,
Thomas

1 Like
23

Hi Thomas,
HA 2024.1.3 here, Shelly Plus PM Mini is detected perfectly:

image
image1284×1140 128 KB

This Shelly is running firmware ver 1.1.0
I cannot see temperature sensor, maybe missing in this Shelly model.
-f

24

Thanks Franz,

Then I know it is something with my setup!
Just to keep up digging!

Cheers,
Thomas

25

Hi,

I got a few Shelly 1 mini (gen 3) and I am unable to add them. They don’t show up and are not detected at all.

They work fine through the app and I can add them using MQTT (they show up in the MQTT explorer) but I’d like to use the integration. I also tried the “ShellyForHass” HACS integration and they don’t show up there either. Also tried the outbound websocket (ws://192.168.1.100:8123/api/shelly/ws) and still nothing Actually I am getting a “Invalid WebSocket handshake response” in the shelly diagnostics. I am very new to HA and have no idea where else to look or check.

Thanks for any tips.

[Edit] OK, found the problem: The websocket address is not as documented EVERYWHERE.

/api/shelly/ws

is wrong! It needs to be:

/api/websocket

It now works like a charm. I am not sure why the websocket needs to be configured. HA documentation suggests that it will autodetect Shelly devices, which is apparently also wrong. But knowing that … it works.

26

Hmm, as mentioned everything is working fine, but I am getting an error message in the debug log in HA:

Auth message incorrectly formatted: extra keys not allowed @ data[‘dst’]. Got ‘ws’ extra keys not allowed @ data[‘method’]. Got ‘NotifyFullStatus’ extra keys not allowed @ data[‘params’].

and this in the shelly log:

INVALID FRAME (854): '{“type”:“auth_invalid”,“message”:"Auth message incorrectly formatted: extra keys not allowed @ data[‘dst’].

Any ideas what to do about that?
Thank you

27

I can report that the PM1 gen 3 mini works very well for me. No MQTT, just out of the box.

I’ve done a 3D printable case if you want to stick this behind a Gira socket:

28

For those who have the Gen 3 1PM Minis working in HA, are you using the Shelly Integration (which I believe only works thru Gen 2)?

I’m using HA Core 2024.3.1 and have multiple Gen 2 relays connected using the Shelly Integration, but cannot get either of a pair of new Gen 3’s to be recognized in HA. Both Gen 3’s can be accessed through a browser via their IP’s. They work thru the Shelly App - just can’t get them into HA. Any help would be appreciated.

After posting this question, I found a solution here…

29

any news on this? I also would like to buy this small relays.

Are they now working with home assistant ?

30

I own two Shelly 1 Mini Gen3 (FW 20240425-141412/1.3.0-ga3fdd3d) devices that integrate and work perfectly with my installation HA 2024.5.2 with Shelly integration.

31

Same issue here … Voltage “sits” at 235.3 V and does not update in HA but it does in the Shelly app. (Shelly PM Mini Gen3)
Watts are showing correctly, its only the voltage.
Anyone any idea?

32

Same issue with a ‘Shelly PM Mini Gen3’, with Power (Watts) updating locally on the device, but ‘sticking’ (usually on a higher number of watts from when load was last used) on what is reported in HA.

Looking at local device GUI also note it has this message at the top:

“PM1 (0) experienced an error:out of range:current.” and ‘N/A’ showing for Current.

33

Latest FW version? v1.3.2

No websocket settings, as it is not a battery-operated Shelly.

34

Yes v1.3.2

35

Can you connect a toaster or iron to your Shelly?

36

I’m having troubles with the Shelly. I don’t see an entity in HA to toggle the actual smart switch.

Updated to latest 1.4.2 on the Shelly MiniPMG3 and HA is also on latest. (Core
2024.8.3 & Operating System 13.1)

For all my other shelly devices I have a switch entity, but not for the Mini PM. Anyone has a similar situation and a solution to that?

37

This Shelly have no Relay :wink:

The Shelly Mini1PMG3 have a Relay

1 Like
38

Not related to the topic but pm mini gen3 (no relay).
It seems to report energy (kwh) in wrong scale. E.g. today it showed my dishwasher using 3482 kWh in one hour! These ’spikes’ happens 1-2 times per month. Other times energy is reported ok.
Because the same data is sent over mqtt and websocket, so I’m sure it’s bug in Shelly firmware.

Anyone else has similar obversations?

39

Hi Thomas, would you be so kind to share info on how did you manage to integrate Shelly PM Mini Gen3 into home assistant . Thank You

40

I can share my experience, I have two Shelly PM mini Gen 3 working in Home Assistant. Installed in October (i think) on HA 2024.10 with the Shelly Integration. First, install device in the Shelly app on your phone and update device firmware. Then Home Assistant should discovered the devices automatically, it did for me.

41

Hello, I had the same message as you (INVALID FRAME (854): ‘{“type”:“auth_invalid”,“message”:"Auth message incorrectly formatted: extra keys not allowed @ data[‘dst’]}’") with a Raspberry Pi HA installation (dockerized).

I eventually found a solution, but the issue was not related to the dockerization. It turns out that, in addition to my internet box, I have a Deco Wi-Fi mesh router that was creating a dedicated subnet mask (the Raspberry Pi was on 192.168.1.X and the Shelly on 192.168.68.X). Switching the Deco from router mode to access point mode instantly solved the problem.

It’s very specific, but I hope this can help others!