Fibaro Motion Sensor ZW5 Always 0% Battery

🛎️ Get Help
14

Here's a snippet. A good bit in a short amount of time. I have it set to report quite often since I've been fooling with it.

All seems to be working as intended except for the battery.

dev:2442019-06-23 03:39:53.155 pm infoFibaro: temperature is 63.4

dev:2442019-06-23 03:39:35.972 pm infoFibaro: illuminance is 133

dev:2442019-06-23 03:38:52.735 pm infoFibaro: temperature is 63.9

dev:2442019-06-23 03:38:35.694 pm infoFibaro: illuminance is 125

dev:2442019-06-23 03:37:52.435 pm infoFibaro: temperature is 64.3

dev:2442019-06-23 03:37:35.461 pm infoFibaro: illuminance is 127

dev:2442019-06-23 03:37:20.393 pm infoFibaro: motion is inactive

dev:2442019-06-23 03:37:09.739 pm infoFibaro: motion is active

dev:2442019-06-23 03:36:52.260 pm infoFibaro: temperature is 64.3

dev:2442019-06-23 03:35:56.818 pm infoFibaro: motion is inactive

dev:2442019-06-23 03:35:51.834 pm infoFibaro: temperature is 63.7

dev:2442019-06-23 03:35:47.524 pm infoFibaro: motion is active

dev:2442019-06-23 03:35:34.959 pm infoFibaro: illuminance is 159

dev:2442019-06-23 03:35:18.866 pm infoFibaro: motion is inactive

dev:2442019-06-23 03:35:10.536 pm infoFibaro acceleration is active

dev:2442019-06-23 03:35:09.695 pm infoFibaro: motion is active

dev:2442019-06-23 03:34:51.764 pm infoFibaro: temperature is 63.2

dev:2442019-06-23 03:34:43.760 pm infoFibaro: motion is inactive

dev:2442019-06-23 03:34:43.723 pm infoFibaro: motion is inactive

dev:2442019-06-23 03:34:35.269 pm infoFibaro: motion is active

dev:2442019-06-23 03:34:34.710 pm infoFibaro: illuminance is 157

dev:2442019-06-23 03:33:51.507 pm infoFibaro: temperature is 62.6

dev:2442019-06-23 03:33:49.577 pm infoFibaro: motion is inactive

dev:2442019-06-23 03:33:40.740 pm infoFibaro: motion is active

dev:2442019-06-23 03:33:37.266 pm infoFibaro: motion is inactive

dev:2442019-06-23 03:33:34.389 pm infoFibaro: illuminance is 166

dev:2442019-06-23 03:33:27.331 pm infoFibaro: motion is active

dev:2442019-06-23 03:32:57.282 pm infoFibaro: motion is inactive

dev:2442019-06-23 03:32:51.259 pm infoFibaro: temperature is 61.9

dev:2442019-06-23 03:32:50.967 pm infoFibaro: motion is active

dev:2442019-06-23 03:32:31.196 pm infoFibaro: illuminance is 164

dev:2442019-06-23 03:31:50.999 pm infoFibaro: temperature is 61.4

dev:2442019-06-23 03:31:30.940 pm infoFibaro: illuminance is 171

dev:2442019-06-23 03:30:50.760 pm infoFibaro: temperature is 60.8

dev:2442019-06-23 03:30:30.678 pm infoFibaro: illuminance is 165

dev:2442019-06-23 03:29:50.443 pm infoFibaro: temperature is 60.8

dev:2442019-06-23 03:29:30.391 pm infoFibaro: illuminance is 161

dev:2442019-06-23 03:28:50.266 pm infoFibaro: temperature is 61.0

15

Hmm, now it's look fine but you have probably using this problematic driver? To get more info please try to use Basic Z-Wave tool driver.
Than you will see something like this:
dev:1952019-06-23 22:05:57.518 debugskip: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 3, 0])
dev:1952019-06-23 22:05:54.650 debugskip: Crc16Encap(checksum:65535, command:5, commandClass:113, data:[0, 0, 0, 255, 7, 0, 1, 3])
dev:1952019-06-23 22:05:31.378 debugskip: Crc16Encap(checksum:65535, command:7, commandClass:132, data:[])

16

Hi Mike.
Any more thoughts on this.
Everything works fine apart from battery reporting.

17

I was doing some rummaging around this morning in HE and my motion detector is now only reporting on motion, nothing else. In my memory, these did work earlier, and a search on events seems to suggest this, but only a long time ago.

I am using the built-in driver.

image
image.png1670×549 31.9 KB

18

Hi @mike.maxwell
Just bumping this.
Battery reporting still not working for the Fibaro Motion Sensor.
Any thoughts?

19

Interested to follow this for future updates...

I use these devices throughout my house back from my ST days and am keen to get them all working. Been a bit flacky with parameter updates until I discovered the Basic ZWave Tool however the behaviour of the devices are not respecting certain parameters (specifically the LED brightness) - hence my interest in a firmware update being a possible cause.

Anyway, we'll wait and see...just glad to see others in a similar boat.

20

Just bumping this as it's still outstanding over a year later...

21

I was looking back at this topic as I would like other data than motion to come through, but found a thread with information about it possibly being a firmware version thing.

I have previously mentioned that I found information from Fibaro that they will supply firmware to hub/gateway manufacturers, but there has not been any movement on that (that I know of) from the HE team.

Maybe at one point I have to consider simply replacing this piece of kit if I want more information than just movement ?

Digging into the forum I see a lot of posts about this sensor and not working correctly. HE staff have been tagged, but I can only imagine that fixing this is not high priority.

I am getting fed up with ZWave in general. It seems to work worse than Zigbee. At least my old ZWave equipment.

22

I feel your frustration. I've got two of these devices (had three until my son decided to roll it around on the floor :slight_smile: ) linked through HubConnect as they pair immediately with all features on Smartthings. They can be picked up relatively cheaply these days but you can almost be certain they're the old firmware version as the newer versions are stupidly expensive.

I agree on the zigbee piece, I find them more responsive and far cheaper. Other people may have their reasons for ZWave but for my personal circumstance - I don't want to break the bank to get motion automations working.

1 Like
23

I have one of these. I did get it as a cheaper (and perhaps better) alternative to the Aeon Labs Z-Wave sensors which are the workhorses in my house. Everything seems to work on it for me except battery which is reporting 1%. I do have to adjust temp by -10F to get a semi-accurate reading.

I am guessing by the age of this thread that the battery issue is not going to be solved? Thanks.

1 Like
24

I have two of these. One works great. The other doesn't report anything correctly but for motion and lux and if I pick it up, it gets that as well. It believes the room is 33F and the battery is at 0%, no reset works. I was just about to try removing and reinstalling it, now I'm glad I didn't.

One is newer than the other, so maybe I just have the two firmwares?

And I'm guessing this issue isn't going to be fixed?

25

Hey @katsrevenge

No such luck unfortunately, I ended up integrating these through Smartthings as I had the old hub I migrated across from. The device is supported there.

Not much help, but good for you to check in.

26

I only have a hubitat. That is kinda sucky, these are adorable little sensors (as far as sensors go), and when they work they are great.
I excluded, removed, re-included. It seems to be sort of fixed but is now claiming a very show range for connectivity. I just stuck it in a window to measure lux. It can at least do that @ 5 feet away from the hub.

27

I've got a bunch of these sensors from my Smartthings set up and am trying to pair with Hubitat. Has anyone come up with a solution? At the moment I really only care about illuminance but I'm not getting changes for any of the measurements.

Thanks!

28

I have one of these and I use the built-in driver. I opened the device page and clicked the include button 3 times fast and it will turn blue. At that time I clicked on Configure and waited until the blue light went away and all was working correctly.

There is also an advanced version of the driver.
https://raw.githubusercontent.com/tyuhl/FibaroZW5Motion/main/FibaroMotion.groovy

2 Likes
29

Wow thanks so much for that clarification. I figured this was a lost cause but it works now. Advanced driver version FTW!

1 Like
30

Sorry to be a dunce, but how do you wake up the device?

31

Push the button either once, or three times, I think three...

32

Thanks