Pluto guide data does not have a lot of lead time. For your Channels Sources that include Pluto channels, try setting the guide refresh to 1 hour.
It always has been set to refresh every hour if you actually looked at the image, he would see that that is current time right now guide data and if there is none whatsoever.
Something in the scraping is not working correctly at times it’s been perfectly fine until recently
My Pluto guide data is up to date.
nothing new on my end, but i'll look into it closer to see if anything funny.
Not sure if anyone even uses Vidaa (I had mine turned off on my prod server) and noticed Vidaa guide was blank on test box. I went to their website and saw this. I'll keep an eye on it over next week and see if the whole thing is dead.
▎ VIDAA CHANNELS IS CLOSING
▎ Dear VIDAA Channels viewer,
▎ VIDAA Channels is closing on June 30, 2026 - thank you for watching with us.
▎ The good news: your favorite content is moving with you.
▎ Open the VIDAA TV app on your TV to keep watching. On newer VIDAA TVs, you'll find it in the TV Channels> app.
2 Likes
Bummer.
I have 55 Vidaa channels enabled in a feed, they are still streaming and the xmltv channels (non-gracenote) have guide data through next Monday morning.
UPDATE: I do see lots of vidaa epg chunk scraper errors in the log
I highly doubt it'll be missed here. So little channels worth watching over there. Obviously, they're not gonna make a dent against the FAST services so that was that for them
1 Like
I did a little research:
VIDAA the OS rebranded to HomeOS. VIDAA the company? rebranded to V. On my android Hisense TV they introduced Hisense channels to replace VIDAA channels. Hisense channels is based on XUMO in the US (may be different in other countries). Not sure what any of this means for the project or whether it is helpful for you.
I had a couple of questions in regard to channel numbers. If I set the starting channel number at 7500
-
How does is the channel number assigned to a particular channel from a particular source. For example, I noticed a one channel from Frndly having a number of 7500 and another one having a channel number of 10,000?
-
Is there a way to specify the starting channel number for a particular source, and still have it combined into one line up? (Example Plex start at 7500, Pluto start at 7700, etc).
In my example from Q1, I was able to manually filter on a line up and manually update the channel number for each, but it looks like it would be a "one at a time" update.
Or if I want to specify the channels without much manual updating, I would need to create separate feeds?
Thought maybe there was some recent backend change that need adjusting in your app..
Might have been something else or specific to that program.
When you set the starting channel number, that's the first one used and every channel in the source is incremented by 1. Take a look at your settings in Channels DVR server for this and all your other sources. That's the setting that matters. The one from FastChannels may not be used in the Channels Source Configuration,
working fine over here. i'll keep an eye on it though.
2 Likes
StreamFAB to prerecord is the only thing that works reliably for me.
1 Like
Yeah for vod (Playon Cloud is an option) and either Prismcast or ah4c for firetv for live tv stuff
Any way to add a second toggle to the catagory selector in the feed setup to exclude categories?
Like a check for include or a X to exclude.
I would like include all (some channels dont have categories) but exclude only Kids.
1 Like
i have this coming in new version - this work?
1 Like
I 
the Channel Changes Report and use it almost every day.
Next time you're in there can you check the accuracy of the Source Health
It's not reflecting the scrape interval I set
2026-07-01 17:50:59,355 INFO app.worker: [vidaa] Scrape job started
2026-07-01 19:50:59,270 INFO app.worker: [vidaa] Scrape job started
2026-07-01 21:50:59,281 INFO app.worker: [vidaa] Scrape job started
2026-07-01 23:50:59,279 INFO app.worker: [vidaa] Scrape job started
2026-07-02 01:50:59,281 INFO app.worker: [vidaa] Scrape job started
2026-07-02 03:50:59,318 INFO app.worker: [vidaa] Scrape job started
2026-07-02 05:50:59,280 INFO app.worker: [vidaa] Scrape job started
2026-07-02 07:50:59,280 INFO app.worker: [vidaa] Scrape job started
2026-07-02 09:50:59,282 INFO app.worker: [vidaa] Scrape job started
2026-07-02 11:50:59,279 INFO app.worker: [vidaa] Scrape job started
2026-07-02 13:50:59,280 INFO app.worker: [vidaa] Scrape job started
TIA
Ahh it’s probably not updated since I added that cron style interval. Will fix.
1 Like
We hope so, since your Pluto is recommended
No pressure
I just updated the headers to the new Google Chrome version and noticed a new (at least I don't remember it being there) clientTime parameter and added it. These changes probably won't make any difference. Some users are having issues recording a few of the news channels using my project and I can't find any issue in the way it's working. I don't think these changes will have any effect on it,
1 Like