Create bouquet for all network types / per network (was: map all services through json api...)
The ability to start the map all services function was removed from the json api.
In the USA - we need a simple way to scan muxes (which does exist in the json api) and then have the new services automatically mapped to channels. With all of our ATSC 3.0 changes coming, stations are going to be changing frequencies. I would like to trigger this from my frontend without having to go through the web interface.
Could this "start" function for the mapping services api be put back in?? If not - what is the method to map services through the current json api options?
#1 Updated by Jaroslav Kysela about 2 years ago
- Target version set to 4.2
Check the webui - you may send the service uuid list to the /api/service/mapper/load .
Anyway, it may be better to manage a bouquet of all services in network. Then users may enable the automatic service mapping through the bouquets. I'll work on it.
#2 Updated by edit4ever ! about 2 years ago
Thanks for looking into this! I'm striggling with sending the uuid to the /api/service/mapper/load - perhaps I'm not formatting the request properly?
I've tried the following:
But no change. I'm sure it's something simple - so thank in advance for providing the correct format for the list.
#3 Updated by Jaroslav Kysela about 2 years ago
Sorry, it should be:
You can use any browser's debugger (network view) to check which values the webui sends to tvh.
#4 Updated by Jaroslav Kysela about 2 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset tvheadend|e76171c573492fe52d56bba25c768db901e017f7.
#5 Updated by Jaroslav Kysela about 2 years ago
You can (since v4.3-60-ge76171c) create a bouquet per network now. It means that if you check 'Create bouquet' flag in the network settings, you can configure the auto channel mapping inside the created bouquet for your whole network. No external tool is required now.
#8 Updated by Jaroslav Kysela about 2 years ago
edit4ever ! : Don't use http requests for the kodi. All /api http requests are available through the htsp protocol / session, too. Just use "args" (map) and "path" (string) for the "api" method. The result is same htsmsg structure as json result for http calls.