Shelly Motion coiot_update_period doesn't work

gufalcon1

Hi! I have about 12 shelly motion and they're draining battery like mad. We're talking a full recharge after two weeks and it doesn't really matter how often they trigger or not.

So I thought they have to boot up their WIFI module more often than necessary and I read about the settings/coiot_update_period field in the documentation.

But I cannot set it. It doesn't matter what I try, it always stays the same.

Maybe someone can help.

Here's a sample REST-request trying to set it (tried both GET and POST with the same result of it being set to 3600)

What is happening here and how am I the only one getting this?

Firmware is up to date. Doesn't matter if I reset the Shelly...

Code

10.10.197.25/settings?coiot_update_period=3500
# OUTPUT:
{
    "device": {
        "type": "SHMOS-01",
        "mac": "60A423DAE52A",
        "hostname": "shellymotionsensor-60A423DAE52A",
        "num_outputs": 0
    },
    "wifi_ap": {
        "enabled": false,
        "ssid": "shellymotionsensor-60A423DAE52A"
    },
    "wifi_sta": {
        "enabled": true,
        "ssid": "dahoam",
        "ipv4_method": "dhcp",
        "ip": null,
        "gw": null,
        "mask": null,
        "dns": null
    },
    "mqtt": {
        "enable": false,
        "server": "192.168.33.2:1883",
        "user": null,
        "id": "shellymotionsensor-60A423DAE52A",
        "clean_session": true,
        "max_qos": 0,
        "retain": false,
        "update_period": 60
    },
    "sntp": {
        "server": "time.google.com",
        "enabled": true
    },
    "login": {
        "enabled": true,
        "unprotected": false,
        "username": "admin",
        "default_username": "admin"
    },
    "pin_code": "!8j6FA",
    "name": null,
    "fw": "20211223-144928/v2.0.5@3f0fcbbe",
    "discoverable": false,
    "build_info": {
        "build_id": "20211223-144928/v2.0.5@3f0fcbbe",
        "build_timestamp": "2021-12-23T14:49:28Z",
        "build_version": "2021122314"
    },
    "cloud": {
        "enabled": false
    },
    "coiot": {
        "enabled": true,
        "update_period": 3600,
        "peer": "10.10.196.4:1901"
    },
    "timezone": "Europe/Vienna",
    "lat": 48.323040,
    "lng": 14.290930,
    "tzautodetect": true,
    "tz_utc_offset": 3600,
    "tz_dst": false,
    "tz_dst_auto": true,
    "time": "15:39",
    "sleep_time": 0,
    "motion": {
        "sensitivity": 10,
        "blind_time_minutes": 3,
        "pulse_count": 1,
        "operating_mode": 0,
        "enabled": true
    },
    "tamper_sensitivity": 0,
    "led_status_disable": true,
    "dark_threshold": 20,
    "twilight_threshold": 200,
    "schedule": false,
    "schedule_rules": [],
    "hwinfo": {
        "hw_revision": "dev-prototype",
        "batch_id": 0
    },
    "sleep_mode": {
        "period": 60,
        "unit": "m"
    }
}

Alles anzeigen

biomass

You've enabled DHCP. Are you able to assign it a fixed IP or give it a fixed DHCP IP ? Your CoIOT peer is on a slighlty different network than the Shelly motion (10,10,197.x vs 10.10.196.x). If any timeouts results in the Wifi radio of the Motion being on for a long time, that will hurt battery life? How is the connectivity while you have the device on the charger?

gufalcon1

The connectivity is perfect while on charger. And it's perfect while off as well. No problem there. My network submask is 255.255.0.0, so no routing there at all. It's not a connectivity issue.

The Shellys get their IP every time without fail (it's fixed on the firewall that acts as a DHCP server).

The problem is the battery draining.

But the real problem is that I cannot change the setting while every documentation says I can.

Can somebody this as a problem please.

thx

Gerald

biomass

According to the API for the Motion, the parameter that you see in the generic HTTP API, is not available. Since the Motion is battery operated, I would think that you cannot change that parameter as it would change the energy consumption drastically depending on the user input. The parameter is mostly there for software like Home Assistant to know when the device is offline (e.g. has not come back with an update within 1 hour).

If the 1 hour update period is a given, how often do you see your Motion devices connect to your AP?

Seven of Nine

From what I know Coiot_update_period is fixed to once per hour (3600 seconds) and cannot be changed.

But I doubt this is related to the problem..

gufalcon1

Do you use an external system to ping the shelly motion or query their REST-API regularly? this would be a real battery killer..

Shelly Motion coiot_update_period doesn't work

Betreiber hat sich geändert

Shelly 3EM

Shelly EM

Shelly PRO 4PM

Ähnliche Themen

Shelly Motion: all i/o actions are gone

Shelly Cloud Skill in Canada Not working

Shelly Motion weird behaviour

Shelly Motion forgets CoIoT setting after reboot

Working with switch

Shelly 1 - web hooks doesn't work after firmware update

Tags