Does it respond on the firmware web interface? If so, what does a page by page comparison tell you?
Beiträge von biomass
-
-
BobSwede : Look at the top left of your browser window and check out the notifications page.
Anyone else is welcome to try and get a response from my control panel shown above
-
PS: check Account Management: Settings - Notifications
-
Synchronizing the time means you need to use the WiFi signal. I would not worry about the radio energy levels, your head would get much warmer from putting your head on or under your pillow.
-
Does your AP allow this traffic for the Shelly? Are local Wifi clients allowed to connect to other members of the LAN? Is the webserver on your LAN? Have you tried entering the server URL with the IP address instead of the hostname?
And most importantly: which firmware are you using with the device? I don't have issues saving an URL with Current version: 20210727-201754/v1.11.2-g25b6953
PS: check Account Management: Settings - Notifications
-
Which firmware are you using? I have had a Shelly Motion on the v2.0.0 firmware for just over 5 months, and it consumed around 5.8% per month. I just updated it to 2.0.5 because it stopped working at 69% battery level.When I tried to revive it on the charger, it came back alive with a battery level of around 45%. Did you charge it to 100% in Home Assistant or till the red charge light would no longer turn on?
Things that may affect your motion sensor battery life is poor reception by your AP and/or sensor, the WiFi radio then needs to be used at its highest powersetting and transmission retries will also sap the battery level. The battery consumption does not look normal if you ask me, but you should also check if you see any registration/deregistrations of the Shelly Motion on your WiFi accesspoint during the use with Home Assistant. If it is reregistering a lot, that might explain the high battery usage figures.
In that five month period I had the MQTT and CoIoT protocols but Shelly cloud or time sync was not enabled (to conserve power on the connectivity, I had no usecase for disabling the sensor on any interval)