[RELEASE] Aeon Multisensor 6 (Advanced)

dth_sensors

#283

Great documentation!


(Micheal ) #284

Thanks. Always a work in progress. Feel free to point out and weak areas or something that might be missing.


(Hendre) #285

Hi @erocm1231. I have been using your DTH for some time and it has been working fantastic. Thank you for creating the DTH.
I have, however, now added a new Sensor to my setup after updating to firmware FW 1.11. (Euro version). Before including the sensor, I upgraded the DTH to the latest version.
I don’t seem to be able to get the sensor to sync the configuration, as the red dot remains on the “Configure” tile. The sensor appears to be working fine. I tried excluding and re-including the sensor but that did not help.
The sensor was included in secure mode:
zw:Ls type:2101 mfr:0086 prod:0002 model:0064 ver:1.11 zwv:4.54 lib:03 cc:5E,98,84,5A sec:86,72,59,85,73,71,80,30,31,70,7A role:05 ff:8C07 ui:8C07

I tried various settings, but nothing seems to help. Currently, the settings are the following:

Preferences (edit)
Name Type Value
paragraph
101 enum 240
111 number 3600
201 decimal 0
202 number 0
203 number 0
204 number 0
3 number 10
4 number 5
40 enum 0
41 number 10
42 number 10
43 number 20
44 number 10
45 number 2
5 enum 1
8 number 30
81 enum 1
enableDebugging boolean false

Edit (Further info):
I use Z-wave tweaker to clear all settings on the sensor. After changing back to your DTH, I went into settings and pressed Save without changing any settings. The configuration sync completed successfully. I again went into settings, again without changing anything, but this time the sync did not complete after pushing “Save”. I tried a few time more with the same result.

The IDE log of this process shows the following. It seems that parameter 41 may be the issue?:

 10f568bf-158d-492c-8898-92427b917260 08:07:01: debug Living Room Sensor parameter '41' with a byte size of '4' is set to '1310976'
10f568bf-158d-492c-8898-92427b917260 08:06:59: debug Parameter 41 will be updated to 1311231
10f568bf-158d-492c-8898-92427b917260 08:06:59: debug Device Living Room Sensor woke up
10f568bf-158d-492c-8898-92427b917260 08:06:10: debug Living Room Sensor parameter '41' with a byte size of '4' is set to '1310976'
10f568bf-158d-492c-8898-92427b917260 08:06:08: debug Parameter 41 will be updated to 1311231
10f568bf-158d-492c-8898-92427b917260 08:06:08: debug Configuring Device For SmartThings Use
10f568bf-158d-492c-8898-92427b917260 08:05:48: debug Living Room Sensor parameter '41' with a byte size of '4' is set to '1310976'
10f568bf-158d-492c-8898-92427b917260 08:05:46: debug Parameter 41 will be updated to 1311231
10f568bf-158d-492c-8898-92427b917260 08:05:46: debug Configuring Device For SmartThings Use
10f568bf-158d-492c-8898-92427b917260 08:03:46: debug Living Room Sensor parameter '41' with a byte size of '4' is set to '1310976'
10f568bf-158d-492c-8898-92427b917260 08:03:43: debug Parameter 41 will be updated to 1311231
10f568bf-158d-492c-8898-92427b917260 08:03:43: debug Configuring Device For SmartThings Use
10f568bf-158d-492c-8898-92427b917260 08:03:36: debug Living Room Sensor parameter '41' with a byte size of '4' is set to '1310976'
10f568bf-158d-492c-8898-92427b917260 08:03:36: debug Living Room Sensor parameter '41' with a byte size of '4' is set to '1310976'
10f568bf-158d-492c-8898-92427b917260 08:03:33: debug Parameter 41 will be updated to 1311231
10f568bf-158d-492c-8898-92427b917260 08:03:33: debug Requesting device firmware version
10f568bf-158d-492c-8898-92427b917260 08:03:33: debug updated() is being called
10f568bf-158d-492c-8898-92427b917260 08:03:33: debug Parameter 41 will be updated to 1311231
10f568bf-158d-492c-8898-92427b917260 08:03:32: debug Requesting device firmware version
10f568bf-158d-492c-8898-92427b917260 08:03:32: debug updated() is being called
10f568bf-158d-492c-8898-92427b917260 08:03:09: debug Living Room Sensor parameter '81' with a byte size of '1' is set to '0'
10f568bf-158d-492c-8898-92427b917260 08:03:09: debug Living Room Sensor parameter '81' with a byte size of '1' is set to '0'
10f568bf-158d-492c-8898-92427b917260 08:03:07: debug Living Room Sensor parameter '3' with a byte size of '2' is set to '240'
10f568bf-158d-492c-8898-92427b917260 08:03:06: debug Living Room Sensor parameter '3' with a byte size of '2' is set to '240'
10f568bf-158d-492c-8898-92427b917260 08:03:05: debug Living Room Sensor parameter '43' with a byte size of '2' is set to '100'
10f568bf-158d-492c-8898-92427b917260 08:03:04: debug Living Room Sensor parameter '43' with a byte size of '2' is set to '100'
10f568bf-158d-492c-8898-92427b917260 08:03:02: debug Living Room Sensor parameter '41' with a byte size of '4' is set to '1310976'
10f568bf-158d-492c-8898-92427b917260 08:03:02: debug Living Room Sensor parameter '41' with a byte size of '4' is set to '1310976'
10f568bf-158d-492c-8898-92427b917260 08:03:00: debug WakeUpIntervalReport WakeUpIntervalReport(nodeid: 1, seconds: 240)
10f568bf-158d-492c-8898-92427b917260 08:03:00: debug WakeUpIntervalReport WakeUpIntervalReport(nodeid: 1, seconds: 240)
10f568bf-158d-492c-8898-92427b917260 08:02:58: debug Parameter 81 will be updated to 0
10f568bf-158d-492c-8898-92427b917260 08:02:58: debug Parameter 3 will be updated to 240
10f568bf-158d-492c-8898-92427b917260 08:02:57: debug Parameter 43 will be updated to 100
10f568bf-158d-492c-8898-92427b917260 08:02:57: debug Parameter 41 will be updated to 1311231
10f568bf-158d-492c-8898-92427b917260 08:02:57: debug Setting Wake Interval to 240
10f568bf-158d-492c-8898-92427b917260 08:02:57: debug Requesting device firmware version
10f568bf-158d-492c-8898-92427b917260 08:02:57: debug updated() is being called
10f568bf-158d-492c-8898-92427b917260 08:02:57: debug Parameter 81 will be updated to 0
10f568bf-158d-492c-8898-92427b917260 08:02:57: debug Parameter 3 will be updated to 240
10f568bf-158d-492c-8898-92427b917260 08:02:57: debug Parameter 43 will be updated to 100
10f568bf-158d-492c-8898-92427b917260 08:02:57: debug Parameter 41 will be updated to 1311231
10f568bf-158d-492c-8898-92427b917260 08:02:56: debug Setting Wake Interval to 240
10f568bf-158d-492c-8898-92427b917260 08:02:56: debug Requesting device firmware version
10f568bf-158d-492c-8898-92427b917260 08:02:56: debug updated() is being called
10f568bf-158d-492c-8898-92427b917260 08:02:43: debug Configuring Device For SmartThings Use
10f568bf-158d-492c-8898-92427b917260 08:02:33: debug WakeUpIntervalReport WakeUpIntervalReport(nodeid: 1, seconds: 3600)
10f568bf-158d-492c-8898-92427b917260 08:02:30: debug Setting Wake Interval to 3600
10f568bf-158d-492c-8898-92427b917260 08:02:30: debug Requesting device firmware version
10f568bf-158d-492c-8898-92427b917260 08:02:30: debug updated() is being called 

Thanks


(Juris Ducens) #286

Hi!

I have the same setup (FW 1.11, same DTH) and same problem with parameter 41 (Temperature Threshold). Only difference - I use sensor in insecure mode.

When I removed this parameter from sensor configuration page in my mobile app - all the configuration sync for other parameters succeed.


(Hendre) #287

That worked for me as well.


(Mikkel Winther) #288

Do you know if there’s a way to push a sync? It’s been close to two weeks now and the dot is still present.


(Neil Broussard) #289

Extremely newbie question; When I edit the sensor to change the DH, what is the DH I am looking for? I only see 1 that makes any sense. I have the code published. THX


(Eric M) #290

Custom handlers are down at the bottom of the list. If it is published it should say “Aeon Multisensor 6 (Advanced)”

@MikkelWinther If you open the device and press the button on the back, it should sync the parameters. If it hasn’t synced them in that long, there might be one that isn’t working properly. Watch the logs when it syncs to see if there is an issue.

@949BFN There may be something wrong with the parameter conversion for the euro version for parameter 41. I’ll take a look.

Edit: I made a change that I think will fix parameter 41 for EU fw 1.11

@BartschLabs I also made a change so the OOMI sensor config parameters should get unlocked. Credit goes to niothiel on Github for the pull request.


#291

I have several of these in my home and for the most part they work great with your code. Thanks so much for your work on this.
One thing that’d odd. All of my battery powered sensors always show 100% on the battery level.
Is this normal?


(Yuri Dogandjiev) #292

Hey guys, after updating two out of my six sensors to firmware v1.10 I am seeing a consistent (and inaccurate) jump in the temperature and relative humidity readings from both. Anyone else seeing that? Is it possible to roll back to firmware v1.08?


(Alwas) #293

Yes, Eric, I FINALLY have the orange dot for the first time since I bought this v 1.08 sensor 2 months ago! And thank you to everyone who helped troubleshoot this thing, good work. The battery life on these things are amazing anyway, but finally I can change away from the default parameters.


(Alwas) #294

@zwizard yes showing 100% battery is completely normal. I have a v 1.07 in the garden still showing 100% that’s been running for 458 days!


(Yuri Dogandjiev) #295

I would highly recommend against anyone updating their MultiSensor 6 to firmware v1.10. I’ve updated all 6 of my sensors and here is my experience so far:

  • 4 of the sensors are reporting firmware v1.10 and working fine thou the temperature and relative humidity readings seem to be slightly elevated
  • 1 of the sensors is reporting firmware v1.10 but it has an empty square where the lux reading is supposed to be and the rest of the metrics seem really wrong
  • 1 of the sensors appears stuck in v1.08 no matter how many times I try to update it; the Configure option has a permanent red dot next to it now

I’ve been using an Aeotec Z-Stick to do the updates and I am running @erocm1231’s latest DTH. I’ve reached out to Aeotec about these issues and will report back once I hear from their support team.


(www.smartukhome.co.uk) #296

Was about to buy a Aeotec Z-Stick to do the updates. All I want to do is disable the LED in the bedroom not sure if its worth it then.


#297

It should be possible to roll back. Just run the 1.08 fw update process.


(Neil Broussard) #298

Figured it out. Grabbed the wrong handler from your repo…duh


(John P. Hoke) #299

Is this DTH tied to firmware versions 1.08+? I am running some @ 1.07 and as I do not have a ZStick nor a windows device handy, I cant really do the firmware upgrade … will have to get a stick and borrow a windoze laptop from someone to do this when I can

:frowning:


#300

@JohnHoke, both the MichaelS DTH and the erocm1231 DTH that it’s based on accommodate firmware versions between 1.06 and 1.11. Anybody please correct me if I’m wrong.


(Micheal ) #301

Correct. I am treating @erocm1231 as the one source of truth and I update based on his changes.


#302

@ydogandjiev, thanks for describing the details of your experience with f/w 1.10. Personally, all of my 4 sensors upgraded to 1.10 fine and display readings correctly (although I did have to adjust each temperature offset by varying amounts). However, I’m trying to figure out the right combination of settings to achieve expected reporting/update intervals. I’m not sure if the problem is caused by the f/w update. I’m leaning towards something in the DTH.