I just purchased a Fibaro Motion Sensor ZW5 that was a bit flaky at first but seems to have settled into reporting accurate motion, temperature, and luminance. But the battery is reporting 0%. The device is working so it's gotta have power.
Has anyone else experienced this problem with this or any other battery driven device? Is it possible that it is reporting 0% because the Fibaro doesn't report battery level? Any help would be appreciated.
I have the same device and use the same driver. The device can report battery, but there is something not working correctly in the driver. Just yesterday a user here released his take on the Fibaro smoke alarm that finally now works correctly. Not sure if techniques from his driver can be applied to the motions sensor driver.
Edit: Actually, my driver says 100% all the time, not 0%. But, it can take a while for a Z-Wave device to properly update after changes have been made.
Thanks for the information. I'll just keep an eye on it, then do an exclude/include in a couple of months. All of the sensor functions work except for the battery, so it is functioning as it should for the moment. But, I'll play with it a bit before actually depending on it for anything crucial.
Yes, same here.. Everything works fine, except for the battery. That of course also means, once the battery is depleted, I won´t know 
Can you see any battery level reports in the events log for the device?
Edit: Just checked one of mine and I've not had a battery report since last November probably when I paired it.
@mike.maxwell is there an issue here with the HE Fibaro Motion Sensor ZW5 driver not reporting battery levels.
Similar situation here.. has not reported battery in a long time, since December last year, most likely when I installed it.
I mentioned above that a user @urbanski managed to create a nicely working port of the Fibaro DTH for the Smoke Sensor to include all functions. I reviewed what he had done to fix this and tried my hand at applying the same to the motion sensor DTH, but unfortunately I failed 
I have no battery level reports in the logs.
I decided to take drastic measures. I excluded the ZW5, did a factory reset, then ran inclusion. 100% battery level?
Yes. But now neither the luminance level nor the temperature level are changing. It's always 83.9 degrees in my house with a luminance level of 203.
Nothing changes and nothing gets logged except motion, including the 100% battery. Perhaps Fibaro is not for me. Any recommendations for a multi sensor?
I would suggest it's not a device issue but a driver issue. It works OK with ST and reports everything as expected.
Any suggestions @mike.maxwell?
Yeah, I'm sure that's the case. The LED on the device has colors/patterns indicating the various states of things and it is functioning as it should. But, if there is a multi sensor out there that has drivers that are proven to "play well" with Hubitat, I'm willing to go that route.
Try changing one of the preference settings, the current state attribute pendingChanges should change to 1, if you wake up the device that setting should apply and pendingChanges should go back to 0.
I've done as requested and saw it change to 1 and back to 0 after it updated.
Looking at the events could see illuminance, temperature and motion reports but no battery report after the update.
Hi 
Could someone maybe add raw logs from this device?
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
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:[])
Hi Mike.
Any more thoughts on this.
Everything works fine apart from battery reporting.
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.
Hi @mike.maxwell
Just bumping this.
Battery reporting still not working for the Fibaro Motion Sensor.
Any thoughts?
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.
Just bumping this as it's still outstanding over a year later...
Download the Hubitat app
