You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently updated my Folding at Home from v7 to v8.3, which includes breaking changes. AFAIK the webui and advanced control are no longer locally hosted, and I now connect via https://v8-3.foldingathome.org/ rather than the IP:Port.
Since the update, my F@H Control entities no longer connect to F@H. I also tried deleting and re-adding my F@H account in F@H Control in Home Assistant (as if setting up for the first time) and it cannot connect.
This entity is no longer being provided by the foldingathomecontrol integration. If the entity is no longer in use, delete it in settings
F@H is hosted on a VPS, and the previous in-built webui and advanced UI ports were exposed and working with F@H control. I'm a relative novice at all of this, and from what I can tell the shift to v8 has resulted in a different way of connecting/reaching the F@H server.
Version of the custom_component
v2.4.2 installed via HACS on Home Assistant (Docker)
The text was updated successfully, but these errors were encountered:
Thank you for reporting this and providing the links. I had a look and it is a complete rewrite. hass-foldingathomecontrol is not compatible with v8. It will take some effort to create a version which (also) adds capability for v8. I am currently working on other repositories so it I won't work on it any time soon.
Thank you for reporting this and providing the links. I had a look and it is a complete rewrite. hass-foldingathomecontrol is not compatible with v8. It will take some effort to create a version which (also) adds capability for v8. I am currently working on other repositories so it I won't work on it any time soon.
I am however happy to help any PR along.
Hey thanks for the reply! There's absolutely no rush or expectation, all the best and thank you so much for your work. Hopefully someone can step in and help, and if it does ever get updated for v8, that's amazing, and if not, no worries at all.
Describe the bug
I recently updated my Folding at Home from v7 to v8.3, which includes breaking changes. AFAIK the webui and advanced control are no longer locally hosted, and I now connect via https://v8-3.foldingathome.org/ rather than the IP:Port.
See: https://foldingathome.org/v8-3-client-guide/
Since the update, my F@H Control entities no longer connect to F@H. I also tried deleting and re-adding my F@H account in F@H Control in Home Assistant (as if setting up for the first time) and it cannot connect.
F@H is hosted on a VPS, and the previous in-built webui and advanced UI ports were exposed and working with F@H control. I'm a relative novice at all of this, and from what I can tell the shift to v8 has resulted in a different way of connecting/reaching the F@H server.
Version of the custom_component
v2.4.2 installed via HACS on Home Assistant (Docker)
The text was updated successfully, but these errors were encountered: