The Shelly integration on my HA picked it up immediately and it exposes 4 entities:
sensor.sensor_movimento_despensa_battery
sensor.sensor_movimento_despensa_luminosity
binary_sensor.sensor_movimento_despensa_motion
binary_sensor.sensor_movimento_despensa_vibration
I do have the values for all sensors on HA from the time the device was set up, but it’s not updating as it should. The main sensor I want to use is, of course, the binary sensor for motion, but it just doesn’t update.
I can successfully set up scenes at the Shelly Cloud app and they fire immediately when motion is detected, but nothing happens on HA.
I have added the sensor to Lovelace just for monitoring purposes and it never updates. I’ve also set up an Automation that, of course, never fires. If I use the developer tools to change the binary sensor state, the Lovelace widget is immediately updated and the Automation runs perfectly.
In sum:
Is this device supported by the Shelly integration already?
Is anyone using it with HA successfully? What am I missing?
What’s the meaning of life? (You don’t need to answer, it’s 42)
I have eventually got these setup working on my home network.
Had problems with the app in that when I went to add device, I would be able to select the motion sensor but then when I selected on connect it would briefly show connection successful but then display an error indicating that it was unable to load the configuration via WIFI.
Anyway, I finally got it connected onto my home network via the WebUI. Still haven’t been able to get it to appear in the Shelly app though. Did you have similar experiances?
I have both the Shelly and the Shelly for HASS integrations added. Guess i really only need one. Not sure of what the difference is though.
I have the shelly motion sensor device being added although I only get one entity which is for the battery, and that is showing as unavailable. How were you able to get this working with the motion detection entities etc?
I have problems adding ANY Shelly device to their app. It’s a trial and error thing.
Make sure you’re using 2.4Ghz WiFi and disable mobile data on your phone while doing it.
What is that port (5683) on your HA instance? Your mqtt server, main web gui, or what? I just entered my HA’s IP and the only sensor that showed up was the battery one.
— EDIT ---- I actually just looked at mine now and it appears the shelly added the 5683 to it.
I just installed the Shelly Motion with integration. It worked pretty flawless, then I went and upgraded the firmware. Now it sometimes works and sometimes doesn’t. Any ideas? Can I factory reboot, and go back to the original firmware?
Hi, mine does still not work, what is the firmware, that is supposed to work? And have you HA in the same network as shelly motion? maybe I need to change that to get it working. But all other shellies work in my separate iot subnet.
UPDATE: After Factory Reset, latest version of firmware 1.1.0 and using the ColoT it started to work
ive been having this problem this morning on two devices!!! i wants able to connect them on their app! I WAS ABOUT TO BREAK MY HOLE HOUSE! tomorrow ill try your steps and Marco
@Soccs I don’t think you need to factory reset it. Just update it, make sure HA is updated also and use the default Shelly integration to add it to HA. Then add the HA IP on the Motion WebUI ColoT field.
You can factory reset using the web interface, you might not need it, but a factory reset assures that you set all config back to default, when you fiddle too much around as I did
