You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix bug preventing timer rules assigned a specific channel number to be changed back to 'Any channel'
Change how start and end times are reported for Record series timer rules so they show as 'Any day at any time'
(Matrix) Apply workaround for Kodi error 'In order to add/update a timer the end date and time...' when editing a Record series rule
Update SQLite database engine to version 3.35.4
Third-party dependency update; no anticipated impacts to the system.
Update cURL library to version 7.76.0
Third-party dependency update; no anticipated impacts to the system.
Fix bug preventing timer rules assigned a specific channel number to be changed back to 'Any channel'
This was a missed impact from some point in the past; the backend API used to expect the caller to set the channel number to "null" in order to remove any specific channel that had been set.
Change how start and end times are reported for Record series timer rules so they show as 'Any day at any time'
Ever since v1.0.0 I've been setting a start time for the Kodi Timer rules so that wouldn't display December 31st, 1969, or if you're on the other side of GMT, January 1, 1970:
While investigating something else, I saw in the Kodi code that if you set the Weekdays attribute of the timer to Any Weekday, Kodi will instead display "Any day at any time", which is more appropriate based on how the HDHomeRun recording rules work. Record once rules will still have the date and starting time as before:
(Matrix) Apply workaround for Kodi error 'In order to add/update a timer the end date and time...' when editing a Record series rule
In Matrix 19.0 RC1, a change was made that verified the start and end times for a timer when it's being edited. The HDHomeRun doesn't support these (see "Change how start and end times..." above). Since I wasn't setting an end time, the new logic was flagging it as invalid and preventing the change. I'm calling this a workaround rather than a fix since the logic in Kodi is expected to be adjusted to handle this in Matrix 19.1.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Build 7769 - v3.5.1 / v4.5.1 (2021.04.09)
Update SQLite database engine to version 3.35.4
Third-party dependency update; no anticipated impacts to the system.
Update cURL library to version 7.76.0
Third-party dependency update; no anticipated impacts to the system.
Fix bug preventing timer rules assigned a specific channel number to be changed back to 'Any channel'
This was a missed impact from some point in the past; the backend API used to expect the caller to set the channel number to
"null"
in order to remove any specific channel that had been set.Change how start and end times are reported for Record series timer rules so they show as 'Any day at any time'
Ever since v1.0.0 I've been setting a start time for the Kodi Timer rules so that wouldn't display December 31st, 1969, or if you're on the other side of GMT, January 1, 1970:
While investigating something else, I saw in the Kodi code that if you set the Weekdays attribute of the timer to Any Weekday, Kodi will instead display "Any day at any time", which is more appropriate based on how the HDHomeRun recording rules work. Record once rules will still have the date and starting time as before:
(Matrix) Apply workaround for Kodi error 'In order to add/update a timer the end date and time...' when editing a Record series rule
In Matrix 19.0 RC1, a change was made that verified the start and end times for a timer when it's being edited. The HDHomeRun doesn't support these (see "Change how start and end times..." above). Since I wasn't setting an end time, the new logic was flagging it as invalid and preventing the change. I'm calling this a workaround rather than a fix since the logic in Kodi is expected to be adjusted to handle this in Matrix 19.1.
Questions, Concerns? Let me know!
Beta Was this translation helpful? Give feedback.
All reactions