I am not staff, nor do they share plans with me. However, my guess is that they'd consider the built-in driver complete. For "advanced" device features (which with stock Hubitat drivers often includes anything not easily exposed via "standard" capability attributes), you often need a custom driver. I'm not sure if anyone has one for this device. But if the max/min thing above is the only issue in question, there are lots of ways to achieve that on Hubitat already (with or) without a device that supports tracking it in its own (and you'll likely get more flexibility too), so that's something else to consider. For mold, I don't believe any Hubitat capability matches that measurement, so that's probably why it is not exposed in the stock driver.
I had been working under the, now realised false, assumption that the best Drivers were those built by the Hubitat team for Hubitat.
Understood, the built in Hubitat Drivers will offer basic functionality until a more comprehensive Driver is built by the community.
I am sure a min/max functionality can be constructed in a Rule, but the one built into the Device is a freebie - no CPU cycles required by the Hubitat Hub, as a rule I had expected the tiny Hubitat Hubs to be CPU limited and therefore expected optimised.
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.
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.
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
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.
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.