Aeotec tri sensor problems

I have a new aeotec trisensor. I connected it as I’ve done with other multisensors. It seemed to connect, but there don’t appear to be any config value options. Clicking on the config values does nothing.

The original wakeup time was 28800 (8 hours), so I tried changing it to 900, but now somehow it’s set to 1800. I tried a factory reset based on reading some other threads, but all that did was add 3 extra entities to the list of entities found.

Now I don’t know what I should do. How can I remove the node entirely from HA? I tried remove node, but that doesn’t seem to do anything.

Originally it came up with the node name aeotec_limited_unknown_0202_0005, so I renamed the ‘unknown’ part to TS10 (Trisensor node 10). It says that it is ‘Complete’, but it’s been sleeping the last 21 hours

So, I just unboxed another TS and started from scratch again. Add node didn’t seem to have an effect, but add node secure seemed to work and it’s recognised as Node011. It completed OK, like the first one did, but still there are no config values shown.

I know there does seem to be a timing thing going on when you first add devices, which I don’t understand and it does appear that the devices are functional, but the lack of config values doesn’t seem right. There should be a bunch of them.

Which trisensor are you trying to add? Is it Zwave version 1.6 maybe? Got a similar issue with a new Aeotec siren, caused by Home Assistant not having support for Zwave 1.6 yet

Not sure @jasper1983x. It’s a recent aeotec trisensor. How can I find the version number?

I don’t have this device, but was curious…I believe this is part ZW005A (for the U.S. anyway).
In OpenZwave version 1.4, there is a manufacturers xml file, and this part is not listed.
In OpenZwave “master branch” (version 1.6+) it is listed as follows:

    <Product config="aeotec/zwa005.xml" id="0005" name="ZWA005 TriSensor" type="0002"/>
    <Product config="aeotec/zwa005.xml" id="0005" name="ZWA005 TriSensor" type="0102"/>
    <Product config="aeotec/zwa005.xml" id="0005" name="ZWA005 TriSensor" type="0202"/>

and there is also n aeotec specific xml file for this device which contains the configuration parameters. This file is:
aeotec/zwa005.xml

If you’re using Home Assistant’s native ZWave, it uses OpenZWave version 1.4 which would explain why you don’t get these to show up. If you know how to get to these files on github and as well as how to get to these on your HA, you may want to edit/add those files for this device and see what happens. There is some incompatibility between versions 1.4 and 1.6, but most likely won’t be too hard to figure out.

Thanks @wmaker, the devices actually seem to work OK, with a 30 minute wakeup and are reporting data. I looked at the files on github and it does appear that the XML could transfer to my haasio setup. I might leave it for another day though as my pain threshold these days for solving IT problems is not what it used to be :smile:

Did anyone figure out how to get this Tri Sensor to report motion in a timely manner in HA?