I’m looking for a way to automate some stair lights. I’ll have motion detectors in the stairway, I’d like the stair lights to turn on when motion is detected and off when motion stops. BUT, if the stair lights are turned on using the wall switch I’d like them to stay on regardless of the motion detectors turning on/off.

I haven’t picked a smart switch yet, but would prefer a switch with ESPhome, I’d consider Zwave if needed.

Is there someway to differentiate in HA when a wall switch his used to turn the light on? If so, I figure I could set a template binary sensor to “on” when the wall switch is used and set a condition that the template sensor needs to be “off” for the motion activated lights.

1 post - 1 participant

Read full topic

I just installed a new ceiling fan and inovelli red series fan/light dimmer, the physical switch works great and I was able to add the node to home assistant, however, when I go to turn on the light it also activates the ceiling fan and there doesn’t seem to be a way to control the two independently of each other. I’ve gone through my entities and there’s only the single entry for the light. Is there a way to control the two individually?

1 post - 1 participant

Read full topic

Hi,

I would like to configure the recorder in order to keep my snapshots rather small. I found some examples of what people exclude and include in their recorder but I could not find a general tip on what I should or should not exclude in order to keep the system functioning. Is there some kind of general guideline I can apply?

Basically I only use the DB for some temperature sensor, but I am really just interested in the last 24h or so. The rest would not need to be stored as far as I am concerned, but I don’t know how or if excluding entire domains would break scripts, automations etc or if I could as well just exclude basically everything.

Thanks in advance!

1 post - 1 participant

Read full topic

Hello together,

I created this automation:

alias: Aussen u Weihna aus
description: Aussen- und Weihnachtsbeleuchtung aussschalten
trigger:
  - at: '23:00'
    platform: time
  - platform: numeric_state
    entity_id: sensor.helligkeit_2
    above: '30'
condition: []
action:
  - device_id: 63de5b12639347dd9701de211f924f45
    domain: light
    entity_id: light.wled_bieber_master
    type: turn_off
  - type: turn_off
    device_id: b2a32e84ecb9efaa1dcf6a91284766c4
    entity_id: light.wled_gruenwichtel
    domain: light
  - type: turn_off
    device_id: 03d7308c00ef7471e0b72653a465f507
    entity_id: light.wledfcblampe
    domain: light
  - type: turn_off
    device_id: 9fd74c3622a94fa997af527fdc6b8b87
    entity_id: switch.shelly_shsw_1_1d9ff5
    domain: switch
  - service: switch.turn_off
    data: {}
    entity_id: switch.balkon
  - service: notify.mobile_app_oneplus_a6003
    data:
      title: Aussen- u-Weihnachtsbeleuchtung ausgeschaltet
      message: >-
        Die Aussen- und Weihnachstsbeleuchtung wurde durch
        {{trigger.to_state.attributes.friendly_name}} ausgeschaltet
      data:
        color: green
        ledcolor: green
        sticky: 'true'
mode: single

The automation is working fine, but I have some problems with my notification.
If the automation is triggered by sensor.helligkeit_2 I get the notification, but if it is triggered by time I dont get it.

How can I change this behavior?

Best regards,
Stefan

1 post - 1 participant

Read full topic

Hello, I have this rather simple automation that I am able to trigger, but the action is failing:

- id: '1606285490337'
  alias: Test Notification
  description: ''
  trigger:
  - platform: state
    entity_id: switch.upstairs_hallway_light
    to: 'on'
    for: 00:00:05
  condition: []
  action:
  - service: persistent_notification.create
    data:
      message: 'Test message'
  mode: single

The log says:

2020-11-25 01:56:00 ERROR (MainThread) [homeassistant.components.automation.test_notification] Test Notification: Error executing script. Invalid data for call_service at pos 1: extra keys not allowed @ data['entity_id']
2020-11-25 01:56:00 ERROR (MainThread) [homeassistant.components.automation.test_notification] While executing automation automation.test_notification
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 433, in async_trigger
    await self.action_script.async_run(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1010, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 245, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 253, in _async_step
    await getattr(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 460, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1405, in async_call
    processed_data = handler.schema(service_data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: extra keys not allowed @ data['entity_id']

The UI originally generated an irrelevant entity_id under action which I have since removed. But the log is still referring to entity_id. What am I doing wrong?

Thanks.

1 post - 1 participant

Read full topic

Hello everybody,

I have installed a qubino din dimmer in my z-wave network.
The dimmer is working perfectly when switched from the wall switches and when using HA frontend.
My problem is that I can’t distinguish between switching on by the wall switch and switching on between a motion sensor.

I got an info from qubino support showing a difference in a hex dump.

Switched by wall switch (hardware)

switched by HA (software)

How can I see this in HA, either as event or a state change???

Thanks for helping out.
Ralf

1 post - 1 participant

Read full topic

I have a strange problem I can’t solve, I hope that someone here knows a solution.

I’m using Home assistant on a Raspberry pi.
And a sonoff RF-Bridge flashed with Tasmota.
I have two RF devices assigned to button 1 and button 2
Using the UI of Tasmota pressing the buttons 1 and 2, do what you expect. On/Off when pressing 1 and ON/Off when pressing 2

I also have added code to home assistant to be able to give voice commands by Google Home.

Device 1 does work as expected. When you say ON it turns on, when saying OFF it turns off
The problem I have is with device 2. When I say ON nothing happens (only google home says “I turn kitchen on”), when I say kitchen OFF the light turns on, when I say again Kitchen OFF it turns off !?
Both devices have the exact same code, except the name and button number of course.

“Above commands are given in Dutch, but for the forum I wrote them in English”

Please see below the used code in Home Assistant.

/config/switch.yaml

#CandleLED
  - platform: mqtt
    unique_id: Kaars
    name: 'Candle'
    command_topic: "cmnd/RF_Bridge/RfKey1"
#KitchenLED
  - platform: mqtt
    unique_id: Keuken
    name: 'keuken_led'
    command_topic: "cmnd/RF_Bridge/RfKey2"

/config/configuration.yaml

####################################################
#            Google HOME / Assistant                                               #
####################################################   
google_assistant:
  project_id: home-assistant-*****
 #12032020 uitgezet: api_key: ******************************************
  service_account: !include Home Assistant-***************************
  report_state: true
  expose_by_default: false
  exposed_domains:
    - script
    - light
    - switch
  entity_config:
    switch.candle:
      name: Kaars
      expose: true
    switch.keuken_led:
      name: Keuken
      expose: true

1 post - 1 participant

Read full topic

Prerequisites:

custom:browser-mod
custom:vertical-stack-in-card
custom:thermostat-dark-card
custom:button-card

Create (change names as required throughout):

sensors:
  - platform: template
    sensors:
    
      living_room_hvac_mode:
        value_template: >
          {{ states('climate.living_room') }}

      living_room_preset_mode:
        value_template: >
          {{ state_attr('climate.living_room','preset_mode') }}

#Celsius:
      living_room_eco_temp:
        friendly_name: Living Room ECO Temperature Range
        value_template: >
          {% if 19.5 < state_attr('climate.living_room', 'temperature')|round(1,"half") < 28 %}
            none
          {% else %}
            eco
          {% endif %}

##Fahrenheit:
#      living_room_eco_temp:
#        friendly_name: Living Room ECO Temperature Range
#        value_template: >
#          {% if 67 < state_attr('climate.living_room', 'temperature')|round(1,"half") < 82 %}
#            none
#          {% else %}
#            eco
#          {% endif %}
#          
#      living_room_setpoint:
#        value_template: >
#          {{ state_attr('climate.living_room', 'temperature') }}

Lovelace Raw Config:

## Your Climate page
  - title: Environment
    path: environment
    icon: 'hass:thermostat'
    theme: ''
    badges: []
Add:
    popup_cards:
      sensor.living_room_hvac_mode:
        title: ' '
        card:
          style: |
            .card-header {
              line-height: 20px;
            }
            .card-header .name {
              font-size: 14px;
              color: gray;
            }
          type: entities
          show_header_toggle: false
          title: 'Set thermostat to:'
          entities:

## Auto (if available)
#            - type: button
#              icon: 'mdi:hvac'
#              action_name: Auto
#              name: ' '
#              tap_action:
#                action: call-service
#                service: climate.set_hvac_mode
#                service_data:
#                  entity_id: climate.living_room
#                  hvac_mode: auto

# Heat
            - type: button
              icon: 'mdi:fire'
              action_name: Heat
              name: ' '
              tap_action:
                action: call-service
                service: climate.set_hvac_mode
                service_data:
                  entity_id: climate.living_room
                  hvac_mode: heat

## Cool (if available)
#            - type: button
#              icon: 'mdi:snowflake'
#              action_name: Cool
#              name: ' '
#              tap_action:
#                action: call-service
#                service: climate.set_hvac_mode
#                service_data:
#                  entity_id: climate.living_room
#                  hvac_mode: cool

# Off
            - type: button
              action_name: 'Off'
              name: ' '
              tap_action:
                action: call-service
                service: climate.set_hvac_mode
                service_data:
                  entity_id: climate.living_room
                  hvac_mode: 'off'
      sensor.living_room_preset_mode:
        title: ' '
        card:
          style: |
            .card-header {
              line-height: 20px;
              font-size: 14px;
              white-space: normal;
              text-align: center;
            }
            .card-header .name {
              font-size: 14px;
              color: gray;
              white-space: normal !important;
              text-align: center;
            }
          type: entities
          show_header_toggle: false
          title: >-
            Save energy by using Eco Temperatures when no one's home. Or turn
            them on manually any time.
          entities:
            - type: button
              icon: 'mdi:leaf'
              action_name: START ECO
              name: ' '
              tap_action:
                action: call-service
                service: climate.set_preset_mode
                service_data:
                  entity_id: climate.living_room
                  hvac_mode: eco
            - type: button
              icon: 'mdi:leaf-off'
              action_name: STOP ECO
              name: ' '
              tap_action:
                action: call-service
                service: climate.set_preset_mode
                service_data:
                  entity_id: climate.living_room
                  hvac_mode: none

New card:

type: 'custom:vertical-stack-in-card'
cards:
  - type: 'custom:thermostat-dark-card'
    name: Living Room (new)
    entity: climate.living_room
    chevron_size: 50
    step: 0.1
    pending: '1'
    idle_zone: '2'
    hvac:
      states:
        'off': 'off'
        cooling: cool
        heating: heat
    attribute: hvac_action
    away:
      sensor:
        sensor: sensor.living_room_eco_temp
    style: |
      ha-card {
        {% if is_state_attr('climate.living_room', 'hvac_action', 'heating') %}
          background: #EB6D00;
          border-bottom: 1pt solid #E65E00;
        {% else %}
          {% if is_state_attr('climate.living_room', 'hvac_action', 'cooling') %}
            background: #0055FF ; 
            border-bottom: 1pt solid #00008B;
          {% else %}
            background: #373F48 ;
            border-bottom: 1pt solid #2b333a;
          {% endif %}
        {% endif %}
        box-shadow: 0 0 20px;
       }
       .dial_title {
         color: white !important;
       }
  - type: entities
    entities:
      - entity: sensor.living_room_humidity
        name: Inside Humidity
    style: |
      ha-card {
        color: white;
        {% if is_state_attr('climate.living_room', 'hvac_action', 'heating') %}
          background: #EB6D00;
          border-bottom: 1pt solid #E65E00;
        {% else %}
          {% if is_state_attr('climate.living_room', 'hvac_action', 'cooling') %}
            background: #0055FF ; 
            border-bottom: 1pt solid #00008B;
          {% else %}
            background: #373F48 ;
            border-bottom: 1pt solid #2b333a;
          {% endif %}
        {% endif %}
        box-shadow: 0 0 10px;
        font-size: 1.0rem;
       }
       "#states.card-content":
         $: |
           state-badge {
             display: none;
           }
  - type: entities
    entities:
      - entity: sensor.openweathermap_temperature
        name: Outside Temp.
    style: |
      ha-card {
        color: white;
        {% if is_state_attr('climate.living_room', 'hvac_action', 'heating') %}
          background: #EB6D00;
          border-bottom: 1pt solid #E65E00;
        {% else %}
          {% if is_state_attr('climate.living_room', 'hvac_action', 'cooling') %}
            background: #0055FF ; 
            border-bottom: 1pt solid #00008B;
          {% else %}
            background: #373F48 ;
            border-bottom: 1pt solid #2b333a;
          {% endif %}
        {% endif %}
        box-shadow: 0 0 10px;
        font-size: 1.0rem;
       }
  - type: horizontal-stack
    cards:
      - type: 'custom:button-card'
        entity: sensor.living_room_hvac_mode
        name: MODE
        show_name: true
        tap_action:
          action: more-info
        color_type: icon
        state:
          - operator: template
            value: |
              [[[ return states['climate.living_room'].state === 'off' ]]]
            icon: 'mdi:none'
            color: white
          - operator: template
            value: |
              [[[ return states['climate.living_room'].state === 'heat' ]]]
            icon: 'mdi:none'
            color: 'rgb(239, 140, 0)'
          - operator: template
            value: |
              [[[ return states['climate.living_room'].state === 'cool' ]]]
            color: blue
            icon: 'mdi:none'
        show_state: false
        style: |
          ha-card {
            font-size: 85% !important;
            color: white;
            background:
            {% if is_state_attr('climate.living_room', 'hvac_action', 'heating') %}
              #EB6D00 ;
            {% else %}
              {% if is_state_attr('climate.living_room', 'hvac_action', 'cooling') %}
                #0055FF ; 
              {% else %}
                #373F48;
              {% endif %}
            {% endif %}
            box-shadow: none;
          }
          ha-icon {
            background-image: url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' width='24.1' height='24.1' viewBox='-282.6 655.7 611.9 511.8' fill='%23FFF'%3E%3Cpath d='M235.4 1039.5c-38.3 30.7-76.8 46.1-117.7 46.1-51.2 0-99.7-23-153.5-74.2-61.4-58.8-127.9-110-194.5-110-12.8 0-25.6 2.6-38.4 5.1-2.3.7-5.7 1-7.6-2.6-1.7-3.2 0-5.1 2.6-7.6 38.3-30.7 76.8-46.1 117.7-46.1 51.2 0 99.7 23 153.5 74.2 61.3 58.8 127.8 110 194.4 110 12.8 0 25.6-2.6 38.3-5.1 2.8-.5 5.9-1.2 7.6 2.6 1.6 3.3.1 5.1-2.4 7.6zM-194.5 991c38.3 0 76.8 18 115.2 56.3 46.1 43.5 97.2 84.4 145.9 84.4 10.2 0 20.5-2.6 28.2-5.1 2.6-.7 4.6.1 5.7 2.1 1.7 3.1-.6 5.6-.6 5.6-28.2 23-58.8 33.2-87 33.2-38.3 0-76.8-18-115.2-56.3-46.1-43.5-97.2-84.4-145.9-84.4-10.2 0-20.4 2.9-28.2 5.1-2.3.7-4.2.7-5.7-2.3-1.5-2.8.6-5.3.6-5.3 28.1-20.6 56.3-33.3 87-33.3zM327.4 799c-28.2 23-58.8 33.2-87 33.2-38.3 0-76.8-18-115.2-56.3-46-43.4-97.1-84.4-145.8-84.4-10.2 0-20.5 2.6-28.2 5.1-2.2.7-4.3.2-5.6-1.8-2.2-3.5.5-5.9.5-5.9 28.2-23 58.8-33.2 87-33.2 38.3 0 76.8 18 115.2 56.3 46.1 43.5 97.2 84.4 145.9 84.4 10.2 0 20.5-2.6 28.2-5.1 2.1-.8 4.3-1.1 5.7.7 1.5 2.1 1.9 4.5-.7 7zM81.9 811.9c61.4 58.8 127.9 110 194.5 110 12.8 0 25.6-2.6 38.3-5.1 2.6-.7 5.7-1.2 7.6 2.6 1.6 3.1 0 5.1-2.6 7.6-38.4 30.7-76.8 46-117.7 46-51.2 0-99.7-23-153.5-74.2-61.4-58.8-127.9-110-194.5-110-12.8 0-25.6 2.6-38.3 5.1-2.6.7-5.7.7-7.6-2.6-1.8-3.1 0-5.1 2.6-7.6 38.3-30.7 76.8-46.1 117.7-46.1 51.1 0 99.7 23.1 153.5 74.3z'/%3E%3C/svg%3E");
            background-position: 25%;
            background-position-x: 50%;
            background-position-y: center;
            background-repeat: no-repeat;
            height: 44px;
            margin: 0 
            auto 3px;
            width: 26px;            
            }
      - type: 'custom:button-card'
        entity: sensor.living_room_preset_mode
        name: ECO
        label: ECO
        tap_action:
          action: more-info
        color_type: icon
        color: green
        icon: 'mdi:none'
        state:
          - operator: template
            value: >
              [[[ return states['climate.living_room'].attributes.preset_mode ==
              'none' ]]]
            icon: 'mdi:none'
            color: white
        show_state: false
        show_name: true
        style: |
          ha-card {
            font-size: 85% !important;
            color: white;
            background:
            {% if is_state_attr('climate.living_room', 'hvac_action', 'heating') %}
              #EB6D00 !important;
            {% else %}
              {% if is_state_attr('climate.living_room', 'hvac_action', 'cooling') %}
                #0055FF !important; 
              {% else %}
                #373F48 !important;
              {% endif %}
            {% endif %}
            box-shadow: none;
          }  
          ha-icon { 
            background-image: url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' width='24.1' height='24.1' viewBox='0 0 26 24' fill='%23FFF'%3E%3Cpath class='st0' d='M.8 20.7c6.3 4.5 13.1 4.7 19-1.7 6.1-6.5 6.4-14.5 6.2-19-3.3 4-9.5 2.2-18.2 5C1 7.2.1 15.3 0 18.7c1.6-1.7 4.6-4.5 8.5-5.9 6.2-2.3 8.9-2.3 12.6-5.1-2.3 2.6-5.3 4.1-11.1 6.2-4.2 1.5-7.9 5.3-9.2 6.8z'/%3E%3C/svg%3E"); 
            background-position: 25%;
            background-position-x: 50%;
            background-position-y: center;
            background-repeat: no-repeat;
            height: 44px;
            margin: 0 
            auto 3px;
            width: 26px;            
          }
      - type: 'custom:button-card'
        entity: climate.living_room
        name: SCHEDULE
        action: url
        navigation_path: 'https://home.nest.com'
        color_type: card
        icon: none
        show_state: false
        show_name: true
        style: |
          ha-card {
            font-size: 85% !important;
            color: white !important;
            background:
            {% if is_state_attr('climate.living_room', 'hvac_action', 'heating') %}
              #EB6D00 !important;
            {% else %}
              {% if is_state_attr('climate.living_room', 'hvac_action', 'cooling') %}
                #0055FF !important; 
              {% else %}
                #373F48 !important;
              {% endif %}
            {% endif %}
            box-shadow: none;
          }   ha-icon { 
            background-image: url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' width='22' height='24.1' fill='%23FFF'%3E%3Cpath d='M17 24.5H5c-2.8 0-5-2.2-5-5v-12c0-2 1.2-3.8 3-4.6v1c0 1.4 1.1 2.6 2.5 2.6S8 5.3 8 3.9V2.5h6v1.4c0 1.4 1.1 2.6 2.5 2.6S19 5.3 19 3.9v-1c1.8.8 3 2.5 3 4.6v12c0 2.8-2.2 5-5 5zm-1.7-7.9l-3.8-2.2V9c0-.6-.4-1-1-1s-1 .4-1 1V15.6s0 .1.1.1l.1.1.1.1s.1 0 .1.1l4.3 2.5c.5.3 1.1.1 1.4-.4.4-.6.2-1.2-.3-1.5zM16.5 5c-.6 0-1-.4-1-1V1c0-.6.4-1 1-1s1 .4 1 1v3c0 .6-.4 1-1 1zm-11 0c-.6 0-1-.4-1-1V1c0-.6.4-1 1-1s1 .4 1 1v3c0 .6-.4 1-1 1z'/%3E%3C/svg%3E"); 
            background-position: 25%;
            background-position-x: 50%;
            background-position-y: center;
            background-repeat: no-repeat;
            height: 44px;
            margin: 0 
            auto 3px;
            width: 26px;            
          }
      - type: 'custom:button-card'
        entity: climate.living_room
        name: HISTORY
        action: url
        navigation_path: 'https://home.nest.com'
        color_type: card
        icon: 'mdi:none'
        show_state: false
        show_name: true
        style: |
          ha-card {
            font-size: 80% !important;
            color: white !important;
            background:
            {% if is_state_attr('climate.living_room', 'hvac_action', 'heating') %}
              #EB6D00 !important;
            {% else %}
              {% if is_state_attr('climate.living_room', 'hvac_action', 'cooling') %}
                #0055FF !important; 
              {% else %}
                #373F48 !important;
              {% endif %}
            {% endif %}
            box-shadow: none;
          }  ha-icon {
            background-image: url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' width='24' height='24' viewBox='0 0 26 24' fill='%23FFF' stroke='%23FFF'%3E%3Cpath stroke-width='.05' d='M12.5 24c-6.6 0-12-5.4-12-12s5.4-12 12-12c.6 0 1 .4 1 1s-.4 1-1 1C7 2 2.5 6.5 2.5 12s4.5 10 10 10 10-4.5 10-10c0-.6.4-1 1-1s1 .4 1 1c0 6.6-5.4 12-12 12zM22.9 8.4c-.5.2-1.1 0-1.3-.5-.2-.5 0-1.1.5-1.3.5-.2 1.1 0 1.3.5.2.5 0 1.1-.5 1.3zm-3.6-3.7c-.4-.4-.4-1 0-1.4s1-.4 1.4 0c.4.4.4 1 0 1.4-.4.4-1 .4-1.4 0zm-2.1 11.7l-5.2-3s-.1 0-.1-.1l-.1-.1-.1-.1-.1-.1v-.1-.1-.1-.1-.1-7.1c0-.6.4-1 1-1s1 .4 1 1v6.4l4.7 2.7c.5.3.6.9.4 1.4-.4.6-1 .7-1.5.5zm-1.1-14c-.5-.2-.8-.8-.5-1.3.2-.5.8-.8 1.3-.5.5.2.8.8.5 1.3-.2.5-.8.7-1.3.5z'/%3E%3C/svg%3E"); 
            background-position: 25%;
            background-position-x: 50%;
            background-position-y: center;
            background-repeat: no-repeat;
            height: 44px;
            margin: 0 
            auto 3px;
            width: 26px;            
          }

1 post - 1 participant

Read full topic

I am brand new to HA, so I don’t know whether my finding is common knowledge.

The Twilio Call integration is quite useful. I was hoping to find a way to route the service through my Twilio SIM card (instead of my home network). This would be useful if one wanted to receive a notification that the power had gone out (with the machine plugged into a backup battery, of course). Or, perhaps you want to set up a small HA environment for a motorhome, or similar.

I purchased a Huawei E3372h-510 and flashed it with “stick mode” firmware as I describe in this post. Then, with my Twilio SIM up and running, I simply added the device: /tty to my twilio_call configuration in the yaml file.

notify:
  - name: test_call
    platform: twilio_call
    device: /dev/ttyUSB0
    from_number: +12345678900

1 post - 1 participant

Read full topic

Hi,
I have a Telldus outdoor switch that used to have entity ID like 0b11000685bc0cfe05010f70 but after upgrading hassio it has changed (i think). I have one rfxtrx433e connected to my hassio machine. I do NOT have any telldus stick. The telldus remote is also gone so I can not trigger the device. My problem is how to get the new entity ID of my Telldus switch. Is it possible to “convert” between the old ID and the new?

Regards Perssola

1 post - 1 participant

Read full topic

I’ve been trying out some theming and adding rounded corners to my cards using ha-card-border-radius but when I do this it looks like the corner radius isn’t applied to the graph.

Screenshot_20201125-081916_Home Assistant1249×493 64.9 KB

this is with extra roundiness to demonstrate the problem

How do I stop this from happening ?

1 post - 1 participant

Read full topic

is it since 118 that this template

{{state_attr('sensor.laundry_sensor_light_level','lightlevel')}}

which is a number with value ‘6551’:

Schermafbeelding 2020-11-25 om 09.33.47772×698 35.1 KB

Schermafbeelding 2020-11-25 om 09.34.552184×474 55.3 KB

now shows in the frontend with a comma ‘6,551’:

in entities card:

Schermafbeelding 2020-11-25 om 09.40.28976×130 3.82 KB

and more-info:

Schermafbeelding 2020-11-25 om 09.34.01780×446 9.64 KB

the comma is a true error, and shouldn’t be there. Is this a backend template issue, or a frontend bug. We simply need the actual value, not some formatting of that if that’s what’s happening)

using an template-entity-row card does show the correct format:

Schermafbeelding 2020-11-25 om 09.50.02972×112 5.51 KB

with code:

      include:
        - entity_id: '*_sensor_light_level'
          options:
            type: custom:template-entity-row
            name: >
              {{state_attr(config.entity,'friendly_name').split(' sensor light level')[0]}}
            state: >
              {{state_attr(config.entity,'lightlevel')}} lm.  # <-------

1 post - 1 participant

Read full topic

Not sure when the lovelace card editor got so good, but it is awesome how it allows you to edit nested cards. I’m really loving it:

image1060×675 89.1 KB

If this is some HACS component that I installed and I didn’t know, I apologize in advance for causing confusion.

1 post - 1 participant

Read full topic

Hello. I’m new and I’m learning. I beg your help to subtract some time in automation from the next wake-up call sensor. I’d like to turn on the heater in front of the alarm.

{{states(‘sensor.p30_lite_xxxx_next_alarm’) ***_minus 1 hour 17 minutes }}

I deed for your help

1 post - 1 participant

Read full topic

The Lifx integration supports setting affected zones when calling lifx.set_state but it seems I cannot get it to work for my Lifx Candle Color bulb. According to their specs the bulb have 26 customizable zones. Whatever I put into zones in the call the whole bulb changes color. Here’s two example calls, both changes the color of the whole bulb:

entity_id: light.enhorning
color_name: red
zones: 0

entity_id: light.enhorning
color_name: red
zones:
  - 0
  - 1
  - 2
  - 3
  - 4
  - 5

Does anyone have any experience with this or know about any limitations in the integration or if I’m doing something wrong here?

1 post - 1 participant

Read full topic

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

1 post - 1 participant

Read full topic

Hi
I do have Tyua WIFI motion sensors but as we all know they do not show in HA. I was wondering if Tuya zigbee motion sensors will show or not?
If not if there are any other motion sensors that can be purchased that work without workarounds?

2 posts - 2 participants

Read full topic

Hi all,

I have been happily using Google Assistant in Manual mode and devices were coming through when in the middle of use the account unlinked its self.

I have since gone through recreating from the start how ever when I get past the log in screen the app defaults back to the add device screen.

Any suggestions in relation to the latest build as I have found quite a lot relating to when the API was changed ('18) but nothing recent ?

# Google Assistant
google_assistant:
  project_id: xxxxxxxxxxx
  service_account: !include xxxxxxxxxxxx.json
  expose_by_default: true
  report_state: true
  exposed_domains:
  - cameras

Thanks Terran

1 post - 1 participant

Read full topic

Hi there,
Does anyone know an addon maybe to get some view with HA logs where I can apply ad-hoc filtering similar to grep expressions or something?

I found https://github.com/hassio-addons/addon-log-viewer but it doesn’t seem pretty useful since it just redirect a log from the text file into the browser/mobile app page.

Of course I can tweak my logging settings to modify what is written in the log but that’s not the case I’m trying to cover. Just imagine that you put different things to be logged for a while and you are exploring what you’ve got. Now, you have to go to the HA instance, grub a log file, and make you filtering somewhere. It would be super convenient to avoid this somewhere to filter logs in the same place where you do changes (HA). Regex must be needed for sure, so browser search can’t fit that requirement.

1 post - 1 participant

Read full topic

Hi, I have setup my LG6 as Webcam via
Android IP Webcam

My setup in configuration.yaml is

stream:
android_ip_webcam:
  - host: 192.168.1.71
    port: 8080
    sensors:
      - audio_connections
      - battery_level
      - battery_temp
      - battery_voltage
      - light
      - motion
      - pressure
      - proximity
      - sound
      - video_connections
    switches:
      - exposure_lock
      - ffc
      - focus
      - gps_active
      - motion_detect
      - night_vision
      - overlay
      - torch
      - whitebalance_lock
      - video_recording

plus following setup at the very beginning of configuration.yaml to get access to the share folder
(before I get errors ‘no path access’

homeassistant:
  allowlist_external_dirs:
     - /config/www
     - /share

Now I receive via Service test (in developer section)

an empty jpg file with 0kB.

Any help is appreciated…
The mobile phone with IP Webcam App is running…

IP: 192.168.1.71 at port 8080.

Regards
Joerg

1 post - 1 participant

Read full topic