Quantcast
Channel: Configuration - Home Assistant Community
Viewing all 108763 articles
Browse latest View live

Generic weather?

$
0
0

Is there an integration that bundles the data from a local weather station into a “weather” type?

There are plenty of cards to display the current weather nicely, but I haven’t found anything like that for a bunch of measurements. And while looking at 30 raw values certainly is interesting, usually a quick overview is more convenient.

2 posts - 2 participants

Read full topic


Modbus queueing requests

$
0
0

My HA has been in productive use for quite some time and is running 24/7. Modbus so far is purely experimental with all devices – three sensor units and one relay board – on my workbench. Last night on going to bed I turned off the sensor units. This morning they ignored the scan_interval and kept being read as fast and frequently as the bus allows. The relays were not accessible.
That looks as if requests were queued and now all those stored up during the night were executed first before anything new can be done. Not what I want. My plan is to call devices periodically, in practical use once per minute or less, and failed calls should just be thrown out and ignored after the timeout. How can that be achieved?
Another thing. In the developer tools reloading modbus.yaml does nothing, just a permanet blue ring, and restart->quick reload does not work for modbus. Only a full restart works. Is that normal with modbus? I’ll add my full setup.
Danke
Axel

#modbus:
- name: modbus_hub
  delay: 3
  message_wait_milliseconds: 100
  timeout: 2
  type: serial
  port: /dev/ttyUSB1
  method: rtu
  baudrate: 9600
  bytesize: 8
  parity: N
  stopbits: 1

  switches:
    - name: SW001
      unique_id: REL1
      slave: 1
      address: 0
      write_type: coil
    - name: SW002
      unique_id: REL2
      slave: 1
      address: 1
      write_type: coil
    - name: SW003
      unique_id: REL3
      slave: 1
      address: 2
      write_type: coil
    - name: SW004
      unique_id: REL4
      slave: 1
      address: 3
      write_type: coil
    - name: SW005
      unique_id: REL5
      slave: 1
      address: 4
      write_type: coil
    - name: SW006
      unique_id: REL6
      slave: 1
      address: 5
      write_type: coil
    - name: SW007
      unique_id: REL7
      slave: 1
      address: 6
      write_type: coil
    - name: SW008
      unique_id: REL8
      slave: 1
      address: 7
      write_type: coil

  sensors:
    - name: T01
      unique_id: t01t
      scan_interval: 15
      slave: 201
      address: 0
      data_type: int16
      device_class: temperature
      input_type: holding
      state_class: measurement
      scale: 0.1
      offset: 0
      precision: 1
      unit_of_measurement: "°C"
    - name: T03
      unique_id: t03t
      scan_interval: 15
      slave: 203
      address: 0
      data_type: int16
      device_class: temperature
      input_type: holding
      state_class: measurement
      scale: 0.1
      offset: 0
      precision: 1
      unit_of_measurement: "°C"

    - name: r0t
      unique_id: r0t
      scan_interval: 10
      slave: 180
      address: 11
      data_type: uint16
      device_class: temperature
      input_type: holding
      state_class: measurement
      scale: 0.1
      offset: -100
      precision: 1
      unit_of_measurement: "°C"
    - name: r0dt
      unique_id: r0dt
      scan_interval: 10
      slave: 180
      address: 12
      data_type: uint16
      input_type: holding
      state_class: measurement
    - name: r0h
      unique_id: r0h
      scan_interval: 10
      slave: 180
      address: 13
      data_type: uint16
      device_class: humidity
      input_type: holding
      state_class: measurement
      scale: 0.1
      offset: 0
      precision: 1
      unit_of_measurement: "%"
    - name: r0dh
      unique_id: r0dh
      scan_interval: 10
      slave: 180
      address: 14
      data_type: uint16
      input_type: holding
      state_class: measurement
    - name: r0tst
      unique_id: r0tst
      scan_interval: 10
      slave: 180
      address: 15
      data_type: uint16
      input_type: holding
      state_class: measurement
# define REG_LED 21
# define REG_STMP 22

1 post - 1 participant

Read full topic

Openwakeword/assist stack on HA core (using M5 echo)

$
0
0

On and off I have now tried for months to get a voice stack running on HA core and just can’t seem to get there (on HAOS it’s not problem).

I have an M5 echo, and that is properly installed using the ESPHome integration. (For instance, when I push the button on the M5, the integration immediately recognizes the button push.) Then, I am running the wyoming-openwakeword docker container. Using the Wyoming integration, I can successfully connect to this container using port 10400. (At least the Wyoming integration does not complain; when I use another, incorrect port, it does.) I also set up a voice assistant where I selected openwakeword in the “Wake Word” field. (That’s the entity created by the Wyoming integration.) However, the system just does not react to the wake word. (“OK, nabu”)

The command line log of the wyoming-oww container first looks ok, but then it says this:

DEBUG:wyoming_openwakeword.handler:Client connected: 87059888107312
DEBUG:wyoming_openwakeword.handler:Sent info to client: 87059888107312
DEBUG:wyoming_openwakeword.handler:Client disconnected: 87059888107312

So it looks like somehow, it’s not connecting, and the integration never seems to receive any audio from the M5. I completely disabled my firewall for testing purposes, and I even tried running the container in privileged and host modes, but no change. What’s missing?

I have yet to set up stt stack (probably whisper). I figured that would be the next step, and I first have to get the wakeword trigger figured out. Or does the wake word not even trigger when no stt system is in place?

1 post - 1 participant

Read full topic

Understanding Script & Automation --> e.g. home presense simulation

$
0
0

Hello there,

I am pretty new to this forum and also relatively new to HomeAssistant.

Right now I am running a test system to try things out. I only have a few Shellys connected to HA.

As a practical application I want to make a home-presense simulation.

So shut on an of the light and open and close some window covers (raffstore).

Right now I have a, propably trivial, issue to get it all running.

I have created a script that that checks for the sunrise and sunset and does a random switching on the light shelly for example.

The problem is, that the script only runs once. So each day I have to restart the script.

then I have tried to make an automation to trigger the “script”. Somehow, this also doesn’t work.

I have tried several combinations of where to put the condition (after sunset & before sunrise) and also how to trigger the complete presense-simuation (vacation mode = on/off).

My questions:
What is the correct way to do this?
Do I only need one script, or several? (for several entities)
Do I need automations at all?

I know that there are several solutions out there, but I want to build my own solution as I want to learn the (correct!) process.

thank you for your comments.

Objects I have created:

  • A helper switch (vacation mode)
  • A script (random_raffstore_1) → see below
  • A automation (

Script:

alias: random_raffstore_1
sequence:
  - repeat:
      count: "999999"
      sequence:
        - device_id: 8fd2857bee9352e8ce8bbe02c774d217
          domain: cover
          entity_id: c65dcbe8dce926f03e42377621a99e1c
          type: open
        - delay:
            hours: 0
            minutes: "{{ range(20, 150)|random|int }}"
            seconds: 0
            milliseconds: 0
        - device_id: 8fd2857bee9352e8ce8bbe02c774d217
          domain: cover
          entity_id: c65dcbe8dce926f03e42377621a99e1c
          type: close
        - delay:
            hours: 0
            minutes: "{{ range(20, 150)|random|int }}"
            seconds: 0
            milliseconds: 0
mode: restart

Automation:

alias: Call_Raffstore_Script
description: ""
trigger: []
condition:
  - condition: sun
    before: sunset
    after: sunrise
action:
  - service: script.random_raffstore_1
    data: {}
mode: single

2 posts - 2 participants

Read full topic

Jukebox-card varible

$
0
0

Hello, I am using the jukebox-card integration and it works quite well. I wanted to ask for a little help on how to use variables instead of writing the URL directly? This is my code:

type: "custom:jukebox-card"
links:
  - url: http://streams.greenhost.nl:8080/jazz
    name: Concertzender Jazz
  - url: http://fs-insidejazz.fast-serv.com:8282/;stream.nsv
    name: Inside Jazz
  - url: http://stream.srg-ssr.ch/m/rsj/mp3_128
    name: Radio Swiss Jazz
  - url: http://stream.beachlatinoradio.com:8030/;?d=
    name: Beach Latino Radio
  - url: http://streams.calmradio.com/api/43/128/stream/;?d=
    name: Calm Radio
  - url: http://swr-swr1-bw.cast.addradio.de/swr/swr1/bw/mp3/128/stream.mp3
    name: SWR 1
  - url: http://94.23.252.14:8067/stream
    name: Nature Sounds
entities:
  - media_player.wuerfel_wohnzimmer

Sorry, I’ve only recently started using Home Assistant and I would like to understand a bit about how to use variables. Thank you.

1 post - 1 participant

Read full topic

Location Type Recognition - Am I at a gas station or supermarket?

$
0
0

Hi!
I would like to trigger automations based on if I am x seconds at a type of a location.
Currently I only see the possibility to set my own zones, but obviously this is no scalable solution.

  1. E.g. I am parking at a supermarket (or at least close) for x seconds, then I want to sent a notification to my phone with the shopping list. Obviously I could have some conditions (when I ticked the last time items on the list… to not trigger it always when I am going to a place close to a supermarket. Amazing would be if I can as well filter the name of the place, e.g. “Rewe” or “Walmart” as a coniditon.

  2. I am at a gas station in Germany and because of business car I need the information about how many kilometers I have driven in total (German topic…). So I want to sent a notification with these info based on my already existing Mercedes integration.

So, can I get somehow a trigger saying: Fire the trigger if I am at a certain location type (“Supermarket”, “Gas Station”) for certain time?
If it would be google maps based it would be fantastic because of the accuracy and additional information but I would take whats possible :smiley:

1 post - 1 participant

Read full topic

Run the towel heater when sufficient solar energy is available

$
0
0

Hey,

we upgraded our towel heater with a electric heating addon. I only want this to run when:

  • There is enough power available in either the battery, or when power goes to the grid when someone showers
  • There goes power to the grid and someone showered in the last two hours
  • There is enough power in the battery and someone shoered in the last two hours

However, the heating shall be turned on only once per day.

I have build this automation, which simply just doesn’t fire and I can’t figure out why. I have manually checked all paramaters and they come back as true, but the heater doesn’t turn on.
Does someone can give me a hint why?

alias: Handtücher heizen
description: ""
trigger:
  - platform: numeric_state
    entity_id:
      - sensor.klima_bad_humidity
    above: 55
    id: Duschen
  - platform: numeric_state
    entity_id:
      - sensor.solarnet_leistung_vom_netz
    for:
      hours: 0
      minutes: 0
      seconds: 0
    below: -1000
    id: Einspeisen
    enabled: true
  - platform: numeric_state
    entity_id:
      - sensor.byd_battery_box_premium_hv_ladezustand
    for:
      hours: 0
      minutes: 0
      seconds: 0
    above: 80
    id: Batterie
    enabled: true
  - platform: time
    at: "00:01:00"
    id: Reset
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - Duschen
          - condition: or
            conditions:
              - condition: numeric_state
                entity_id: sensor.solarnet_leistung_vom_netz
                below: -1000
              - condition: numeric_state
                entity_id: sensor.byd_battery_box_premium_hv_ladezustand
                above: 40
            enabled: true
          - condition: state
            entity_id: input_boolean.handtuchheizung
            state: "off"
        sequence:
          - service: switch.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: switch.handtuchheizkorper
          - delay:
              hours: 1
              minutes: 0
              seconds: 0
              milliseconds: 0
          - service: switch.turn_off
            metadata: {}
            data: {}
            target:
              entity_id: switch.handtuchheizkorper
          - service: input_boolean.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: input_boolean.handtuchheizung
        alias: Duschen
      - conditions:
          - condition: trigger
            id:
              - Einspeisen
          - condition: state
            entity_id: input_boolean.handtuchheizung
            state: "off"
          - condition: state
            entity_id: input_boolean.duschen_in_den_letzten_zwei_stunden
            state: "on"
        sequence:
          - service: switch.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: switch.handtuchheizkorper
          - delay:
              hours: 1
              minutes: 0
              seconds: 0
              milliseconds: 0
          - service: switch.turn_off
            metadata: {}
            data: {}
            target:
              entity_id: switch.handtuchheizkorper
          - service: input_boolean.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: input_boolean.handtuchheizung
        alias: Überschuss
      - conditions:
          - condition: trigger
            id:
              - Batterie
          - condition: state
            entity_id: input_boolean.handtuchheizung
            state: "off"
          - condition: state
            entity_id: input_boolean.duschen_in_den_letzten_zwei_stunden
            state: "on"
        sequence:
          - service: switch.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: switch.handtuchheizkorper
          - delay:
              hours: 1
              minutes: 0
              seconds: 0
              milliseconds: 0
          - service: switch.turn_off
            metadata: {}
            data: {}
            target:
              entity_id: switch.handtuchheizkorper
          - service: input_boolean.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: input_boolean.handtuchheizung
        alias: Volle Batterie
      - conditions:
          - condition: trigger
            id:
              - Reset
        sequence:
          - service: input_boolean.turn_off
            metadata: {}
            data: {}
            target:
              entity_id: input_boolean.handtuchheizung
mode: single

1 post - 1 participant

Read full topic

Sonos - playing from media_Iibrary

$
0
0

In 2024.5.0, the play_media functions in Sonos have been enhanced. The purpose of this article is to provide that documentation while we wait for PR to be merged into the HA docs.

Sonos Favorites support notes

The favorites sensor provides the names and media_content_id values for each of the favorites saved to My Sonos in the native Sonos app. This sensor is intended for users that need to access the favorites in a custom template. For most users, accessing favorites by using the Media Browser functionality and “Play media” script/automation action is recommended.

When calling the media_player.play_media service, the media_content_type must be set to “favorite_item_id” and the media_content_id must be set to just the key portion of the favorite item.

Example service call using the item id:

service: media_player.play_media
target:
  entity_id: media_player.sonos_speaker1
data:
  media_content_type: "favorite_item_id"
  media_content_id: "FV:2/31"

or using the Sonos playlist name:

service: media_player.play_media
target:
  entity_id: media_player.sonos_speaker1
data:
  media_content_type: playlist
  media_content_id: stevie_wonder

Sonos Music Library

If you have configured a Sonos music library; you can play music from it.

Play all albums by the Beatles.

service: media_player.play_media
target:
  entity_id: media_player.sonos
data:
  media_content_type: album
  media_content_id: A:ALBUMARTIST/Beatles

Play a specific album:

service: media_player.play_media
target:
  entity_id: media_player.sonos
data:
  media_content_type: album
  media_content_id: A:ALBUM/The Wall
  enqueue: replace

Or add a specific album by a specific artist to the queue. This is useful in case you have multiple albums with the same name.

service: media_player.play_media
target:
  entity_id: media_player.sonos      
data:
  media_content_type: album
  media_content_id: A:ALBUMARTIST/Neil Young/Greatest Hits
  enqueue: add

Play all albums by a composer.

service: media_player.play_media
target:
  entity_id: media_player.porch
data:
  media_content_type: composer
  media_content_id: A:COMPOSER/Carlos Santana
  enqueue: play

1 post - 1 participant

Read full topic


Find the GPS location of a photo (Exif ? Metadata?) exif_read_data

$
0
0

Hello everyone,

I’m looking for how to retrieve the GPS location of an image file (photograph). I would like to be able to display the link for taking a photo in a slideshow.
I can’t find anything at all about retrieving this information.
I had developed a “diaporama” plugin on Jeedom, it retrieved the GPS coordinates then queried the Google Maps API to get the City and Country.

thank
image

1 post - 1 participant

Read full topic

Govee over MQTT with Effect

$
0
0

After the last update of the addon (Govee to MQTT Bridge), the effects are now also available for the H70A1 strips in the view.

But what’s still a problem is that I see effects there, but they are somehow only effects from my other Govee strips. When I create new effects for the H70A1 strips, they somehow don’t appear in the Home Assistant.

What I’m now noticing is that when I go to the other strips, for which I already have effects in the Home Assistant and they also work, I create new effects and they don’t arrive in the Home Assistant either.

Does anyone have an idea as to what I still need to do here to ensure that the new ones arrive.

1 post - 1 participant

Read full topic

Replacing Life360

$
0
0

I am currently working to replace Life360 with Home Assistant and have made major headway. I am actually probably 85% of the way there using Node-Red. One of the last hurdles I have currently is does anyone know of a way to display a map and put sensors on the map the will dynamically move? IE The mapping feature from Life360. It’s the last piece of the puzzle but I haven’t found anything that does this yet. The front-end map will show the current location but it doesn’t update as the sensor moves and that’s the part I’m having an issue with.

Below is a front end button card I built specifically to display locational info.

1 post - 1 participant

Read full topic

How con we center Title in a ''stack-in-card''?

$
0
0

I have the following mushroom template card in a ‘‘stack-in-card’’ and I can’t find a way to center the ‘‘stack-in-card’’ title (Porte Poulailler), is there anyway to do so ?

thanks for any help on this.

image

type: custom:stack-in-card
title: Porte Poulailler
mode: vertical
cards:
  - type: custom:mushroom-template-card
    layout: vertical
    primary: >-
      {% if is_state('lock.serrure_poulailler','unlocked') and
      is_state('binary_sensor.maison_zone_27','on') %}
        Open and Unlocked
      {% elif is_state('binary_sensor.maison_zone_27','on') %}
        Door Open
      {% elif is_state('lock.serrure_poulailler','unlocked') %}
        Unlocked
      {% else %}
        Locked
      {% endif%}
    icon: >-
      {% if is_state('lock.serrure_poulailler','unlocked') and
      is_state('binary_sensor.maison_zone_27','on') %}
        mdi:door-open
      {% elif is_state('binary_sensor.maison_zone_27','on') %}
        mdi:door-open
      {% elif is_state('lock.serrure_poulailler','unlocked') %}
        mdi:lock-open
      {% else %}
        mdi:lock
      {% endif%}
    icon_color: >-
      {% if is_state('lock.serrure_poulailler','locked') and
      is_state('binary_sensor.maison_zone_27','off') %}
        green
      {% else %}
        red
      {% endif%}
    badge_icon: >-
      {% set battery_level = (states('sensor.serrure_poulailler_battery_level')
      | int / 10) | round(0) | int * 10 %} {% if battery_level == 100 %}
      mdi:battery {% elif battery_level > 0 %} mdi:battery-{{ battery_level }}
      {% else %} mdi:battery-alert-variant-outline {% endif %}
    badge_color: >-
      {% set battery_level = states('sensor.serrure_poulailler_battery_level') |
      int %}

      {% if battery_level > 90 %} green

      {% elif battery_level > 60 %} light-green

      {% elif battery_level > 50 %} lime

      {% elif battery_level > 40 %} yellow

      {% elif battery_level > 30 %} amber

      {% elif battery_level > 20 %} orange

      {% elif battery_level > 10 %} deep-orange

      {% else %} red

      {% endif %}
    tap_action:
      action: none
    secondary: >
      Dernier changement
      {{as_timestamp(states.lock.serrure_poulailler.last_changed) |
      timestamp_custom('%Y.%m.%d %H:%M:%S') }}

      {{ states('input_text.serrure_poulailler_last_status') }}

      {{ states('input_text.serrure_poulailler_last_user_name') }}
    multiline_secondary: true
    card_mod:
      style: |
        :host {
          --ha-card-border-width: 0px;
          }
  - type: grid
    square: false
    columns: 1
    cards:
      - type: custom:mushroom-lock-card
        entity: lock.serrure_poulailler
        name: Front Door
        primary_info: none
        secondary_info: none
        icon_type: none
        card_mod:
          style: |
            :host {
            --ha-card-border-width: 0px;
            }
card_mod:
  style: |
    ha-card {
      {% if is_state('lock.serrure_poulailler','locked') and
      is_state('binary_sensor.maison_zone_27','off') %}
          background: rgba(101,170,91,0.2);
      {% else %}
          background: rgba(226,84,66,0.2);
      {% endif %}
    }

1 post - 1 participant

Read full topic

Siri ask my on or off - why?

$
0
0

Hello,

I want to control my Roborock S8 maxv Ultra with HA. Now I want to use Siri to say to HomePod, for example: “Hey Siri, clean kitchen”. I use an automation for this and add it to HomeKit. Now when I give the command, Siri asks me, “Do you want to turn this on or off?”

Does anyone have any idea that Siri won’t ask me that?

1 post - 1 participant

Read full topic

HA lost some configuration after server reboot

$
0
0

Hello,

I have HA running in Docker on Ubuntu and when I reboot the server I lose some of the changes made to HA, for example, the names of entities.

If you just restart the HA, the changes will be maintained.

Has it ever happened to anyone?
Any clues?

Thank you.

Captura de ecrã 2024-05-01 150900

1 post - 1 participant

Read full topic

My light automation doesn't work

$
0
0

Hello, dear community. This is my first attempt at automation, and so far, it’s failing. I have three Tuya wifi motion sensors, two Tuya door sensors, and a Tuya light switch.

I have one automation for door sensors and one for motion sensors. I want the light to turn on whenever one of the doors opens and stay like that for 4 minutes regardless of whether the door closes afterward. The other one is for motion sensors. I want the light to keep on as long as a motion is detected on either of the three sensors and keep it on for 4 minutes before turning it off.

My problem is that sometimes(most of the time), the light doesn’t turn on even though the motion sensor sees the movement and reports it to HA. Sometimes, it doesn’t turn to either also, regardless of the fact that the HA registers the change in the sensor state.

Here’s the code for motion sensor:

alias: Garage Lights Control by Motion
description: >-
  Keep garage lights on when motion is detected and turn off after no motion for
  4 minutes.
trigger:
  - platform: state
    entity_id:
      - binary_sensor.senzor_prisutnosti_garaza_1_motion
      - binary_sensor.senzor_prisutnosti_garaza_2_motion
      - binary_sensor.senzor_prisutnosti_garaza_3_motion
    to: "on"
condition: []
action:
  - service: switch.turn_on
    target:
      entity_id: switch.garage_switch_1
    data: {}
  - wait_for_trigger:
      - platform: state
        entity_id: binary_sensor.senzor_prisutnosti_garaza_1_motion
        to: "off"
        for: "00:04:00"
      - platform: state
        entity_id: binary_sensor.senzor_prisutnosti_garaza_2_motion
        to: "off"
        for: "00:04:00"
      - platform: state
        entity_id: binary_sensor.senzor_prisutnosti_garaza_3_motion
        to: "off"
        for: "00:04:00"
    continue_on_timeout: false
  - service: switch.turn_off
    target:
      entity_id: switch.garage_switch_1
    data: {}
mode: restart

And the code for the doors:

alias: Otvaranje vrata u garaži
description: ""
trigger:
  - type: opened
    platform: device
    device_id: bbc129be15f4a821e9a7fc00da804cfa
    entity_id: c39d4fe6099929ba1d35227f2f705eca
    domain: binary_sensor
  - type: opened
    platform: device
    device_id: c6643925d5f0e5e81315e950fb62591b
    entity_id: 06e8656446a0ca0e58d3c6d721ed4106
    domain: binary_sensor
condition:
  - condition: device
    type: is_off
    device_id: 998d3dba3138453c8ccba3f1c83eba52
    entity_id: 52836c3bf856f372bb65f50b46dedd93
    domain: switch
action:
  - type: turn_on
    device_id: 998d3dba3138453c8ccba3f1c83eba52
    entity_id: 52836c3bf856f372bb65f50b46dedd93
    domain: switch
  - delay:
      hours: 0
      minutes: 2
      seconds: 0
      milliseconds: 0
  - type: turn_off
    device_id: 998d3dba3138453c8ccba3f1c83eba52
    entity_id: 52836c3bf856f372bb65f50b46dedd93
    domain: switch
mode: single

Thank you all for your time in advance.
Nik

1 post - 1 participant

Read full topic


Creating Custom Weather Forecast Entity from Sensors

$
0
0

I am trying to create a Weather Forecast entity based on a JSON file which is created from a CSV file generated by a software package WXSIM which is running locally. This package generates an hourly forecast for my location.

I have successfully created a JSON file, and have that in HA using rest, and it appears as a sensor (sensor.wxsim). I can see the values in Developer Tools.

I am now trying to create a Forecast entity, initially to just populate a weather card.

I am using a third party integration to bring in current data from my weather station, which appears to work, but the forecast bit does not.

Below is what I have so far, but it doesn’t work.
Template in Developer Tools returns the error “TypeError: ‘NoneType’ object is not iterable”

Can someone point me in the right direction please?

weather:
  - platform: template
    name: "WXSIM"
    condition_template: "{{ state_attr('sensor.wxsim', 'WX Type 1') }}"
    temperature_template: "{{ states('sensor.meteobridge_air_temperature') | float }}" 
    temperature_unit: "°C"
    humidity_template: "{{ states('sensor.meteobridge_relative_humidity') | float }}"  
    visibility_template: "{{ states('sensor.meteobridge_visibility') | float }}"
    forecast_hourly_template: |
      [
      {% for datetime_list in state_attr('sensor.wxsim', 'time') %}
        {% if loop.index > (now().hour|int)+1 %}
          {% set temperature_list = state_attr('sensor.wxsim', 'temperature')[loop.index0] %}
          {% set humidity_list = state_attr('sensor.wxsim', 'Rel.Hum.')[loop.index0] %}
          {% set precipitation_list = state_attr('sensor.wxsim', 'Tot.Prcp')[loop.index0] %}
          {% set wind_bearing_list = state_attr('sensor.wxsim', 'Wind Dir.')[loop.index0] %}
          {% set wind_speed_list = state_attr('sensor.wxsim', 'Wind Spd.')[loop.index0] %}
          {% set condition_list = state_attr('sensor.wxsim', 'WX Type 1')[loop.index0] %}
          
           "datetime": "{{datetime_list | as_datetime}}",
           "temperature": {{temperature_list | float}},
           "humidity": {{humidity_list | float}},
           "precipitation": {{precipitation_list | float}},
           "wind_bearing": {{wind_bearing_list | int}},
           "wind_speed": {{wind_speed_list | float}},
           "condition": "{{condition_list | float}},
        {% endif %}
      {% endfor %}
      ]

1 post - 1 participant

Read full topic

Combine two temp sensors, only at certain time

$
0
0

I have two temperature sensors.
I want to create a new sensor that records the value of sensor 1, except in the hours between 07:00 and 12:00. At that interval record sensor 2 instead.

How to achieve that?

3 posts - 3 participants

Read full topic

Aqara E1 Blinds voice not working with Alexa or Google

$
0
0

just wondering if anyone can help me out with Aqara E1 blinds working with voice with me using Cloudflare? Google Home does not seem to be doing it for the setup using Zigbee, any help be great on this, please. Is it going to be better to change over to Nabu Casa and get rid of Cloudflared? or is there a way to get Cloudflare into Google Home Linked services?

1 post - 1 participant

Read full topic

Use IKEA TRADFRI Motion Sensor to activate cast of dashboard on Google Nest Hub

$
0
0

Hi!

I’m lost. I have a script that was doing well to cast a dashboard on my google nest hub.



alias: Cast Dashboard Test
sequence:
  - service: cast.show_lovelace_view
    metadata: {}
    data:
      entity_id: media_player.nest_fr
      dashboard_path: lovelace
      view_path: test
mode: queued
icon: mdi:tablet-dashboard

The issue is that the dashboard disappears after a while. So I browse the forum and found people using motion sensor to trigger the script… It looks fine and worked fine for me for the first execution.

alias: DashDisplay
description: ""
trigger:
  - type: motion
    platform: device
    device_id: e20dfb5853dd6986d97784911e5cc8d8
    entity_id: 1fed900387b29a3390669bba050ae338
    domain: binary_sensor
condition: []
action:
  - service: script.cast_dashboard_test
    data: {}
mode: single

But then it stopped… It seems that when the automation kick in it does not only put the dashboard on it turn it off also on the next motion detection…

Now I cannot even execute the script alone… It runs but nothing happen…

Anyone to point me on what I did wrong?

1 post - 1 participant

Read full topic

Two ethernet interfaces

$
0
0

Hi,

I have two ethernet interfaces (virtualized in Proxmox). How do I tell Matter server, which interface should it use?

1 post - 1 participant

Read full topic

Viewing all 108763 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>