If you are seeing this message, the config editor failed to load. Most probably this is because you are not
serving this page from a webserver but instead opened it from a local file. As a consequence, you should see
error messages on your browser's console which indicate that some XMLHttpRequests have been
blocked by its CORS
policy. By default the file:// scheme is not supported by cross origin requests.
chrome.exe --disable-web-security --user-data-dir="c:/someFolderName"google-chrome --disable-web-security --user-data-dir="/tmp/someFolderName"
You can deploy your config directly from this editor to a running instance of SKIVI Home. Both need to be connected to the same MQTT broker with
support for native MQTT (app) and MQTT over WebSockets (editor). The MQTT settings of the app are made
in the mqtt config node while the editor can be configured with the form below.
The internal config of the app connects to a free HiveMQ Cloud cluster which is also this form's default. Please adopt the values in case the app you are targeting uses another broker. If the app disabled MQTT, it obviously cannot receive your config. However, you can temporarily force SKIVI Home to load predefined configs with MQTT support via its developer menu in system settings.
The resulting JSON config.