AEOTEC TRisensor fw 1.21 (20200731) cannot set association groups

  • Platform information:
    • Hardware: Intel® Core™ i7-4785T CPU @ 2.20GHz, 32 GB RAM, 13 TB storage
    • OS: OS Name: Microsoft Windows Server Core Datacenter 10.0.18362 N/A Build 18362
    • Java Runtime Environment: Zulu 8.48.0.53-CA-win64) (build 1.8.0_265-b11)
    • openHAB version: 2.5.7
  • Issue of the topic: After firmware update of AEOTEC Trisensor to 1.21 not reporting either temp/motion/illumination information. I cannot set Accotiation Groups, log says Configuration update ignored.
  • If logs where generated please post these here using code fences:

2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update received
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_30_2 to 0 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_31_2 to 0 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored binding_cmdrepollperiod to 1500 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_11_1 to 2 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_10_1 to 1 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update set group_1 to null (null)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Association 1 consolidated to []
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Unknown association group 1
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update set group_3 to null (null)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Association 3 consolidated to []
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Unknown association group 3
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update set group_2 to null (null)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Association 2 consolidated to []
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Unknown association group 2
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored wakeup_node to 0.0 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_12_1 to 0 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_13_1 to 0 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_15_1 to 0 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_20_1 to 0 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_21_2 to 25 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored action_failed to false (Boolean)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored wakeup_interval to 28800.0 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored action_remove to false (Boolean)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored binding_pollperiod to 86400 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored action_heal to false (Boolean)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_1_2 to 30 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_100_2 to 1024 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_7_2 to 239 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_2_2 to 240 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_3_1 to 11 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_22_2 to 100 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_4_1 to 0 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_23_2 to 3600 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_5_1 to 3 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_24_2 to 3600 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored node_id to 4 (BigDecimal)
2020-08-20 12:23:19.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_6_1 to 0 (BigDecimal)

While waiting, perhaps our log viewer can provide hints. Unfiltered logs are needed for troubleshooting though.

According to the specification on AEOTEC support page some of the Command classes and its versions are changed compared to the ZWave database. Without any deeper knowledge of Z-Wave standards I noticed the following changes. Maybe this is the cause of inoperability:

  • COMMAND_CLASS_ZWAVEPLUS_INFO has improved to V2
  • COMMAND_CLASS_SECURITY_2 is new
  • COMMAND_CLASS_TRANSPORT_SERVICE is new
  • COMMAND_CLASS_MANUFACTURER_SPECIFIC has impoved to V2
  • COMMAND_CLASS_NOTIFICATION is new
  • COMMAND_CLASS_SUPERVISION is new

I also noticed that the device has no XML generated but on the UI it is recognized correctly.

That sometimes happens with newer firmware versions. we may need to create a new entry but the community maintained database is currently in transition to a new home.

thje device has not been fully discovered then and will not function properly in openHAB. The XML file is also needed to assist in updating the database.

So I’m stuck right now. I removed and included the device again but still no XML file, however it is reported in PaperUI correclty. How is that?
Also the device is only online if I wake it up manually…

Here is the log files:
ZWave0.log (1018.1 KB)
ZWave1.log (1018.0 KB)
ZWave2.log (578.8 KB)

Battery operated devices usually need to be woken up multiple times until OH discovery is complete.

OH needs the information from the device. Even if the database is incorrect, that information is stored in the XML file. The Z-Wave standard requires the device to respond with that information.

And what is the correct way of doing that?

After inclusion is initiated on Paper UI I pressed the button on device once, according to the manual. After that I pressed it several timer while the device is still in Inbox. If I see the correct name/id of the device I add it as a Thing but still no XML.

The second method I tried is that I added the device from Inbox as Unknown and after it is in Things tab I pressed the wake up button several times (and meanwhile I initiate an inbox search of ZWave binding). It sometimes gets the correct ID but sometimes not. The device has a fresh battery. No xml either.

Same stuggle here: ZWave not generating XML for Aeotec TriSensor

Even thought I was able to get the XML file generated, my struggle with the Aeatec TriSensor is far from being over. Unfortunately, I have no time to get you the details. I will send you the details next week.

Thank you. I wait for that.

Good day, I have updated my issue. Il is available now. Not sure if it will help you.

1 Like

Hi!

I have no idea how but this little evil alien device is working. Without any Z-Wave XML in the userdata/zwave folder. How is it possible? It reports motion/temp even battery status. I changed parameter 1 to 241 as AEOTEC support suggested to @Old-techno. And voilá it works since then. Even its configured association groups are kept. Is this xml file mandatory and I should expect later errors or I can relax and check this project completed?