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

Once again upgrading OS hosed Z-Wave JS

$
0
0

Every single time I upgrade the HA OS the Z-Wave JS Add-On gets messed up and rather than rebuild it again I would really like to fix it as well as understand why this happens.

I am using a Zwave.me stick on a USB 3 port of a Raspberry Pi 4

My settings are still intact, but it fails to talk to the stick with the following info:

Failed to save add-on configuration, Device ‘/dev/serial/by-id/usb-0658_0200-if00’ does not exist in Z-Wave JS (core_zwave_js)

I have to assume that when I upgrade the OS something happens to the Device /dev/xxx. I assume if I can find the dang Device and replace it in YAML it would work but I can’t find it in Host Hardware. I did try /dev/ttyAMA0 for kicks, but I believe that is mapped to something else, maybe Bluetooth but in any event it fails.

Can someone point me in the right direction to correct this?

1 post - 1 participant

Read full topic


Range reduced after update of Deconz to 6.11.X

$
0
0

I Updated my deconz version from 6.10.0 to 6.11.0 and 6.11.1 and noticed one of my aqara humidity sensors is losing connectivity and not updating at all. Even when I manually push the button, the values wouldn’t update, but if I move the sensor closer to my conbee II, they start updating on its own. With the deconz 6.10.0 I never had this issue. Though the sensor and my conbee II are located at diagonally opposite ends, I would assume the issue would be present with deconz 6.10, if range was the only factor.
So my hardware is:
Conbee II plugged into a usb extension cable on raspberry pi 4
Sensor: Aqara humidity sensor model no: WSDCGQ11LM

Anyone else had this issue?

1 post - 1 participant

Read full topic

Template binary_sensor using weather

$
0
0

Hi,

I have the following template for binary_sensor:

template:
  - binary_sensor:
      - name: "Previsão de chuva nas próximas horas"
        icon: mdi:weather-pouring
        state: >-
           {% set c = namespace(chuva = false) %}
           {% for hora in state_attr("weather.damha_vi_hourly", "forecast")[:4] %}
             {% if hora.condition == "lightning_rainy" or hora.condition == "pouring" or hora.condition == "rainy" %}
               {% set c.chuva = true %}
             {% endif %}
           {% endfor %}
           {{ c.chuva }}

When I restart HA, I see no error on log, but it never finishes starting… It keeps saying that not all entities are already available. If I remove this template from configuration, HA starts with no problem or delay.

Is there anything wrong with this template?

Thanks

2 posts - 2 participants

Read full topic

Pulse Button Swith Help pls

$
0
0

I’m starting my first setup on HA.

already have some KNX devices working. but i’m struggling now to create a pulse switch.
Have some doors with electric pulses (main door, garage door, street door, etc) and have read and watched some videos for
this kind of triggers in HA and I have no more ideas what is wrong:
I have this yaml:

SWITCHs

- name: "Main Door"
  address: "1/0/10"
  state_address: "1/0/100"

TRIGGERS

automation:

  • trigger:
    platform: state
    entity_id: switch.main_door
    to: “on”
    for: “00:00:01”
    action:
    • service: switch.turn_off
      entity_id: switch.main_door

what is wrong here?
first i can’t understand how the trigger knows the switch entity_id, but if I try to add it in the UI it appears as switch.main_door, so.
Already tried to put an entity_id in the switch but it raises an error while chekhing the yaml file.

thanks in advance

1 post - 1 participant

Read full topic

XIAOMI VIOMI V9 integration

$
0
0

Hi All

I can’t add my new VIOMI V9 in Home Assistant
Somebody had the same issue?

I’ve tried many solutions but none seems working.

Thanks!
Ciao

1 post - 1 participant

Read full topic

Cannot access websockets over DNS

$
0
0

Hi, I’m trying to configure remote access to my Homeassistant through NGINX reverse proxy. I have set up port forwarding and the proxy and everything seems to work except websockets.

My Homeassistant is running on port 8123 and NGINX is running on 80 and 443 with Let’sEncrypt SSL certificates.

When I try to access Homeassistant through local IP over https on port 443, everything works, websockets and all, but when I try to access it from the internet via DNS I can’t connect to a websocket. Static files are working fine, only websocket is unreachable, in the web developer tools in my browser I get no response for the websocket request so I’m guessing it’s timing out.

Do you have any ideas why this might be? I thought maybe router settings but since both ports 443 and 80 work that hopefully shouldn’t be a problem.

1 post - 1 participant

Read full topic

Is a new template entity required to do some minimal changes to an entities value?

$
0
0

I have a numerical input helper. This helper has a step size of 1, so it only ever shows integers. However, it always shows up as x,0. Not a huge deal, but it annoys me (probably more than it should).

I’ve been looking around, and it seems like this can only be fixed by creating a new template entity in the configuration file, something like this:

- sensor:
  - Name: "test"
    value_template: "{{ states('input_number.test') | int }}"

If this would be reusable, and these three lines could be applied to multiple numerical inputs, that would be acceptable, but having to copy/paste this section for every numerical input I have? There has to be a better way.

So, is there an easier way to slightly modify the value of an entity?

1 post - 1 participant

Read full topic

Combined Lock Entity?

$
0
0

I’m very new to yaml, so bear with me…Is it possible to create a sensor/entity that’s a combination of a sensor and a lock status. I have a yale YRD 256 lock. One of the entitys (lock.lock_front_door) will report if the door is locked or unlocked…and another sensor (binary_sensor.lock_front_door_access_control_locked_jammed) will report if the lock is jammed or not. It’s a combination of a door lock and door open sensor.

My goal is to create a sensor that I can view on my lovelace dashboard that will report the status of the door:

  • “Open” when door sensor is open
  • “Locked” when door sensor is closed and door lock is locked
  • “Jammed" when deadbolt isn’t seated properly.

Any guidance would be appreicated!

1 post - 1 participant

Read full topic


Shelly1PM water heater wiring

$
0
0

Im having difficult figuring out how I need to place the Shelly1PM in between my power and water heater.

Below is how it currently is and how far I got on the schematic with the Shelly1PM in between. Can someone finish it for me?


3 posts - 3 participants

Read full topic

Nortek HUSBZB-1 - At my whit's End

$
0
0

Hi All,

I recently purchased the above stick due to it being highly recommended. After getting it setup (aka - plugged in), I stood up my first few Zigbee devices to test. Everything seemed to work, but overnight the controller went offline (though Z-Wave stayed up). After looking into it, I’ve applied the various fixes that I found online, all to no avail.

  • Used a USB extension to move the dongle away from interference - No Change
  • Tried various ports and USB extension cables - No Change
  • Updated the firmware to the latest available - No Change
  • Changed my AP’s channels to not interfere with Zigbee - No Change
  • Changed the channel within HA to 11 - No Change

To be fair, despite increasing the logging, I can’t see if the stick has accepted the new channel, though I did delete the integration and recreate to be safe. I am honestly out of ideas and am considering just getting rid of the stick and purchasing to separate ones to save myself the headache. This is a hail mary in case I missed something obvious.

Thanks in advance!

~Spritz

1 post - 1 participant

Read full topic

Why Sonoff disappeared from HA

$
0
0

Why Sonoff disappeared from HA
I apologize for my English, I am from Ukraine.
prompt in which folder you need to install the “custom_components” folder
and of course the component itself is SonoffLAN.
For some reason he disappeared from the store?
on my Debian 11, Doker, Home Assistant,

  • Hass.io “Home Assistant Supervised”.

1 post - 1 participant

Read full topic

Automation with visual editor: Error: extra keys not allowed @ data['domain']

$
0
0

Hi,

i made a pretty simple automation for locking door after 22:00.

alias: Automatisk låsing av dører kl. 22:00
description: Automatisk låsing av dører kl. 22:00
trigger:
  - platform: time
    at: '22:30'
condition: []
action:
  - device_id: de260b43ba2b0e42e0009bd8824f75d8
    domain: zwave_js
    type: set_config_parameter
    parameter: 1
    bitmask: null
    subtype: 49-112-0-1 (Door lock mode)
    value: 3
  - device_id: 832099209b7d4b601d9c0c4b2449580e
    domain: zwave_js
    type: set_config_parameter
    parameter: 1
    bitmask: null
    subtype: 48-112-0-1 (Door lock mode)
    value: 3
mode: single

When testing, i got an error “extra keys not allowed @ data[‘domain’]”
im lost, since here was none coding by my self. Whats the reason ?

1 post - 1 participant

Read full topic

Create timer with Hue remote

SSH e Home Assistant Core

$
0
0

Hi:

I have a HA Core installed on a PI 4 and I was interested in accessing trough SSH a OpenWRT to execute operations. However, outside HA Core everything runs well but inside HA Core no, I had the famous error 255. After some digging I managed that to work and I am putting here may experience.

The first phase is the normal one, I created the private and public keys using PuttyGen and I use the private on my SSH client and the public I upload it trough OpenWrt Luci Portal but copy it from the PuttyGen Screen APP because the generated file is not accepted by SSH on OpenWRT. IS according to my understanding format issues.

The private key I need to export it on PuttyGen as a OpenSSH format because the default format is not accepted by SSH client on PI 4. And I put the private key on /root/.ssh with its default name, id_rsa and the file permissions as 600, because if the files permissions was others this does not work. Must be access only by root.

So, with this the following line works perfectly

ssh user@ip ‘comand’ (The command inside comas)

However, if I try running this inside HA Core trough Shell Command this does not work. And, after some investigation I managed to do that with the following steps:

  • The private key must be on another folder, a folder inside the homeassistant main folder, the /home/homeassistant/.ssh/id_rsa because the SSH client invoked by HA Core apparently can not access the key on /root/.ssh
  • The permissions must be less restrictive, so must be 0664
  • Copy the sshhosts file to this folder also.

And now the new commando will be:
ssh -i /home/homeassistant/.ssh/id_rsa user@ip ‘command’
The -i option tell do client to find the private key on another folder.

With this works perfectly.

Also, if you need to debug a little more I recommend the following command:
logsave /tmp/debug.txt ssh -v -i /home/homeassistant/.ssh/id_rsa user@ip ‘command’

  • The logsave is an application that catches everything for stdout and write to a file, in this case on /tmp/debug.txt
  • the -v option on ssh command tell ssh to enter in debug mode a write everything on stdout.

I hope this can help others because I did not find any help on this here and others places.

Best regards

CGR

1 post - 1 participant

Read full topic

MQTT Sensor not working

$
0
0

I configured the MQTT Broker integration and i defined some sensors. I tested the connection with MQTT.fx where i got the results I expected. But in HA the sensors says “not available”.
The binary_sensor.mosquitto_broker_running says “running”.
Here’s my configuration.yaml

#
mqtt:
  broker: 192.178.xxx.xx   #mqtt 
  port: 1883
  certificate: auto



sensor:
  - platform: mqtt
    state_topic: Schlafzimmer/Luftfeuchtigkeit
    name: "Schlafzimmer-Luftfeuchtigkeit"
    icon: mdi:water-percent
    unit_of_measurement: "%"
  - platform: mqtt
    state_topic: Schlafzimmer/Temperatur
    name: "Schlafzimmer-Temperatur"
    unit_of_measurement: "°C"
  - platform: mqtt
    state_topic: Schlafzimmer/Fenster
    name: "Schlafzimmrt-Fenster"
    icon: mdi:window-open
  - platform: mqtt
    state_topic: "Schlafzimmer/Batteriespannung"
    name: Schlafzimmer-Batteriespannung
    icon: mid:power-plug
    unit_of_measurement: "V"

I doublecheckt the IP & Port. It works with MQTT.fx
What do I miss?

1 post - 1 participant

Read full topic


Hive Heating Script/Automation

$
0
0

Hi everyone - just started out using Home Assistant, and looking at some automation with Hive heating. One thing that has always bugged me about Hive heating is that when the heating is on, the boiler will constantly remain on until the target temperature is reached. What my previous “dumb” thermostat did was let the boiler run for 20/30 mins so that the radiators are hot, and then switch off the boiler for 10 mins to use the ambient heat being generated from the radiators and then turn the boiler back on again and the cycle would continue. What this did is save on the amount of gas used, as the ambient temperature of the radiators is used to heat the house between boiler “pauses”.

I would like to create a script or an automation to do something similar, but not really sure how if or how this could be achieved. So for an hour boost script for example I would perhaps turn the heating on for 25 mins and then pause for 10 mins and then turn the heating on for 25 mins.

Any help or tips appreciated.

1 post - 1 participant

Read full topic

Change to Senic Switch (via hue) switching options?

$
0
0

For some time I’ve been using Senic Switches in our HA setup to trigger scenes (using them to switch on / off input boolean which then triggers a node red sequence for things like cinema room start up etc). These were always integrated into our HA via Hue, as the switches were added to hue for light control and we rode on the back of that for scene control.

All was working well and it made these switches way more powerful than they would otherwise be.

I have however recently noticed that the option for the 2 button press in HA has vanished, all options are not just a single button press (be that short, long or release), this has removed a chunk of useability from our system. I can’t see anyway to get that back either.

We’re using ZHA as our zigbee controller so I’m wondering if there is a change there or if its more to do with how HUE are handling these ?. As far as a I can see all double button presses programmed into hue are still there.

anyone got any ideas ?

1 post - 1 participant

Read full topic

MQTT Cover - how to split position payload?

$
0
0

Hi,
I like to set up my system so that there is some kind of “subsystem”, that manages the complete control for 8 window blinds/covers. It controls the switches, calculates positions and so on.

This subsystem shall communicate to my HA instance.
It will report the position of all 8 covers in one single MQTT message as a string where the individual positions are separated by a separator character (’;’ for example).
This means the position message sent by the subsystem to my HA instance will look like this:

home/windows/covers/positions/[12;87;100;69;0;47;78;55]

Now my python skills are less than limited. I think I can extract the position for the individual covers by a template. But I just don’t know how.
This is my current config for 2 of the 8 covers:

- platform: mqtt
  name: "first"
  command_topic: "first/window/cover/position/set/"
  position_topic: "home/windows/covers/positions/"
  set_position_topic: "first/window/cover/position/set/"
  payload_open: "100"
  payload_close: "0"
  payload_stop: "-1"
  state_open: "100"
  state_closed: "0"
  position_template: |-
  { here is where I don't know how to extract the FIRST position (12) from the payload }

- platform: mqtt
  name: "second"
  command_topic: "second/window/cover/position/set/"
  position_topic: "home/windows/covers/positions/"
  set_position_topic: "second/window/cover/position/set/"
  payload_open: "100"
  payload_close: "0"
  payload_stop: "-1"
  state_open: "100"
  state_closed: "0"
  position_template: |-
  { here is where I don't know how to extract the SECOND position (87) from the payload }

Might be just a single python line - but currently still beyond my knowledge… :confused:

Thanks and greetings!

1 post - 1 participant

Read full topic

BE369 Lock

$
0
0

I have a Schlage BE369 smart lock that I would like to pair with my ZWave stick.

I know there are a few threads about this already, but I have no idea how to add a network key, or even generate the necessary key.

I assume this lack of a network key is why my light flashes red when I try to pair the device…

Any help on how to generate the key and get it in the proper configuration file is appreciated!

2 posts - 2 participants

Read full topic

3 out of my 4 Fibaro Dimmer2 are not reporting local switch status quickly, but one does

$
0
0

I’ve got 4 dimmer2 devices that respond correctly when switching remotely. However if I switch them locally, then 3 of them do not update status in HA, yet one does. I do not know if this has always been the case, because I have only just tried using an automation where rapid update of status is necessary.

I have tried re-interviewing the nodes, but made no difference.

I am using Z-wave JS to MQTT v 0.32.2 on a Pi. MQTT is on a different machine.

Any other pointers I can try to diagnose? The devices are just over a year old and were all bought at the same time.

Cheers

1 post - 1 participant

Read full topic

Viewing all 106204 articles
Browse latest View live


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