Well first off swarm doesn’t work with environment variables, so if you pass any in you’re going to need to pipe the output of docker compose read into docker swarm service create.

Your port settings are gonna give it a problem too, swarm doesn’t support that new syntax, and as a result you can only assign a single network interface to a service.

Regarding networking, since the whole paradigm is that you’re not defining a single container but a service that can live/move across multiple nodes; any traffic to any node in your swarm will be routed (round robin style) across the copies of that service. (This makes logging setup a PITA, ask me how I know!)

Bind mounts aren’t recommended, volumes are preferred. Otherwise everything needs to be mirrored across all nodes, depends on the use case.

That being said I’m not convinced that swarm is the right answer here, I concur with @[email protected]. You should just install pangolin on your second machine.

Wow fuck those readium guys

You can have a JD Vance NFT, as a treat.

Also follow hashtags!

Seconding this, I have two aurora dimmers and they’re awesome.

You’re right, it was a bit too off the cuff of a remark. Though I can’t imagine they’ve had fun there since the Muppet took over. Can you imagine being the poor bastard who had to tell Phony Stark about this whole thing? They probably had to remind him that their office existed only to have him sack everyone.

…and nothing of value was lost

Found the Google employee

Hint: the answer is very likely no…

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

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.