Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: ${intensity.previous} value passing control #1227

Closed
peskdale opened this issue Aug 24, 2020 · 4 comments · Fixed by #1266
Closed

Feature request: ${intensity.previous} value passing control #1227

peskdale opened this issue Aug 24, 2020 · 4 comments · Fixed by #1266
Milestone

Comments

@peskdale
Copy link

I have a couple of uses in my setup where I don't need to know a new brightness value on a dim command, but rather the difference relative to the old one.

e.g . I'm using the dim functionality to exec a script to increase/decrease of the volume of a device. I don't care what the actual brightness value of the 'light bulb' is - I just want to know if an increase or decrease has been requested.

Currently, I'm making this work by storing the previous intensity value in a text file that I can look up next time the dim command is executed. But that number already exists in ha-bridge, and is even used in calculating the new value.

It would be great to have an additional command that could accommodate workflows like mine, which returns the previous intensity, allowing it to be used in directly by other scripts.

@peskdale peskdale changed the title Feature request: ${intensity.previous} value control command Feature request: ${intensity.previous} value passing control Aug 24, 2020
@audiofreak9
Copy link
Collaborator

@peskdale Could you leverage the GET light attributes and state prior to executing your command command?

@peskdale
Copy link
Author

@audiofreak9 Thanks for the suggestion. I have just tried implementing that request at the start of my script.

However, it seems that the new brightness value is already present in the response.

@bwssytems bwssytems added this to the 5.3.1 milestone Dec 8, 2020
@bwssytems
Copy link
Owner

This will be in the next release

@bwssytems
Copy link
Owner

The components available will be

${intensity.previous_percent}
${intensity.previous_decimal_percent}
${intensity.previous_byte}

bwssytems added a commit that referenced this issue Dec 14, 2020
Dev branch 5.3.x to create v5.4.0

#1044 Alexa app, error "Device doesn't support requested value" bug question
#1118 Device status update in Alexa App is not working correctly for ha-bridge devices bug duplicate question
#1126 Can't get XY ColorData into URL enhancement question
#1127 Can't get separate hue, saturation and brightness enhancement question
#1128 Wrong color calucation in HS mode bug question
#1131 Changing color temperatur is not working correctly bug question
#1132 Conversion from CIE to RGB incorrect bug question
#1139 Device ID creation fails bug question
#1150 Home Assistant gets null exception during initialization bug question
#1170 Alexa not sending the correct color codes duplicate
#1171 Please add option: If bright request present with on, only send dim enhancement
#1184 Alexa will not discover HABridge question
#1191 When "Use UPNP Address Interface Only" is selected, echo cannot find ha-bridge bug
#1210 [Enahnacement] Have link button timeout be configurable enhancement
#1215 Alexa unable to discover recently added devices to ha-bridge duplicate question
#1227 Feature request: ${intensity.previous} value passing control enhancement
#1239 HA-Bridge has suddenly given up itself - Exception in thread "main" java.lang.NullPointerException bug question
#1243 Alexa device discovery now broke question
#1253 HABridge hue ColorDecode 0 0 0 bug question
#1256 Homeassistant devices not appearing bug question
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants