You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @djtimca , I had some tips to add to the wiki for the new v2 lights, and used some of the stuff you have in the documentation and wiki as a starting point.
This is the result of what I put together for my pool dashboard using the OmniLogic HACS integration:
Step 1) Input Select Custom Order and Text
For one thing, I wanted to beautify and re-order how my light shows/solid light colors were displayed. What I wanted was to have clean names without the all capital letters and underscores, and also wanted to move the shows (non-solid colors) to the top of the list because I use those most frequently.
To do this I created a new input select in Settings > Devices & Services > Helpers.
The raw file from my home assistant storage is this:
I needed to have sliders to set my brightness and speed, aka input_number. I created 2 helpers in Settings > Devices & Services > Helpers to achieve this. Here is the raw code from .storage in home assistant config:
Since I need something specific to happen to use the v2 light API I cannot use the normal light object's on/off toggle. I created a input_boolean (toggle) in Settings > Devices & Services > Helpers. Here is the raw configuration from .storage:
Now that we have helpers, we can assemble automation. In my case I was able to initially get things working with a single automation, however I found that if I power my lights on with the Hayward OmniLogic phone app, my helper toggle would be out of sync, and therefore landed on 2 automations. Here is the raw code to save time:
Step 5) Setup automations
Automation 1) Main custom light control for v2 lights
Automation 2) Keep state of light and toggle in sync
alias: Pool - Ensure Pool Lights helper toggle button matches light statedescription: >- Ensures if the light is turned off with the Hayward app that the boolean toggle reflects the state of the actual light and stays in sync.trigger:
- platform: stateentity_id:
- light.home_huff_pool_color_lights_2condition: []action:
- choose:
- conditions:
- condition: stateentity_id: light.home_huff_pool_color_lights_2state: "off"sequence:
- service: input_boolean.turn_offdata: {}target:
entity_id: input_boolean.colorlogic_light
- conditions:
- condition: stateentity_id: light.home_huff_pool_color_lights_2state: "on"sequence:
- service: input_boolean.turn_ondata: {}target:
entity_id: input_boolean.colorlogic_lightmode: single
Step 6) Create a nice all in one dashboard experience
Here's the code to my card setup for all of the above configurations, and it works really nice.
________________________________
From: Andrew J. Huffman ***@***.***>
Sent: Tuesday, July 30, 2024 5:51 PM
To: djtimca/haomnilogic ***@***.***>
Cc: Steve Campbell ***@***.***>; Comment ***@***.***>
Subject: Re: [djtimca/haomnilogic] Wanted to share some ColorLogic light tips to the Wiki but don't know how (Issue #52)
None of it is "necessary" unless you want a nice dashboard for your lights. This was an example on how to achieve that.
—
Reply to this email directly, view it on GitHub<#52 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADUPRMICL544RMJEKCQUP4DZPAKGHAVCNFSM6AAAAABLXGMB66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJZGMZTCOJSGM>.
You are receiving this because you commented.Message ID: ***@***.***>
Hi @djtimca , I had some tips to add to the wiki for the new v2 lights, and used some of the stuff you have in the documentation and wiki as a starting point.
This is the result of what I put together for my pool dashboard using the OmniLogic HACS integration:
Step 1) Input Select Custom Order and Text
For one thing, I wanted to beautify and re-order how my light shows/solid light colors were displayed. What I wanted was to have clean names without the all capital letters and underscores, and also wanted to move the shows (non-solid colors) to the top of the list because I use those most frequently.
To do this I created a new input select in Settings > Devices & Services > Helpers.
The raw file from my home assistant storage is this:
Step 2 & 3) Input Sliders
I needed to have sliders to set my brightness and speed, aka input_number. I created 2 helpers in Settings > Devices & Services > Helpers to achieve this. Here is the raw code from .storage in home assistant config:
Step 4) Toggle
Since I need something specific to happen to use the v2 light API I cannot use the normal light object's on/off toggle. I created a input_boolean (toggle) in Settings > Devices & Services > Helpers. Here is the raw configuration from .storage:
Now that we have helpers, we can assemble automation. In my case I was able to initially get things working with a single automation, however I found that if I power my lights on with the Hayward OmniLogic phone app, my helper toggle would be out of sync, and therefore landed on 2 automations. Here is the raw code to save time:
Step 5) Setup automations
Automation 1) Main custom light control for v2 lights
Automation 2) Keep state of light and toggle in sync
Step 6) Create a nice all in one dashboard experience
Here's the code to my card setup for all of the above configurations, and it works really nice.
Again, this is what you will end up with:

The text was updated successfully, but these errors were encountered: