I released my standalone cync-lan project about a year and a half ago, today it has been upgraded to be a Home Assistant add-on!
‘CyncLAN bridge’ is a software stack that masquerades as the Cync cloud controller. DNS redirection and a self-signed certificate chain is required to trick the Cync devices into connecting to the local nCync TCP socket server. The Cync devices think they are talking to the cloud!
Modern UI exporter
A static webpage using tailwinds, animation and prism is now served by a FastAPI export server to facilitate exporting your Cync device config from the Cync cloud API by using an emailed OTP. To access the device exporter, enable the sidebar option or click the OPEN WEB UI button on the add-on management page. (see screenshots below)
DNS redirection
Please see the DNS redirection documentation for detailed examples for pfsense/opnsense and pi-hole.
First run
Before you can control your Cync devices locally, you must have DNS redirection configured and export your device config from the Cync cloud API
- Configure the add-on with your Cync account username/password and the MQTT broker details/credentials
- Enable DEBUG level logging (turn off after confirming that everything works)
- Start add-on
- Go to the ‘ingress’ webpage by using the sidebar CyncLAN (
mdi:bulb) icon or navigating to the add-on management page and clickingOPEN WEB UI - Click the
Start Exportbutton - Check your Cync account email address for the OTP
- Enter and submit the OTP
- Wait for the export to complete (config file stored on HASS host:
/homeassistant/.storage/cync-lan/config/cync_mesh.yaml) - Optional: download the resulting
cync_mesh.yamlfile for a backup/reference - Restart the add-on to load the newly exported config file
- View the add-on log to see if Wi-Fi Cync devices are connecting
