![](https://midwest.social/pictrs/image/05e5fb55-23dc-4b5c-a7db-1bb3d50e1baf.png)
![](https://lemmy.world/pictrs/image/94b2b808-7c9c-4de0-a35b-966d14ae40fd.png)
Yeah it looks like OP is using the device actions instead of dealing with the entity directly.
Yeah it looks like OP is using the device actions instead of dealing with the entity directly.
deleted by creator
So let me see if I get this straight, We don’t get RSS feeds for our saved posts because the developer of a federated service that was created in response to increased centralization and lockdown of user’s content in other platforms doesn’t see the need for it?
Ope, didn’t mean to comment on this one, sorry.
EDIT: Alright WTH, Sync is playing silly buggers with my comment display.
With style!
Well of course not, ever since they got that deal with Uncle Sam they knew they could do anything up to Steve Ballmer kicking a secret service agent in the nuts and stealing the Football. Maybe even including that, won’t know until it happens lol.
No problem! I’ve been puttering around trying to figure this out and this post gave me the push I needed lol
It looks like it’s being used for cooling in some areas and static control in others.
I did just check to see if you can pass along wildcards in an automation, which you can! I used this automation:
alias: sentence test
description:
trigger:
- platform: conversation
command:
- When is [my] {date}
condition: []
action:
- set_conversation_response: curses, that damnable {{ trigger.slots.game }}
enabled: false
- choose:
- conditions:
- condition: template
value_template: '{{ ''birthday'' in trigger.slots.date }}'
sequence:
- set_conversation_response: >-
curses, that damnable {{ trigger.slots.date }}! It completely
slipped my mind
- conditions:
- condition: template
value_template: '{{ ''christmas'' in trigger.slots.date }}'
sequence:
- set_conversation_response: sir you know when {{ trigger.slots.date }} is!
This should give you a framework to build off of. It looks like when you don’t define a list of slots in an intent it just passes the wildcard along in a slot.
I can think of a couple ways you could have it be one automation, the first is you’d have multiple triggers with different ids and use the choose action to select the response based on the trigger id.
The other way that I’m a bit less sure about is passing the name of the input_date helper through to the response with a wildcard. You’d probably have to set the {{ trigger.slot.event }} as a variable and match that to an alias or an entity_id.
So I found this which might help. I tried defining my own intent scripts too, but it was too much of a PITA, I ended up using automations instead.
Or get a geofence warrant
Yeah I use bitwarden and it was pretty panless. My only issue was on github the addon didn’t pick up on the passkey initially, had to make a new one.
Yeah I had the traefik reverse proxy set up for a while until it updated to 2.x and all my configs broke. At that point I gave up and just paid for the nabu casa URL.
Ardumower is the one I’ve always intended to roll with. Eventually lol. The original nav method is a buried perimeter wire, but they do offer a GPS-RTK kit.
Ehhh, it’s not like I’d actually do it, but the thought of doing it while I’m pumping gas gives me warm fuzzy feelings inside.
One of these days I’m going to find out where they hide those speakers and when I do I’m bringing an icepick to the pump.
Yeah IDK what they’re talking about, I’ve got a 8yo cartridge in a 19yo printer. When’s the last time you saw an inkjet last that long?
Someone is working on replicating echo show functionality in home assistant, it’s called View Assist.
How I keep that sort of thing in a single automation is by using trigger IDs and a service call with a template for said trigger id.
Something like this:
alias: Hallway Motion Light description: "" trigger: - platform: state entity_id: - binary_sensor.hallway_motion_occupancy to: "on" id: "on" - platform: state entity_id: - binary_sensor.hallway_motion_occupancy to: "off" id: "off" for: hours: 0 minutes: 1 seconds: 0 condition: [] action: - service: light.turn_{{ trigger.id }} data: transition: 3 target: entity_id: light.hallway_light_2_2 mode: single