![](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.
If you’re looking for a commercial product it’s called a whole house fan. The tl;dr is there are vents in the places you want cooled connected to this fan that sits in your attic. Twice a day or so it exhausts the hot air letting it be replaced by the cooler basement air. Depending on the humidity you might need to run the AC to dehumidify the air a bit.
Cobalt.tools worked flawlessly!
EDIT: Ope, thought you were asking lol. Cobalt.tools rocks!
Thats what really kicked me into using obsidian as much as I do.
Basically you can mirror the instapapered versions of your saved pages as markdown files in your obsidian vault. You can customize the whole thing basically so you can put it wherever and have it tie in to your PKM system however you want. I’ve got mine organized in weekly folders with a dataview block in my daily note showing the articles I’ve saved that day.
I’m just curious as to how you think these are insurmountable problems while every instance in existence today is already managing to navigate these issues.
The only thing the author is suggesting is to pool the resources that are going to waste copying media posts around the fediverse into a new backend (that means it’s not directly user accessible and presumably subject to the same restrictions as posts right now) so that the cost of media hosting is more distributed between all the fediverse instances instead of having the big ones hogging all the bandwidth of the small ones with memes because some users decided to subscribe to a community on say Lemmy.world.
Did you even read the article? It’s not like all the users just get unrestricted access to storage to treat like a google drive, this is a backend thing. This guy is trying to find a solution to all the wasted bandwidth and storage space from sending copies to all the other instances they’re federated with, which is a legimate issue that the instance admins are already dealing with on a daily basis. This will let them pool resources to help lower costs for smaller instances.
As to the CSAM thing I can only imagine it would be easier for one instance to purge fifty images/restore from a backup and everyone else just have to redo their thumbnails as opposed to all the instances having to purge and restore but that’s just me.
Literally just set one up yesterday on neocities, it was surprisingly easy. Of course then I managed to break it because I’m not as familiar with git as I’d like to be lol.
I would also like to know this, best I could come up with was one of those electric water cooler pumps that fit over the top of the bottle.
Former intoxicology tech, was both guys daily lol.
No problem! I’ve been puttering around trying to figure this out and this post gave me the push I needed lol
Have you tried going into the setting for the feed itself and using the CSS selector filters? You might be able to cut out the extraneous bits using that.
It looks like it’s being used for cooling in some areas and static control in others.
Oof, that’s what killed my V1 setup lol
They couldn’t effectively serve ads through it lol
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.
Not out yet unfortunately.
EDIT: I lied, link is here. There’s no releases as of yet.
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