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.
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.
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.