Beiträge von gufalcon1

gufalcon1

Nice.

Thx to all of you.

The 'problem' that this setting isn't available was of course not connected to the battery drainage problem, as you all rightfully stated.

It wasn't clear to me from reading the documentation that this 'standard' setting isn't available on battery-driven devices. Maybe someone could point that out to make it clearer and avoid future misconceptions.

As to the battery problem... I got around it and the cause was rather stupid

So I turned off the LEDs, as one does.

And then I woke them up using a pin and by pressing the button until the shelly showed a reaction (4 times... which, of course, puts it in a mode where it stays connected to the WLAN)...

This of course would have been obviously visible when the LEDs would have been on, which they weren't... and so I didn't see this.

By getting them out of this mode (by pressing the button again 4 times) the battery consumption now has normalized and I can barely recognize any drainage at all... been 3 weeks and they went down a few percent ...

Thx for your help,

Gerald

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

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

Beiträge von gufalcon1

Betreiber hat sich geändert

Shelly Motion coiot_update_period doesn't work

Shelly Motion coiot_update_period doesn't work

Shelly Motion coiot_update_period doesn't work

Shelly 3EM

Shelly EM

Shelly PRO 4PM