Loose configuration when Homey reboot

[dokmadeinitaly]

Hi Robert, Thanks for your job! I’m running iOS 16.2 with Home app updated and Homey last firmware.

When i reboot Homey or HomeKitty app, i loose HomeKit configuration of all virtual devices (created directly with Homey not with virtual devices app). I loose devices, automation, scene evrithing. I don’t loose other devices configuration created with other Homey app like switchbot or philips Hue, i loose configuration only of Homey virtual devices (all switches).

Can you help me? Thank you!

[robertklep]

I can't reproduce your problem: I tested with both a virtual switch and a virtual button, and both seem to retain their Home configuration when I restart HomeKitty or reboot my Homey (I haven't tested automations because I don't have a proper Home hub).

It's also very strange that it's just those devices that don't work.

Can you restart the HomeKitty app and then create a diagnostic report for it? Perhaps there's something in the log that points to a reason.

[raymondwigmore]

Hi Robert, I actually have the same issue with HomeKitty flow starter devices. They actually don't disappear, but are coming up as new devices in my default room for domotica. And as mentioned by the other user: the associated scenes do disappear, additionally I can not recreate the scenes (I think that's because somehow apples home app keeps old scenes in a file although the devices are no longer there). VD's app doesn't seem to have the issue.

[robertklep]

@raymondwigmore strange. Does it always happen, or only sometimes?

Can you make a note of the device's serial number (in the Home app, long-press the device's tile, choose Accessory Details, then scroll down to find its serial number) and check if it has changed when the device comes up as a new device?

[raymondwigmore]

@raymondwigmore strange. Does it always happen, or only sometimes?

Can you make a note of the device's serial number (in the Home app, long-press the device's tile, choose Accessory Details, then scroll down to find its serial number) and check if it has changed when the device comes up as a new device?

Hi again... happens every time after a restart and/or update (which means a restart anyway). Just restarted the HoneKitty app and serial numbers and all other details remain the same

[OlivierZal]

Same here:

[log] 2022-12-20 15:33:23 [ManagerDrivers] [Driver:flow-starter] FlowStarterDriver has been initialized
[log] 2022-12-20 15:33:23 [ManagerDrivers] [Driver:flow-starter] [Device:a5306832-5283-4ab8-ae07-e7eaabee40ad] FlowStarterDevice has been initialized
[log] 2022-12-20 15:33:23 [ManagerDrivers] [Driver:flow-starter] [Device:a5306832-5283-4ab8-ae07-e7eaabee40ad] adding to HomeKit

but serial number in Apple Home: 3bb545d0-3ec7-4bfc-9bc0-df52ff908bd6

[robertklep]

I wonder if it might have to do with the bridge coming up before the device is ready to be published. Will investigate.

Yes, I can reproduce it for the Flow Starter device. I'll be able to fix that, but I won't be able to fix it for devices from other apps (it already tries its best to wait for other apps to "ready" their devices after a reboot, but it can't wait indefinitely for that).

[robertklep]

Try v1.2.6 (current test).

[OlivierZal]

I didn't notice the issue when updating HomeKitty.

[raymondwigmore]

Try v1.2.6 (current test).

Seems to resolve one of the issues: restarted app 2x, devices remain in room etc. Does not resolve the issue of recreating the scenes within Apple Hone app. It gives a generic. Can't add the scene error for scenes that o had initially created with the de ices that were dropped previously by HomeKitty. It's like they stay in some kind of buffer in HomeKit somewhere

[robertklep]

@raymondwigmore you may have to delete the flow starter device and create a new one to replace it.

[raymondwigmore]

@raymondwigmore you may have to delete the flow starter device and create a new one to replace it.

Nope, checked... didn't resolve. Had the issue before also with HomeKit, after installing HomeKitty I could create the new scenes. Probably as I started with a clean slate. I created a work around for now by adding the buttons as favorites in Apple home app, rather than creating a scene with them. Not as fancy but it works... perhaps in the future you can investigate if HomeKit keeps record / breadcrumbs of old scenes that were removed after devices were removed. Could be an Apple issue ;-)

[robertklep]

@raymondwigmore Home losing configuration for devices is quite common, it's really not very well implemented. That's why I don't use any automations (or scenes) with HomeKit, I'll leave that to a proper home automation platform (Home Assistant in my case).

[dokmadeinitaly]

Hi, I’v restarted the (last update 1.2.6) app and send diagnostic report df211a1c-0e82-4adb-9212-deff231f7947: Now virtual devices lose all configuration and return all to the default room. I’ve used old HomeyKit app 4 years also with iOS 16.2 Home update and never have this issue, hope you can reply the same problem resolution!

[robertklep]

@dokmadeinitaly can you give me the names of (some of) your virtual devices so I know what to look for? And does it still happen every time you restart the HomeKitty app, or only if you reboot Homey?

[dokmadeinitaly]

All “Sensore …” (Sensore Cucina, Sensore Ingresso, Sensore Salotto etc…), “Notifica Camera”, “Notifica Cameretta”. Problem reappeared also after Homey 8.1.1 update. Problem happen every time i restart Homey or when reboot app always

[robertklep]

I can see in the diagnostics report that all those devices are added at the proper time, so there's nothing I can do to fix this problem.

Have you upgraded your HomeKit to the new architecture, which Apple introduced with iOS 16.2? Because apparently there were so many problems with it that Apple has stopped providing that option: https://9to5mac.com/2022/12/21/apple-pulls-new-home-app-architecture-in-ios-16-2-as-users-complain-about-homekit-issues/

Also, are you using a Home Hub (like an iPad or Apple TV)? Perhaps it's related to that.

[dokmadeinitaly]

Yes i have updated to new architecture but i had no problem with new architecture and old homeykit app. Yes i use Apple TV and HomePod hub, they are all updated. Hope you don’t remove old app untill Apple resolve the problem.

[robertklep]

@dokmadeinitaly are you still running HomeyKit? If not, can you try it to see if it still works? You should be able to run both HomeKitty and HomeyKit next to each other.

[dokmadeinitaly]

I’m not running homeykit now but yes i’ll try it again, but have a question about it: Ok, i can run both app next to each other, but wich hub i must use to show devices in HomeKit for this experiment: Homekitty or HomeyKit? If i use both, i’ll duplicate every virtual devices in HomeKit right? Then what i must try about?

[robertklep]

You should be able to run both. The best way is to create a new home in the iOS Home app and add the HomeyKit bridge to it. That way, you'll keep all devices separate from each other.

[dokmadeinitaly]

Ok, i’m doing, then i must try to reboot app and/or Homey right?

[robertklep]

@dokmadeinitaly yes, to see if the devices still work correctly with HomeyKit.

[dokmadeinitaly]

Results: Reboot homeykit app, all ok, all devices stay to theyr room and config. Then i rebooted the Homey, same situation all Homeykit app v.d. stay in room and configured but all homekitty app vd device lose room, config etc… Also i can confirm @raymondwigmore workaronud: if i put a virtual device in HomeKit favorite, they don’t loose config with homekitty app.

[robertklep]

@dokmadeinitaly actually, from what I understood, the issue that @raymondwigmore had with virtual devices was solved entirely. The only issue that he had was with the Flow Starter device that HomeKitty provides.

[dokmadeinitaly]

I only saw that if i put a vd in Apple home favorite and restart app and/or homey, i did’nt lose config of that device. Same workaround found by @raymondwigmore. Maybe the problem is about you suggested in 9to5mac link, strange i don’t have it with homeykit app.

[robertklep]

@dokmadeinitaly I do think this is a HomeKit issue and not so much a HomeKitty issue, especially if it keeps on working if you favorite the device (which is completely beyond the control of HomeKitty). Since @raymondwigmore was still having issues with not being able to create scenes for no apparent reason, it sounds a lot like iOS is using "old" information for a device that isn't valid anymore.

Another possible fix might be to remove your current HomeKitty home from iOS entirely an then perform a HomeKitty reset (from the app settings), in the hope that that will remove all stored information and basically start over.

[dokmadeinitaly]

I’ll try and let you now, thakyou for the moment!

[raymondwigmore]

@dokmadeinitaly I do think this is a HomeKit issue and not so much a HomeKitty issue, especially if it keeps on working if you favorite the device (which is completely beyond the control of HomeKitty). Since @raymondwigmore was still having issues with not being able to create scenes for no apparent reason, it sounds a lot like iOS is using "old" information for a device that isn't valid anymore.

Another possible fix might be to remove your current HomeKitty home from iOS entirely an then perform a HomeKitty reset (from the app settings), in the hope that that will remove all stored information and basically start over.

I agree with all you said Robert. It will be good to find out what happens afwater a complete reset and removal of the Homekitty controller and devices from Apple Home... but it will take me a full day of readding all devices (100+) again... not ready for that now ;-)

[robertklep]

@raymondwigmore I think that in certain situations HomeKit gets confused, and when it does, it won't recover from it. I had hoped that removing the offending device(s) would solve that issue, but apparently it doesn't (you already tried), which only leaves a full reset.

Not being able to reproduce the issue myself makes it very difficult to debug (and besides, I have no access to the information that iOS stores about its Homes), but the only scenes and automations that I have (not a lot) are only for testing so I don't normally notice if anything goes wrong with them.

[dokmadeinitaly]

Whith actual version it’s all ok

[marko0703]

Hi Robert,

I have the same problem. After every Reboot of the Homey I loose almost all devices and configuration in the Homekit. Almost all devices are assigned back to the Default room and I need to reassign again everything to the correct room including other settings like device type. It‘s a problem for all Aeotec, Fibaro, Hue devices. SwitchBot is remaining as well as Nuki. It‘s really annoying to configure again and again over 100 devices.

Can you help on that?

Thank you! Marko

[robertklep]

@marko0703 are you running the latest test version? Have you read this?

[marko0703]

Hi Robert,Now fully understood the problem. Not using the test version. As soon the new version is released I will setup the recommended 10-15 min  delay.Thanks!Marko Von meinem iPhone gesendetAm 12.07.2023 um 06:55 schrieb Robert Klep @.***>: @marko0703 are you running the latest test version? Have you read this?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[robertklep]

@marko0703 I would really recommend installing the test version.

[marko0703]

How can I do this again? Don’t know anymore?!Von meinem iPhone gesendetAm 12.07.2023 um 15:25 schrieb Robert Klep @.***>: @marko0703 I would really recommend installing the test version.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[robertklep]

https://homey.app/a/name.klep.homekitty/test/

[marko0703]

Now working with the test version. I will double check this setting and will see if the problem is ghan solved for me ;-)Thanks!Von meinem iPhone gesendetAm 12.07.2023 um 15:30 schrieb Robert Klep @.***>: https://homey.app/a/name.klep.homekitty/test/

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>