Appdaemon

Latest version: v4.4.2

Safety actively analyzes 681866 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 12

2.1.10

Not secure
**Features**

- Renamed the HADashboard input_slider to input_number to support
HASS\' change
- Fixed `select_value()` to work with input_number entities

**Fixes**

None

**Breaking Changes**

The `input_select` widget has been renamed to `input_number` to support
the change in HASS

2.1.9

Not secure
**Features**

None

**Fixes**

- broken [disable_apps]{.title-ref} temporary workaround

**Breaking Changes**

None

2.1.8

Not secure
**Features**

- Refactor of dashboard code in preparation for HASS integration
- Addition of check to highlight excessive time in scheduler loop
- Split app configuration out into a separate file in preparation for
HASS integration
- Enhance widget API to handle all event types instead of just click
- Add example HADashboard focused Apps for Oslo City Bikes, Caching of
local AppDaemon events, Monitoring events and logging, Google
Calendar Feed, Oslo Public Transport, YR Weather - contributed by
[Torkild Retvedt](https://github.com/torkildr)

**Fixes**

- Fixed a bug that gave a spurious \"text widget not found\" error

**Breaking Changes**

- App configuration is now separate from AppDaemon, HASS and
HADashboard configuration
- The Widget API has changed to accommodate different event types and
now needs an `action` parameter to specify what the event type to be
listened for is

2.1.7

Not secure
**Features**

- Converted docs to rst for better readthedocs support
- Added custom widget development
- Enhanced API support to handle multiple endpoints per App
- Added helper functions for Google Home\'s APP.AI - contributed by
[engrbm87](https://github.com/engrbm87)
- Added `immediate` parameter to listen state to trigger immediate
evaluation of the `delay` parameter

**Fixes**

None

**Breaking Changes**

- Existing API Apps need to register their endpoint with
[register_endpoint()]{.title-ref}

2.1.6

Not secure
**Features**

- API now runs on a separate port to the dashboard

**Fixes**

None

**Breaking Changes**

- API requires the `api_port` configuration value to be set and now
runs on a different port from the dashboard
- SSL Setup for API now requires `api_ssl_certificate` and
`api_ssl_key to be set`
- `ad_key` has been renamed to `api_key`

2.1.5

Not secure
**Features**

None

**Fixes**

None

**Breaking Changes**

- `get_alexa_slot_value()` now requires a keyword argument for
slotname

Page 6 of 12

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.