-
Notifications
You must be signed in to change notification settings - Fork 75
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
Remote HA Broken with 2023.7 beta #236
Comments
I have a similar issue and I have updated the one that the info feeds to. Logger: homeassistant.setup Setup failed for custom integration remote_homeassistant: Unable to import component: cannot import name 'SERVICE_CALL_LIMIT' from 'homeassistant.core' (/usr/src/homeassistant/homeassistant/core.py) |
looks like that SERVICE_CALL_LIMIT has been changed or removed since the changes on response on service in 2023.7 Lets see if this remain in the release as well, if so then a change is needed in remote HA , as this will block me any upgrade to 2023.7.0. |
Could be related. |
Same problem with release of 2023.7 |
I can confirm, this integration completely fails init in 2023.7 official release. |
Same for me release 2023.7 |
Same here..... |
same problem with 2023.7 Thx. |
Same here. I wish I checked before updating. Going to restore from backup for now. |
I have the same error in my log.
The remote_homeassistant integration should now load without problems during the reboot. |
@mchangsp - nice share ! I already downgraded. For anyone that chooses to downgrade, here is the short that I followed to do it in a few minutes. https://youtube.com/shorts/iigi1ZgUSMo?feature=share |
updated today to 2023.7.0 same problem as above !! |
I made the the modifications detailed by @mchangsp earlier today. This resolved the error and is an excellent workaround if you do not wish to downgrade. Thank you! @mchangsp 's fix:
|
Question: Should this fix only correct the inability to restart HomeAssistant due to the error in the custom_components, or should it also allow remote_homeassistant to continue working? In my case, the remote_homeassistant device is in the "connecting" state but is unable to connect to my remote instance. |
Thanks for the temp fix..... |
Same problem as the rest. |
As everyone has said, this is an issue with the released 2023.7.0 version. Thank you to @mchangsp with his workaround. |
I applied the workaround fix on one of my Remote Assistant instances where i updated HA to 2023.7. I have not updated my main instance to 2023.7 though. |
workaround solved the issue! |
thanks to @mchangsp your fix fixes my Day ;) |
thanks to @mchangsp Muchisimas gracias :) |
Like described here: custom-components#236
Thank you @mchangsp so much! saved my day too, I have created a PR so it would be easier to see |
When we can expect integration update to correct this error? |
Thanks for the reports
I will aim to release a new version either this evening, or tomorrow |
* Update proxy_services.py to include SERVICE_CALL_LIMIT Like described here: #236
I just pulled down version 3.9 on both my main and remote hosts. remote_homeassistant v 3.9 appears to be working as expected on both hass.io 2023.7.0 and docker 2030.7.0 instances. Thank you @lukas-hetzenecker, @wojked, and @mchangsp for your quick work on this fix 👍 |
Thanks for the confirmation and @wojked for the fix |
All credits to @mchangsp |
@lukas-hetzenecker - Really appreciate this integration. It works so well and has allowed me to manage multiple HA instances from one view. Thanks for developing and maintaining ! |
I get the following breaking error when I upgrade my HA to 2023.7 beta. I have only upgraded the main system that I am sharing entities from, the one I am sharing to has not been upgraded.
The text was updated successfully, but these errors were encountered: