Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

13 Good

1 Follower

About FoxxMD

  • Rank
    Advanced Member

Recent Profile Visitors

1103 profile views
  1. @abb0r Hey so it turned out to be easier to integrate Plex than I expected! I've created a CA app for a scrobbler application I am developing that can scrobble from Plex/Tautulli to Maloja. Check it out and let me know if you have any feedback.
  2. Application Name: multi-scrobbler Application Site: https://github.com/FoxxMD/multi-scrobbler Github Repo: https://github.com/FoxxMD/multi-scrobbler Docker Hub: https://hub.docker.com/r/foxxmd/multi-scrobbler Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview multi-scrobbler is a web application for scrobbling music you play from multiple sources to multiple scrobble clients. It's aim is 1) to provide a self-hosted alternative to capturing track plays and 2) fill in the gaps for track sources and scrobble clients that don't have existing methods of communication. I am the developer of multi-scrobbler. It is in active development and not mature code yet. Current state of connectivity for m-s: Track Sources (can capture plays from): Spotify Plex or Tautulli Scrobble Clients (can scrobble plays to): Maloja Feature highlights of m-s: Handles Spotify authentication for unattended use after first-time setup Logs track discovery/scrobbles to rotating daily files Configurable using JSON files or environmental variables (through Docker or Node) Provides static web page for displaying source/client status, discovery statistics, and recent log activity Usage/Configuration Configuration of m-s is done through json config files or through environmental variables (set in the unraid docker template). Do note that settings defined in config files will override environmental variables. The CA template has default settings to map a config and logs directory, but neither mapping is mandatory. Please refer to the github documentation to find environmental variable names as well as example config files for each source/client. Also note that docs contain guides on how to setup a source/client if necessary (registering a spotify application, for instance). Support/Feature Request Please feel free to give me any feedback on anything (unclear instructions, features you'd like to see, problems you are experiencing, etc.) as I am still developing this app. Please use github issues if you can as this will be easier for me to track.
  3. Yes webhooks would be the easiest but it is also gated behind Plex Pass (paid subscription). It even has a media.scrobble event for just such a use case. Another option would be using Tautulli with a custom script for a notification agent or webhook on the Watched trigger. Well...can lead a horse to water 😅 If I have any free time in the upcoming week I'll see what it would take to throw together something to do this
  4. @WNSwins So I know its not changing colors but szurubooru does support a dark theme now
  5. @pmcnano it looks like this is a known issue (and not an issue with the unraid template)
  6. Hi everyone. This plugin is fantastic and its almost working flawlessly for me! My question regards the actual number of "fan controls"... I have not found a clear answer in this thread...why does the Fan Settings section only show Fan1234, FanA? Do I need to do some additional configuration to break out the fans into separate controls? My board, a supermicro x9dr7-ln4f, supports Fans 1-6, A & B. I can see all of the connected fans with readouts in available sensors. with ipmisensors, and in the sensors config for this plugin (set all my thresholds individually) -- but can only control them in two "zones", I guess, based on Fan1234/FanA. ipmisensors -t fan ID | Name | Type | Reading | Units | Event 406 | FAN2 | Fan | 825.00 | RPM | 'OK' 607 | FAN5 | Fan | 825.00 | RPM | 'OK' 674 | FAN6 | Fan | 675.00 | RPM | 'OK' 741 | FANA | Fan | 825.00 | RPM | 'OK' This is working fine but I would like to have individual control over each, if possible. EDIT: I've had this plugin installed for a long while (but always updated)...do I need to delete configs and reinstall the plugin?
  7. @TuskenUnRaider what error is that? I will add your troubleshooting fix to the main post
  8. I just tried a fresh install and am seeing this issue now...it seems the login attempt is redirecting and then not passing the form data correctly. I'm looking to see if there is any troubleshooting info on this... EDIT: @Mattyfaz can you try setting the Config path to a new (non-existing) location? I was able to login after using a clean path.
  9. It seems since last time I checked the author has moved the docker image from his personal account (hunterlog/statping) to an official account (stating/statping) -- the personal account is 4 months out of date. I have updated the template with the new registry. I'm not sure if this will update your templates as well, in case it doesn't you should go to Edit for the statping unraid app, switch to Advanced View and set the Repository field to statping/statping:latest You may also want to update the Docker Hub URL field to https://hub.docker.com/r/statping/statping
  10. Application Name: ozwdaemon Application Site: https://github.com/OpenZWave/qt-openzwave Github Repo: https://github.com/OpenZWave/qt-openzwave Docker Hub: https://hub.docker.com/r/openzwave/ozwdaemon Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview ozwdaemon is a docker container for running the OpenZWave MQTT Adapter as well as a web GUI for managing your z-wave network with ozw-admin. In layman's terms this container can do the following: Connect to your z-wave dongle and provide a website for managing your z-wave network Bridge your z-wave network to an MQTT server (send z-wave events as messages and consume MQTT messages as z-wave commands) ozwdaemon vs zwave2mqtt zwave2mqtt's bridge solution is a node wrapper (translates messages) on top of openzwave while ozwdaemon has no wrapper zwave2mqtt translates zwave events into generic MQTT lights, switch, etc. messages while ozwdaemon just puts event data straight into MQTT payloads zwave2mqtt could be more useful if you want to manage your z-wave network outside of home assistant (for now) zwave2mqtt is a community project while ozwdaemon is maintained by openzwave developers currently (Sept 2020) zwave2mqtt is more mature -- ozwdaemon (and qt-openzwave) are still in active development however qt-openzwave is set to be the new, official control panel for openzwave More technical details can be found here Which Should I Use? If you want to use z-wave in conjunction with Home Assistant you should use this container as it is being developed alongside HA with the new z-wave integration If you need the latest openzwave versions (going forward) you should consider this container as openzwave maintains it. zwave2mqtt will need to update their node wrapper translations before upgrading versions. If you already use zigbee2mqtt and manage your network outside of HA (EX with node-red w/o HA integration) you should consider using zwave2mqtt as the message format will be resuable from your existing flows Requirements An MQTT server (available in CA) A z-wave dongle Usage Template Configuration: MQTT Host -- IP Address of your MQTT server USB Z-Wave Device -- The path on host (unraid) where your USB/serial device (z-wave dongle) is located. USB Path -- Environmental variable for the container path to the USB/serial device (z-wave dongle). This tells qt-openzwave where to look for the device in the container. It should be the same as USB Z-Wave Device Web UI Port -- (Optional, default: 7800) The port to be used for accessing ozw-admin (for managing the z-wave network and MQTT connection) MQTT Port -- (Optional, default: 1883) The port to connect to your MQTT server on MQTT User -- (Optional) Username for MQTT authentication MQTT Password -- (Optional) Password for MQTT authentication Zwave Network Key -- (Optional) Existing key for your z-wave network. If not included secure inclusion is not possible. ozw-admin Port -- (Optional, default: 1983) -- Port to access ozw-admin interface if using ozw-admin desktop GUI For Home Assistant After setting up ozwdaemon and verifying your network is running follow the instructions for the new openzwave integration. Your devices should be discovered automatically shortly after the integration is added.
  11. Mine is similar to strike but it works with less configuration: server { listen 443 ssl http2; server_name search.yourDomain.me; # ssl specific to my machine # nothing whoogle specific in here though, same for all subdomain ssl include /config/nginx/sub-strong-ssl.conf; location / { include /config/nginx/proxy.conf; # default proxy conf included in docker-letsencrypt container proxy_pass http://yourHostIp:whooglePort/; } }
  12. Unfortunately I do not think there is an easy way to go about this just using docker. The Dockerfile for the client shows that the source is copied to a working directory, then built, and then copied to the www folder. There is a CLIENT_BUILD_ARGS argument for adding arguments to the end of the build command but that's a bit unwieldy. Your options boil down to: Build szurubooru yourself locally, then map your built css folder to the www folder Open an issue (or better yet PR) on the repo to implement some kind of user-defined intermediate step between initial code copy and building, like... Specify an additional folder the Dockerfile could check for files in and copy those after the initial source copy -- that way a user could map their own source style files into that and have them overwrite files original source files before the build step Yes, it is safe to remove! Thank you for catching that I had forgotten to update the template.
  13. @buzzra are you sure you read any of the docs? The entry for enabling new registration, in the docs The entry for creating a superuser as well as accessing admin panel where you can manage users, in the docs Support here is for supporting the docker template on unraid or other specifics about running on unraid -- not for reading the manual for you.
  14. Application Name: pgadmin4 Application Site: https://www.pgadmin.org/ Github Repo: https://github.com/postgres/pgadmin4 Docker Hub: https://hub.docker.com/r/dpage/pgadmin4/ Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview pgAdmin is the most popular and feature rich Open Source administration and development platform for PostgreSQL, the most advanced Open Source database in the world. Some features: Designed for PostgreSQL 9.5 and above Access and manage multiple databases CRUD for all the things and raw SQL execution Wizards and graphic tools for many administrative tasks (ACL, backup/restore, etc.) Monitoring dashboard How is this different than the existing CA template for pgAdmin4? The dockerhub repo (fenglc) used for that template has not been updated in 2 years and is now archived This dockerhub repo (dpage) is the official image for pgAdmin4 and is up to date fenglc only supports utilities (pg_restore, etc.) for postgres 9 while dpage contains utilities for postgres 9.5, 9.6, 10, 11, and 12 fenglc has hardcoded default credentials while dpage supports supplying your own default user/pass for new installations dpage supports many more environmental variables for configuration Usage NOTE: On initial container build there may be a noticeable delay (10-20 seconds) between when the container starts and when the UI becomes available. === Migrating from fenglc or bringing your own data === Use the Config path (under "Show More Settings") in the template to map your working directory. If you are migrating from fenglc just use the same folder from appdata. If you use this approach you can safely ignore or remove the Email/Password variables from the template. === New Installations === You must provide values for Default Email and Default Password in the template or the container will not start. The email is not actually used, it's just a username. After the container has been started for the first time these variables can be removed from the template. Configuration All other configuration for the container can be found in the pgAdmin docs.
  15. For current users: After v2.2 Elasticsearch is no longer needed. You do not have to take any action in order to upgrade but it is still recommended to backup your postgres DB and data folders beforehand. Once you have started the new (upgraded) container do not stop/update the container until post data has been rehashed -- progress can be checked by viewing the logs. After hashing is complete you can safely remove the Elasticsearch Host variable from your unraid template and restart the the container.