2019-01-14, 20:49
You're correct, the data is in Kodi, however not in the addon (the addon passes it from the engima device to kodi). I could keep a set of the data in the addon but it wouldn't make sense as it would use a bunch of memory with little or no purpose.
If the info is stored in long description then the timeradd call correctly populates the right field in the recording data. However if it's in short description it doesn't but in this case it can be overidden in the timeradd call. This is a function of the engima platform and not the addon. I can however load a single event using the json API in this case.
There is a call to use only the epg id called timeraddbyevent however this does not work for recordings that start partway trough a recording. Fixing this in Openwebif won't help anyone on an older version. So the solution would be to use timeradd (populating description in your use case) for instant recordings and timeraddbyevent for those in the future where we let enigma handle it.
Here's the AddTimer code:
https://github.com/kodi-pvr/pvr.vuplus/b...s.cpp#L445
If the info is stored in long description then the timeradd call correctly populates the right field in the recording data. However if it's in short description it doesn't but in this case it can be overidden in the timeradd call. This is a function of the engima platform and not the addon. I can however load a single event using the json API in this case.
There is a call to use only the epg id called timeraddbyevent however this does not work for recordings that start partway trough a recording. Fixing this in Openwebif won't help anyone on an older version. So the solution would be to use timeradd (populating description in your use case) for instant recordings and timeraddbyevent for those in the future where we let enigma handle it.
Here's the AddTimer code:
https://github.com/kodi-pvr/pvr.vuplus/b...s.cpp#L445
