-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All devices unavailable #117
Comments
Exactly the same here. It is also not possible to find any hub even if you delete and reinstall the app. Homey doesn't find any harmony hub. Checked every setting in my networkt. Switched from fixed IPs to DCHP and back. All my other devices which interact with the harmony hub are working well. See 75647bc8-5aa4-4c81-8f8f-cde417e735a9 |
I have similar error. 043d94e2-fc6a-4b11-b2cd-f4112445523c |
Same here, after reinstall of hamrony app, no hubs can be found anymore. |
I have the same issue after migrating to a homey 2023, I was hoping for a workaround here |
No news on this one? |
Looks like this fault still exist 2024 August . only workaround is to reboot Homey and it will work good for a while |
Describe the bug
![IMG_3496](https://private-user-images.githubusercontent.com/28279147/265482701-83fd403c-0205-4bcb-8696-b98d8e21f338.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNjY5MzUsIm5iZiI6MTczOTI2NjYzNSwicGF0aCI6Ii8yODI3OTE0Ny8yNjU0ODI3MDEtODNmZDQwM2MtMDIwNS00YmNiLTg2OTYtYjk4ZDhlMjFmMzM4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDA5MzcxNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM3YTA3MzcyNjE5YjFhZGQ2NjVhMWExYThiYThjZWRkMDhhNDdiZmNjMTUxYmJlODI1NWM0M2I4ZDIyZmMzOWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ejLUrw3HM8Zsb0IGq9M5zb6ZO_0jwN__FQGTc11IxLo)
All devices are unavailable after update to v10.0.4-rc.9.
Log: 52429037-a31e-4740-8539-a08a823930f9
The text was updated successfully, but these errors were encountered: