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.
I feel your frustration. I've got two of these devices (had three until my son decided to roll it around on the floor ) 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.
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.
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?
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.
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.
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.
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.
) 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.
