Beiträge von rousveiga

    I have the same issue with a Shelly Plug (FW v1.10.4-g3f94cd7) connected to a fridge; it's been cutting power at random times during the night, but when I check the power sensor history it doesn't show any noticeable peaks (for instance, when it happened last night it had been at about 90W for a few hours).

    But it doesn't affect everyone. I have another one on my washing machine, this one works without problems.

    Coincidentally, someone I know also has one on their washing machine, and theirs works perfectly as well.

    Hello!

    I have three battery-operated Shelly sensors (H&T, Door/Window 2 and Motion). I put this in the DW2 subforum because the system won't let me select more than one Shelly, but this applies to all three of them.

    Firmware version is v1.10.1 for the H&T, v1.1.0 for the Shelly Motion, and v1.10.2 for the DW2. I've configured them to use CoIoT and specified my host IP (my host is a Raspberry Pi with Home Assistant).

    My issue is, they don't seem to update values regularly, or very often, when left on their own. For instance, if I open and close the door my DW2 is on, it will report the illuminance, temperature, vibration, and open/close values. It might update frequently for a while, but after some time it stops (or takes a few hours to report again).

    Same thing happens if I shake my Shelly Motion, triggering the vibration sensor.

    I imagine the updates are not meant to be at regular intervals, and are instead triggered by changes sensed by the auxiliary sensors, in order to lower energy consumption. However, it seems that it only reports if the "main" sensor. Does anyone know how this works? Would it be possible, for example, to get my Shelly DW2 to report the values of all of its sensors if any of them change?

    Not trying to reverse-engineer the firmware here 🙂 I just want to know if I can use the DW2 as a temperature sensor as well as a door sensor, or if it's limited exclusively to being an auxiliary sensor for door status updates.

    Also, I'm now aware that the Shelly Motion has a bug that makes it go offline if no activity takes place for a long time.

    tl;dr: I've been trying to use secondary sensors in my Shelly sensors, like the illuminance sensor in the DW2 and Motion. However, these values don't get reported often (and the device often appears unavailable). Any info about how the Shellies decide when and which values to send would help.

    Thanks in advance!

    I have a similar issue as well; I'm trying to use the illuminance sensor in my Motion as a standalone sensor, as well as an auxiliary sensor for the Motion to know when to wake up, and the device going into low power mode mode so often makes it hard to get illuminance values. I'm glad to know the devs are working on it.

    And it turns out you can just tell the device that it's on external power in the UI eventhough it's actually on a battery and it'll then log every 10 minutes. :)

    Thank you for this tip! I've been looking for a way to make my battery-operated Shellies report values more often for a long time.

    Hello! Do these work with the original Shelly firmware? I'm looking to connect a PIR sensor to the GPIOs available for flashing, but I can't figure out how the firmware would detect that a PIR sensor has been connected, and I'd rather not go the Tasmota route.

    Thanks in advance!