Change development port You can change development server port when the default one (8080) is taken on your system. # Run vuepress in dev mode on specified port npx cross-env DEV_PORT=<PORT_NUMBER> npm run dev # Example for port no 15080 npx cross-env DEV_PORT=15080 npm run dev Docke...
I have looked through the change logs and nothing specific is mentioned about MQTT broker changes. The exact configuration given below was working perfectly on version 1.15.0. I have tried using core-mosquitto, localhost and the actual ip address with and without the port. None of this works....
if you are using the default port then there is no need to add it . However if you use a different port then use this syntax. server:'mqtt://localhost:1884' The docs describe all of the available configuration file settingshere I would only do the minimum configuration manually as you c...
Brand new install, using a Conbee II, below is my configuration.yaml: permit_join: true mqtt: base_topic: zigbee2mqtt server: 'mqtt://<ip>' user: <user> password: <pass> reject_unauthorized: false include_device_information: true serial: adapter: deconz port: /dev/ttyACM1 frontend: po...
Draft note: Environment variables are currently the easiest way to set those settings. Open an issue if you need it to be in a configuration file/folder. Docker Compose example If you're using Docker Compose, fell free to use this. 8880 is the port where the service will be available, ...
To fix this, I have to change the port NOT over the hassio web ui, BUT manually in/usr/share/hassio/share/zigbee2mqtt/configuration.yamlrespectively/share/zigbee2mqtt/configuration.yaml. After that, I don't even need to restart the add-on, it just works with the next restarting iteration...
Browse to device's IP adress (You can find the device's IP address in your balenaCloud dashboard) on port 3218 (for example http://192.168.1.42:3218 or http://192.168.1.42/hass-conf/) to access hass-configurator. Open configuration.yaml and add this lines to enable reverse proxy: http...
Yes, my configuration file is this data_path: /config/zigbee2mqtt external_converters: [] devices: devices.yaml groups: groups.yaml homeassistant: true permit_join: false mqtt: base_topic: zigbee2mqtt server: mqtt://localhost:1883 user: my_user password: my_passwd serial: port: /dev/tty...
Shifting the container, configuration and device to the Raspberry Pi 3 from the x64 HP PC didn't change anything, the error still occurred. When this network crashes/fails Mains Powered Devices show as offline in the Web UI - however battery devices still show online - but they failed (Phi...
/opt/zigbee2mqtt/data/configuration.yaml: homeassistant: false permit_join: true mqtt: base_topic: zigbee2mqtt server: mqtt://localhost serial: port: /dev/ttyACM0 disable_led: true advanced: log_level: debug devices: '0xcc86ecfffec39a69': friendly_name: SEA802 groups: '1': friendly_...