There's no universal way to tell that a driver is a virtual one. We can selectively (and manually) flag our own drivers as "virtual" because we own the code and know that they are.
Apple only allows builtin devices to show up in Homekit. Ok so I guess this changed for user devices but virtual devices did not make it for some reason.
@gopher.ny is the "supportedThermostatFanModes" an obligatory attribute for the HomeKit integration (even if the thermostat does not support any fans, like the eTRVs for example) ?
I'll have to revisit that. Can you point me to the source code for the driver?
I don't see a way to do that and to enforce Apple's "no IP based devices" rule, which is mandatory for getting HomeKit certification, at the same time.
@gopher.ny Would it be possible to create a Hubitat driver that is a virtual presence switch driver. The community one from @ogiewon shows up for me in Homekit, but I don’t want to move this automation off of Homebridge to the HomeKit beta to have the user driver stop working.
Edit: actually, the virtual driver must have stopped being included with one of the recent updates.