Fix: sensor being updated constantly when value doesn't change #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amadeo-alex
added a commit
that referenced
this pull request
Mar 3, 2024
### Changes - Added "SetAudioInputCommand" (thanks to Chrisdegod for the suggestion) - #41 - Added "ScreenshotSensor", functioning as camera entity (huge thanks for @denisabt for the inital PR with implementation to the original repo)- #42 - Added option to ignore the MQTT/connection grace period when system wakes from hibernation (thanks to @larena1 for the suggestion)- #51 - Added option to use modern (white on transparent) icon for the HASS.Agent's trayicon (big thanks to @MBaliver for the suggestion and the icon) - #55 - Added note to "PowershellSensor" description as a reminder to Home Assistant's 255 character limit for the payload/state (thanks to @EpicLPer for suggestion) - #58 - Last but not least, all dependencies have been bumped to the newest possbile version - #56 ### Fixes - "SetAudioOutputCommand" and "SetApplicationVolume" commands are now properly configurable from the UI (thanks to Chrisdegod for reporting) - #39 - Updated VirtualDesktop management library to stop it crashing on some Windows 11 systems - #40 - Sensor state being evaluated constantly, ignoring the configured update interval (thanks to @shupershuff for reporting) - #45 - "PowershellCommand" arguments not being bound/parsed properly when provided with payload/action (thanks to @shupershuff for reporting) - #47 - "ActiveWindow" sensor not using proper encoding, resulting in some characters being replaced with "?" (thanks to @greghesp for reporting) - #50 - Sensor/command discovery payload messages are now sent on HASS.Agent start and configuration change instead of constantly - should reduce the load on Home Assistant (thanks to @Anto79-ops for reporting) - #5 - "MicrophoneProcessSensor" description has been changed to more accurately describe its function (thanks to @Gvolten for reporting) - #57 #### Note This beta release includes changes from [2.0.2-beta1](https://github.com/hass-agent/HASS.Agent/releases/tag/2.0.2-beta1) and [2.0.2-beta2](https://github.com/hass-agent/HASS.Agent/releases/tag/2.0.2-beta2)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes issue where the "LastUpdated" value is not updated if sensor value is same as previously.
Thanks to @shupershuff for reporting the issue :)
Due to this issue sensor's "GetState" would be called every second or often. For most of the sensors it wasn't an issue but in some cases where custom code (for example PowerShell sensor) is used, this may result in the code/script being run "constantly" without respect for the "Update every" sensor configuration.
Before:
After:
