I believe I've upgraded to the lasts qubino driver from Eric Maycock:
And I have the parameter:
Digital temperature sensor reporting Range: 0 to 127 Default: 0 (Disabled) set to 1 in the driver.
This used to give me temp updates for every 1F, but now the temp no longer updates unless I push a change to the device preferences.
The ercom driver was updated 13 days ago, and the commit has a message of:
Hubitat not properly parsing sensorbinaryreport. Using Notificationreport for sensing i2 open / close
Not sure what that's all about, but again my temp sensor that used to report at 1F intervals is no longer reporting. This is a pretty serious problem for me since this sensor control my hotwater return loop. It's worked for the last year without issue.
have you tried the stock Hubitat Qubino Thermostat Module driver?
I am using the Qubino Z-Wave Plus On Off Thermostat Module ZMNHID3 with that driver and my hot water re-circulation system. Still working fine.
Yeah, it was. As I said, it's been working for a year. Maybe it just needs a reboot, but that's a bit of a problem since I have to flip the breaker to do that... unless I put another switch in? I might have, can't remember...
could be a faulty zwave device jamming the zwave network.
I had a GE zwave switch that would mess up my schlage zwave locks whenever it was physically turned on. Removed the switch and everything worked fine again.
I had to power one device at a time off to find the problem device.
if you have saved a backup file from before you lost the first device you could try and install that
If that doesn't work maybe try going back to an old firmware version.
I try to always save a backup before doing a firmware update.
I had a firmware update corrupt my hub once and had to get support to create a restore file. firstname.lastname@example.org
In my case rule machine was corrupted and they rebuilt it with all my rules or I would have had to remove rule machine and recreate all my rules again one at a time.
You could try and kill power to one half of your devices and reboot the hub and see if zwave logging is still slow then power off the other half of the devices and power back on the first half and reboot the hub again and test the logging again.
That would tell you if it is a device causing the problem.
I would keep each half grouped as the same types of devices (multiple types in each half)
just in case it is a custom device driver causing the issue.
Alright well, after last night the qbino flush1D still wasn't reporting properly. Sometimes it seemed to want to report at 1m intervals, other times it wasn't reporting all together.
I went down to the basement this am and flicked the breaker. Rebooting it seems to have brought it back to reporting .5C intervals like I want, so this seems to be an issue with the qbino firmware. I hate having to do this because it reboots everything else on that circuit too, obviously.
One of the things on that circuit is one of those little iRobot floor mop robots and its charger. Here's a little thing to never do if you're an alleged "software engineer". When the power is lost to the iRobot mop while on the charger, it sends you a little error beep code. Every minute or so. Forever. Even after the power comes back on, it continues to beep until you go tend to it.
If my power goes out for 1 second in the middle of the night, the whole house is woken up by the beep code every minute until I get up and smash all the buttons on the robot, or yank the battery to make it stop.
Does the machine serve me or do I serve it? This has become my #1 deciding factor in allowing new technology into my home, and the vast majority of tech fails this test.