digiblur

Members
  • Posts

    121
  • Joined

  • Last visited

Everything posted by digiblur

  1. Try the password and user on the dashboard commands possibly. Not sure if it works passing it in as docker run commands, just never tried it. https://esphome.io/guides/cli.html?highlight=authentication#dashboard-command
  2. Which firmware do you have on it? EDIT: I'm using https://github.com/NabuCasa/silabs-firmware/blob/main/RCPMultiPAN/beta/NabuCasa_SkyConnect_RCP_v4.3.1_rcp-uart-hw-802154_460800.gbl
  3. You need to pass in the multipan firmware stick as the path you provide.
  4. Check the tags here to be sure https://hub.docker.com/r/koenkk/zigbee2mqtt/tags
  5. Reading part of the log you might be using conbee? https://github.com/Koenkk/zigbee2mqtt/issues/21162
  6. You could always try to map it to another location to start fresh and see if there is something causing that. Another thing is to check to see if anyone else has this issue on the github for the container. https://github.com/Nico640/docker-unms I'm not currently using my edgerouter anymore to test this.
  7. Looks like it is called UISP. Not Unifi. If you don't have the /config mapping then that is probably the issue.
  8. It is between your browser and the container.
  9. Esphome is finnicky about networks and such. Probably the biggest down fall of the project but once you get it working it isn't an issue.
  10. Sounds like your network has mdns issues and can't resolve the names. You will have to go the route of giving them reserved IPs on your router. Then doing a use_address in your wifi section of the yaml of each device.
  11. Host is what it should be set to. Can you hit the logs on the devices and do they show?
  12. Host should work but if you have vlans involved mdns might be me making it across and need an mdns repeater enabled. You can turn on the ping option environment variable
  13. Thanks, definitely enjoying the speed of the /cache mapping and the speed of the hair prep in the morning!
  14. Probably due to all the disk I/O and that's the UnRaid not the container. You can try mapping to the folder /cache in the container to say /tmp/espcache on the host. If of course you have enough memory to hold the temp files. It speeds things up quite a bit.
  15. I only maintain the template, it is pointing to the official project docker container. I've switched to Tasmobackup myself as I had too many issues with Tasmoadmin causing watchdog resets and rebooting Tasmota devices.
  16. I don't recall this container building this file for you and the wiki has instructions on the setup https://github.com/tsightler/ring-mqtt/wiki/Installation-(Docker)
  17. Same as on 6.11.x when I tried a new z2m container. I rolled back the version of z2m to a year ago for funsies and it creates the yaml file. I might have missed this new "feature" in the changelogs of z2m but it does look like the current version no longer creates the sample configuration yaml file for you. You have to create it manually now. There is a minimal yaml config here you can use to get the GUI up, then once the GUI is running you can just add/change whatever else. https://www.zigbee2mqtt.io/guide/configuration/
  18. I've always used the yaml files with Esphome myself and it makes the devices in the list and builds the bin files. This is the esphome official container so everything is the same as listed in their documentation.
  19. If no devices are showing then you need to add your yaml files from the device you are migrating from. Don't forget your secrets file of you had one.
  20. Modified it for now and included the environment variable in the desc so people don't have to go digging for it when it is needed.
  21. The ports are mapped to the GUI. No need to run full bore as host but if the user wants to do so they can change it. The default is set to false. If the value of false doesn't work then I would open a bug with ESPHome to correct this issue.
  22. Looks like it was updated 2 days ago. https://hub.docker.com/r/nico640/docker-unms