@david_b wrote:

Just updated to 111.0 and now get the error

Setup failed for wled: Unable to import component: No module named ‘packaging’

Any idea what that means… TIA

I tried to delete the component and set up again but can’t delete, oh for the days when you could just comment out the yaml file. I think ill go back to the old ways.

Posts: 1

Participants: 1

Read full topic

@RetroTim wrote:

Since 0.111 it’s possible to expose an input_select, which works kind of. My input_select shows up in the Google Home app as a sensor. Is it supposed to do that? I don’t see any value or whatever.

Also, how am I supposed to call this through Google Assistant? I’ve tried a lot of things but it won’t change the input_select.

Who can help?

Posts: 1

Participants: 1

Read full topic

@uphillbattle wrote:

I have some 433 MHz temperature sensors. Their signals are picked up using rtl_433 and that program publishes MQTT messages with the sensors’ messages. The MQTT messages are picked up by Home Assistant using an automation:

- id: rtl_mqtt_trigger
  alias: RTL MQTT trigger
  trigger:
    platform: mqtt
    topic: 'rtl_433/RPi4/events'
  action:
    event: RTL_MQTT
    event_data_template:
      topic: '{{ trigger.topic }}'
      payload: '{{ trigger.payload }}'

The RTL_MQTT event is picked up by an automation in AppDaemon. Everything works as intended.

However, the RTL_MQTT event is fired several times a minute, so my logbook was initially filled with these events. I put this code in configuration.yaml:

logbook:
  exclude:
    entities:
      - automation.rtl_mqtt_trigger

… and the filling of the logbook ceased …

… until 0.111.0. Now my logbook is filling up again with these events.

Did anything change with the latest update?

Posts: 1

Participants: 1

Read full topic

@jaswalters wrote:

I had a cast device auto added by discovery as I run default_config. I have seen numerous blurbs on how to remove this but nothing concrete. What is the best approach as I need to try to add it in a different manner?

Posts: 1

Participants: 1

Read full topic

@Matt_Barnes wrote:

I have 7 temp or door sensors in my house from Xiaomi and a raspbee premium on my RPi3+ running Deconz on HA.

Just noticed 3 of the temp sensors have gone unavailable. Looking on the VNC viewer for them I can see all three are not showing as connected to the raspbee but other sensors further away from the raspbee are.

I do not have a big house (4 bedroom) and one of the disconnected sensors is ground floor, 2 stories below my Pi which is in the attic.

Are these sensors just no use for a house without lots of powered devices to keep the signal?
Should I just forget this method of temperature sensing?
Is there a way to reconnect a dropped device without having to delete it, then add it as a new sensor and change all my references to it?
Can I reconnect a sensor in VNC somehow?

Thanks!

Posts: 1

Participants: 1

Read full topic

@sender wrote:

Hi, just upgraded to

And wow! this starts to get somewhere.

But I have 3 issues:
1: when clicking on the webui I can’t see the mouse cursor anymore. I can “guess” where it is and that responses. But it is not correctly.
Mouse is in middle but not visible:

image890×673 93.6 KB

2: according to the documentation:
Accessing the ozw-admin application via VNC

You can access the built-in ozw-admin application via a VNC viewer.

Please note, you can access the same interface using the “OPEN WEBUI” button, described above.

To enable it:

Set a port number for VNC in the "Network" configuration section of the add-on and hit "SAVE". Advised is to use port 5900, but any other port above 5900 works as well.
Restart the add-on.

But I cannot set a port for VNC (deleted the network key):

image933×431 6.14 KB

3: I cannot use the windows instaler artifact thin version 0.1.0 anymore, it hangs at 64%:

image1022×845 19.2 KB

Any tips?

Posts: 1

Participants: 1

Read full topic

@ravimohta wrote:

Hi,

I have my home assistant connected to VeraPlus via the integration and it works fine.

The only issue I have is that some of my RGB Led Strips (using Fibaro RGBW zwave devices) are identified in Home Assistant as just on-off light switches. This happens to just some RGB Led strips.

Any idea how I can fix it?

Thanks.

Posts: 1

Participants: 1

Read full topic

@vital411 wrote:

I have Home Assistant Core running on an Unraid Docker. I added the straighforward integrations first (ecobee, abode alarm, weather) which were obviously easy. I can’t for the life of me get any of my brand new GE Embrighten Zwave Dimmers or Fan Switches to pair.

What i’ve done so far:
Added Zwave to the configuration mapping my AEON GEN 5 Usb stick and specified a network key.The USB Stick shows up as my 1 node in Home Assistant.

When i press “add node” or “add secure node” (tried both) and then press the Up toggle on my zwave switch i get the following in the log:

2020-06-10 22:44:58.801 Detail, Queuing (Controller) Add Device 2020-06-10 22:44:58.801 Info, Add Device 2020-06-10 22:44:58.801 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0b, 0x7a 2020-06-10 22:44:58.801 Detail, Notification: ControllerCommand - Starting 2020-06-10 22:44:58.801 Detail, 2020-06-10 22:44:58.801 Info, contrlr, Sending (Command) message (Callback ID=0x0b, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0b, 0x7a 2020-06-10 22:44:58.803 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0b, 0x01, 0x00, 0x00, 0xb8 2020-06-10 22:44:58.803 Detail, 2020-06-10 22:44:58.803 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK: 2020-06-10 22:44:58.803 Info, contrlr, ADD_NODE_STATUS_LEARN_READY 2020-06-10 22:44:58.803 Detail, Node001, Expected callbackId was received 2020-06-10 22:44:58.803 Detail, Node001, Expected reply was received 2020-06-10 22:44:58.803 Detail, Node001, Message transaction complete 2020-06-10 22:44:58.803 Detail, 2020-06-10 22:44:58.803 Detail, contrlr, Removing current message 2020-06-10 22:44:58.803 Detail, Notification: ControllerCommand - Waiting 2020-06-10 22:44:58.803 Info, WriteNextMsg Controller nothing to do 2020-06-10 22:44:59.291 Detail, Received: 0x01, 0x07, 0x00, 0x4a, 0x0b, 0x02, 0x00, 0x00, 0xbb 2020-06-10 22:44:59.291 Detail, 2020-06-10 22:44:59.292 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK: 2020-06-10 22:44:59.292 Info, ADD_NODE_STATUS_NODE_FOUND 2020-06-10 22:44:59.292 Detail, Notification: ControllerCommand - InProgress 2020-06-10 22:45:00.162 Detail, Received: 0x01, 0x07, 0x00, 0x4a, 0x0b, 0x07, 0x00, 0x00, 0xbe 2020-06-10 22:45:00.162 Detail, 2020-06-10 22:45:00.162 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK: 2020-06-10 22:45:00.162 Info, ADD_NODE_STATUS_FAILED 2020-06-10 22:45:00.162 Detail, Removing current message 2020-06-10 22:45:00.162 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4 2020-06-10 22:45:00.162 Detail, Notification: ControllerCommand - Failed 2020-06-10 22:45:00.162 Detail, 2020-06-10 22:45:00.162 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4 2020-06-10 22:45:00.214 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0b, 0x06, 0x00, 0x00, 0xbf 2020-06-10 22:45:00.214 Detail, 2020-06-10 22:45:00.214 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK: 2020-06-10 22:45:00.214 Detail, Node006, Expected reply was received 2020-06-10 22:45:00.214 Detail, Node006, Message transaction complete 2020-06-10 22:45:00.214 Detail, 2020-06-10 22:45:00.214 Detail, contrlr, Removing current message 2020-06-10 22:45:00.214 Detail, Notification: ControllerCommand - Completed

Any thoughts on what i can do to get these added? I have tried factory resets on all of the switches as well and have no luck.

Thanks!

Posts: 1

Participants: 1

Read full topic

@paulster wrote:

The 8-button mini remotes had been working well with each button configured to toggle on/off stage.

With 0.111.0 installed every time I press a button I get a button-on and then a button-off event, so I can’t use any of my remotes now.

I couldn’t see any documentation for an expected behaviour change, so is there a means to fix this without having to downgrade again?

Thanks

Posts: 1

Participants: 1

Read full topic

@cree8 wrote:

Hello,

I was wondering if anyone else has a sort of sanity check to check if a command to turn the light off actually did so? (I use node red for automations)

In my case, sometimes a light group will have a straggler that does not appropriately respond after the command was issued. I will then need to reissue the command to get the last light or two to match the rest.
I was thinking of having a node to check the status after a command is sent from one of my switches that will check the light status a few seconds after it was issued. Does anyone else do this?

Thanks!

Posts: 1

Participants: 1

Read full topic

@Teleportist wrote:

I’m using the Internet Printing Protocol (IPP) integration to monitor the ink levels in my printer.
This works well when the printer is online, with the following gauge cards (horizontal stack) appearing.

However, when the printer is switched off I get this.

Is there any way to override this, so the card is displaying the last known sensor state (excluding unavailable) instead? I just want to be able to see what the ink levels are/were last time the
printer was online.

Here’s the card yaml.

cards:
  - entity: sensor.hp_photosmart_5520_series_cyan_ink
    max: 100
    min: 0
    name: Cyan
    severity:
      green: 25
      red: 0
      yellow: 10
    type: gauge
  - entity: sensor.hp_photosmart_5520_series_magenta_ink
    max: 100
    min: 0
    name: Magenta
    severity:
      green: 25
      red: 0
      yellow: 10
    type: gauge
  - entity: sensor.hp_photosmart_5520_series_yellow_ink
    max: 100
    min: 0
    name: Yellow
    severity:
      green: 25
      red: 0
      yellow: 10
    type: gauge
  - entity: sensor.hp_photosmart_5520_series_black_ink
    max: 100
    min: 0
    name: Black
    severity:
      green: 25
      red: 0
      yellow: 10
    type: gauge
title: Printer Ink
type: horizontal-stack

Many thanks

Posts: 1

Participants: 1

Read full topic

@JHWas wrote:

I tried integrating rain forecast for today and for tomorrow with no success.

I would like to start the garden irrigation only, if today was less than 0.3 mm rainfall in total and tomorrow the forecast is below 0.3mm (in total) for the whole day.
Even better, if the “chance of rain” ist high for tomorrow and more than 0.3 mm rainfall.

So far the irrigation automation works fine (using sonoff 4ch Pro wifi relays), but I cant stop it from watering, if it is not necessary.

I tried so far:

• Openweathermap
  There is a forecast in the weather integration (card), but I can not use it as a condition in automation
• me.to
• weatherunderground (only works wit weather station)
• yr
• Darksky is said to be no longer working.

Any help is heartily appreciated.

Posts: 1

Participants: 1

Read full topic

@kaczkalolo wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic

@Chaandgus wrote:

Hello,

First of all, it’s my first post…so : THANKS SO MUCH to EVERY DEVELOPPERS of HA !! Very nice job ! Next, sorry for my english ;

I’m running Hassio on Tinker Board-S, in Docker (under Debian GNU/Linux 10), HA version .

I have some integrations already working like Z-Wave, Neato, Netatmo…Etc. But, I’d like to pass through the Do It Yourself usinf ESP8266, ESP32CAM….Etc.

I tried that video but I had no issues : https://www.youtube.com/watch?v=H5miv_fdBZY. I asked myself if it’s not because I’m running in Dockers.

In Portainer The IPV4 Subnet is 172.20.32.0/23

I always have the HAssio notification "Login attempt or request with invalid authentification from 172.30.32.2.

I have indeed that notification lot of time while my Tinker Board IP is : 10.0.4.120.

I tried that solution…but it doesn’t works also :

Login « Ha » and password « Hamp » are not mines but it’s just an example

I installed Mosquitto Broker :

•     Login : Ha 
  

•     Password : Hamp
  

I bought Anavi thermometer : https://github.com/AnaviTechnology/anavi-thermometer-sw and flashed the binary file [anavi-thermometer-sw-102-20200510.bin] from “relases” with ESP-Home Flasher.

I didn’t included parameters in the .bin but directly through Wifi configuration :

image750×1334 59.6 KB

The ANAVI Thermometer IP Adress is 10.0.4.51 and it looks to works well in the Home Flasher Log :

In HA, I installed ESPHome :
esphome:
name: exmaple
platform: ESP8266
board: nodemcuv2

The problem is : I can’t use MQTT and include my Anvi Thermometer in HAssio…

The parameters in Hassio’s MQTT integration are :

•     IP : 10.0.4.120
  

•     IPort : 1883 1
  

•     ILogin : Ha
  

•     IPWD : Hamp
  

Question 1 : Must I have to enter my docker IP adress instead of my Tinker Board IP please.

I also have the problem with my Sdomotica configuration for Bticino (Legrand) :

'Question 2 : It doesn’t Works. Must I need to create files for Mqtt too ?

Hope it is clear’

Many thanks for your help and again thank you to the developers. Hope I’ll help too when I’ll be (a little bit) better

Augustin

Posts: 1

Participants: 1

Read full topic

@mitchell wrote:

As the title, is there anything i should have changed? I couldn’t see anything obvious in the change log. It’s super annoying.

Here is a video of it:

Posts: 1

Participants: 1

Read full topic

@srpablillo wrote:

Hello, I am new on this. I am moving from a z-wave hub to HA on a RP4.

This is my configuration.yaml

zwave:
  usb_path: /dev/serial/by-id/usb-0658_0200-if00
  network_key: !secret zwave_network_key

I did some trial-error process to include my old zwave devices. I removed and factory reset them. I can add some of them with no problem (and then they work properly), but for others log is showing no problem but I see them nowhere. All the devices I am adding are the same manufacturer-model (Fibaro FGS-223)

I’ve read similar issues on the forum but none of the solutions worked for me (such as remove and reinstall the zwave integration, remove zwcfg.xml file and restart, check entity registry file, etc)

This is what I see on the log after adding a device which never appears on the Config>ZWave drop down. Any help would be really welcome as I am running out of ideas. Thanks!

image1536×716 334 KB

Posts: 1

Participants: 1

Read full topic

@mirekmal wrote:

For me one of always missing integrations was Synology Download Station. So I decided to fill in the gap… and here it is… sort of.
Since I’m not familiar with python, I did not took challenge to build proper integration, but I figured out how I can link with SDS using standard tools available for everyone within HA. It ended with creation of yaml package containing everything that is needed to integrate SDS into HA. Before you begin, however, a few words of warning:

• it is entirely based on sensor created in configuration.yaml, so it probably not as efficient as it would be while using proper integration.
• since I use rest sensors to obtain information from SDS and use other set of sensors to process this data, propagation of information takes time. I believe rest sensors are updated every 15 seconds and it takes up to 3 cycles to update ‘child’ sensors. Not ideal, but given the fact that sometimes file downloads are very long process I believe this speed of update is acceptable.
• WARNING: since I found no way to template secrets, configuration of this ‘integration’ is hardcoded in sensors. Especially it concerns user ID and password used to access Synology NAS via API and also exposes session token (required to access API after logging in) as one of sensors ! ! !
• since using this method I can’t create dynamically sensors, these are somehow reusable. You should consider each sensor as representing download slot rather that actual individual task. It means that these sensors are ‘reusable’ and if one download is completed and removed from SDS, this slot might be used for other pending download task, effectively changing history of task from old to new one… especially inconvenient for charts (like download speed). Also when task is removed or added to SDS it might cause some inconsistency of displayed data, before sensors values changes in up to 3 iterations I mentioned in point #1.

So, to the actual implementation:
You need to copy all the code from gist below into download.yaml file inside your config directory (or obviously modify setup to your liking! )

• Since everything is packaged into single download.yaml package file, your configuration just need to be updated by adding following to your configuration.yaml:

homeassistant:
  packages:
    download: !include download.yaml

• within download.yaml, you need to update 2 first sensors (sds_login and sds_tasks_list) replacing following statements with actual data:

 _SDS_IP_    - IP address of your NAS
 _SDS_PORT_  - port to connect on. in standard setup it is:
               5000 for Synology Diskstation Manager or
               8000 for Synology Download Station
               either of these 2 can be used
 _SDS_USER_  - DSM user with permission to use SDS
 _SDS_PASS_  - password for above user

• if you have proper ssl access configgured on your NAS, you can change prtocol to hppts and update port accordingly (5001 or 8001).
• you also need to update _SDS_IP_ and _SDS_PORT_ within all sds_task_# sensors.
• I created sensor templates for 10 download slots. All corresponding to specific download slot sensors have name ending with _#, where # represent number of slot, starting with 0 and ending with 9. If you do not expect such number of slots to be used you can safely delete some and decrease number of created sensors. If you download more, you can also add new sensors with # starting from 10…

Following sensors are created:

• sensor.sds_login - it is used to initially log on to SDS and obtain the API token. Not used elsewhere.
• sensor.sds_tasks_list - contain list of basic data for all download tasks. This list will be empty if no downloads or might contain information about more than 10 tasks, but the tasks 10+ will be disregarded (until you create additional sensors). Otherwise this sensor has no use.
• sensor.sds_task_# - contains detailed information about download task as reported via SDS API. Based on information from this sensor all other sensors are created. If you feel confident with templating, you can uses these sensors directly!
• sensor.sds_sid - this is the sensor that holds API token used by rest sensors to retrieve data via API. No for direct use.
• sensor.sds_task_id_# - set of sensors used by SDS API to identify unique tasks. Used as reference by other sensors only.
• sensor.sds_tas_name_# - name of downloaded file
• sensor,sds_task_size_# - size of downloaded file in MB
• sensor.sds_task_downloaded_# - size of already downloaded part of file in MB
• sensor.sds_task_completed_# - download progress in %
• sensor.sds_task_speed_down_# - task download speed in kbps
• sensor.sds_task_speed_up_# - task upload speed in kbps
• sensor.sds_task_status_# - status of task (downloading, error, finished, unknown for just started, unavailable for empty slot)

Set of statistical sensors, useful for example to dynamically scale some charts, or dynamic color representation:

• sensor.sds_max_download - sensor reporting download speed of fastest task
• sensor.sds_avg_download - sensor reporting average download speed of all tasks
• sensor.sds_min_download - sensor reporting download speed of slowest task (frequently 0)
• sensor.sds_max_upload - sensor reporting upload speed of fastest task
• sensor.sds_avg_upload - sensor reporting average upload speed of all tasks
• sensor.sds_min_upload - sensor reporting upload speed of slowest task (frequently 0)
• sensor.sds_max_transfer - representing fastest one of upload and download, useful if you want to use one graph to display both and have uniform scale.

As you can see package I prepared contains lots of sensors, in your particular implementation perhaps some might be useless, so can be safely deleted decluttering configuration.

As a bonus I’m attaching template of lovelace card I created to use with this ‘integration’. It requires following components to be installed:

• button-card
• custom:mini-graph-card
• custom:config-template-card
• custom:button-card
  

Following code is for download slot 0. To create similar cards for subsequent slots you need to replace in the names of sensors use ‘_0’ with proper number. Card is autohiding, if slot not in use, to keep UI declustered.

card:
  aspect_ratio: 1.3/1
  custom_fields:
    bar:
      card:
        direction: right
        entities:
          - entity: sensor.sds_task_completed_0
        height: 25px
        max: 100
        min: 0
        positions:
          icon: 'off'
          indicator: 'off'
          minmax: 'off'
          name: 'off'
          target: 'off'
          value: inside
        severity:
          - color: '#7b55d5'
            from: 0
            to: 25
          - color: '#fc70f3'
            from: 25
            to: 50
          - color: '#00b8fe'
            from: 50
            to: 75
          - color: '#7cff73'
            from: 75
            to: 100
        type: 'custom:bar-card'
        width: 10%
    graph:
      card:
        card:
          entities:
            - entity: sensor.sds_task_speed_down_0
              color: var(--greenish)
              state_adaptive_color: true
              name: Download
            - entity: sensor.sds_task_speed_up_0
              color: var(--light-magenta)
              state_adaptive_color: true
              name: Upload
              y_axis: secondary
              show_state: true
          height: 100
          hours_to_show: 1
          line_width: 2
          points_per_hour: 600
          show:
            points: false
            fill: fade
            icon: false
            name: false
            labels: false
            labels_secondary: false
          type: 'custom:mini-graph-card'
        entities:
          - sensor.sds_max_download
          - sensor.sds_avg_download
          - sensor.sds_task_speed_down_0
          - sensor.sds_task_speed_up_0
        type: 'custom:config-template-card'
        variables:
          - 'states[''sensor.sds_max_download''].state'
          - 'states[''sensor.sds_avg_download''].state'
  entity: sensor.sds_task_name_0
  hold_action:
    action: none
  show_name: false
  show_state: true
  styles:
    card:
      - padding-left: 10px
      - padding-right: 10px
    custom_fields:
      bar:
        - filter: opacity(100%)
        - overflow: unset
        - margin-left: '-51%'
        - width: 105%
      graph:
        - filter: opacity(100%)
        - overflow: unset
    state:
      - color: var(--cyanish)
    grid:
      - grid-template-areas: '"s" "graph" "bar'
      - grid-template-columns: 1fr
      - grid-template-rows: 1fr 1fr
  type: 'custom:button-card'
conditions:
  - entity: sensor.sds_task_id_0
    state_not: unavailable
type: conditional

And the final word… I tested this only with torrent downloads, but given the nature of SDS API I’d expect that it should work equally fine with any supported by SDS transfer protocol (BT, FTP/HTTP, NZB, RSS).

Happy downloading!

Posts: 1

Participants: 1

Read full topic

@nightkid wrote:

I thought I’d share how I deployed CUPS via Portainer alongside hassio. I am a beginner using docker and it wasn’t clear how I would start, so hopefully this helps someone.

I am using the Portainer addon, so make sure you have that (Supervisor > Add-on Store > Portainer).

*and for the advanced users, please let me know if I am mis-configuring something!

1. Add container
   

2. • Input a name
     • I am using “rpi-cups”
   • Input name of docker image from hub (*this is just the name; it will pull the image)
     • I am using “lemariva/rpi-cups:latest” but probably any CUPS docker with a raspberry-pi implementation would work
   • Make sure “Always pull the image” is enabled
   • Click on “publish a new network port” and set it from 631 to 631
     
3. • Go to “Volumes”
   • “map additional volume”
     /var/run/dbus:/var/run/dbus
   • “map additional volume”
     /dev/bus/usb:/dev/bus/usb
     
4. • Go to “Restart policy”
   • Choose “Unless stopped”
     
5. • Go to “Runtime & Resources”
   • Enable “Privileged mode”
     

6. Go back up top and “Deploy the container”
   

After that, you should be able to access CUPS via http://localhassip:631 and setup your printer.

Posts: 1

Participants: 1

Read full topic

@Ordovicium wrote:

Hi,
I have from my garbage schedule multiple dates, when they will come. I would like to save these dates within an array. Then on the lovelace screen I will have a card, which shows me the next upcoming date within this array. Hope you can support me, because with YAML I am not very familiar yet.

Posts: 1

Participants: 1

Read full topic

@burg93 wrote:

Hey, I have the below automation working but it seems a bit messy. Does anyone have any suggestions on improving it without having to buy an IR blaster to solve the main issue of turning the TV on?

Goal: An automation triggers to turn on the Virgin media box, set the channel, turn the TV on and swap to the correct HDMI input.

TV: UE55MU6400UXXU

My TV loses network connectivity (even over LAN) when turned off so I can’t turn the TV on directly remotely. So in order to do that I can turn the attached Chromecast on, then cancel out of the forced media player before eventually changing HDMI input.

It feels like there are some un-necessary steps in here and the steps themselves work fine if I trigger them each individually from the dev console (e.g. the switch source works immediately as expected) but they just don’t work properly if I put them in an automation unless I litter with delays and a couple of repeated commands, I assume this is because the steps need time to complete and the automation is triggering them too quickly…

Any thoughts appreciated!

action:
  - data: {}
    entity_id: media_player.virgin_v6
    service: media_player.turn_on
  - delay: 00:00:01
  - data:
      entity_id: media_player.virgin_v6
      source: ITV
    entity_id: media_player.virgin_v6
    service: media_player.select_source
  - data: {}
    entity_id: media_player.living_room_chromecast
    service: media_player.turn_on
  - delay: 00:00:02
  - data: {}
    entity_id: media_player.living_room_chromecast
    service: media_player.turn_off
  - delay: 00:00:05
  - data:
      entity_id: media_player.living_room_samsung_tv
      source: HDMI3
    entity_id: media_player.living_room_samsung_tv
    service: media_player.select_source
  - data:
      entity_id: media_player.living_room_samsung_tv
      source: HDMI3
    entity_id: media_player.living_room_samsung_tv
    service: media_player.select_source

Posts: 1

Participants: 1

Read full topic