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

Toggling Between HVAC_MODE in the Floorplan.yaml

$
0
0

@Geffrey wrote:

I’ve been trying to figure out how to switch between hvac modes when pressing one icon on the floorplan. ‘Heat’ and ‘off’. I’ve been Googling and trying solution for several hours now.

This is what I have so far:

in floorplan.yaml

  - name: Heating
          entities:
             -  climate.living_room
          text_template: '${entity.attributes.current_temperature ? Math.round(entity.attributes.current_temperature) : "99"}°'
          states:
            - state: 'heat'
              class: 'heating-on'
            - state: 'off'
              class: 'heating-off'
          action:
            domain: climate
            service: set_hvac_mode
            data_template:
              hvac_mode: "
              {% if is_state('entity.hvac_mode'), 'off' %}
                  heat
                {% else %} 
                  off
                {%endif %}"

I have no clue what I am actually doing. Could somebody guide me in the right direction? I just need to be able to toggle between two states. Heating and not.

This is what the floorplan section of HASSIO said when I click the heating icon, by the way:

Thank you in advance!
Geffrey

Posts: 1

Participants: 1

Read full topic


Are template lights still a thing?

$
0
0

@Lyshco wrote:

HA 0.101.2 running on RP3+

First post. Set up HA a couple of weeks ago and very impressed. May have overestimated my technical competence but have managed to figure out everything I needed to. Until today.

Came across the idea of a template light for Alexa integration and thought “I want one of those”. I copied the code direct from https://www.home-assistant.io/integrations/light.template/

# Example configuration.yaml entry
light:
  - platform: template
    lights:
      theater_lights:
        friendly_name: "Theater Lights"
        level_template: "{{ sensor.theater_brightness.attributes.lux|int }}"
        value_template: "{{ sensor.theater_brightness.attributes.lux|int > 0 }}"
        turn_on:
          service: script.theater_lights_on
        turn_off:
          service: script.theater_lights_off
        set_level:
          service: script.theater_lights_level
          data_template:
            brightness: "{{ brightness }}"  

but I just keep getting the message:

Invalid config for [sensor.template]: [lights] is an invalid option for [sensor.template]. Check: sensor.template->lights.

which seems to suggest I can’t create the light this way anymore. Or am I being a fool? (most likely)

If anyone can point out the nature of my foolishness I’d be grateful. Ta

Posts: 11

Participants: 6

Read full topic

Sonoff Mini auto discovery

$
0
0

@Nicko1 wrote:

Hi everyone
I’m new HA and I’ve had problems with the Mqtt Broker addon auto discovery feature with a Sonoff Mini device.
I found a lot of heated discussions about the mqtt integration in HA but nothing on here about my solution… if I’m wrong please let know…
The sonoff Mini would not show up in mqtt broker integration until I added the correct sonoff mini template https://blakadder.github.io/templates/sonoff_mini.html
So the setoption19=1 is important but its also crucial that the device flashed with tasmota has the correct template that matches the device.
Is there any high ranking members that could add the info to the Hassio Mqtt Integration documentation, would save some time for new members.
Thanks to all for contributing to this community
Nicko

Posts: 1

Participants: 1

Read full topic

Scene problems in 101

$
0
0

@ATWindsor wrote:

The scenes has been changed in 101, it is listed as a breaking change, but to be honest I didn’t find it to well explained, so I am unsure why i have problems, but i suspect it is because of input select. For instance this scene:

- name: do_vanlig
  entities:
    light.do_ltak:
      state: true
      brightness_pct: 50
    input_select.dolys:
     option: 50

I get this error (among a lot of others…)

Invalid config for [scene]: State for input_select.dolys should be a string for dictionary value @ data[‘states’][0][‘entities’]. Got None. (See /config/configuration.yaml, line 89). Please check the docs at https://home-assistant.io/integrations/scene/

Posts: 2

Participants: 2

Read full topic

Action template

$
0
0

@matteos1 wrote:

i have this automation but not work
the switch of input.boolean stay always on

- id: luci_spente_cucina
  alias: 'luci spente cucina'
  trigger:
  - platform: state
    entity_id: switch.plug_158d000163fbb8 #Luci Mensola
    from: 'on'
    to: 'off'
  - platform: state
    entity_id: switch.plug_158d00010ac8ad #Luci Centrali
    from: 'on'
    to: 'off'
  - platform: state
    entity_id: switch.netatmo_led_cucina #Luci led cucina
    from: 'on'
    to: 'off'
  - platform: state
    entity_id: switch.plug_158d0002366d21 #Coppa vapore
    from: 'on'
    to: 'off'
  action:
  - service_template: >
           {%- if is_state('input_boolean.luci_mensola', 'off') and is_state('input_boolean.luci_centrali', 'off') and is_state('input_boolean.coppa_vapore', 'off' ) and is_state('input_boolean.luci_led_cucina', 'off' )-%}
             input_boolean.turn_on
           {%- else -%}
             input_boolean.turn_off
           {%- endif %}
    entity_id: input_boolean.luci_spente_cucina

someone that could help me?

Posts: 6

Participants: 3

Read full topic

Automation wont work

$
0
0

@Prater wrote:

Hello people,

I am new here and try to make a automation work on hassio. On motion i want to turn on a light but i dont know why it wil not turn on.
This is in my automations.yaml and i add automations.yaml in the config file.

- id: beweging licht aan
  alias: 'licht aan' 
  trigger: 
    platform: state
    entity_id: binary_sensor.woonkamer_beweging
    from: 'off'
    to: 'on'
  action:
     service: light.turn_on
     entity_id: light.bf19b8bb789510a78eue48    

After 2 days i almost beginning to pull out some hairs.

Thx

Posts: 7

Participants: 3

Read full topic

Auto-entities filter by attribute not working

$
0
0

@UN4 wrote:

Hello, I am new to home assistant and I am trying to setup an automatic card that shows different media players based on their status. For this I use auto-entities custom card. The problem I ran into is that for fireTV in developer tools -> States I see the following attributes:

app_id: org.xbmc.kodi
app_name: Kodi
source: org.xbmc.kodi
adb_response: null
friendly_name: Fire TV
supported_features: 22961

However when I try to use these attributes to filter my lovelace card with auto-entities it does not seem to work:

card:
  show_header_toggle: false
  type: entities
filter:
  include:
    - domain: media_player
      entity_id: '*kodi'
      options:
        artwork: cover
        artwork_border: true
        hide:
          icon: true
        type: 'custom:mini-media-player'
      state: /playing|paused|idle/
    - domain: media_player
      entity_id: '*fire_tv'
      options:
        artwork_border: false
        group: true
        hide:
          icon: true
          power: true
          progress: true
          source: true
          volume: true
        type: 'custom:mini-media-player'
  exclude:
    - domain: media_player
      entity_id: '*fire_tv'
      attributes:
        app_id: org.xbmc.kodi
show_empty: false
type: 'custom:auto-entities'

However when kodi is open on firetv i see two media players [kodi and firetv] in my card, fire tv is not filtered out.

I tried to debug java script in chrome and it appears that object media_player.fire_tv does not even have app_id attribute even though it is displayed in developer tools.

image

Is there a way to force the attributes I want to be available for auto-entities to see?

Posts: 1

Participants: 1

Read full topic

Turn on light for X minutes, but not off when manually turned on

$
0
0

@Stooovie wrote:

Hi, I’m using Aqara motion sensor on our nappy change table (sorry, I’m not English native).

The idea was to automatically turn on lamp for a couple of minutes when it’s dark. I have the automation for ON, but what I’m looking for is a kind of “run for 3 minutes” action parameter.

I did have the separate automation to turn the switch to “off” when no motion was detected BUT that had the unfortunate effect of also turning off the light when It was manually turned it on before. So this approach doesn’t work in this case.

Any tips?

Posts: 7

Participants: 3

Read full topic


Architectural question regarding execution of python script

$
0
0

@dm82m wrote:

hey guys,

I want to execute a python script that checks the forecast for the next days solarenergy and depending on that stops or starts the heating for warm water with the gas heating.

First guess was to put it into python_scripts and just execute it with an automation every 24hours. But that isnt working as there is only a limited python sandbox environment for these scripts with very less functionalities (so no imports, …).

Next I added the script as shell_command and executing within an automation. Its working but feels not perfect.

Are there any other (better) solutions out there?

Best,
Dirk

Posts: 1

Participants: 1

Read full topic

Can I completely remove the http section from configuration.yaml?

$
0
0

@Emphyrio wrote:

I stil have this http configuration in my configuration.yaml:

#http (for Let's Encrypt on Duckdns.org)
http:
  server_port: 99999
  base_url: https://xxxxxx.duckdns.org:99999
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  ip_ban_enabled: false
  login_attempts_threshold: 20

I’m planning to move to 100.3 soon, where api password is deprecated. Also, I am now using Nabu Casa for remote access, so I believe I don’t need DuckDNS anymore. My Hassio add-ons all support Ingress.

Can I simply remove the http section entirely? Or do I still need certain lines for some purpose?

Posts: 1

Participants: 1

Read full topic

Ability to use color_temp in Light Profiles

$
0
0

@stephen wrote:

Hi All,

I’ve recently setup default light settings using the light_profiles.csv as described in https://www.home-assistant.io/integrations/light/. This is a huge help as we use scenes quite a bit and the lights would default to whatever we had used last, which might not be ideal.

We have a mix of Hue Ambiance and Hue Color bulbs. I can set the default xy color for all the Hue Color bulbs via the light_profiles.csv, which works. However, it is my understanding that the Hue Ambiance only support the color_temp and my efforts to set the color temp via the xy in the light_profile has failed.

Curious if anyone knows if it is possible to use color_temp in the light_profiles?

Thanks for any help!

Posts: 1

Participants: 1

Read full topic

Cast to old Android tablet? (Is there a way to turn tablet into Cast Receiver?)

$
0
0

@jschwalbe wrote:

With the new casting interface earlier this year, I thought it would be great to convert an old tablet into a casting destination. But I’ve come up blank. Does anyone know how to do this? Is it possible without rooting?

Posts: 1

Participants: 1

Read full topic

Template Switch - On/Off Flickering Behavior

$
0
0

@TheNr1Guest wrote:

Hi all,

I have a shutter that I control via a template switch. When turned on, the switch sets the shutter to a fixed position. Then the switch is turned off, the shutter opens. This works fine, but in the UI the switch behavior could be improved.

When the shutter is fully open and I toggle the switch, the following behavior is observed:

  • Switch turns on
  • A few seconds pass
  • Switch turns off
  • Many seconds pass
  • Switch turns on

I use the Somfy API to control my shutter and this causes a delay in cover status updates (since it’s not a local API). And that makes the switch behavior noticeable. Is there a way to fix this?

Posts: 2

Participants: 2

Read full topic

Roomba issue

$
0
0

@GiulioG wrote:

Roomba has very verbose logs, almost one row every second

i solved this with

logger:
  default: info
  logs:
    roomba: warning

but there is another problem

Roomba stay always connected h24 and the Clean green led is always on
there is a way solve this? or a workaround or a way to dinamicallu disable it when not used?

this is my code

vacuum:
  - platform: 'roomba'
    host: !secret vacuum_host
    username: !secret vacuum_username
    password: !secret vacuum_password

Thanks

Giulio

Posts: 1

Participants: 1

Read full topic

Travel time with “waze” and “here”

$
0
0

@GiulioG wrote:

I’m using “waze” and “here”
If i put in the config the option

name:

they stop work, without the option

name:

they work but when configured more than one they are not correctly identified
and sometimes the time is excenged beetwen one to another

There is someone with these issue?

There is a way to resolve them?

Thanks

Giulio

Posts: 11

Participants: 2

Read full topic


Bticino termostato x8000

Is it possible to determine within HA the IP address of the browser viewing it?

$
0
0

@Dan_Bowkley wrote:

I’d like to set up a page with a bunch of cameras on it. Of course, they’re all 1080p so streaming that outside of the home LAN would be slightly ridiculous. Each camera has several RTSP streams of different resolutions. So what I’d like to do is have HA somehow determine whether the browser viewing that page is on the local LAN or outside it, and then via templating have the page feed either the low-res or high-res streams appropriately. Is there any way to implement this? I guess I could just have a low-res and a high-res tab and let the user (me) choose whichever I want, but I’d kinda like to automate this if possible.

I guess something like

camera: > 
  {% if is_state('person.dan' , 'home') %}
    camera.high-res1 
  {% else %} 
    camera.low-res1
  {% endif %}

would mostly work, but I’d vastly prefer to do it on a per browser basis.

Any ideas?

Posts: 1

Participants: 1

Read full topic

Automation value_template match 2 conditions?

$
0
0

@kroonen wrote:

Hi.

I will do an automation wit 2 conditions from zigbee2mqtt
 zigbee2mqtt:info 11/9/2019, 6:50:10 PM MQTT publish: topic 'zigbee2mqtt/remote', payload '{"linkquality":39,"last_seen":"2019-11-09T17:50:10.385Z","action":"on","action_group":146}'

I have this

- alias: "remote lamp staand on"
  trigger:
   - platform: mqtt
     topic: 'zigbee2mqtt/remote'
  condition:
     condition: template
     value_template: '{{ "on" == trigger.payload_json.action }}'
  action:
     service: light.turn_on
     data:
       entity_id:
         - light.staandelamp

How can I make an and statement?

 value_template: '{{ "on" == trigger.payload_json.action }}'  and '{{ "146" == trigger.payload_json.action_group }}'

Posts: 3

Participants: 3

Read full topic

What sun integration events are available

$
0
0

@baz123 wrote:


Are the events related to the sun integration, documented anywhere? I know of sunrise and sunset which I presume are related to next_rising and next_setting.

Is there a dawn and dusk - it seems not but I thought I’d check :grin:

I think the next_dawn time is related to the start of civil twilight. Is this correct?

Posts: 1

Participants: 1

Read full topic

Configuring hold amplifier as media player

$
0
0

@claudiosala80 wrote:

Hello all

I have an old amplifier and I want reproduce Spotify and, if there is a way to create an FM radio in home assistant, the FM radio

I can connect it to the raspberry 3.5mm jack or it is connected as bluetooth device and it is one of the possible output in Google Assistant

Is there a way to define it?
Is there a way also to control the volume via broadlink?

Thanks all
Claudio

Posts: 1

Participants: 1

Read full topic

Viewing all 109130 articles
Browse latest View live


Latest Images

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