+1 on this.
I have been starting a kodi interface for rescanning and adding channels - something we need to do in the US with all of our OTA changes. I have been able to build out the mux scanning, but now I need the api to automatically map the new services to a channel.
Was there an issue with the previous /api/service/mapper/start function??
It seem sit was removed with the move to simple idnode. Does this mean we have to pass a set of parameters to the load or save api in order to get the channels mapped?
If the previous start function was not hurting anything - please add it back as a simple option to map all services through the api.
