Pyduofern

Latest version: v0.36.2

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

Scan your dependencies

Page 4 of 7

0.4.3

- reduce verbosity to fix 27
- some preapration to allow setting the auto update timeout later.

0.4.2

Very beta release.

- limit outgoing message frequency
- fix services.yaml

0.4.1

**Fixes:**
- Renames the ``duofern.update_device_state`` service to ``duofern.ask_for_update``
- Make it accept an entity as argument (updating all entities reliably didn't work for me - presumably as the entities were all answering at the same time). The service menu should allow selecting from a dropdown.
- Add a low-key auto update by letting the devices schedule an update themselves every five minutes when duofern asks for their state

**Still testing/possibly still broken:**
- Will the self-update heal devices stuck in "moving" state?

0.4.0

Added functionality

Opening and closing states

While digging for a way to get devices to re-send their state without side effects I stumbled upon the opening and closing states for the covers which are now reflected in the UI. Note: Especially when multiple covers are triggered at once and send their state reports at the same time, sometimes the visual representation gets stuck in an``opening`` or ``closing`` state. This seems to happen when the message from the shutter isn't received - e.g. due to crosstalk between the devices. Using the ``duofern.update_device_state`` service below can help updating the state to the actual state of devices. I have a button next to my covers to update the state in case of doubt:

![image](https://user-images.githubusercontent.com/44007906/210173934-33c5030e-2e50-456e-a89c-6cd986bb9ab0.png)

It runs this script:
<img src="https://user-images.githubusercontent.com/44007906/210173958-d106f007-e03f-4bc1-be44-900d5a6d8ed5.png" width="400">




Two new services

``duofern.update_device_state``

Ask all duofern devices to re-send their state in case of lost messages. Can be used in setups where RF is finnicky.

``duofern.dump_device_state``
Dump the current last received state for all duofern modules as a warning level message to the log. This reflects the current state of all RF messages received from devices - What's not here wasn't received by the stick or came in garbled.

0.3.4

Depend on latest version of pyduofern.

0.3.2

Re-enabled pushing even when polling -> makes status updates faster.

Page 4 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.