Quick fix for the remote access disable switch in the web ui.

Author: QuinnDamerell

homeway/CHANGELOG.md

@@ -2,7 +2,7 @@
 <!-- This is used in the homeway UI to show updates, so keep it up to date. -->
 
 
-## 2.5.0 - 2.4.0
+## 2.5.1 - 2.4.0
 
 - 🤖 Google Home & Alexa device filtering is here!
     - You can now use the same Home Assistant UI as you do with Nabu Casa to expose or un-expose devices to Alexa, Google Home, and Sage.

homeway/config.yaml

@@ -53,4 +53,4 @@ image: ghcr.io/homewayio/homeway/{arch}
 # Note when this version number changes, we must make a release to start a docker container build immediately, since HA will start looking for the new version.
 # Basically: Make the final commit -> test and check lint actions (if a docker change, push to docker-test to ensure it builds) -> bump the version number -> create GitHub release.
 # UPDATE THE CHANGE LOG!
-version: 2.5.0
+version: 2.5.1

homeway/homeway_linuxhost/webserver.py

@@ -472,7 +472,8 @@ def do_GET(self):
         const remoteSwitch = document.getElementById('enable-remote-access-switch');
         remoteSwitch.onchange = (event) => {
             const enabled = remoteSwitch.checked;
-            fetch("/api/remote_access_enabled", {
+            // This must be relative to this page, since the hosted web page in HA is a long path.
+            fetch("api/remote_access_enabled", {
                 method: "POST",
                 headers: {
                     "Content-Type": "application/json"