I cannot get the third one paired any more. Same results as others are complaining…
Did you reboot your hub?, I guess that exorcism I paid the shaman to do on my network was worth the money…
I just wonder what this java warning means, I am getting it when I pair the sensor.
Exception ‘java.lang.StringIndexOutOfBoundsException: String index out of range: 3’ encountered parsing ‘cmd: upda, payload: ted’
No clue… 29.5 characs
Giving up for the night. Missus is start raving mad… The temp appeared from somewhere at 80 some degrees of it’s own after a while… May be the lux will appear if there is 200 lux change. Will leave this outdoors to check tmrw morning. Leave it outside tonite to see if the temp falls.
Where is @wackware? We desperately need you, buddy! Here is where I stand! 2 sensors which i paired a week back working perfect in all respect. New one that I paired today only detects motion, vibration some times, temp stuck at 85 (sitting outside at 30 some degrees), lux and battery blank. And two remain unopened if I decide to return.
Something is definitely wrong with configure.
Couldn’t resist it… I have three round sexy paperweights. oh @wackware hear our call, friend! Help us help us we beg of you !
It is not an issue and not causing anything.
OK folks, I think I have narrowed it down to hub firmware version. I found that with the new hub firmware version, it is difficult to consistently pair the motion sensor.
With the older hub firmware version (000.011.00709), I can consistently pair the device with all capabilities enabled.
This has been reported/submitted to ST. I will keep you all updated as I get info.
@wackware Wonder what the experience is for other Fibaro device pairing after the firmware update.
Me too. But I’ll have to check tomorrow. It’s my Birthday so I thought I’d take the day off and:
- Get windshield replaced (rock off gravel truck shattered it)
- Get car smog checked after that.
- Go to DMV and wait 2-3 hours to update car registration.
WOOOOHOOOO!
Happy Nappy Day, @wackware! Enjoy your day.
Sorry to hear about the windshield. And coincidence I just renewed my car registration online this morning.
Thanks guys for getting this narrowed down. Pair-unpair-reset hub-reset sensor-pair-unpair… was driving me mad!
Even after the latest firmware update it is back to square one - not working! We have no option but to wait for the gurus. Of course it is not supported officially but guys like @wackware, @Mike_Maxwell and others make it work for users like us…
Internally I am sure the temp. in it works fine as the motion flashes colors change based on the actual temp (flash colors are based on temp. by default). Same with vibrations. I think somehow the configure command after update while pairing has changed.
Not even in Todds league, but thanks for the mention!
Without @wackware there would be no Fibaro integration. As an average user, I would have not understood the params without you @Mike_Maxwell unless Mr. Todd put it in simple terms. Guys like @geko @scottinpollock @tslagle13 @625alex @beckwith ST support and each and every individual here so inspire me by whatever they are contributing.:. I didn’t want to mention names but these are some of the people I interact with and annoy on a daily basis. please don’t kill me if I didn’t mention any name in my admiration club. Hats off and cheers to you all.
Looks like I just got the firmware update. I had to reset my hub to get the zwave devices running again.
Has anyone tried using their Fibaro Motion Sensor as a Z-Wave Range Tester?
I would try mine but am afraid it might unpair.
Will try it tonight after work…