Can you provide a snapshot of the settings page for the Astros app?
The Houston Astros device shows up for me when I add it, so I'm not able to recreate the issue unfortunately.
Can you provide a snapshot of the settings page for the Astros app?
The Houston Astros device shows up for me when I add it, so I'm not able to recreate the issue unfortunately.
Looks like SportsData.IO has changed the team IDs / keys in their API. I need to make some updates to the code to account for the API change. I think it'll make it to where everyone will have to re-install the app because they changed their keys. I'm not sure if it will fix the issue you are having, especially since it's only happening for one of your teams, but I suppose there's a chance.
Thanks for the update. Will send to you the Astros page when I get home.
On the bright side NFL is in offseason so I'm not in a hurry .
Was wondering if it okay to use the same API key on both hubs at the same time?
Yes, shouldn't be an issue. Obviously the API calls from both hubs will combine to count towards your call limit, though.
Here is the settings page for the Astros:
Edit: the above image is too small let me break it down into a couple of screenshots:
For the Texans app I made the settings identical between the original hub and new hub. I then compared the settings between the two and here is the difference:
Original Hub:
New Hub:
The first 7 application states are not generated in the new hub. It starts with Season: "2022OFF" Not sure if that provides you any additional insight. Is it possible it has something to do with creating this child app during the offseason? That is the only current difference between NFL vs NBA/MLB that I can think of.
I've been watching the thread and saw the reference to the API. I monitor 2 NHL teams and usually I get quota exceeded by the 3rd week of the month.
I just solved that recently - I used a 2nd email account to create a 2nd trial with sports.io and obtained a second API - so I've different API's working AFAIK.
I don't actually have proof its working since I have to wait for the start of the month for the first API to reset the quota...
Yup, that's the issue. For whatever reason, SportsData.IO views the 2022 offseason as a historical season that only paid users have access to. Not sure why, but it doesn't really matter that much. As soon as the current season comes around, it should be fine again. Here's the full API call that they return:
{"HttpStatusCode":401,"Code":401,"Description":"Unauthorized Season: You are not authorized to pull data for the requested season. To unlock this historical data, please contact sales@sportsdata.io.","Help":"Please contact support@sportsdata.io for assistance"}
I'm sure if you look at your logs you will see an authorized warning.
In the meantime, I'll look into if there's a way to handle this exception/error more gracefully, in a way that doesn't mess up creation of the child device.
Ok v1.5.7 should handle the unauthorized API access attempt more gracefully and still allow creation of the new child device.
I just installed the v1.5.7 and added Texans. The child device populated instantly. Thank you for continually fine tuning this app to perfection!
I just re-added an MLB team at the start of the season and got a 'approaching an API quota limit' email. Figured I'd mention it here in case it's known. It's only the second week of MLB season so I'm wondering if I'm going to hit the limit this or next month?
I just added a single MLB team. I also have a college basketball team but never got any quota emails for it. Maybe there's a setting that I can adjust to have it check less frequently?
I got the same email today. Strange because it had been working flawlessly at the end of the last MLB season. I’ll look into it and report back with a fix.
FWIW - I did change the refresh rate during a live game to 30 mins (from 10). Figured that might help a little too
v1.5.8 should fix this issue, which appears to have been a bug introduced in v1.5.5 with configurable update interval. Granted, it may take until next month to confirm, since your quota may have been exceeded for this month already.
feature request - now that my team(s) has finished it's season - I'd like to disable them until next year. I am aware I can open the 'disabled' column in HE, BUT, I'd love to see a red marker on the child and have the ability to 'pause' or hold a team settings instead of using HE to do it.
By using HE, I risk not being aware I have a disabled child since normally I have that whole column hidden. Also, I contend that disabling a child in this way creates possible breaks when Gametime Parent updates come out as I believe and HE disabled app is ignored by HPM.
Also, having that whole column on screen for a single child for months just seems like a waste of screen real-estate. PS. I really love this app, it has been a rock.
I've thought about this. It would have to be a manual disable/enable option, since there's no good way to determine when to automatically re-enable the app. At the end of the season, for instance, we don't know what date the first game of next season will be. Would manual disable/enable suit your needs?
Curious: I don't think there's very many API calls or much activity during the off season. Just a couple calls a day. I guess you want to really lean up your HE huh?!?
LOL - I hadn't thought of the impact on cycles, I was cleaning the dashboard! I run the Hubitat Dashboard for Android by the magnificent @Jpage4500 ... The maker API pushes the tiles to it and I was just recovering screen real estate!
Absolutely a - Enable/Disable for a child would suit the desire!
was reviewing things today - I've got GameTime app disabled, and I don't think there is a 'disable' button for devices - but my logs show schedules firing... I can't explain why!
(I've had the gametime app disabled for about 3 weeks now...)
Of course this is not a big deal - but I think it ties into the 'disable' feature we discussed a few weeks ago - might want to add that as a check item when/if you implement or update.
v1.5.9 adds manual disable option at the bottom of each child app. Keeps everything in place for the next season, but doesn't subscribe to updates. So you'll need to manually re-enable when desired, since there's no way to automatically re-enable once the season starts.
This app seems awesome and appears to be just what I've been looking for.
I'm probably doing something boneheaded, but I seem to be stuck on the installation. I installed via HPM and added the app, but when I try to go in to add child app instances, all I see is this:
Any assistance would be appreciated.