FYI @Bloodtick_Jones @gopher.ny
After updating C7 (this one is in charge with all LAN/Cloud related integrations) drivers for
all HubiThings Replica devices were re-assigned with Generic Contact Sensor driver.
Everything became normal after I manually re-assigned a correct Replica drivers for all
affected devices. All other custom integrations seems to be OK,
I found no issues when updating my C8 hub. Devices kept their Replica drivers
No issues with that on my C-5, but I only have a Samsung Oven on SmartThings.
Were these hub mesh devices or just regular plan ones?
All these Replica devices are just regular devices but Hub Mesh is enabled on this C7 hub.
What was the upgrade path? I have a C7 running HubiThings on the beta program, now running 2.3.7.139 from 2.3.6.146, and have not seen any reassignment. Honestly, I'm not sure how that could happen in the application layer either; there is no way I know of to actively change the device type.
Happy to look into anything the support team flags as possible bad actor.
Its not possible, I have tried to find a way to do it from a parent driver and was told it cannot be done.
Could corruption cause it to display the wrong driver name, but actually be using the correct driver?
Hub is C7, dedicated to all LAN/Cloud integrations was running 2.3.6.146
The upgrade was straight forward single step jump to the latest (at that time) 2.3.7.138
I have few HubiThings Replica devices which are Samsung Microwave (it presented with
two devices: Microwave and Hood), Samsung Fridge and Samsung TV. At this time I have
only one automation which turns On/Off Hood Light depend on Stove Status.
Right before the update this automation turned On Hood Light. But light was not turned
Off after cooking was done. I looked into C7 Aps and Devices and to my BIG surprise drivers
for ALL HubiThings Devices became Generic Contact Sensor drivers. I reassigned back all
appropriate drivers and everything became normal. All other integrations did not have this
problem. I have no idea why and how did this happens but it was what it was.
All the correct drivers were reassigned the Generic Contact Sensor drivers.
The update on both hubs (C7 and C8) went in two stages.
At the begging it was a message reporting some sort of reassigning drivers, etc. (I am sorry,
but I do not remember the exact wording) followed by second reboot(?) and normal update
sequence. To my eyes it looks like it was one time deal related to transition from
2.3.6.X to 2.3.7.X platforms.
It does this with every update now, but it says something like updating drivers to version 2.3.7.x, updating apps to version 2.3.7.x, then rebooting. The reboot after driver and app updates is to free up more memory without having to do a reboot after the hub has restarted to accomplish this.
Yes that is correct, but it does not say it is reassigning drivers. I think it says something about reloading or updating the drivers. What I understand is that it is extracting the app and driver code from the platform update and putting them in place on the hub, overwriting the old versions. It has been doing this on every update but they recently added the message to the boot screen and added the extra reboot to gain back the cached memory from installing all that code into the hub.
It could be happening long time ago but visible double reboot sequence and few new messages
is definitely started from 2.3.7.138
OK, just now I updated C7 to the latest 2.3.7.139
This time all drivers are intact.
Download the Hubitat app
