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


Aeotec Multisensor 6 -no longer working after soft reconfig /reconfig


Pete123

Recommended Posts

Hi, 

 

I have a couple of Aeotec Multisensor 6. Two of them I did a soft reconfiguration. After that, once triggered, they are always triggered and will not update at all, like last trigger.

Then I tried a full reconfiguration, but it did not help at all. I have reset all parameters to default, same result.

 

Another I did nothing to, that one is working just fine.

 

Does anyone have a workaround for that?

Link to comment
Share on other sites

If those were working before, please restore the backup.
In the meantime we will try to reproduce the issue and prepare a fix for next beta. 

Link to comment
Share on other sites

Hi
You are not alone

Please login or register to see this link.

Please login or register to see this link.

:-)
After the last Firmware update to V 5.141.59
, I also did a soft-recon on all MS6 Sensors. ( as described in the Release Notes)
Now I have ALL (20x) MS6 NOT clearing motions anymore.

 

A "Restore & convert" did NOT do the trick.
"Restore with Version" it is!
So back to the previous Firmware - great

and soon we will have to go trough 20 soft recons AGAIN

👍Thanks to home-automation😁
What would we do with all the spare time?
 

Link to comment
Share on other sites

I suppose it is related with default value of parameter 5, the way the device sends Motion Detection report - it if possible please check if there is value 2 set there when there is a problem on new version?

Link to comment
Share on other sites

...update
Even a restore with version does NOT solve this
I will now go through the parameter setting AGAIN

I checked but Parameter 5 it was set to 1
Changing to 2 seems to do the trick - at least the 1st sensor cleared the motion now
ONLY 19 to go
The latest firmware:

Please login or register to see this link.

According to change log:
 

Quote

V1.14 Changelogs:

  • Basic Set faster report trigger when motion detected (when Parameter 5 [1 byte] = 1)

...until later I guess

Link to comment
Share on other sites

I changed all P5 to "2" and I run to trigger each and every sensor.
Most of them clear the motion now
EXCEPT for 2 Sensors
They where finally convinced after I sett P5 back to "1" and than to "2" again. (2 times)

SO ALL of them clear the motion now - GREAT 👍
 

So should we keep P5 on 2 now or change back to the default¨1¨ ??
...and then trying to update to the latest HC3 Firmware ?

 

Link to comment
Share on other sites

I will request to change the parameters template and change default value to 2 in next hub version.
In this case reconfiguration it will be set correctly next time automatically. 

Thanks guys for quick reaction and feedback!

Link to comment
Share on other sites

Hi thanks for your efforts👍

...but I do not think, that this is not the right way to go.

The question should rather be:
"Why do perfectly working Sensors, need a different setting after a template change?¨

 

Link to comment
Share on other sites

... and the question still is:

 

... and the question still is:

Should we keep P5 on "2" now or change back to the default¨1¨ ??
...and then trying to update to the latest HC3 Firmware ? 

Link to comment
Share on other sites

Sorry for the hijack.........

Do the Aeotec MS6 now report as USB device or still as battery operated devices?

That's the case in the Z-wave engine 3.0 beta

Link to comment
Share on other sites

I did not check that, but all my MS6 are USB powered.
How could a template change that?

USB or Battery powered:

Maybe it does that if "during inclusion" it was Battery powered??
Currently NONE of the MS6 sensors are showing "Battery powered"

Restoring the last Backup with Firmware, did not solve the problem.
Only the changing of P5 to"2" did restore the PIR sensor clearing. WHY?

 

I will now update to the latest Firmware 5.141.59 (beta)again.
I will check again after update BUT before any soft-recon.

 

Link to comment
Share on other sites

... update
to answer 

Please login or register to see this link.


After the firmware update, all MS6 are NOT showing "Battery Powered" - GOOD
... still on Z-wave engine 2

 

I then did a soft-recon on the 1st device .
Except for the UV Sensor, MOST of the MS6 sensors kept there ID's, except for the UV Sensor.
I have seen this again and again with all soft-reconfigured devices!
Randomly some of the devices get new ID's
This is NOT suppose to happen!!!
Has anybody else noted this ??
 

However, with P5=2, the PIR sensor is now detected correctly and motion is detected and cleared - GREAT 👍

 

I then tried the P5=1 again and then the motion is not even detected anymore. 😥
Changing back to P5=2  and the motion is detected and cleared - Good 👍

I am afraid that sending the "Sensor Binary Report CC" will cause a lot more z-wave traffic!
Am I right?

The next update will hopefully resolve this issue.

so long 👍
Jürgen

 

Link to comment
Share on other sites

In this case no, and Basic set commnad is not a report - it is a controlling frame and should not be used.

In this case Binarny Sensor Report is protocol complient.

 

Anyway, I asked the team to verify also why Basic Set is no longer mapped to motion detection - even if this configuration is not fully correct anyway.

Link to comment
Share on other sites

I understand.

Sadly this seems to be unknown to Aeotec!
The latest firmware:

Please login or register to see this link.

According to change log:

V1.14 Changelogs:

  • Basic Set faster report trigger when motion detected (when Parameter 5 [1 byte] = 1)
Link to comment
Share on other sites

However,

I will use the P5=2 setting from now on.👍

Thanks for your help :-)

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

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...