Because change is inevitable. v2.1.0 backlog items have been tabled to deal with a more pressing matter....
Version 2.0.3 (2019.05.20)
- Adapt to HDHomeRun RECORD engine 20190516beta2 breaking changes
- Use HTTP POST method when setting tuner channel visibility flags
Downloads:
Kodi 16 "Jarvis" :
https://github.com/djp952/pvr.hdhomerun ... odi-Jarvis
Kodi 17 "Krypton" :
https://github.com/djp952/pvr.hdhomerun ... di-Krypton
Kodi 18 "Leia" :
https://github.com/djp952/pvr.hdhomerun ... -Kodi-Leia
Release History:
https://github.com/djp952/pvr.hdhomerun ... se-History
This release only deals with breaking changes made to HDHomeRun RECORD engine, version 20190516beta1 or newer. The engine was changed so that it will only accept HTTP POST queries for certain operations, this release provides the necessary changes to handle that.
Specific PVR operations that will fail after update to RECORD engine 20190516beta2 (or newer) if the PVR add-on is not updated:
- Deleting a Recording
- Setting the "Last Played Position" of a Recording
- "Poking" the RECORD engine to tell it that the backend Recording Rules have been modified
Also of note is that I removed v1.3.13 from the available auto-updates (Leia) as it has now been rendered obsolete and non-functional. If there is anyone still using v1.3.13 and would like an update for that to v1.3.14 to deal with this issue, please let me know. The changes were not prohibitive and can be back-ported to that baseline as necessary. Leia auto-update is now limited to just v2.0.3 and v2.0.2.
Now that I am up to release 20190516beta2 here as well, I will set up a second HDHomeRun RECORD engine. move some Recordings over to it, and ensure that the PVR works as expected when multiple RECORD engines are available. It *should* since it was designed to handle this, but you never know for certain until you try!
Enjoy!