Running OH3 (under OpenHabian), and after having some issues migrating from 2.x to 3.x, I’m just now starting to dig into the new structure for HomeKit metadata associations.
Back on OH2, it was done with Tags, and sadly, with the upgrade to 3, that didn’t convert/carryover to Homekit in OH3, which wiped out all the HomeKit items, needing them to be manually re-added.
Once the metadata is added, they do populate again in HomeKit, but in the default room, so they still have to be manually moved and all automation/scene rules completely rebuilt.
In doing so, I discovered an oddity. We had a pool temp sensor (in OH2, the tag used was “CurrentTemperature”). In OH3, I’ve added the HomeKit metadata of “TemperatureSensor.CurrentTemperature”, as that seems the most logical match to the original.
Indeed, it now appears, but in OH2, this appeared as Fahrenheit. Now, in OH3, it’s showing as Celsius. On OH’s web portal the pool temp sensor shows 92 (as Fahrenheit is coming from the Omni alarm panel, which is the temp source), but in HomeKit, it’s showing 38 degrees. Still trying to understand the “config” options for a given HomeKit metadata item. Is there something I can add to the “code” section of that metadata that would make it force Fahrenheit? The system-wide option of UseFahrenheit is active but hasn’t seemed to have any affect on this figure.