Shelly 3em

hi folks, so I had shelly 3em on my old HA working.

now with the new and current HA the discovery via mqtt does not work due to shortcomings of the shelly mqtt implementation…

at least thats what i gathered, i found some hacs integrations, but they seem to be way outdated, i tried one and it spammed my log with deprecated messages.

how do i fix that?

i own a bunch of these sensors. and im not toooo hot about replacing them. aside from the work they where quite expensive, did what i wanted and i dont know a replacement thats better.

maybe update to tasmota?

any input would be appreciated.

thanks
manny

EDIT after fixing it:

Aside from the marked solution, pleas also see

for further details on why it did not work.

Shelly devices don’t support MQTT discovery. If you want to configure the device via MQTT you can use Shellies Discovery.

1 Like

hi there,

thanks, but i have to admit i cant even follow the prerequisites, as i cant get the python to work, when i put

python_script:

as indicated by the help, into my configuration.yaml, nothing changes…

manne

Why can’t you just use the Shelly integration?
https://www.home-assistant.io/integrations/shelly

1 Like

cause it does not work…

FW rules:

Settings in 3EM

(i also tried setting CoIoT to IP:5683, and tried to set the port in HA to 5683…) no change

I do have MQTT messages dropping in, but HA does not do anything with it.

And when I try to add a shelly device, it ends like this

It does not matter what I set for Settings, its not communicating.

but i clearly can ping it from HA:

fixed, I had to again set the MQTT user Password, after activating CoIoT!!!

What an awesome Firmware shelly is providing to us here. Nothing indicating that the MQTT while activated, was not active or successfull in establishing a connection.

and btw. for my setup with subnets, and the HA being the project based VM: it only worked with CoIoT peer set to IP:port for unicast.

For discovery both work, but after a while there is a notification that push updates are unsucessfull.

It is not recommended to use Shelly integration if the HA server and devices are in different subnets, but I know users who managed to configure forwarding rules and everything works. In my opinion, in such a situation, using MQTT is simply easier and more reliable.

thank you for the feedback.

however i now have it working over vpn from several remote sites, vpn tunnels that are not handled by my unifi udm pro g(h)ateway but are piped into my network on the “side”. i also run em successfully across networks locally.

i concur that i too would prefer to use mqtt only.

but i cant get your integration to work, and you did not provide any feedback on my question further up in the thread, hence i did not spend further time in that.

regards,
manne

Ask clear questions and you will get answers :man_shrugging: