Release v5.4.0

[tsightler]

v5.4.0

This release is mostly to get back to stable ring-client-api version with final fixes for camera notification issues, however, managed to sneak in one highly requested feature and a few minor improvements as well.

New Features

• Alarm control panel now includes lastArmedBy/lastDisarmedBy attributes making it possible to determine who/what triggered an arm/disarm event.

Other Changes

• Device Name/System ID is now displayed in the Web UI and CLI authentication tools providing easier identification of the corresponding device in the Authorized Devices section of the Ring Control Center.
• Camera event management has been completely reworked using a new event management API. Primary goal was to avoid API throttling issues that could occur with large numbers of cameras (>50% reduction in API calls, even more during startup).

Bug Fixed

• Fixed an issue where motion snapshots might return an cached snapshot instead
• Fixed an issue with panic switches where a burglar alarm could trigger both police and fire panic states.

Dependency Updates

• ring-client-api v11.8.0
• bashio v0.15.0

[Stefan300381]

Hi,

I run watchtower to automatically upgrade my containers. After upgrading to 5.4.0 I noticed that no rtsp URL will be offered. Rollback to 5.3.0 solved the issue. Am I missing something?

best regards

Stefan

[tsightler]

I'm not really sure what you mean by "no rtsp URL will be offered" do you mean the source stream attribute is missing or something else? I don't see this behavior myself and there were no (intentional) changes to this part of the code and, even if the source stream attribute was missing it wouldn't have changed from prior versions.

This isn't the correct place to ask such things though so please start a new thread in the discussion forum or, if you are prepared to provide logs or other information, open an issue.