Fibaro FGMS-001 excessive Battery drain

Configuration Z-Wave
1

I’ve switched over to Hassio, I’m not sure if this is a hardware issue or a hassio / z-wave config issue. For the last 2 weeksI’m going through batteries like crazy, I’ve reset to default and removed from hass and reinstalled. I’m at a loss, any ideas?
Here’s the node info:

averageRequestRTT: 23
averageResponseRTT: 8017
battery_level: 74
capabilities: routing,beaming
friendly_name: Fibaro
is_awake: false
is_failed: false
is_info_received: true
is_ready: true
is_zwave_plus: true
lastRequestRTT: 24
lastResponseRTT: 9016
manufacturer_name: FIBARO System
max_baud_rate: 40000
neighbors: 1,2,4
new_entity_id: zwave.fibaro
node_id: 3
node_name: Fibaro
old_entity_id: zwave.fibaro_3
product_name: FGMS001-ZW5 Motion Sensor
query_stage: Complete
receivedCnt: 175136
receivedDups: 3025
receivedTS: 2017-10-27 06:54:44:388
receivedUnsolicited: 175094
retries: 1
sentCnt: 72
sentFailed: 0
sentTS: 2017-10-27 06:02:40:845
wake_up_interval: 1

Tanks in advance for any help

2

The wake up interval is too short. It should be no less than 7200 (2 hours).

Your sensor is basically awake all the time, draining the battery.

3

Makes sense, I wonder why it changed when it had been working great for months. Also, I’m on my phone at the moment. How would I go about changing it? Thanks in advance

4

Use the control panel :wink:

5

That makes perfect sense… Lol. Never reply when distracted by work… :pensive:

6

So I did the wake up, refresh, set wake up value and reboot steps and in the node config options it still shows 1. When I looked in the OZW log I it shows Node003, Received Wakeup Interval report from node 3: Interval=7200, Target Node=1. So I guess it’s set now? Never mind it’s still awake at all times