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

Graph actual value and 24h ago

$
0
0

@jaime.payan wrote:

Hi, I’m a little bit new here. I want to graph a comparisson betwen today and yesterday energy consumption. I am using the mini graph card from HACS to graph the last 48 hours so I know that the data is there. I would like to make an input or a template that can give me the value 24 hours ago. so that way I can graph that input and the actual value from the sensor.

Is it possible?

Posts: 1

Participants: 1

Read full topic


Installed version of HassOS to compare with latest available?

$
0
0

@f00dagi wrote:

Hi!

I want to indicate in my UI frontend if there are new home assistant and hassOS versions by comparing latest available with current. I have managed this for home assistant but not for hassOS.

To get the latest available version I use the following code to create a sensor.

- platform: template
  sensors:
    hassos_available_version:
      value_template: "{{ state_attr('sensor.latest_available_version', 'hassos') }}"

I have still not found a way to identify the current installed version. My best lead has been to get the information through the command line but it seems the information is not available from within home assistant?

I tried different variants of

- platform: command_line
  name: hassos
  command: hassio host info

Anyone that has a suggestion on how to proceed? Thanks!

Capture

Posts: 1

Participants: 1

Read full topic

Designing automations to be robust to errors/exceptions in actions

$
0
0

@naumz wrote:

First time poster here. I recently setup HA on a Raspberry PI and have had a lot of fun with it. As I create more automations, I was curious about different ways to design automations to be robust to errors/exceptions in actions.

This came to my mind because a recent update changed the behavior of the Roku integration on my TCL TV to raise Connection errors when the current state is standby (https://github.com/home-assistant/core/issues/36094). I dealt with it by using a service_template with an explicit condition on the state and using a noop script with 0 delay in the else statement ({% if ... elif ... else %} with no else - what do you do?).

I also read about creating a separate script with the action that is likely to throw an error so the main automation doesn’t fail.

The first approach requires knowing the exact state that may cause an error, and the second one doesn’t but requires splitting it out into a separate file.

Are there other/recommended ways of achieving a similar outcome?

For reference, here is the relevant part of my original automation:

- id: '1588671360892'
  alias: Play Youtube video
  description: Play Youtube video at a certain time
  trigger:
  - platform: template
    value_template: '{{ as_timestamp(states(''sensor.date_time_iso'')) == as_timestamp(states(''sensor.sunset_time''))
      }}'
  action:
  - data:
      is_volume_muted: true
    entity_id: media_player.living_room_tv
    service: media_player.volume_mute
  - entity_id: media_player.living_room_tv
    service: media_player.media_play_pause
  - data_template:
      volume_level: '{{''0.4'' if now().hour >= 21 else ''0.6''}}'
    entity_id: media_player.bedroom_speaker
    service: media_player.volume_set
  - data:
      entity_id: media_player.bedroom_speaker
      media_content_id: https://www.youtube.com/watch?v=XYZ
      media_content_type: music
    service: media_extractor.play_media
  - data:
      is_volume_muted: false
    entity_id: media_player.bedroom_speaker
    service: media_player.volume_mute
  - delay: 00:03:25
  - data:
      volume_level: '0.4'
    entity_id: media_player.bedroom_speaker
    service: media_player.volume_set
  - delay: 00:00:10
  - entity_id: media_player.living_room_tv
    service: media_player.media_play_pause
  - data: {}
    entity_id: media_player.living_room_tv
    service: media_player.volume_up

This is what I had to change the specific action section to:

  - entity_id: media_player.living_room_tv
    service_template: "{% if states('media_player.living_room_tv') != 'standby' %}\n\
      \  media_player.media_play_pause\n{% else %}\n  script.noop\n{% endif %}\n"

Posts: 1

Participants: 1

Read full topic

Custom icon in logbook entries?

$
0
0

@f00dagi wrote:

Hi!

The logbook is an amazing tool but I am missing one small feature: setting custom icons for each entry.

I am using the ‘custom entries’ at the bottom of the documentation:https://www.home-assistant.io/integrations/logbook/. The documentations does not mention the possibility to add a custom icon but as can be seen in the picture below home assistant obviously can change the icon for stated and stopped.

image

- service: logbook.log
  data_template:
    name: "alarm triggered:"
    message: >
      front door: {{ states('binary_sensor.aeon_labs_zw112_door_window_sensor_6_sensor_2') }}

Posts: 1

Participants: 1

Read full topic

Zwave entities on restart greyed out

$
0
0

@nmsaini wrote:

I am running 0.110.1 with Aeotec Z stick integration. My Z-wave entities are now showing greyed out after a homeassistant core restart. I am running in a docker-container.

From the logs I see-
WARNING (MainThread) [homeassistant.components.zwave] Z-Wave not ready after 300 seconds, continuing anyway
INFO (MainThread) [homeassistant.components.zwave] final network state: 0 Network is stopped

Posts: 1

Participants: 1

Read full topic

Node-red enable/disable flow via dashboard toggle switch (binary_sensor?)

$
0
0

@raspbender wrote:

Howdy folks,

Simple question, but after searching around I’m still not able to find an answer.

I have an automation for covers in node-red that works fine and opens/closes depending on the sun position and a few other parameters.

Sometimes, I want to “manually override” this flow automation, i.e. temporarily disable it, to set the cover position myself (e.g. when cleaning the windows) and until I decide to resume it. To this extent I thought it could be possible to create a binary_sensor and map it to a toggle switch widget on the dashboard, then have node-red check before any other action if the sensor is true/false.

Probably is very simple, but not sure how to define a binary_sensor whose status is updated manually (and toggle-able from the ha dashboard).

Open for suggestions if you feel there’s a better way to do it (could be a timer instead of a binary state).

Posts: 1

Participants: 1

Read full topic

Send all data after wifi reconnection

$
0
0

@mgim wrote:

Hello everyone,
I use a Wemos D1 mini with a photoresistor to detect my power meter consumption by adding a Wh at every power meter LED blink. It works great!
Now, it brings me to another challenge: I turn off my wifi at night using Home Assistant. For this, I use two input_datetime which I can change in Lovelace to determine when it switches off then on the wifi.

How can I tell through esphome to my Wemos D1 mini to send all the night data when it reconnects to the wifi in the morning? Will it create duplicates?

Posts: 1

Participants: 1

Read full topic

ZHA integration "Add Devices" search does not find devices

$
0
0

@dylandonkersgoed wrote:

The ZHA integration does not seem to be picking up my XIaomi Zigbee sensors when adding devices. These are the only Zigbee devices I have currently so I’m not sure whether the issue is specific to these sensors or a general issue. I’ve been searching around trying to find a solution but it seems like what I’m encountering is not typical - mostly people are running into issues either picking up the adapter or after discovering devices.

The specific sensors I’m using are:

I’ve seen other posts from people successfully using Xiaomi sensors. Sometimes with hiccups, but they’re able to at least connect.

I’m using the the Elelabs Zigbee USB Adapter.

I just updated in the hopes it would fix my issue so I’m on the latest Home Assistant version, 0.110.2. I’m using HomeAssistant on a desktop computer converted into a server via Docker but not using Hass.io.

The USB serial device is passed through to docker. I’m fairly confident the ZHA integration is connecting to and recognizing the device because I added it through the wizard which picked up the device, initially wasn’t able to connect due to the wrong baud rate, and then connected successfully after setting the correct baud rate.

Though I currently have it configured through the wizard I initially had it configured in configuration.yaml using the following configuration. The same values were added in the wizard:

zha:
  # I know "usb_path" is now deprecated - I used the wizard after updating home assistant partly for this reason.
  usb_path: /dev/ttyUSB0
  database_path: /config/zigbee.db
  baudrate: 115200

The ZigBee devices overview has picked up a “Silicon Labs EZSP” which I believe is the actual USB dongle.

What I’ve been doing is:

  1. Clicking the “Add devices” button at /config/zha/dashboard
  2. Holding the reset button at the top of a sensor for a few seconds until the light starts blinking
  3. Repeatedly tapping the button once every second or so to keep it awake while waiting near the adapter
  4. Waiting until the search completes

This is what the screen looks like after searching for devices:

There’s nothing in the logs at /developer-tools/logs related to ZHA after a device search. I do have the debug logs configured. These are the zha-related messages that it gives after booting:

Summary
2020-05-24 18:39:44 DEBUG (MainThread) [zigpy.appdb] Loading application state from /config/zigbee.db
2020-05-24 18:39:44 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for None None (d0:cf:5e:ff:fe:54:06:17)
2020-05-24 18:39:44 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
2020-05-24 18:39:44 DEBUG (MainThread) [zigpy.quirks.registry] Found custom device replacement for d0:cf:5e:ff:fe:54:06:17: <class 'bellows.zigbee.application.EZSPCoordinator'>
2020-05-24 18:39:44 DEBUG (MainThread) [bellows.ezsp] Resetting EZSP
2020-05-24 18:39:46 DEBUG (MainThread) [bellows.ezsp] Send command version: (4,)
2020-05-24 18:39:46 DEBUG (MainThread) [bellows.ezsp] Application frame 0 (version) received: b'06020063'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command version: (6,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 0 (version) received: b'06020063'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Switched to EZSP protocol version 6
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] EZSP Stack Type: 2, Stack Version: 25344
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_ADDRESS_TABLE_SIZE: 5>, 16)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_TRUST_CENTER_ADDRESS_CACHE_SIZE: 25>, 2)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_APPLICATION_ZDO_FLAGS: 42>, 3)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_SECURITY_LEVEL: 13>, 5)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_KEY_TABLE_SIZE: 30>, 4)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_INDIRECT_TRANSMISSION_TIMEOUT: 18>, 7680)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_PAN_ID_CONFLICT_REPORT_THRESHOLD: 34>, 2)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_MULTICAST_TABLE_SIZE: 6>, 16)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_MAX_END_DEVICE_CHILDREN: 17>, 32)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_SOURCE_ROUTE_TABLE_SIZE: 26>, 16)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_SUPPORTED_NETWORKS: 45>, 1)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_STACK_PROFILE: 12>, 2)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_END_DEVICE_POLL_TIMEOUT: 19>, 60)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_END_DEVICE_POLL_TIMEOUT_SHIFT: 27>, 8)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue: (<EzspConfigId.CONFIG_PACKET_BUFFER_COUNT: 1>, 255)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getConfigurationValue: (<EzspConfigId.CONFIG_APS_UNICAST_MESSAGE_COUNT: 3>,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 82 (getConfigurationValue) received: b'000a00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.zigbee.application] APS_UNICAST_MESSAGE_COUNT is set to 10
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command addEndpoint: (1, 260, 48879, 0, 0, 1, [], [1280])
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 2 (addEndpoint) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.zigbee.application] Ezsp adding endpoint: [<EzspStatus.SUCCESS: 0>]
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setConcentrator: (False, <EmberConcentratorType.HIGH_RAM_CONCENTRATOR: 65529>, 600, 1800, 2, 5, 0)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 16 (setConcentrator) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.zigbee.application] Set concentrator type: [<EmberStatus.SUCCESS: 0>]
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command networkInit: ()
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 23 (networkInit) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 25 (stackStatusHandler) received: b'90'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getNetworkParameters: ()
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 40 (getNetworkParameters) received: b'0001fcd527c97c5394fbfc76080f0000000000f8ff07'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setPolicy: (<EzspPolicyId.TC_KEY_REQUEST_POLICY: 5>, <EzspDecisionId.GENERATE_NEW_TC_LINK_KEY: 82>)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 85 (setPolicy) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setPolicy: (<EzspPolicyId.APP_KEY_REQUEST_POLICY: 6>, <EzspDecisionId.ALLOW_APP_KEY_REQUESTS: 97>)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 85 (setPolicy) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command setPolicy: (<EzspPolicyId.TRUST_CENTER_POLICY: 0>, <EzspDecisionId.ALLOW_PRECONFIGURED_KEY_JOINS: 1>)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 85 (setPolicy) received: b'00'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getNodeId: ()
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 39 (getNodeId) received: b'0000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getEui64: ()
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 38 (getEui64) received: b'170654feff5ecfd0'
2020-05-24 18:39:47 INFO (MainThread) [zigpy.application] Device 0x0000 (d0:cf:5e:ff:fe:54:06:17) joined the network
2020-05-24 18:39:47 DEBUG (MainThread) [zigpy.application] Skip initialization for existing device d0:cf:5e:ff:fe:54:06:17
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.zigbee.application] EZSP nwk=0x0000, IEEE=d0:cf:5e:ff:fe:54:06:17
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getConfigurationValue: (<EzspConfigId.CONFIG_MULTICAST_TABLE_SIZE: 6>,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.zigbee.application] Starting EZSP watchdog
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 82 (getConfigurationValue) received: b'001000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (0,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (1,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (2,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (3,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (4,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (5,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (6,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (7,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (8,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (9,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (10,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (11,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (12,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (13,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (14,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Send command getMulticastTableEntry: (15,)
2020-05-24 18:39:47 DEBUG (MainThread) [bellows.ezsp] Application frame 99 (getMulticastTableEntry) received: b'00000000'
2020-05-24 18:39:47 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] Loading battery powered devices
2020-05-24 18:39:47 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] Loading mains powered devices
2020-05-24 18:39:47 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x0000](EZSP): started initialization
2020-05-24 18:39:47 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x0000:ZDO](EZSP): 'async_initialize' stage succeeded
2020-05-24 18:39:47 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x0000](EZSP): power source: Mains
2020-05-24 18:39:47 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x0000](EZSP): completed initialization
2020-05-24 18:39:47 INFO (MainThread) [homeassistant.components.cover] Setting up cover.zha
2020-05-24 18:39:47 INFO (MainThread) [homeassistant.components.lock] Setting up lock.zha
2020-05-24 18:39:47 INFO (MainThread) [homeassistant.components.fan] Setting up fan.zha
2020-05-24 18:39:47 INFO (MainThread) [homeassistant.components.light] Setting up light.zha
2020-05-24 18:39:57 DEBUG (MainThread) [bellows.ezsp] Send command nop: ()
2020-05-24 18:39:57 DEBUG (MainThread) [bellows.ezsp] Application frame 5 (nop) received: b''
2020-05-24 18:40:07 DEBUG (MainThread) [bellows.ezsp] Send command nop: ()
2020-05-24 18:40:07 DEBUG (MainThread) [bellows.ezsp] Application frame 5 (nop) received: b''
2020-05-24 18:40:17 DEBUG (MainThread) [bellows.ezsp] Send command nop: ()
2020-05-24 18:40:17 DEBUG (MainThread) [bellows.ezsp] Application frame 5 (nop) received: b''
2020-05-24 18:40:27 DEBUG (MainThread) [bellows.ezsp] Send command nop: ()
2020-05-24 18:40:27 DEBUG (MainThread) [bellows.ezsp] Application frame 5 (nop) received: b''
2020-05-24 18:40:37 DEBUG (MainThread) [bellows.ezsp] Send command nop: ()
2020-05-24 18:40:37 DEBUG (MainThread) [bellows.ezsp] Application frame 5 (nop) received: b''
2020-05-24 18:40:47 DEBUG (MainThread) [bellows.ezsp] Send command nop: ()
2020-05-24 18:40:47 DEBUG (MainThread) [bellows.ezsp] Application frame 5 (nop) received: b''
2020-05-24 18:40:57 DEBUG (MainThread) [bellows.ezsp] Send command nop: ()
2020-05-24 18:40:57 DEBUG (MainThread) [bellows.ezsp] Application frame 5 (nop) received: b''
2020-05-24 18:41:07 DEBUG (MainThread) [bellows.ezsp] Send command nop: ()
2020-05-24 18:41:07 DEBUG (MainThread) [bellows.ezsp] Application frame 5 (nop) received: b''
2020-05-24 18:41:13 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x0000](EZSP): started initialization
2020-05-24 18:41:13 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x0000:ZDO](EZSP): 'async_initialize' stage succeeded
2020-05-24 18:41:13 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x0000](EZSP): power source: Mains
2020-05-24 18:41:13 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x0000](EZSP): completed initialization

Posts: 1

Participants: 1

Read full topic


Restored entities?

$
0
0

@gkron wrote:

HI,

Can someone explain to me what has actually changed in 0.110 with the entites creation? My squeezebox players need more time then is being allowed now at start up. They either don’t get populated or they become unavailable if they were there on a restart of the server. Is there a way to overwirte the time given to entites to populate? I would say they appear 1 out of every 20 restarts. Very furstrating. I see sometimes they are listed with a restored icon but activating them doesn’t do anything.

Posts: 1

Participants: 1

Read full topic

Stream to Chromecast in .110?

$
0
0

@TarheelGrad1998 wrote:

I had just begun to work with Cast and want to stream some cameras to a TV Chromecast. I had gotten the below to work and display the camera in Developer Tools on .109.

Today, I upgraded to .110.2 and tried creating automations and now it does not work. It changes to the Chromecast, starts to show a playbar at the bottom of the screen, but then stops with just the Chromecast icon in the center of the screen. This is even doing the same call that worked on .109 via Dev Tools.

  - service: camera.play_stream
    data_template:
      media_player: media_player.living_room_tv_chromecast
      entity_id: camera.carport

Has something about .110 broken this? I also changed back to using default config during the upgrade (as I had previously removed discovery to prevent repeated device detection, now that they can be ignored), but I assume it should have everything necessary for this to work?

Posts: 1

Participants: 1

Read full topic

Help with total time state = "on" influxdb

$
0
0

@yonny24 wrote:

Please I need some help with influxdb addon DB- I need the total time of a device “on” state per day or month. Using sum(value) but the integer being returned does not make sense. I’m looking to return the total times (in hours or mins) from state - “on”. What unit is this returning? 4.0 for today for example doesn’t make sense. Thanks!

SELECT sum("value") AS "time" FROM "homeassistant"."autogen"."state" WHERE time > now() - 2d AND "entity_id"='51746580840d8e63e756' GROUP BY time(1d) FILL(null)

Posts: 1

Participants: 1

Read full topic

Received invalid command: zha/devices

$
0
0

@lancer1991 wrote:

Trying to add my first Zigbee devices and it’s not working. Log issues below. I have a HUSBZ-1. I’ve removed the usb_path: /dev/ttyUSB1 from configuration.yaml per latest update and that didn’t fix it. Completely new to this. Trying to migrate from Wink.

Log Details (ERROR)
Logger: homeassistant.components.websocket_api.http.connection.140153171052560
Source: components/websocket_api/connection.py:84
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 8:25:53 PM (2 occurrences)
Last logged: 8:25:58 PM

Received invalid command: zha/devices
Received invalid command: zha/devices/permit
2020-05-24 20:25:53 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140153171052560] Received invalid command: zha/devices
2020-05-24 20:25:58 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140153171052560] Received invalid command: zha/devices/permit

Posts: 1

Participants: 1

Read full topic

Media_player fail to play local mp3

$
0
0

@vormsty wrote:

Hello,
I have some difficulties to set the correct path for local path.
I run HA with docker.
NGING is used as proxy for https.

for playing media:

 - service: media_player.play_media
   data:
      entity_id: media_player.xbr_49x800e
      media_content_id: https://www.soundhelix.com/examples/mp3/SoundHelix-Song-1.mp3
      media_content_type: 'music'

is working !

In the folder config I created a folder mp3

But If I replace the media content by:

      media_content_id: http://192.168.1.106/local/mp3/doorbell.mp3
    

it doensn’t work.

I have no base_url defined because the local trafic is on http.
How can I debug this situation ?

Many thanks for your help !

Regards!

Posts: 3

Participants: 3

Read full topic

Trying to create an automation to increase light brightness on a press and hold command and stop when released

$
0
0

@BennyB44 wrote:

Ok it’s time to ask for help. I have no coding experience so i apologize if i have made any obvious errors. I have spent weeks searching, reading the docs and learning as much as i can.

I am trying to create a multi press button for our bedside table lamps.
I have currently have a Nodemcu ESP32 with a push button that i have programed to send home assistant events for single click, double click, hold and release from EspHome.

The light is a bulb which i have setup as 3 entities, White, Colour and All (both white and colour for a warm white light) also from EspHome

That works as expected and i can receive all events.

I have single click toggling on the entity id from an input_select. that works fine.

i have Double click changing modes on the input_select and turning the light to that mode.

The problem i have is getting the press and hold to ramp the lights up to full brightness and stop at what ever point i release the button.

I have the hold activate an input_boolean which i use to trigger an automation to run a script to start the lights of a brightness of 5.

I then am trying to get the brightness attribute change to trigger an automation that will loop and run as long as the condition of the input boolean it on. once i release the button the input boolean turns off and so the automation loop should then stop.

I believe where I am having a problem is getting the brightness attribute to trigger the automation.

I have it all in a package which i have included below.

Thanks in advance for any assistance.

    bedroom_lamp:
      name: "Bedroom Lamp"
      initial: false

    bedroom_lamp_dimmer:
      name: "Bedroom Lamp Dimmer"
      initial: false

input_select:
    bedroom_lamp_mode:
      name: Bedroom Lamp Mode
      options:
        - All
        - Colour
        - White
      initial: All
      icon: mdi:lamp

script:
  bedroom_lamp_turn_on:
    alias: Bedroom Lamp Turn On
    sequence:
    - data: {}
      entity_id: light.bedroom_lamps
      service: light.turn_off
    - data_template:
        entity_id: >
            {% if is_state("input_select.bedroom_lamp_mode", "White") %}
              light.bedroom_lamps_white
            {%-elif is_state("input_select.bedroom_lamp_mode", "Colour") %}
              light.bedroom_lamps_colour
            {%-elif is_state("input_select.bedroom_lamp_mode", "All") %}
              light.bedroom_lamps
            {% endif %}
      service: light.turn_on

  bedroom_lamp_dimmer_start:
    alias: Bedroom Lamp Dimmer Start
    sequence:
    - data_template:
        entity_id: >
            {% if is_state("input_select.bedroom_lamp_mode", "White") %}
              light.bedroom_lamps_white
            {%-elif is_state("input_select.bedroom_lamp_mode", "Colour") %}
              light.bedroom_lamps_colour
            {%-elif is_state("input_select.bedroom_lamp", "All") %}
              light.bedroom_lamps
            {% endif %}
        brightness_step: 5
      service: light.turn_on

  bedroom_dimmer_loop:
    alias: Bedroom Lamp Dimmer 
    sequence:
    - condition: state
      entity_id: input_boolean.bedroom_lamp_dimmer
      state: 'on'
    - below: '251'
      condition: numeric_state
      entity_id: light.bedroom_lamps
      value_template: "{{ state.attributes.brightness}}"
    - data_template:
        entity_id: >
            {% if is_state("input_select.bedroom_lamp", "White") %}
              light.bedroom_lamps_white
            {%-elif is_state("input_select.bedroom_lamp", "Colour") %}
              light.bedroom_lamps_colour
            {%-elif is_state("input_select.bedroom_lamp", "All") %}
              light.bedroom_lamps
            {% endif %}
        brightness_step: 5
      service: light.turn_on

automation:

  - id: 'bedroom_lamp_input_boolean_toggle'
    alias: Bedroom Lamp Input Boolean Toggle
    description: ''
    trigger:
    - event_data:
        title: single_click
      event_type: esphome.test_esp_32
      platform: event
    condition: []
    action:
    - data: {}
      entity_id: input_boolean.bedroom_lamp
      service: input_boolean.toggle

  - id: 'bedroom_lamp_turn_on'
    alias: Bedroom Lamp Turn On
    description: ''
    trigger:
    - entity_id: input_boolean.bedroom_lamp
      from: 'off'
      platform: state
      to: 'on'
    condition: []
    action:
    - data: {}
      service: script.bedroom_lamp_turn_on

  - id: 'bedroom_lamp_turn_off'
    alias: Bedroom Lamp Turn off
    description: ''
    trigger:
    - entity_id: input_boolean.bedroom_lamp
      from: 'on'
      platform: state
      to: 'off'
    condition: []
    action:
    - data: {}
      entity_id: light.bedroom_lamps
      service: light.turn_off

  - id: 'bedroom_lamp_mode'
    alias: Bedroom Light Mode
    description: ''
    trigger:
    - event_data:
        title: dbl_click
      event_type: esphome.test_esp_32
      platform: event
    condition: []
    action:
    - data: {}
      entity_id: input_select.bedroom_lamp_mode
      service: input_select.select_next
    - data: {}
      service: script.bedroom_lamp_turn_on

  - id: 'bedroom_lamp_dimmer_input_boolean_turn_on'
    alias: 'Bedroom Lamp Dimmer Input Boolean Turn On'
    trigger:
    - event_data:
        title: hold
      event_type: esphome.test_esp_32
      platform: event
    action:
      - data: {}
        service: input_boolean.turn_on
        entity_id: input_boolean.bedroom_lamp_dimmer

  - id: 'Bedroom_lamp_dimmer_input_boolean_turn_off'
    alias: 'Bedroom Lamp Dimmer Input Boolean Turn Off'
    trigger:
    - event_data:
        title: release
      event_type: esphome.test_esp_32
      platform: event
    action:
      - data: {}
        service: input_boolean.turn_off
        entity_id: input_boolean.bedroom_lamp_dimmer

  - id: 'bedroom_lamp_dimmer_loop_start'
    alias: Bedroom Lamp Dimmer Loop Start
    description: ''
    trigger:
    - entity_id: input_boolean.bedroom_lamp_dimmer
      platform: state
      to: 'on'
    condition: []
    action:
    - data: {}
      service: script.bedroom_lamp_dimmer_start 

  - id: 'bedroom_lamp_dimmer_loop'
    alias: Bedroom Lamp Dimmer Loop
    description: ''
    trigger:
      platform: state
      entity_id: light.bedroom_lamps
    condition:
      - condition: template 
        value_template: >
          {{ trigger.to_state.attributes.brightness !=
            trigger.from_state.attributes.brightness }} 
      - condition: state
        entity_id: input_boolean.bedroom_lamp_dimmer
        state:  'on'
    action:
    - delay: 100ms
    - data: {}
      service: script.bedroom_lamp_dimmer_loop

group:
  bedroom_lamp:
    name: Bedroom Lamp
    entities:
      - input_boolean.bedroom_lamp
      - input_boolean.bedroom_lamp_dimmer
      - input_select.bedroom_lamp_mode
      - script.bedroom_lamp_turn_on
      - script.bedroom_lamp_dimmer_start
      - script.bedroom_dimmer_loop
      - automation.bedroom_lamp_input_boolean_toggle
      - automation.bedroom_lamp_turn_on
      - automation.bedroom_lamp_turn_off
      - automation.bedroom_lamp_mode
      - automation.bedroom_lamp_dimmer_input_boolean_turn_on
      - automation.bedroom_lamp_dimmer_input_boolean_turn_off
      - automation.bedroom_lamp_dimmer_loop_start
      - automation.bedroom_lamp_dimmer_loop

Posts: 1

Participants: 1

Read full topic

What is the sensor data format?

$
0
0

@stevemann wrote:

I have a device that is publishing a JSON string of various status values.

In my sensors.yaml include file, I have this entry:

  • platform: mqtt
    name: “Garden_Status”
    force_update: true
    state_topic: “garden2/statusJson”

In Developer Tools, States, I can see the sensor, but the data is the whole JSON string:
{"temp":"77.68","wet":"114","raw":"861","rssi":"-66","sleep":"10"}
How can I split it into attributes to use in an automation, for example?
(I am guessing that I need to use a template, but how?)

Posts: 1

Participants: 1

Read full topic


How to override date/time with value from mqtt data?

$
0
0

@eborst wrote:

I have a sensor which updates on a time interval. the sensor provides multiple attributes / sub sensors, so I have split it to separate sensors in Home-assistant. so far so good.
Only thing I’m stuck with is the data / time provided in the data. in Home assistant the sensors are showing the data at the time the data is published. I want this to be the date/ time provided by the sensor in the data. How can I do this?

Posts: 1

Participants: 1

Read full topic

iFrames not loading

$
0
0

@abelson wrote:

I just upgraded home assistant to run on https and now I am having trouble with iFrames loading. I am assuming that it is because I am trying to embed web pages running off a local server that are not using https. Is there a way to allow an http webpage to load in an iFrame even though HA is running over https?

Posts: 1

Participants: 1

Read full topic

Running Multiple OpenZWave Intergrations

$
0
0

@Minsk11 wrote:

Hi,

I’m currently running both US & EU Z Wave controllers on 2 docker containers of HA Core, and am looking to migrate to OpenZWave.

Is it possible instead to configure 2 OpenZWave docker containers using the 2 Z Wave controllers (posting to 2 different MQTT topics) and 2 instances of the OpenZWave HA intergration? I want to remove the other HA docker container if possible.

Posts: 1

Participants: 1

Read full topic

Help to minimize data of value template

$
0
0

@Makis wrote:

Hi
I am trying to display the switches are ON.

I came up with the following which is working but I only need the friendly name and not the rest of info
in order to sent a simple notification to my phone

value_template: >
          {% set switch = states.switch -%} 
          {% set on = switch | selectattr('state','eq','on') | list -%}       
          {{ on }} 
alue_template: >
          [<template state switch.sonoff_10009bd11e=on; rssi=-68, friendly_name=Kitchen Led 2, icon=mdi:led-strip, supported_features=0 @ 2020-05-25T10:27:31.889492+03:00>, <template state switch.sonoff_1000a05283=on; rssi=-66, friendly_name=Kitchen Led, icon=mdi:led-strip, supported_features=0 @ 2020-05-25T10:27:31.326588+03:00>, <template state switch.tradfi_outlet=on; friendly_name=Tradfi outlet @ 2020-05-24T09:37:57.194650+03:00>]

Ideally from the above I would like to get
Kitchen Led
Kitchen Led 2
Tradfri outlet.

Can someone suggest how to proceed?

Posts: 1

Participants: 1

Read full topic

HELP! Updated HACS ... custom tiles not working!

$
0
0

@Tovrin wrote:

Clearly I’m missing something, but I’m damned if I can see it!

I recently updated to the latest HACS (1.0.3) and since then, none of those components work anymore. My Lovelace tiles are getting “Custom element doesn’t exist: mini-graph-card” and “Custom element doesn’t exist: mini-media-player” for the two custom elements I’m using.

It appears the custom integration seems to be working ok … at least as far as I can tell from the states list (… well, they’re not “unavailable” at least).

I’ve tried changing the resources section of my lovelace-ui.yaml file to mate what it says when trying to reinstall to …

resources:
  - url: /hacsfiles/mini-graph-card/mini-graph-card-bundle.js
    type: module
  - url: /hacsfiles/mini-media-player/mini-media-player-bundle.js
    type: module

… but that didn’t make any difference. I tried moving the plugins directly to the www folder and reference that as /local/, but that didn’t work. Any guidance at this point would be greatly appreciated.

Posts: 1

Participants: 1

Read full topic

Viewing all 106132 articles
Browse latest View live


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