Tvheadend

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:

http://192.168.80.67:9981/api/service/mapper/load?uuid=%220bb59670b3aa5d2e412d15ea82fc3c71%22,%220e63e4f90edc546d4d4b7c282f1326b9%22,%220d1c8fa4205a5b8c6f30dde04a098652%22

http://192.168.80.67:9981/api/service/mapper/load?uuid={%220bb59670b3aa5d2e412d15ea82fc3c71%22,%220e63e4f90edc546d4d4b7c282f1326b9%22,%220d1c8fa4205a5b8c6f30dde04a098652%22}

http://192.168.80.67:9981/api/service/mapper/load?uuid=[%220bb59670b3aa5d2e412d15ea82fc3c71%22,%220e63e4f90edc546d4d4b7c282f1326b9%22,%220d1c8fa4205a5b8c6f30dde04a098652%22]

But no change. I'm sure it's something simple - so thank in advance for providing the correct format for the list.

Sorry, it should be:

http://localhost:9981/api/service/mapper/save

JSON parameters:

node:{"services":["cb86b1f9fd5244f522b4792050f34773","501419945e4058bf11b5756491ed5f16"],"encrypted":true,"merge_same_name":false,"check_availability":false,"type_tags":true,"provider_tags":false,"network_tags":false}

You can use any browser's debugger (network view) to check which values the webui sends to tvh.

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.

Awesome - thanks for this. I will test the new create bouquet feature.

Also - thank you for the tip on the debugging web ui. Now I can build out the rest of a kodi interface for basic setup of tvh!

@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.