Beiträge von pauli

    I have a working Home Assistant with Shellies 2.5 and 1pm. You can have it working via the shelly integration. However, I prever it via the MQTT integration, so giving up the cloud of the Shelly. Majorly because of the level of realdtime this gives compared to the cloud solution.

    Also the MQTT is available as an integration in the Home Assistant so very simple to install.

    Set on each shelly the ip address of the MQTT server and userid and password and it is finished.

    this afternoon again a disconnect of a shelly 2.5. It has a very good wifi signal with RSSI of -62 dBm. In order to further pinpoint the error I have yesterday the network traffic lowered by disabling Coiot (so only using MQTT with a refresh interval of 600 seconds). So now only MQTT is used for the shellies. I also opened a ticket at supportdesk of shelly but no progress till now. It surely has something todo with the firmware: when I upgraded last week to v1.11.0 it also started. Before I ron for at least 6 months without any error...

    This morning again maultiple disconnects. The shellies do no longer send messages to the mqtt broker. Also they do not respond on ping or anything.

    I can bring them back with a power cycle or by globally stop/start my wifi.

    I need a solution for this. I will make a wireshark network trace of the shellies.

    One thing I noticed is the large number of messages that is send to the mosquitto mqtt broker. There is no status changes (all are cover shutter) so why so many messages. Maybe that brings the mongoos’ out of memory ?

    After upgrading my 19 shellies yesterday to level 1.11.0 I noticed that frequently some shellies are no longer on the network. The only way to revive them is a power cycle. What is causing this? Do I need to upgrade to 1.11.4-rc2 ?

    After the power cycle they seem to work again. But some time later it starts again on same or other shelly.
    I do not use the cloud of Shelly but a MQTT Mosquito server which conencts to my home assistant. It worked flawlessly from may this year till yesterday when I upgraded the firmwares.

    ;(