#is script.inovelli_led something that it is referencing out of somewhere else?
1 messages ยท Page 1 of 1 (latest)
it's a script for doing the LED lights
Right, do I need to have that present elsewhere?
or are you defining it in that block?
i have the script loaded
here's where you can nab it https://community.home-assistant.io/t/inovelli-z-wave-red-series-notification-led/165483
I'm looking through this, the github link as well and I'm not seeing a separate file or anything that I'd have to put in some script dir
does the giant sequence portion need to go in scripts.yml?
shove this file https://raw.githubusercontent.com/brianhanifin/Home-Assistant-Config/e62794c5578a3b12657081fb49c29da9b5ee9482/scripts/notifications/inovelli_led/inovelli_led.yaml into your scripts directory ๐
Oh
No it didn't, I don't know what I did but I didn't put in the scripts.yaml, I just went back did that and reloaded scipts and got this
Source: config.py:443
First occurred: 11:01:04 AM (5 occurrences)
Last logged: 11:48:58 AM
Invalid config for [script]: expected a dictionary. Got OrderedDict([('default_config', {}), ('homeassistant', OrderedDict([('packages', OrderedDict())])), ('tts', [OrderedDict([('platform', 'google_translate')])]), ('http', OrderedDict([('use_x_forwarded_for', True), ('trusted_proxies', ['172.30.33.2'])])), ('group', OrderedDict([('garage', OrderedDict([('name', 'Garage'), ('entities', ['cover.garage', 'sensor.garage_status'])]))])), ('automation', [OrderedDict([('id', '1605131350180'), ('alias', 'Turn on entryway lights at sunset'), ('descriptio.... (See /config/configuration.yaml, line 14).
Invalid config for [script]: [zwave_integration] is an invalid option for [script]. Check: script->zwave_integration. (See /config/configuration.yaml, line 14).
Invalid config for [script]: [entity_id] is an invalid option for [script]. Check: script->entity_id. (See /config/configuration.yaml, line 14).```
oh
try adding inovelli_led: above the mode: parallel
ie:
inovelli_led:
mode: parallel
variables:
# REQUIRED to be one of these options: "zwave", "ozw", "zwave_js"
zwave_integration: "zwave_js"
...
wait should I have just created inovelli_led.yaml or something?
that's how i do it
I don't have a scripts directory, just the scripts.yaml so I copied the contents
but I will make the folder
script: !include_dir_merge_named scripts/
i use that in my config
putting it in scripts.yaml should technically work
if you add that line
not yaml familiar
I have ```script: !include scripts.yaml
do I just do the !include_dir_merge_named after scripts.yaml?
hold on, i don't want you breaking your scripts ๐
I have none ๐
oh I got it
!include scripts.yaml
!include_dir_merge_named scripts/```
dunno if that'll work
okay I reloaded and got no errors with that
although configuration > scripts doesn't show that script, not sure if it should
in this case
it should
woo! then that didn't work
I'll just do the dir_merge and not the scripts.yam
hmmm, so I changed it to ``` script: !include_dir_merge_named scripts/
still getting that error from above
give this a shot https://pastebin.ubuntu.com/p/sVjtW3XWSw/
oh the paste you sent, starting on line 246 it isn't indented, so there are visual errors in VSCode
missing property "sequence"
property entity_id is not allowed
do I just need to indent that whole section?
VSCode says it's good on my end ๐
if they don't matter then I will ignore.
those are all valid, ignore the errors
I blame...err....the internet!
@snow remnant tell me if I'm wrong about this, but to make the automation, I just have it triggered when cover.garage attribute Door State is Open
I'm at that point confused about the Trigger ID, from, to, for
yup
Door State doesn't really have a range, are From and To just "Open"
Although, I would also like it to trigger when door state is unknown
oh does that specify when state goes "from" closed "to" open
I thought it was a range of states that would trigger....I'm dumb
if you do "from: closed" it'd trigger if it was 'closed' then goes unavailable or opening opened open
correct
do I put anything in Trigger ID?
this in the UI?
ya leave it blank
your action will be 'call service'
the service will be script.inovelli_led
okay
and it should have stuff for you to fill in
then just
entity_id: zwave.dimmer_family_room
color: purple
dimmer: "true" # Set to "false" for the non-dimmable switch.
duration: 10 seconds
effect: chase
level: 10```
yup
but with whatever info?
data:
entity_id: switch.downstairs_hallway
color: red
duration: 2 Minutes
effect: Pulse
level: 10
model: switch
^ this is what i use for my garage door being open
but i have it set to auto close if opened for more than 15 mins
yeah I want this to just act as a reminder if it's open
you can set the duration to "indefinite" to keep it going until you turn off the LED via another automation
okay, will that disable it or return it to normal function?
yup
and make a separate data section per dimmer?
comma separated?
entity_id: dimmer1, dimmer2
kk
weird, all of them are light.location_dimmer
swear they were marked as switches idk
oh
duh
Okay I tried to "run actions" and it isn't making the pretty lights.
data:
entity_id: >-
light.entryway_dimmer, light.kitchen_dimmer, light.living_room_dimmer,
light.master_bedroom_dimmer
color: orange
duration: Indefinitely
effect: Chase
level: 10
model: dimmer```
tried capitalization on the different bits but that doesn't seem to be it
any errors in the log?
Didn't see any but I might have not looked in the right place.
where is that
/config/logs all the way at the bottom
Seems like there are quite a few instances of it having trouble updating the cover status as well
it's saying parameter 16 doesn't exist on your dimmers
I see that, looking at the dimmers there are like 20+ params
you using zwavejs2mqtt?
the page for zwave device configuration exists and shows all of those, they just don't have numbers
no just zwavejs, but I have mqtt installed and can swap between the two
it looks like its specifically for node 11 that its having issues?
er, all 4 are inno red, they all came in the same shipment
looks like node 11 was missing some info, its reinterviewing
that one had a weak connection before I added the booster
its still showing as unknown manufacturer/model
but even looking at it, it still shows all the available configuration params
the reinterviews were quick and now "run actions" works
lots of chasing orange light switches
data:
entity_id: >-
light.entryway_dimmer, light.kitchen_dimmer, light.living_room_dimmer,
light.master_bedroom_dimmer
effect: Clear
okay so it worked when I did "run actions" but it isn't working now testing it
pretty sure it's "Off" to stop em
so what you can do now is hit the trace button to find out why it didn't trigger
yeah so it shows 5 minutes ago I manually ran it
I'm thinking instead of cover.garage and Attribute Door State
I should have used sensor.garage_status
yeah that got it to trigger
However now I the garage door is stuck in "opening" even though it is closed....hmmmm
when you view it in yaml it should look like this:
platform: state
entity_id: cover.garage_door_controller
from: closed
seems like my garage door integration just shat the bed
ooof
won't open/close and it is stuck in state "opening"
ya it's a safety thing, can't command it while in motion
does it think its in motion until it receives "open"?
yes
oh I guess I didn't leave it open long enough
looks like it takes ~30 seconds to update from when the physical door is open
can't say I've ever pulled the car in or out in under 30 seconds so that's fine
you can if you floor it
lol
but both worked, thank you for your help as always
no problem man
now to add another two dozen notifications to the dimmers so I forget what all of them are for
I have the mobile app, is there a way to clear a notification without doing so manually?
IE just show a notification that its open and then disappear when it closes?
yup you can make them timeout
but with an indefinite amount of time?
you can swipe em away
bookmarked, thank you
@snow remnant is the little control button on the dimmer usable for functions? Was thinking if the lights are showing the door is open a single press could trigger it to close?