I flashed v2.0.0 and I have again a lot of problems. I rolled back to v1.1.3-rc16 yesterday.
I have had one running for a couple of weeks with no issues and a definitely planning to buy some more. I am on firmware 2.0.3.
I am not sure of the hardware, but there must be some interesting tech in there on the wifi side, as I seem to be able to wake it up almost instantly using wifi and it has a pretty comprehensive rest api, so to preserve battery life further I disable motion detection using an automation when the alarm is disabled.
I was expecting to have wifi issues as many of my esp32 and esp8266 devices have issues on my 2.4 iot network, but this device seems to be coping with whatever interference there is around.
I really do want to know how the silicon labs chips is doing this.
I use the shelly integration only (no mqtt and no cloud) and rest api out to the device.
2 Likes
Completely agree - these things are a total pain in the butt and not wort the trouble. I have two units and after a recent firmware upgrade one of them is now constantly red and doesn’t respond to the reset button at all. Utter rubbish.
I’ve even pried the damn thing open and cut the battery lead hoping it would force a reset but it just carries on flashing red.
I cannot reccomend these at all
I have two Shelly motion in my setup and never had an issue.
Running firmware 2.0.3, with shelly integration and no cloud.
WiFi is powered by Ruckus and networking by Fortigate firewall.
I have replaced all zigbee shit devices with Shellies and everything is working flawless since november.
1 Like
Would you recommend such device after all the updates or would you take another one?
This would fit all my needs.
1 Like
I’m still on v1.1.3-rc16 and that is the most stable version for me. Sometimes one of the sensors drops offline for some unidentified reason but that is only once in 3 months or so.
I don’t dare to update anymore because it got even worse for me last time.
E.
I got over 30 of these sensors. they do go offline sometimes if the CoIoT is not well configured
And what are the right ColoT settings if I may ask?
Just put in the IP Address of your Home Assistant instance. If you haven’t messed with the Shelly.YAML configurations, you don’t even need to specify a port; it’ll just default to the one established in the configuration. Mind you, this must be done on the advanced settings page. IDK why, but it’s not available through the app, only the web portal.
I’ve spent more money on Shelly devices than I’m willing to admit to; far more than any other company.
Yeah, they occasionally have bugs, but they also work absurdly well if you’ve got a good WiFi network. They pack a lot of features and customizability into a pretty small (and relatively cheap) little package.
I don’t have to worry about someone accidentally messing with my ZigBee or Z-Wave antennas, because the routers are a home-wide mesh. I don’t have to worry about a dead node flooding the network, or slow bandwidth mandating painfully slow firmware updates.
My main gripe is that their web interface is rather crap; however, in the last few months they’ve made some significant improvements to the app. Honestly, it’s nearly as functional as the Tuya app now, and probably beats LIFX.
They are in the HA docs.
Shelly devices use the
CoIoTprotocol to communicate with integration. For Shelly firmware 1.10.0 or newer,CoIoTmust be enabled in the device settings. Navigate to the local IP address of your > Shelly device, Internet & Security >> ADVANCED - DEVELOPER SETTINGS and check the boxEnable CoIoT.
We recommend using
unicastfor communication. To enable this, enter the local IP address of the Home Assistant server and port5683into the CoIoT peer field and push SAVE button. This is mandatory for Shelly Motion with firmware 1.1.0 or newer. After changing the CoIoT peer, the Shelly device needs to be manually restarted.Integration is communicating directly with the device; cloud connection is not needed.
It seems half of this forum moans that the docs are insufficient, while the other half don’t even read them!
1 Like
yeah. i had over 50 devices z-wave… always issues with updates and all… didnt work for me… i upgraded my router and APs to industrial mode, and now all good! well over 200 devices my network working flawlessly
Version 20211223-144928/v2.0.5@3f0fcbbe firmware seems to be fine here.
OK, if that are the ‘right settings’ I’ve done them from the beginning. I tought I missed some fancy detailed settings…
1 Like
My Shelley Motion sensors have been flawless for quite a while although there is one minor thing that bugs me a lttle.
Even though they are still working with home assistant, I cannot browse to them after a while.
The simple fix is to ping the device. It sometimes tries up to 15 times before getting a reply but after getting replies I can browse to the device.
I suspect that this might be by design to save power.
This morning I updated from 2.0.3 to 2.0.5
Thank you! You are so b… right! Don’t buy this devices. These are the most expensive PIRs it bought and I spent hours to make it working; which does not really work at all! For a fraction of this you can buy, noName china HW, which is working flawless!
Working perfectly here.
No problems here either. Early problems were sorted out ages ago.
I highly recommend these sensors.
Perfect operation here as well. Could clearly separate between dogs and humans to get things sorted out in detail.
1 Like
Hi
My Shelly motion sensor kept losing Wi-Fi connection every 10 mins or so and not updating detection to Home Assistant.
My fault was to enable both MQTT and COIOT. I disabled MQTT and I have no loss off Wi-fi connection so far.
It has only been 3hours now but that is better then losing connection every 10 mins.
Green so far:
Wanted to post this here hoping it will help.