FGDW-002 ingores temperature interval/reporting parameter values

[Duck 0]

Hi,

 

I've tried searching this forum but I could not find a solution for the issues I have with one of the Door/Window sensors (FGDW-002) I experience.

 

The problem

I've installed FGDW-002 at a door and, while the door is closed, I do get temperature reports every ~ 5 minutes (temperature is not changed or only changed 0.1C) while I changed parameters to only update once in a while (or not at all). Other values like door state or battery level or not changed when the temperature values are reported which is as expected (e.g. door was not opened).

 

I've changed parameters (mentioned here:

Please login or register to see this link.

) as follows:

50. Interval of temperature measurements: tried with 0 to disable and with the max value 32400

51. Temperature reports threshold: tried with 0 to disable and values 10, 20 up to 300

52. Interval of temperature reports: tried with 0 to disable and with the max value 32400

52. Interval of temperature reports: tried with 0 to disable

Wake up interval (battery mode): various values like 0 to disable 64800

 

My first concern was the actual setting of the parameter values into the sensor, so to verify values are stored I've changed parameter 1. Door/window state from 0 – closed when magnet near to 1 – opened when magnet near and that works as expected (opening the door changes the state to closed and vice versa).

 

Others things I've tried is changing the battery to a new one or remove the battery for an hour, all without a change of behavior.

 

My question

Is there anything I'm missing here that keeps the sensor reporting the temperature every 5 minutes? I do not need an update that much, once a day is more then enough in my case.

 

Setup

Domoticz (Version: 2023.1 (build 15372))

Zwave JS UI (zwave-js-ui: 8.19.0.487524b zwave-js: 11.0.0)

AEON Labs Z‐Stick Gen5 USB Controller ZW090 (FW: v1.2

Door/Window sensor 2 FGDW-002 Firmware 3.2

 

Best regards,

 

Duck

 

Snippet from Zwave JS UI Debug

{

      "time": "2023-07-12T12:52:18.003Z",
      "event": "wake up",
      "args": [
        1
      ]
    },
    {
      "time": "2023-07-12T12:52:19.037Z",
      "event": "sleep",
      "args": [
        2
      ]
    },
{
      "time": "2023-07-12T12:56:53.987Z",
      "event": "wake up",
      "args": [
        1
      ]
    },
    {
      "time": "2023-07-12T12:56:55.006Z",
      "event": "sleep",
      "args": [
        2
      ]
    },

[JustEnoughDucks 0]

Did you ever figure out this issue? I am having the exact same issue. Or something similar.

 

Reporting interval is 0. If I remove and re-place the batteries, then it works fine for 4-8 hours not reporting and then starts reporting every 30 seconds again.

 

My battery has gone from 100% to 20% in 2 days.

 

It is in a shed and it is between 5-7 degrees. Temperature is changing, but temperature_report_interval says that it supersedes the temperature change parameter.

 

It is still within the operating temperature that Fibaro specifies, using the original battery they provide.