Hello! I’m trying to set automation to get parameter from MQTT broker and set the input boolean state. Here is my code:

  - alias: Test
    initial_state: true
    trigger:
      platform: mqtt
      topic: matrix/WiFiPanel-0/dta
    action:
      - service_template: >
          {% if {{trigger.payload.split(" ")[1].split(";")[0].split("|")[0].split(":")[1]}} == 0 %}
          input_boolean.turn_off
          {% else %}
          input_boolean.turn_on
          {% endif %}
        data:
          entity_id: input_boolean.switch_state

But it doesn’t work. I tried to modify it in different ways, but no luck. I’m getting this error in log:

Invalid config for [automation]: Service input_boolean.turn_"{{ 'off' if {% if {{trigger.payload.split(" ")[1].split(";")[0].split("|")[0].split(":")[1]}} == 0 else 'on' }}" does not match format <domain>.<name> for dictionary value @ data['action'][2]['service_template']. Got None. (See /config/configuration.yaml, line 56).

What I’m doing wrong?

3 posts - 2 participants

Read full topic

I am trying to populate my sensor’s data into InfluxDB. Sadly nothing is written from the sensor domain.
Everything else is written like binary_sensor, sun, etc but not sensor.

I have HA 0.115.6 and InfluxDB 2.0.2 installed separately.

In my configuration.yaml I basically tried every combination, starting from a basic config like this:

influxdb:
  api_version: 2
  ssl: false
  host: 192.168.0.102
  port: 8086
  token: *******
  organization: 7bb6f528e80d4962
  bucket: home_assistant
  max_retries: 3

And tried some other options for includes:

  component_config_glob:
    sensor.humidity_*:
      override_measurement: humidity
  include:
    entities:
      - sensor.humidity_living_room

And also just to include the domain:

  include:
    domains:
      - sensor

There is absolutely nothing in the logs. I even have this:

logger:
  default: warning
  logs:
      homeassistant.components.influxdb: debug

I currently have some AQARA humudity/temp sensors via Deconz.

What can I check or what could be the issue here?

1 post - 1 participant

Read full topic

Hello Thanks for reading this.
I am new in this so sorry if you miss some info.
I am making my first addon is shows up in my addon’s.
But it gives an error when installing.
The error is:
20-12-11 14:15:21 ERROR (SyncWorker_3) [supervisor.docker.addon] Can’t build local/aarch64-addon-hello_world:1: 500 Server Error for http+docker://localhost/v1.40/build?t=local%2Faarch64-addon-hello_world%3A1&q=False&nocache=False&rm=False&forcerm=True&pull=True&buildargs=%7B%22BUILD_FROM%22%3A+%22homeassistant%2Faarch64-base%3Alatest%22%2C+%22BUILD_VERSION%22%3A+%221%22%2C+%22BUILD_ARCH%22%3A+%22aarch64%22%7D&labels=%7B%22io.hass.version%22%3A+%221%22%2C+%22io.hass.arch%22%3A+%22aarch64%22%2C+%22io.hass.type%22%3A+%22addon%22%2C+%22io.hass.name%22%3A+%22Hello+world%22%2C+%22io.hass.description%22%3A+%22My+first+real+add-on%21%22%7D: Internal Server Error (“Cannot locate specified Dockerfile: Dockerfile”)

It is a Rasberry Pi.

image1449×198 10.3 KB

1 post - 1 participant

Read full topic

Using a config like:

# https://www.home-assistant.io/integrations/device_tracker.mqtt/
  - platform: mqtt
    devices:
      bose_quietcomfort_35_bt: ha_mqtt_hub/device_tracker/bose_quietcomfort_35/state

for several devices across instances (published on my Mqtt hub via mqtt state stream)

the device are tracked perfectly (if and when the legacy tracker

device_tracker:
  - platform: bluetooth_tracker

finds them.
However, this is in the states:

Schermafbeelding 2020-12-11 om 15.29.231402×466 41.7 KB

showing attribute source_type: gps which of course it isnt. It’s either MQTT, or preferably even bluetooth…

is this an implementation issue of the mqtt device_tracker, or a user error.

thanks for having a look

1 post - 1 participant

Read full topic

Hi everyone, I am new to Home Assistant and I have struggled through getting the basics up and running. I thought I would try the RomRider button card through HACS but I immediately ran into problems. Here is the instructions that I do not understand:

Installation and tracking with hacs:
1. Make sure the HACS component is installed and working.

2. Search for button-card and add it through HACS

3. Add the configuration to your ui-lovelace.yaml

resources:
  - url: /hacsfiles/button-card/button-card.js
    type: module

4. Refresh home-assistant.

I can not find the ui-lovelace.yaml file. And once I do find it, what ‘configuration’ do they want me to add to it?

Thanks
Sam (I am thinking this is going to be a long, slow painful road)

1 post - 1 participant

Read full topic

Hi! my city water utility provides a website (https://annami.aquahawk.us/) that shows water usage for our house. I would like to parse out the usage information into home assistant. They provide a really nice usage graph and leak detection.

When I try to add ‘a website’ through the gui, the website prompts me to login but then returns me to the home screen.

Could someone advise a better way to access this data through home assistant?

1 post - 1 participant

Read full topic

Dear community,

I am facing trouble with the startup of the KNX integration during the boot of HA.
In the log I see below error (showing up multiple times):

Screenshot 2020-12-11 at 15.57.531002×74 9.8 KB

Log details of the error:

Screenshot 2020-12-11 at 15.57.31971×599 90 KB

My configuration. yaml section:

knx:
  tunneling:
    host: '192.168.50.2'       # IP Gateway
    port: 3671
    local_ip: '192.168.50.5'   # HASS
  light: !include configuration/lights_KNX.yaml
  cover: !include configuration/covers_KNX.yaml

Just for reference (as may be related): after startup of HA, all lights work correctly and I can action the covers. However the covers’ state is NOT correctly reflected.

Can anyone please provide some guidance how to get rid of the error ?

1 post - 1 participant

Read full topic

Anyone can help me how to configure Aqara Opple 3 bands?
I am using Conbee ll and Z2M.
I have only 3 entities: actions, linkquality and battery state.
I can see that correct topics in Z2M logs.
I want to control IKEA tradfri two bulbs, sonoff basic, and cover.
How to do this? It is even possible?

1 post - 1 participant

Read full topic

Hi all,

My Issue
I have an Alarm.com branded T2000 thermostat which I’m having difficulties controlling. I have successfully added it to my Zwave network and can see four entities for it, but three are sensors (temperature, humidity, and battery level) and one is “unknown”, so I am unable to send commands to it as if it were a climate entity. The device is listed as “Building 36 Technologies Unknown: type=0001, id=0001”
I want to display the thermostat as an entity in Lovelace and control it using the GUI.

My Home Assistant Environment
I’m running Home Assistant 0.115.4 in a Docker on an UnRaid server.
My Zwave device is an AEON Labs ZW090 Z-Stick Gen5 US.

What I’ve Tried
Of course I rebooted my server and healed the Zwave network - this made no difference.
I referred to this old thread a lot but have been unable to resolve this issue so far: ADC T200-thermostat help
I’ve done some research and some people are saying that the device isn’t recognized by my instance of Open-Zwave and I need to update the device database. I checked the database online, and it does indeed include an entry for my thermostat. I am confused as to how to update the database though - apparently I need to edit manufacturer_specific.xml, but as I’m running in a Docker, I’m not sure how to edit this file, or if I even should. Am I confused about this step? Do I need to update Open-Zwave so that the device database is up to date, or is this a manual change that I need to make?

I believe that I need to make sure that Open-Zwave recognizes the thermostat properly as a climate device, and then I should be good to go. I just don’t know how to do this or configure it that way. Please let me know if any other details would be helpful.
Any assistance would be greatly appreciated.

2 posts - 1 participant

Read full topic

Hi All, I have the following, hope someone can help me.

In the logs of HA I found errors from my DSMR meter. Since my meter was replaced a couple of weeks back, I thought that was the case. (I still was receiving data). The old meter was DSMR 4 and the new Meter is a Landis &Gir E360 with DSMR 5. This interval between 4 and 5 is different what would explain the errors I saw (CRC errors if I remember correctly, but can’t look em up anymore).

Anyway, I deleted the “Netbeheer Nederland” integration in the GUI hoping that on a reboot it would add itself back in with the correct settings. It did not, but all my sensors are now gone and I cannot find any way to add the integration back in.

The configuration in the sensor part of my config was still there. I tried removing, rebooting, re-adding, reboot, different protocol versions, etc but nothing.

Any creative ideas here?

1 post - 1 participant

Read full topic

Hi there,

This could be a stupid question, but what is the difference between Mosquitto Broker Integration and Mosquitto Broker add-on on hassio (Supervisor section)? Should I use one of them or I need both of them? If they both use the 1883 port how is this working?
When I migrate from a installed version of HA to this HASSIO appliance on a raspberry 4, I adde the Mosquitto integration (needed for shelly and other) but that wouldn’t work until I have the add-on also added. However I see that the integration have 95 entities.

Pedro.

1 post - 1 participant

Read full topic

So I’m trying to connect to the VNC on my OpenZwave addon and it asks for a password. I’ve tried my home-assistant’s admin user password, but that gets denied… what’s the dang password here? None of the docs mention that I’ll get prompted for a password nor indicate what that could be or where it’s set up.

1 post - 1 participant

Read full topic

I’ve been trying to build my first simple automation and I keep getting this one error which I have no idea about.
Yaml is:

alias: Turn Office Lights On
  trigger:
    platform: state
    entity_id: binary_sensor.office_office_motion_178
    to: on

  action:
    service: light.turn_on
    entity_id: light.office_office_lights_160

- alias: Turn off Office Light
  trigger:
    platform: state
    entity_id: binary_sensor.office_office_motion_178
    to: off
    for:
      minutes: "3"
  action:
    service: light.turn_off
    entity_id: light.office_office_lights_160

The error is :
Invalid config for [automation]: expected str for dictionary value @ data[‘to’]. Got None. (See /config/configuration.yaml, line 14).

Clearly I am doing something stupid. Can someone please point me in the right direction.

2 posts - 2 participants

Read full topic

Hello, it’s me again

Problem:
I cannot for the live of me get the GPIO pins to work in Home Assistant. I feel like I’ve tried everything. ALL I NEED is an entity that will say “on” or “off” depending on the state of an output on an external device. It’s just a binary sensor. It should be simple. But it’s not, apparently.

• Hardware: RPi 3B+
• Home Assistant version: 0.118.5
• OS: HassOS 4.16
• My configuration. yaml:

binary_sensor:
  - platform: rpi_gpio
    ports:
      4: armed_state
      24: door_state
    bouncetime: 50
    invert_logic: false
    pull_mode: down

As you can see I am trying to use GPIO 4 and 24. As far as I understand I need to use the GPIO numbering aka the BCM numbering and not the actual pin numbers and that’s what I’ve done. I’m using a Sparkfun GPIO break out board on a breadboard that has BCM numbering on it.

Now my issue is that the state never changes. They are always HIGH. Even if I rip out everything and set the pull_mode to down, it is still high. Which makes no sense to me.

This is an illustration of the circuit:

It doesn’t work.

I then thought “I don’t trust this HA integration”, and went my own way about getting the values from the actual GPIO directory on the RPi. So I unexported GPIO 4 and 24 in /sys/class/gpio and tried to read the values like this:

binary_sensor:
  - platform: command_line
    name: armed_state
    command: "cat /sys/class/gpio/gpio4/value"
    payload_off: "0"
    payload_on: "1"
    scan_interval: 10
  - platform: command_line
    name: door_state
    command: "cat /sys/class/gpio/gpio24/value"
    payload_off: "0"
    payload_on: "1"
    scan_interval: 10

I didn’t know how to set the internal resistors so I made my own pull-up/pull-down resistor circuits.

This is an illustration of that circuit:

This did not work either. The value would now finally change from constantly HIGH to floating about. It probably sounds like my circuits were wrong but I was using the EXACT SAME resistor circuit 2 days ago on my old HA installation where it worked fine. If I cat the value file like I set up the configuration.yaml to do then I can see that value is flip flopping all over the place… What is happening? Is this circuit not correct? It should be pulled down through the 10k resistor when the relay is open but it doesn’t. I feel like I’ve had an aneurysm, I don’t understand why it’s not working.

Interestingly the first binary sensor “armed_state” on GPIO 4 will flip flop like it’s floating (it probably is, but I don’t know how) but the second binary sensor “door_state” does nothing whatsoever. It never changes state. It’s constantly low. Even if I change to a pull-up resistor, it’s low. Either I broke those GPIO pins or the HA messed something up.

Has ANYONE been able to integrate a simple binary sensor into their HA? I’ve been looking for examples of people’s work and have found none. Any help would be much appreciated. I’m just about ready to jump off a bridge.

1 post - 1 participant

Read full topic

Custom header is no longer maintained. I really liked the feature to change icon color based on a state or template. E.g. my plant tab icon turned red if flowers need water, etc.

Is there a way to achieve this without custom header?

Thanks

1 post - 1 participant

Read full topic

Hello. Here is my simple automation which turn on light and off 2 min after movement.

- id: Turn on Garage light when there is movement
  alias: Turn on Garage light when there is movement
  trigger:
  - platform: state
    entity_id: binary_sensor.garaz_motion
    to: 'on'
  condition: []
  action:
  - service: light.turn_on
    entity_id: light.garaz_swiatlo
  mode: single
- id: Turn off Garage light 2 minutes after last movement
  alias: Turn off Garage light 2 minutes after last movement
  trigger:
  - platform: state
    entity_id: binary_sensor.garaz_motion
    to: 'off'
    for: 0:2:00
  condition: []
  action:
  - service: light.turn_off
    entity_id: light.garaz_swiatlo
  mode: single

Everything works until I manually turn off light. I still need to wait 2 minutes to turn light automaticly.
In othe words:

• I open the doors and light turns on
• I close the doors wait 2 min and light turns off
  then
• I open the doors and light turns on
• I press button to turn off light
• I am still in garage and moving and light doesn’t turn on
• After 2 minutes light turns on

2 posts - 2 participants

Read full topic

Hi all,

I have just flashed a second Sonoff Zigbee Hub with Tasmota for my garage. The first one operates in the house under the ZHA integration and works perfectly.

I cannot figure out how to deploy the second hub. HA does not allow a second ZHA integration to be set up, and the first one is unique to the first hub (as shown by the IP address).

What I need, I think, is an architecture that allows a single ZHA integration to have two hubs within it, or for multiple instances of ZHA integration be set up.

I would be very grateful for any advice you may have on how I can get to where I want to be. The main use of the garage hub is for door and window sensors which are two far away from the house network.

Many thanks all.

1 post - 1 participant

Read full topic

I just got the tts.cloud_say setup in my automations but have a question. I can see the tts folder filling up with mp3 from the service. Is there a way to disable caching like with google_translate? If not, do these files get deleted automatically after awhile or will I need to create some kind of job to do that?

Thanks!

1 post - 1 participant

Read full topic

I have a few Zigbee devices (Xiaomi Aquara sensors, temperature, humidity, …) and some keep a 100% battery level a surprising amount of time (months) - still sending realistic data.

I recently changed my Zigbee hub and some of them did not want to join anymore. I bought a new set of batteries and they joined immediately (the blue light was brighter than usual too). So that would point to a weak battery.

The problem is that they report, with this new battery, only 31%. I tested another battery - again 31%.

So either the set I bought is old (these are store-bought VARTA batteries) but that would be surprising (and also the fact that two of them show the same 31%), or the battery level indication is wrong.

1 post - 1 participant

Read full topic

I’ve just received a NUC and as I have never used Proxmox, I decided to go that way and use the whiskerz007 script. I keep hearing how good proxmox is so thought I’d give it a spin. I’m just getting to grips with it and learning, I’ve got Home Assistant set up and working and I do like Proxmox so far!

But what is the difference between snapshots and backups and which one should I be doing? For example if my Hassio VM goes belly up and I need to nuke the VM and start again what is the correct way to restore the Hassio VM?

Leading on from that question, do I still need to take internal Hassio snapshots if I am taking snapshots/backups of the whole VM in Proxmox?

1 post - 1 participant

Read full topic