Status

Current status is unknown.

MQTT

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.

Broker:
://
WebSocket variant.
Hostname or IP address of the MQTT broker.
:
Port for 'ws' or 'wss'.
/
Connection path (typically 'mqtt').
Username required by the MQTT broker, if any.
Password required by the MQTT broker, if any.
Target:
skivi/home/config/<action>/
Enter the ID of the SKIVI Home app you want to send the config to. Check the app logs for 'Client ID' or 'Group ID' and add it here. You can provide multiple IDs separated via comma.
Status: Disconnected.
Errors: None.
Problems? Check browser console. Verify broker address. Try without VPN. Use local broker. Ensure WebSocket support.

Help

No further help content provided.

Config

The resulting JSON config.