The device event history in the app does not depend on the driver or the hub.
I think It depends on the server in your area. There are times that it is delayed by a few minutes, others by several minutes and others it is almost instantaneous. depends on the day.
If you look at the logs with the cli you will see that the driver emits the events instantly and the platform processes them to update the device states in the app instantly and sends and saves them to the history server.
My ST Wifi Hub on f/w 46.10 completes the Zwave network repair. Loading “History” takes an excessively long time (like I can brew a coffee before it populates)
Ah, interesting. Thanks for sharing that, as I really thought it was a bug in the firmware. My Z-wave network actually seems to be working very well (I have ten or so wired Z-wave switches scattered around the house), so I’ll try to leave well-enough alone and not worry too much about what might be wrong with my system, specifically.
Same firmware number doesn’t mean the same firmware: it just means they’ve been updated the same number of times. They are on different development tracks, have different internals, and the firmware is different between them even if it’s the exact same number.
You may want to examine your presence setup. May not be related to any firmware updates - possibly an app update or due to the start of groovy shutting down in January. Do you use virtual presence sensors? If yes, do you remember how you set them up such as simulated presence sensors through IDE?
FYI, I just learned that there is a rare issue for at least one more user, and me possibly being another one, related to this update.
The hub tries to get the update but fails because a hub property is not retrieved properly.
I’ll see if the support team can sort this one out tomorrow.
After hearing from RedTx that it completes for him, I tried again, but from an iPad, as opposed to my Android phone, and the Z-wave repair went to completion. So, at least for my setup, it appears that it may be an Android vs iOS issue and not a problem with my hub.