Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


FGMS001 v2.8 & v3.2 not reporting battery status at all


Recommended Posts

Posted (edited)

After almost a year playing with Fibaro I can say that motion sensors are not reporting their battery status at all. They are all on 100% and that is just impossible! Due to this bug I already had two times problems with them.

 

Unfortunately first time it was motion sensor v3.2 in garage and it just stop working and updating status. I try with moving it near to HC2 and waking up but it didn't work. Then I make mistake (now I know that, but in that time it seemed like only solution) and try to delete it from my system and re-include. Consequence is two orphaned devices from it that can't be deleted and re-included motion sensor that was still acting strangely until I changed battery.

 

Second case just happened with motion sensor v2.8 (OTA upgraded) in kitchen. First I noticed that temperature reading was not correct (11.7'C) and then also light measuring go crazy:

 

Please login or register to see this attachment.

 

First I just manually wake up motion sensor and it updated measuring but was still not correct:

 

Please login or register to see this attachment.

 

so I decided to do SOFT reconfiguration (again MISTAKE!) and result was that battery showed as empty and light sensor disappeared:

 

Please login or register to see this attachment.

 

At the end I finally replaced battery and sensor started to work properly again, but still missing light sensor. So again I did SOFT reconfiguration and it appeared under Unassigned with new ID number and default description, not description i gave to it:

 

Please login or register to see this attachment.

 

Of course, I corrected description and room assignment and I had to change it's ID in one scene that updates table with ID's of all devices, scenes and users so I don't have to edit all scenes that use this sensor.

 

So, when you encounter some battery operated sensor behaving erratically or crazy, FIRST REPLACE BATTERY, and then only if that doesn't help go further with action! I hope that Fibaro will eventually make this battery status working as it should because now it can give users a lot of headache.

 

Thank you for reading and I hope that this post will help some of you to avoid bad experience with re-including battery operated devices, making orphan devices and who knows what other problems when it should be enough just to replace battery!

 

Edited by Sankotronic
Attachment quota filled up / deleting older stuff sorry :-(

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...