ninthwalker

Community Developer
  • Content count

    108
  • Joined

  • Last visited

Community Reputation

7 Neutral

About ninthwalker

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

180 profile views
  1. Or that. lol. Glad you figured it out.
  2. You most likely have an empty Plex Library. Check if you do and delete it then run the report again. Thanks.
  3. I also have bought an API and plan on putting that into the main branch soon. It's in the Dev git branch at the moment. If if they ever raise the cost, I'Il either look into a different API, or allow users to input their own.
  4. Nothing looks specifically wrong in your configs. As long as you know you have it set to test and webonly and such so it wont be sending out emails. It could be your plex library, or more specifically it is searching thetvdb for https://thetvdb.com/?id=315776&tab=series which doesn't exist anymore so the code is hanging/looping on that error possibly. If you are able to identify the show, you could look at the metadata in plex and see if it is marked weirdly or something or map it to the correct tvdb ID. It would be some show that was added in the last 7 days, so that may help you narrow it down.
  5. @dcpdad Sometimes tvdb has connection errors, but temporarily. If you are getting that error all the time, it may be a network connection between your location and tvdb. If you add "-v" to the command line options you can get more logging. @naturalcarr I'll look into adding https for the images/links into the base code. People would have to be running this behind a reverse proxy or insert a valid cert to be fully SSL compatible. I use SSL on all my login sites, but others I don't. PS: Nice image!
  6. NOTE: One of the API's that NowShowing and some other apps use is the OMDBAPI. As of 10MAY2017 they have made their API private and started charging for access. That has begun to effect the title's of some movies in the NowShowing report. So far I've only seen it mess with the years in parenthesis () at the end of titles. I will look into a workaround for this in the coming weeks. Thanks all!
  7. So I played with the HamaTV agent Anime stuff a bit, but I'm probably not configuring it correctly. I don't have too much time these days, so probably won't be able to replicate your issue for now. Maybe if someone else uses the HamaTV agent they could post and let us know if it is working for them.
  8. So the primary code from plexReport to NowShowing was not changed. Obviously some modifications were done, but how it scans and reports Libraries should not have been affected. So while we won't be able to add in support for the HamaTV agent, it should be skipping them as an 'unsupported agent'. You are reporting that is not the case though, so I will have to install the HamaTV agent to look into it more. Just to confirm, is this the install you are using on a library with Anime inside? https://github.com/ZeroQI/Hama.bundle
  9. Assuming you didn't change the GUID or PUID in the docker template, it should be setting all your scripts to xyz:xyz after a restart. Try the following: docker exec -it DashBtn bash cd /config ./rightguard.sh Does that run your rightguard script? If it errors, then try ./tide.sh That should just echo "tide" to the console.Assuming that works, then we can try changing the owner on your rightguard.sh chown xyz:xyz rightguard.sh then try running it again ./rightguard.sh Does that work now? Also, did you ever try putting your mac address into the tide section of dashbtn.py and have that work as expected with "tide" outputting to the console inside the docker container?
  10. Since the log is showing that it correctly captured the button press, it must be something with the script execution. You said the script worked on it's own. Did you execute that test from within the docker? ie, docker exec into the docker, cd /config and ./rightguard.sh ? Off the top of my head maybe try some of the following: Make sure you have restarted the docker after you modify a script. Restarting should apply correct permissions to the script. But you can check to make sure if you docker exec into the container, cd /config and "ls -ls" Your script should be executable and look similar to the below permissions: -rwxrwxr-x 1 xyz xyz 892 Mar 25 08:11 baby_tvshow_goldfish.sh If all that is good and it still doesn't work, try going more basic. If you put in your mac address into the tide.sh example line, all that script does is echo "tide" to the console in the docker. See if that works. If that works, then something is possible funky with the script you wrote.
  11. Correct. I'll try and update the instructions to match the default docker name. Thanks.
  12. I have that same show, and mine reports properly. It could possibly be due to having an agent other than thetvdb on that library at some time and then you changed it over to thetvdb. I have seen not all library items correctly change their agent when that happens. Sometimes a force refresh metadata or unmatch/match on the specific show will update it. Check the specific episode in question in plex: ... > Get Info > View XML Does the guid show "com.plexapp.agents.thetvdb...". If not, then that's the problem. If it does correctly show thetvdb, then I'm not sure why it flagged it as incompatible. Let me know. Thanks.
  13. Correct.
  14. Actually, 2FA should work. You will need to create an app specific password and use that. Glad you like the docker though. See the FAQ on the GitHub Wiki.
  15. Can you post your advanced.config again. Replace the usernames/emails with example@gmail.com and myplexfriend or what not. If you had plex_user_emails set to 'no' then it should not be sending to the plex.tv friends. I use mine this way every week to only send to the emails I want. I'm posting mine below for an example with emails changed. As for the command line version it would be the '-n' option. So it would look like this: docker exec nowshowing emailreport -n All the advanced file does is create a cron with that same command to run. So if you save your advanced with plex_user_emails set to 'no', extra_details 'no', test disabled, report_type: both, then the cron should look something like below. 30 23 * * * webreport -n &> /dev/null 30 10 * * 5 emailreport -n &> /dev/null You can verify this is the case with the below command: docker exec nowshowing cat /etc/crontabs/root Attached is mine as an example of sending out both reports, to only the emails I have listed and my own plex account user email. No other plex account emails go out. advanced.yaml
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.