-
Notifications
You must be signed in to change notification settings - Fork 246
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
[FR] Run playbook based on status (w/o service call) #2160
Comments
I will consider this. |
Implemented with #2170 I cannot do for Will be in next release. You could test it by installing the master branch with HACS. |
@EddyK69 Ok, I only implemented in YAML yet. Will have a look if I can also implement for the GUI. |
Thnx! That was a quick one! Is use the GUI btw. Will test this asap |
Added for GUI with #2176 |
Thnx, but cannot download Master via HACS: get a 404 on |
That's strange it shouldn't try to download the release as it's not actually as release. |
Hi @bramstroker |
@erkr Strange you both are having issues. I cannot make that path available as master is not a release, but just the main branch where releases are made from. |
I have found following issue on HACS issue tracker: It was working in the past, but apparently it does not work anymore when the integration uses zip releases, which is what powercalc does and is the preferred way. If you want to you could download manually. And replace |
@bramstroker I recall from another project that a version must be set in the manifest when you copy the files manually |
That not something I can fix in Powercalc, that's also a HACS issue.
I'm pretty confident that's not required. You can just overwrite the files manually and restart and it should load the new code. |
Today I'm with family, but I will give it a try tomorrow 👍 |
@bramstroker I cannot find the settings in the GUI I'm afraid. Where can I find it? |
@EddyK69 I see, there was actually a problem with the translation keys, causing the labels not correctly rendered. The correct field is this one: |
@bramstroker Thnx. Found the hidden field 😄 But unfortunately i cannot get it working the way i thought it should: I configured a device with a simple on/off state: And added 2 playbooks in de config/powercalc/playbooks folder:
The 'On' playbook seems to work, but the 'Off' playbook doesn't. After switching the device to Off, power is set to 0 immediately and after switching it On again, the playbook doesn't seem to start from the Schermopname.2024-04-19.om.18.27.00.movI would expect that the playbook start over again after every state-change, right? |
@EddyK69 Did you see one of my first comments after I implemented? off state cannot be used for playbook. I will have a quick look if I can find a way to implement without needing to modify too much. |
Have good news, because it was a quicky. Should be fixed with #2210 |
Oops, missed that :| |
Quick indeed! Wil try it again soon, thnx! |
Will be in next release. not sure when yet. maybe this weekend |
Still doesn't seem to work unfortunately :( Schermopname.2024-05-03.om.00.00.35.mov |
@EddyK69 You are sure you are at v1.11.8 now? |
It worked once: switching ON started started to increase the power (see below how the playbooks are defined) and switiching OFF started to decrease, only once! After the OFF playbook was finished, i switched ON & OFF and nothing happens. I tried to restart the integration but that did not fix it.
|
Ok thanks for the extra information. Will have a look if I can reproduce and fix. |
Should be fixed with #2229. According to the unit tests this should fix the issue. |
Thnx! Just updated to V1.12.0 and it seems that is now not starting the OFF-playbook anymore :( |
It's working for me now: Overview.Home.Assistant.mp4You can try by editing
Restart HA afterwards. |
Thanx @bramstroker for the quick fix! Wil try out this weekend |
Yep, works perfectly now! Thanx @bramstroker ! |
Checklist
Is your feature request related to a problem? Please describe.
n/a
Describe the solution you'd like
I would love to have the option to run a playbook based on the status of the device, without the need of a start and stop service.
Every time the status changes, the playbook should start from the beginning
Describe alternatives you've considered
n/a
Additional context
A status change should stop the current running playbook and start the playbook mapped to the new state.
The text was updated successfully, but these errors were encountered: