digiblur

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

Thanks, definitely enjoying the speed of the /cache mapping and the speed of the hair prep in the morning!

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.

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.

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)

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/

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.

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.

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.

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.

Looks like it was updated 2 days ago. https://hub.docker.com/r/nico640/docker-unms

Home Assistant for what part?

Does it give anything in the application logs as to why it stopped?

FYI if you don't feel like waiting for the next release.

Subscribe to the projects github releases and hit the force update button on unraid until they fix the bugs with these.

I've verified it is pointing to the right link on docker hub https://hub.docker.com/r/koenkk/zigbee2mqtt

No need to reinstall. Just hit force update.

Is `<Privileged>true</Privileged>` necessary for most installs? Definitely not a good security practice IMHO.

Side note...others might want to check but I saw something weird. I was helping someone and saw there was no /media/frigate mapping in the default container and it was dropping the database file in the container. Not a good thing so definitely check yours.

Thanks! Hopefully others can chime in on the cache target as I noticed nothing was going in the folder until I fixed it. I also noticed the privileged flag was set to true which I do not recommend unless absolutely necessary.

I noticed some issues with the container especially the tmp mapping. It appeared to be causing excessive writes and not set to the right target in the container. I did a PR but haven't heard from the maintainer. Has it been abandoned?

You don't need to pass in the device to the container. It really is as simple as loading the plugin to get the drivers going and then telling Frigate to use it. detectors: coral_pci: type: edgetpu device: pci

Works great! Thanks for your awesome dedication! I wasn't in a rush as I could have rolled back if it was a massive issue. I usually wait a week or so typically on upgrades.

Upgraded to 6.9.0 stable and I noticed the TPU drivers weren't loaded, I'm guessing an update is needed? I tried the reinstall.. plugin: installing: https://github.com/ich777/unraid-coral-driver/raw/master/coral-driver.plg plugin: downloading https://github.com/ich777/unraid-coral-driver/raw/master/coral-driver.plg plugin: downloading: https://github.com/ich777/unraid-coral-driver/raw/master/coral-driver.plg ... done ----Download is empty please contact the developer of this plugin if the----- ----------plugin has been already built against that Kernel version---------- plugin: run failed: /bin/bash retval: 1 Thanks!

Massive thanks to @ich777 for all the hard work and getting it done quickly! I've tested it on a PCIE based Coral TPU and it works great. Stupid simple to install. While you are installing the plugin, mash the donate button on his profile and throw him a beer/coffee or two