-
Notifications
You must be signed in to change notification settings - Fork 6
Description
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.
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)