Aeotec trisensor 8 issues

🛎️ Get Help Devices
, ,
1

I connected a new aeotec trisensor 8 and provided custom driver code per Setup TriSensor 8 with Hubitat : Aeotec Help Desk

The issue I'm having is that the dashboards I have for temp readings and battery levels have "??" for this device. And on the actual device page, I don't get any status readings at the top outside of 'motion' (see attached).

any ideas?

aeotec-trisensor8
aeotec-trisensor81703×2284 379 KB

2

It's normal.

Attributes don't get updated until an event occurs from the device.

If, for example, updates are 1 hour, then you shouldn't expect to see a value for an hour. Yours is set for 24hours, which is great, but... :smiley:

3

The "official" Aeotec driver for TriSensor 8 (ZWA045 on chip 800) does not work for me at all on:

  • Aeotec TriSensor 8 from EU distribution
  • Hubitat C-8 Pro from EU distribution
  • Driver downloaded from Aeotec help desk
  • Device securely paired (S2) through SmartStart

The key issue of the driver is that it lacks a handler for supervision commands arriving from the device. It appears that, at least in my case, TriSensor 8 encapsulates all reports in supervision. Example log:

image
image1920×919 229 KB

This can be fairly simply fixed by adding a couple lines of code to the driver pretty anywhere:

// Handle S2 Supervision or device will think communication failed.
def zwaveEvent(hubitat.zwave.commands.supervisionv1.SupervisionGet cmd) {
  def result = []

  logger("trace", "zwaveEvent(SupervisionGet) - cmd: ${cmd.inspect()}")
  hubitat.zwave.Command encapsulatedCommand = cmd.encapsulatedCommand(getCommandClassVersions())
  if (encapsulatedCommand) {
    logger("trace", "zwaveEvent(SupervisionGet) - encapsulatedCommand: ${encapsulatedCommand}")
    result = result + zwaveEvent(encapsulatedCommand)
  } else {
    logger("error", "SupervisionGet - Non-parsed - description: ${description?.inspect()}")
  }

  result = result + response(cmdSequence([zwave.supervisionV1.supervisionReport(sessionID: cmd.sessionID, reserved: 0, moreStatusUpdates: false, status: 0xFF, duration: 0)]))

  return result
}

There are also other small things in the driver like some Unicode sign before the degree sign, and fingerprint which does not catch both secure and non-secure devices. I have contacted Aeotec support and provided them with my comments, so hopefully they will address this in the source code of the driver published on their support site.

I am sorry if I posted in the wrong place, I just bought Hubitat and I am both new to the ecosystem and groovy.