Built in Driver for Aeotec AERQ Temp and Humidity Sensors

The zwave network has been great for 10 years - only since Christmas has it ever shown any issues, which coincided with the migration to HE.

Could be a coincidence.

But having 100+ zwave devices with 80+% being mains powered I would expect it to be solid.

Certainly the devices all work Ok, and are reporting nicely, only the Including element is messing up, if you included the barrage of Ghost Devices created by including a device.

So I agree with you, would have stayed with a v5 zwave, but did not see that as an option on 24 Dec.

I have onboarded a lot of devices since Christmas, certainly the Inclusion process has be very clunky indeed, and as they were included 2 ft from the HE Hub don't believe the zwave network quality was a contributing factor in the inherent unreliability and subsequent spawning of ghost devices that require 20+ Remove attempts and hub reboots before they finally go.

These devices, being v7 devices are the absolute worst devices to connect to Hubitat to date and that is a tough one to win, with so much competition for that title.

The Aeotec seems incredibly well built and it is surprising to find them so bad.

I am left leaning towards the issue being HE c7 rather than the device, given that the SiLabs 700 fw bug is causing so many issues inside HE to make HE appear just confused - adding through SMARTSTART once results in 4 Devices showing - ALL OF which fail to include.

Also, the way that you have to press REMOVE so, so very many times to get a ghost device to die.

Well, now that there are other zwave 700 hubs on the market, I guess we'll see for sure whether it is sdk/software/firmware related, or Hubitat specific. :wink:

I have 3 different zwave 700 hubs right now, all different SDK/software versions (including the very latest released on 1 of them), I can make weird crap happen on all of them during pairing, exclusion, and with odd routing behavior - although different weird things on each... lol. So I don't think it is 100% unique to Hubitat, as much as I think it may be SDK/software v7.xx related.

But 'tis what it 'tis.

2 Likes

Feck me, 100+ devices, well that rules out my previous statement, I have about 20.

Definately something funky going on but the debugging on the c7 is only slightly better than c5. Even Home Assistant z-wave debugging is miles ahead.

The AEOTEC AERQ sensors included straight away with a 500 series zwave system- Included both devices in less than 2 minutes.

And that system included the Dew Point reports from the sensor :slight_smile:

So maybe the 700 series is just still too new for now.

I need to start thinking migrating the zwave back and keep the HE for the zigbee and put in MQTT back to the parent controller.

I need a home automation controller that I can add zwave devices to it and not take up a day and only get one of the supported devices to work and by the way drain the £5.99 batteries of two it would not Include.

Ok back to the drawing board for me.

Don't blame you, upgraded to a c7 to fault find my aeotec trv which ended up in a drawer anyway but now have all my fibaro devices paired via S0.

I am using 15 Sprit (AEOTEC) TRVs and they are great!!!!!

Absolutely rock solid!!

I use this driver

1 Like

As long as you don't want/need S2 security that's an option. I want S2, so I won't go back to z2m at this point.

Actually noticed what is missing from the default driver for Aeotec AERQ sensors, the temp offset, and probably the humidity offset, these are in other default/ built in temperature drivers but not this one.

And if the hood is open the Dewpoint report would be useful to grab.

My experience was pants! Using a wired solution now. I did mention my issues in that thread.

Any idea of implementing security on them vaporised earlier this year when I ran into a wall of security related issues.

So I have moved the Hubitats to their own vlan and isolated them, and there they sit on the network ‘naughty step’ :slight_smile:

@JasonJoel

Do you have any idea how/where, that you can share,

I could ask for the built in Aeotec AERQ zwave driver to incorporate a Temperature Offset as supported in other built in Temperature Sensor Drivers?

I think adjustable offsets are a good feature for any sensor that does a measurement that could require calibration (temp, humidity are common ones).

I guess @bcopeland or @mike.maxwell would be the ones to get the request to. A number of other in-box drivers have offset ability, so I would guess they would be receptive to adding it at some point.

1 Like

@JasonJoel Thank you.

@bcopeland / @mike.maxwell what is the best way to request this Temp Offset feature be added to the built in Aeotec AERQ sensor.

BTW - this sensors have settled down and are reporting much more reliably now, need to update my post on initial findings

1 Like

You just did :stuck_out_tongue_winking_eye:

4 Likes

Thank you :slight_smile:

Will help a lot

Any chance the built-in driver's Periodic Report Level could be as low as 5 Minutes? :grin: I am using it with the Bathroom Humidity Fan app, which recommends 5 mins or less.

+1 on a more frequent poll.

Also anyone know how to get access to the dew point reading? Or mould sensor on the aeotec aerq?

Would you not be able to use the Humidity change report function? ie when humidity changes 1% report - the humidity is only really going to change when the room is in use or heating is on in the room.

SO then the threshold of >60% Turn on Extractor Fan.

Just a thought?

I will test it on mine.

1 Like

It is my understanding this is a limit of the firmware on the device. It is a battery saving issue to get the life out it by reducing reporting. Even if it was an option on the driver i dont think it would work. If you really need faster reporting you will likely need a different sensor.

Not sure about the mold sensor, but the dew point is simply some math based on the temp and humidity sensor. You should be able to do that yourself with a rule if needed. I can include for you what I created to do that with RM and a Hub variable if interested.

1 Like

@mavrrick58 that would be awesome if you can. New to all this. Any help would be appreciated.