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

MCO home switches responding slow to HA

$
0
0

@Anthony_Vd_Koppel wrote:

I have a set-up with a Raspberry, Aeotec gen 5 USB Z-Wave controller, a Neo Coolcam switch with two buttons, a MCO home with one butten and a MCO home with two buttons.

Every switch is responding fast when switching from the Lovelace interface. But when switching the MCO home switches, the states send to HA is very slow, and sometimes not working at all.

Then connecting the MCO home switches to a Homey controller, send the state within 1 second to the controller.

Any ideas how to fix this?

Posts: 1

Participants: 1

Read full topic


Input_datetime multiple sensors

$
0
0

@jhart003 wrote:

Need a little help. I was running Home Assistant Core 0.104.3 (Hass.io) and had two input_datetime sensors which were working fine.

I decided to upgrade to 0.106.1. I ran the Check Home Assistant configuration add-in and it identified an issue with how my zone was configured. I fixed that, reran and it said no error found! :slight_smile:

I upgraded to 0.106.1 but keep getting errors saying input_datetime platform can’t be loaded.

I checked Developer Tools - States and it appears my first input_datetime is loading, but my second one isn’t. I compared my yaml to the docs but I don’t see the issue.

Here is my yaml:

input_datetime:
  backyard_floodlight_reset_time:
    name: Backyard Floodlights Reset Time
    has_date: false
    has_time: true
    initial: 00:30
  afternoon_lights_on_time:
    name: Afternoon Lights On Time
    has_date: false
    has_time: true
    initial: 13:00

Any ideas what I am doing wrong?

0.104.3 wanted quotes around the names, but 0.105.X and 0.106.X doesn’t like the quotes.

As always, thank you in advance.

Posts: 4

Participants: 2

Read full topic

Amazon Alexa integration

How to change attributes of a discover mqtt entity? forever to static

$
0
0

@pergola.fabio wrote:

Hi i am playing with a docker image that publishes an alarm control panel with mqtt autodiscovery
so when i start HA, and afterwards the docker, it creates automaticy an entity, in my case an alarm_control_panel

but how to change the attributes, so its really static forever?
in example screenshow below, the arm_code_required = true, i want it to make it false forever?

if i change it there, after a reboot, the config is lost

thnx!

Posts: 9

Participants: 2

Read full topic

Zigbee2mqtt update with OTA

Remove old devices

Trouble with Aeotec Nanomote Quad - HA on UnRAID Docker - missing zwcfg_*.xml?

$
0
0

@FWSpider wrote:

Hi everyone, hoping someone can shed a little light for me. I’m running HA 0.106.0 in Docker hosted on UnRAID, Vera Plus as z-wave hub.

I am trying to configure the Aeotec Nanomote Quad to activate Scenes in HA. The remote is added in Vera, and I can see one “sensor.quadmote1_1_21” in HA under the Vera integration.

That’s about as far as I’ve gotten. I have seen the documentation with the xml data to add to zwcfg_*.xml, but, I don’t seem to have one. I have a zwcfg.xsd, but no .xml, even after shutting down HA.

Anyone have any idea what I’m missing?

Posts: 1

Participants: 1

Read full topic

Display number of lights turned on i a group

$
0
0

@r1kkie wrote:

Hi,

Anyone now how to display how many lights in a group that are turned on?
Either a template sensor or preferably embedded in a custom:button-card under label or custom_varible.

- type: custom:button-card
  template: device_button
  entity: group.livingroom_lights
  name: Lampor
  label: >
       [[[ *code for displaying number of lights turned on* ]]]

Posts: 9

Participants: 3

Read full topic


How to send notification to the HA App

Script / Automation issue

$
0
0

@r.steyn wrote:

Once again I am stuck with an automation that just does not seem to want to run, I am trying to setup an automation, that whenever my “Garage Door” switch is toggled, that it sends me a notification via Push Bullet.
Now if I setup the automation and test the automation it works, however on my front end, when I toggle the switch, the switch activates activated, but the automation does not run.

setup is as follows:

WEMOS D1 mini setup with ESP Home:

switch:
- platform: gpio
  id: relay_1
  pin:
    number: GPIO5
    inverted: False
  restore_mode: ALWAYS_OFF
- platform: template
  name: "Garage Door"
  icon: "mdi:garage"
  turn_on_action:
  - switch.turn_on: relay_1
  - delay: 1s
  - switch.turn_off: relay_1

- platform: gpio
  id: relay_2
  pin:
    number: GPIO4
    inverted: False
  restore_mode: ALWAYS_OFF
- platform: template
  name: "Car Port"
  icon: "mdi:garage"
  turn_on_action:
  - switch.turn_on: relay_2
  - delay: 1s
  - switch.turn_off: relay_2

- platform: restart
  name: 'Garage Door REBOOT'

Entities Card on HASSIO Front end:

entities:
  - entity: switch.garage_door
  - entity: switch.car_port
  - entity: switch.garage_door_reboot
show_header_toggle: false
title: Garage
type: entities

Automation:

device_id: ad490433ae6f40f2a2e05173c7448960
domain: switch
entity_id: switch.garage_door
platform: device
type: turned_on
data:
  message: test
service: notify.phone

am I missing something?

Posts: 7

Participants: 2

Read full topic

Automate Running a Bath

Run Hass OS on VM on Raspberry Pi

$
0
0

@ob2s wrote:

Is this possible with the ubuntu for Pi loaded ? It is a Pi 4 4GB RAM W/ 32GB SD card.

Posts: 1

Participants: 1

Read full topic

Problem with Automation data_template :/

$
0
0

@Rollo wrote:

Hello, I get an error message and do not know what to do and need help pls:

Message malformed: expected a dictionary for dictionary value @ data[‘action’][0][‘data_template’]

data_template: >-
  {% if is_state('binary_sensor.khlschrank', 'off') %}
    message: 'Kühlschrank geschlossen'
  title: 'ENTWARNUNG!'
  {% else %}
    message: 'Kühlschrank offen'
  title: 'WARNUNG!'
  {% endif %}
service: notify.notify

Posts: 7

Participants: 4

Read full topic

Monitoring wifi bulbs

$
0
0

@Unthred wrote:

Hi All,

I recently installed a whole bunch of bulbs that I have flashed with esphome. I seem to be having some issues so I have a bunch of questions.

  1. When I reboot HA it can take 10 - 15 mins for all the bulbs to be connected, Is this considered normal? I wondering if I need to revise my expectations. There are around 80 bulbs.
  2. Sometimes I can see the bulb is connected to my unifi access point but HA thinks its unavailable, is there any way I can make HA retry connecting to it? eventually it will reconnect without any action on my part.
  3. Is it possible to determine real lights from light groups? I would like to create (dont know how yet) a routine to show any bulbs that are unavailable and possibly time how long it takes for them all to get connected after I restart HA.

Thanks All

Posts: 2

Participants: 2

Read full topic

InfluxDB setup questions on HASSIO on RPI4

$
0
0

@not_a_coder wrote:

I don’t understand the instructions for installing Influxdb and hope someone can help me. I used the Supervisor Addon store to install it. I left the config as default

reporting: true
ssl: true
certfile: fullchain.pem
keyfile: privkey.pem
envvars: []

I have SSL and the certfile and keyfile are in the SSL folder of HASSIO and when I click on Open Web UI I get an InfluxDB menu so I am guessing all is good up to there.

The menu on the left has Status, Host List which is empty, Explore which has http://localhost:8086, Dashboards which is empty, Alerting, Log Viewer, InfluxDB Admin which has _internal and users that I have never added, and Configuration which has http://localhost:8086. If I click on http://localhost:8086 in Configuration I have several options some of which are already filled out. They must be default settings since it is not info that I have entered.

What are my next steps in order to get data from sensors that I have in HASSIO? Am I supposed to change the Configuration within the InfluxDB Web UI? Or do I just create Queries and if I am supposed to create Queries where can I find instructions that use HASSIO sensors as examples?

Posts: 2

Participants: 1

Read full topic


Emulated Hue - Error handling UTF Characters

$
0
0

@yonz2 wrote:

I just setup the emulated hue component. Basically it works, however I use “expose_by_default: false” and provide a list of devices to expose:

entities:
    light.kueche_gruppe:
      name: "Küche"
      hidden: false
    light.schreibstube_2:
      name: "Büro"
      hidden: false

so far so good.
When I now add the devices to Alexa, all entities with “ü” in the name appear twice. This seems to have somethingh to do with the handling of UTF-16 characters
In the JSON retuned by “http://hassio/api/pi/lights”. I get this:
{“manufacturername”: “Home Assistant”, “modelid”: “HASS123”, “name”: “B\u00fcro”,
“state”: {“bri”: 254, “mode”: “homeautomation”, “on”: true, “reachable”: true},

In the Alexa App on my Phone I see the light twice: “Büro” (Correct) and as “Büro”

Is there any way to correct this?

Best regards
Yonz

Posts: 1

Participants: 1

Read full topic

Avoid blinds automations to trigger often

$
0
0

@smurfen wrote:

Hi!

My goal is to automate blinds based on combination daylight/sun measurements and temperature inside.
But want to avoid that blinds is going down/up often if measurements is changed rapidly within the tresholds, e.g. wind and partly clouded.
So i think maybe disable the automation that lowering the blinds for maybe 30 minutes after they have been raised and vice versa.
Here is my two automations (not tried yet), any idea to add functionality to achieve my goal?

- id: '1135415443654'
  alias: Blinds down
  description: ''
  trigger:
  - above: '8000'
    entity_id: sensor.lightlevel_40
    platform: numeric_state
  condition:
  - above: '24'
    condition: numeric_state
    entity_id: sensor.temperature_37
  - after: 07:00
    before: '21:00'
    condition: time
  action:
  - entity_id: scene.blinds_down
    service: scene.turn_on

- id: '5655454254784'
  alias: Blinds Up
  description: ''
  trigger:
  - below: '7999'
    entity_id: sensor.lightlevel_40
    platform: numeric_state
  condition:
  - below: '24'
    condition: numeric_state
    entity_id: sensor.temperature_37
  - after: 07:00
    before: '21:30'
    condition: time
  action:
  - entity_id: scene.blinds_up
    service: scene.turn_on

Posts: 1

Participants: 1

Read full topic

NMAP Specific Port?

$
0
0

@jriker1 wrote:

I am trying to figure out if my Xbox 360 is on or off and it does not respond to pings. Any ideas? This is what I found out. If I run nmap there are two ports that show active: 2177 and 3391. So if I run:

nmap -Pn -p 3391 192.168.0.21

It will return up. Won’t work without -Pn. Problem is after I turn the Xbox 360 off, it still returns up. Any idea why and other thoughts how to do this?

Posts: 2

Participants: 2

Read full topic

Delay on Broadlink Rm Pro+

$
0
0

@Hao_Vy wrote:

When I updated 0.106.2, my Broadlink Rm Pro+ delay ~10second. What should I do to fix it? thanks !!!

Posts: 1

Participants: 1

Read full topic

Cannot upgrade HA in a virtualbox

$
0
0

@SKAL wrote:

Hi all,
I have a virtualbox machine that I use for tests with a debian+HA installation.
Actually I run

leo@debian:~$ uname -a
Linux debian 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux
leo@debian:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

and I run a 0.106.0 HA.

I’m trying to upgrade to 0.106.2, but there is no way to do it.
Every time I get the following error:


20-02-28 23:29:12 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
20-02-28 23:29:12 INFO (MainThread) [hassio.core] Hass.io is up and running
20-02-28 23:29:26 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.106.2
20-02-28 23:29:26 INFO (SyncWorker_7) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.106.0 to homeassistant/qemux86-64-homeassistant:0.106.2
20-02-28 23:29:26 INFO (SyncWorker_7) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.106.2.
20-02-28 23:31:15 ERROR (SyncWorker_7) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.106.2 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.106.2: No such image: homeassistant/qemux86-64-homeassistant:0.106.2").
20-02-28 23:31:15 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
20-02-28 23:31:18 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize

Could you help me to fix it pls.

Thanks
SKAL

Posts: 3

Participants: 2

Read full topic

Viewing all 108915 articles
Browse latest View live


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