I’m trying to use a script to only dimm lights that are on in a specific light group.
I use ControllerX to dim up and down with a Philips Hue dimmer.
script is called with:

up_short_release: 
      - service: script.light_dimmer_up
        data:
          lightgroup: group.dimmer_test

script:

light_dimmer_up:
  description: increase light level when dim up button is pressed
  sequence:
    - service: light.turn_on
      data_template:
        entity_id: >
          {{ expand( "{{ lightgroup }}" )| selectattr('state','eq','on') |
          map(attribute='entity_id') | list | join(', ') }}
      brightness_step_pct: 5

entity_id stays empty which results in the error:  not a valid value for dictionary value @ data['entity_id']
probably my syntax for the nested "lightgroup" variable isn't correct.

I can’t get it right

1 post - 1 participant

Read full topic

When using the Blueprint for motion my Ikea lamp turns on but only @4%.

I have tried with brightness: 255 but gets an error. Is it not possible to decide brightness through the Blueprinted service?

1 post - 1 participant

Read full topic

I have the following configuration for a picture-elements card.

type: picture-elements
image: /local/ll_matte_home.png
elements:
   - style:
          color: white
          top: 73%
          left: 12%
          transform: 'translate(-50%, -50%) scale(5, 5)'
     type: state-label
     entity: sensor.matte_hem

I want to make the element of type state-label blink every 4 seconds. What could be done?
Thanks in advance.

3 posts - 2 participants

Read full topic

Looks like MyQ integration is down again. Below is the error. Tried to remove and re-add the integration and still the same error. Anyone else have similar issues?

Logger: homeassistant.components.myq.config_flow
Source: components/myq/config_flow.py:30
Integration: MyQ ([documentation](https://www.home-assistant.io/integrations/myq), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+myq%22))
First occurred: 7:08:47 PM (1 occurrences)
Last logged: 7:08:47 PM

Unexpected exception

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/myq/config_flow.py", line 50, in async_step_user info = await validate_input(self.hass, user_input) File "/usr/src/homeassistant/homeassistant/components/myq/config_flow.py", line 30, in validate_input await pymyq.login(data[CONF_USERNAME], data[CONF_PASSWORD], websession) File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 259, in login await api.authenticate(username, password, False) File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 170, in authenticate auth_resp = await self.request( File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 151, in request return await self._send_request( File "/usr/local/lib/python3.8/site-packages/pymyq/api.py", line 114, in _send_request message = f"Error requesting data from {url}: {data.get('description', str(err))}" UnboundLocalError: local variable 'err' referenced before assignment

2 posts - 2 participants

Read full topic

Good Day!

I have a virtualized instance of home assist that I’d like to remove the port redirection configuration from the nginx conf. I’m having trouble locating the conf files (I’m new to containerization), and would really appreciate some basic context. Specifically I want to comment out the following in the nginx config:

server {
	listen 80;
	server_name hassio.domain.com;
	return 301 https://$host$request_uri;
}  

TIA!! -Steve

1 post - 1 participant

Read full topic

I am using the rest sensors for NWS Alerts as described in https://community.home-assistant.io/t/severe-weather-alerts-from-the-us-national-weather-service/71853

I have my sensors configured in configuration.yaml as:

  - platform: rest
    resource: https://api.weather.gov/alerts/active?zone=[Zone IDs Redacted]
    name: NWS Alert Event Raw
    value_template: >
      {% if value_json.features[0] is defined %}
        {{ value_json['features'][0]['properties'].event }}
      {% else %}
        None
      {% endif %}
    json_attributes:
      - features
    headers:
      User-Agent: Homeassistant
      Accept: application/geo+json
    scan_interval: 60
  
  - platform: template
    sensors:
      nws_alert_event_filtered:
        friendly_name: NWS Alert Event
        value_template: >
          {% if is_state('sensor.nws_alert_event_raw', 'unavailable') or is_state('sensor.nws_alert_event_raw', 'unknown') %}
            {{ states.sensor.nws_alert_event_filtered.state }}
          {% else %}
            {{ states.sensor.nws_alert_event_raw.state }}
          {% endif %}

I then have conditional Lovelace Cards that display only when there is an alert with the following code:

type: conditional
conditions:
  - entity: sensor.nws_alert_event_filtered
    state_not: none
card:
  cards:
    - entity: sensor.nws_alert_event_filtered
      type: entity
    - content: >-
        {% if states.sensor.nws_alert_event_raw.attributes.features[0] is
        defined %}
         
         {{states.sensor.nws_alert_event_raw.attributes.features[0].properties.headline }}

         <b> Details </b>
           {{states.sensor.nws_alert_event_raw.attributes.features[0].properties.description }}

          <b>Instructions</b>

          {{states.sensor.nws_alert_event_raw.attributes.features[0].properties.instruction }}
        {% else %}
          none
        {% endif %}
      type: markdown
  type: vertical-stack

With the release of 0.118 my lovelace cards began displaying the card and text “Unknown” and “None” in a box directly below the unknown when no events were active instead of hiding the card.
When there are no events the endpoint for the raw sensor returns something like this:

{
    "@context": {
        "@version": "1.1"
    },
    "type": "FeatureCollection",
    "features": [],
    "title": "current watches, warnings, and advisories",
    "updated": "2020-12-10T16:00:00+00:00"
}

I found that there were breaking changes in Templates with 0.118 with the helpful advice to add

homeassistant:
  legacy_templates: true

as a transitional fix. This fixes the problem and my cards behave properly – displaying the alert if active or hiding the card if no alerts are active. However, I don’t know what changes I need to make to my sensors and/or lovelace card configuration in order to resolve the breaking template issue long-term. I am currently running 2020.12.7 on Hass.io HassOS 4.17

Could you please point me in the right direction?

1 post - 1 participant

Read full topic

Homeassistant 2020.12.1 running in a Docker container on a QNAP server.

I tried following the example in https://www.home-assistant.io/integrations/nut/ specifying the IP address and UPS name in the configuration.yaml file. Attempting to access the device resulted in failure. I know from other code that access the QNAP NUT instance over the network, requires the timeout on a request to be increased.

Editing homeassistant/components/nut/init.py and changing the 10 to a 5000 in

async def async_update_data():
    """Fetch data from NUT."""
    async with async_timeout.timeout(10):
        await hass.async_add_executor_job(data.update)
        if not data.status:
            raise UpdateFailed("Error fetching UPS state"

has enabled the device to function correctly

1 post - 1 participant

Read full topic

I know it’s not the most popular way to run home assistant, but I’m running in an iocage jail on TrueNAS (formerly FreeNAS)

I just upgrade from 118.5 to the new 2020.12.1, which also required upgrading from Python 3.7 to Python 3.8.

When all was said and done, most things work fine locally, but there are some oddities with the Android app when on the home network, and homeassistant cloud / nabucasa is down hard.

I believe the error that is causing the problem is here:

 Logger: homeassistant.setup
 Source: setup.py:138
 First occurred: 8:00:21 PM (3 occurrences)
 Last logged: 8:00:26 PM
 
 * Setup failed for cloud: Unable to import component: /srv/homeassistant/lib/python3.8/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so: Undefined symbol "sk_pop_free"
 * Setup failed for mobile_app: Unable to import component: /srv/homeassistant/lib/python3.8/site-packages/cryptography/hazmat/bindings/_openssl.abi3.so: Undefined symbol "sk_pop_free"
 * Setup failed for default_config: Could not set up all dependencies.

Looks to be ssl related, but I have no idea where to go from here.

Thoughts?

1 post - 1 participant

Read full topic

I’m setting up HA to manage dropping and raising my projector screen. Currently everything works, but I’m trying to avoid race conditions and having the screen not end up in weird positions. All that I can do/tell from HA is saying UP and waiting say 1minute and down and then wait 40s and then stop, but I can’t ever “know” where the screen is.

I know there has to be a better way then what I’m doing. Currently this is my setup which I’m looking for advice to improve upon.

I use two booleans, one is “screen moving” and the other is “power on/off” via a smart plug that reports power usage. I then have automations to switch the boolean for power on/off but only once (condition of automation is that it’s not already on/off) so it doesn’t flap. I then have a condition of screen not moving and when the screen is moving I turn that boolean on.

Is there not a way I can configure this all in one entitiy? So that when the power comes on, it finishes closing screen and will not attempt to raise it untill drop is finished and vis versa.

Here is some of my code:

switch:
  platform: template
  switches:
    projector_screen_moving_boolean:
      value_template: >
        {{ is_state('input_boolean.projector_screen_moving_boolean', 'off') }}
      turn_on:
        - service: input_boolean.turn_on
          entity_id: input_boolean.projector_screen_moving_boolean
      turn_off:
        - service: input_boolean.turn_off
          entity_id: input_boolean.projector_screen_moving_boolean
    projector_power_boolean:
      turn_on:
        - service: input_boolean.turn_on
          entity_id: input_boolean.projector_power_boolean
      turn_off:
        - service: input_boolean.turn_off
          entity_id: input_boolean.projector_power_boolean

And an automation: (One of many at this point…)

  alias: Projector Down
  description: ''
  trigger:
  - platform: state
    entity_id: input_boolean.projector_power_boolean
    from: 'off'
    to: 'on'
  condition:
  - condition: not
    conditions:
    - condition: state
      entity_id: input_boolean.projector_screen_moving_boolean
      state: 'on'
  action:
  - service: remote.send_command
    data:
      device: projectorscreen
      command: open
    entity_id: remote.broadlinkrmpro4_remote
  - service: input_boolean.turn_on
    data: {}
    entity_id: input_boolean.projector_screen_moving_boolean
  - delay: '00:00:37.5'
  - service: remote.send_command
    data:
      device: projectorscreen
      command: open
    entity_id: remote.broadlinkrmpro4_remote
  - service: input_boolean.turn_on
    data: {}
    entity_id: input_boolean.projector_screen_moving_boolean
  - delay: '00:00:37.5'
  - service: remote.send_command
    data:
      device: projectorscreen
      command: stop
    entity_id: remote.broadlinkrmpro4_remote
  - service: input_boolean.turn_off
    data: {}
    entity_id: input_boolean.projector_screen_moving_boolean
  mode: single

1 post - 1 participant

Read full topic

Hello,

I’m new to ZHA.

I’ve paired 2 Philips motion sensors (1 outdoor and 1 indoor) and some lights to ZHA by using a conbee II usb.
Before it was paired to a Hue bridge, so reset it and paring went well in ZHA.
I see values for the temperature, occupancy, illuminance, power.

But the on_off binary sensor detect never motion, although the occupancy sensor working correctly.

Am I missing something?
Do I need to configure something more?

Thanks!

1 post - 1 participant

Read full topic

Problem statement: HA DB size is big because recorder saves into it all the attributes of the entities. Even the ones related to customization that do never rarely change.

Examples:

I’d like to understand how to configure the system in order to completely get rid of recording the attributes that do not change, or I can put it another way, that I’m not interested in. My interest is only state column so that graphs can be build by Home Assistant default cards.

Does anybody know how to do that?

1 post - 1 participant

Read full topic

Hello,

I am new to this Home assistant concept. I need some help in setting up Arlo alerts in my home. All these days i have Arlo smart premium plan and whenever any motion took place in my front door camera, i used to get email with screenshot. once i removed the subscription, i am only getting email but without any screenshot
i have the below devices in my home

1. Arlo ultra cameras
2. Amazon Alexa
3. Insteon switches ( connected to lights in all my rooms)
4. Tesla car ( planning to get solar and powerwalls in couple of months)
5. Harmony elite remote

Can anyone please suggest me any tips and tricks on how to utilize my devices and utilize my devices with my Arlo cameras

I’d like to build some automation where, if the camera detects motion it will turn light on specific light or trigger alexa to say something or i can buy any Bell device so that bell might ring

I have added arlo into my config and see my Arlo status’s on my home screen UI. how can i see other features ( like motion detection screenshot) on the UI ?

1 post - 1 participant

Read full topic

I’m new to HA and I’m wondering if it’s possible to set up another Raspberry with camera pointing to the house heating system’s indicator leds which tell the state of system. A bright green led is always on if everything is ok and it turns red if there is a fault in the system.

I would like to get a notification if the led turns to red.

I have one extra Pi Zero W and a camera module. My HA is running on RPi 3 B.

1 post - 1 participant

Read full topic

I have a working binary_sensor.
It turns sensor.warmtepomp_boiler ‘on’ or ‘off’

I want an extra condition added to this:
is_state('binary_sensor.qbus_status_warmtepomp', 'off')

This should only be valid when this state is off for 60 seconds, and not immediately, like it is now.

Browsing the forum, I found that I have to add something like:
if trigger.for.seconds|int >= 60
and I have to change
is_state into to_state

But how do I get this in this template, I’m not sure about the correct placing and syntax.

binary_sensor:
  - platform: template
    sensors:
      warmtepomp_boiler:
        friendly_name: Warmtepomp Boiler                      
        value_template: >
          {% if is_state('binary_sensor.qbus_status_warmtepomp', 'off') and (states('sensor.flukso_warmtepomp_vermogen')|int > 500) %}
          on
          {% else %}
          off
          {% endif %}

Thank you

1 post - 1 participant

Read full topic

Hello everyone,

I am currently desperate to integrate my “nodon sin-2-2-01 enocean”.
The “EnOcean_USB_300” USB stick seems to work so far and events are also being received. But how can I send events? The switch is displayed in the overview and also changes its state if the “nodon sin-2-2-01 enocean” is switched manually.
In the end, the “switch nodon01_0” should be controlled via sunrise / sunset.

Log reception event:

2020-12-19 09:31:07 DEBUG (Thread-3) [homeassistant.components.enocean.dongle] Received radio packet: 05:1A:0C:DF->FF:FF:FF:FF (-55 dBm): 0x01 ['0xd2', '0x4', '0x61', '0xe4', '0x5', '0x1a', '0xc', '0xdf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x37', '0x0'] OrderedDict()
2020-12-19 09:31:07 DEBUG (Thread-3) [homeassistant.components.enocean.dongle] Received radio packet: 05:1A:0C:DF->FF:FF:FF:FF (-55 dBm): 0x01 ['0xd2', '0x4', '0x60', '0x80', '0x5', '0x1a', '0xc', '0xdf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x37', '0x0'] OrderedDict()

Configuration.yaml:

enocean:
  device: /dev/serial/by-id/usb-EnOcean_GmbH_EnOcean_USB_300_DC_FT3Z2CLI-if00-port0
 
logger:
  default: error
  logs:
    homeassistant.components.enocean: debug  

switch nodon01_0:
  - platform: enocean
    id: [0x05,0x1A,0x0C,0xDF]
    name: enocean_nodon01_0
    channel: 0


switch nodon01_1:
  - platform: enocean
    id: [0x05,0x1A,0x0C,0xDF]
    name: enocean_nodon01_1
    channel: 1

1 post - 1 participant

Read full topic

Hello,

I would like to put an https access for my home assistant (hassio - 2020.12.1)
I have already an external access with duckdns and nginx installed and working
I can access to my home assistant with http://hassio.local:8123 but the https isn’t working

The problem with that is that I cannot cast media mounted :

Failed to cast media http://192.168.0.34:8123/media/local/test.mp3?authSig=eyJ0eXAiOiJKV1bo from internal_url (http://192.168.0.34:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address

I think my solution could be to pass/activate https to my internal access but I don’t manage to do it

from supervisor my nginx config is like that :

domain: xxxx.duckdns.org
certfile: fullchain.pem
keyfile: privkey.pem
hsts: max-age=31536000; includeSubDomains
cloudflare: false
customize:
  active: false
  default: nginx_proxy_default*.conf
  servers: nginx_proxy/*.conf

My duckdns config is like that

lets_encrypt:
  accept_terms: true
  certfile: fullchain.pem
  keyfile: privkey.pem
token: xxx-40xxc-4xx4-xxx-3xx7axxxx7x3f2
domains:
  - xxx.duckdns.org
aliases: []
seconds: 300

My configuration.yaml is like that (for http part)

http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

Thanks for helping me to put https on my internal access !

1 post - 1 participant

Read full topic

I would like to trigger the powerbutton of my pelletheater when it is above 23°(powering of turning off) and below 21°. It does not work

It triggers and works without “below” and “above” conditions.

This is my automation:

- id: '1608322452545'
  alias: Pellet_thermostaat
  description: ''
  trigger:
  - platform: state
    entity_id: sensor.trapmotion_temperature
  condition:
  - condition: or
    conditions:
    - condition: numeric_state
      entity_id: sensor.trapmotion_temperature
      attribute: unit_of_measurement
      below: 21
    - condition: numeric_state
      entity_id: sensor.trapmotion_temperature
      attribute: unit_of_measurement
      above: 23
  action:
  - type: turn_on
    device_id: f70a99d3b46ecd83bf0a6db3869bd5fa
    entity_id: switch.70116356840d8e5c4814
    domain: switch
  mode: single

1 post - 1 participant

Read full topic

So, I just can’t seem to find any source for the official Home Asisstant Icon - ideally as a vector graphic

Also, what’s the official Home Assistant Blue colour code?

This must be somewhere in the documentation, I’m sure - just can’t find it…

1 post - 1 participant

Read full topic

I initially set up the homekit integration and added a bridge (named HASS Bridge) via the user interface (Configuration > Add Integration)

I then wanted to exclude a few entities because I already have a Phillips hue bridge.

I modified the configuration.yaml file and added:

homekit:
  filter:
   exclude_domains:
      - light
   exclude_entities:
   - lock.front_door
   - sensor.front_door_battery
   - binary_sensor.front_door_open
   - sensor.front_door_operator

Restarted home assistant and now I have a duplicate homekit bridge (named Home Assistant Bridge:51827) and in the home assistant notifications, it’s asking me to set up the new (duplicated) bridge.

Do I need to delete the old bridge ( HASS Bridge) or what am I doing wrong?
The entities that I excluded in the configuration.yaml aren’t excluded after reboot.

Screen Shot 2020-12-19 at 3.22.31 AM680×564 16.9 KB

1 post - 1 participant

Read full topic

I had all of my nest cameras working prior to the upgrade tonight. After the upgrade, all failed to connect. When I try to reinstall the Nest integration, it pulls in zero devices.

All configurations within GCP and APIs are un changed.

Thoughts?

1 post - 1 participant

Read full topic