Hi, I recently bought a ITead Sonoff Zigbee 3.0 USB Dongle. I have problems connecting this dongle to my Home Assistant installation.

I installed home assistant on a nuc using docker on ubuntu server 20.04. I start docker like this:

$ sudo docker run -d --name="home-assistant" --privileged --restart always -v /home/nerd/homeassistant/config:/config -v /etc/localtime:/etc/localtime:ro -v /dev:/dev -v /dev/ttyUSB0:/dev/ttyUSB0 --net=host ghcr.io/home-assistant/home-assistant:stable

This works flawlessly.

Both inside and outside the docker container the device is shown as:

/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_76b207dc82c9eb11adf58f4f1d69213e-if00-port0

In the Home Assistant interface I try to add it as an integration. So I click on “Add integration” and choose “Zigbee home automation”. ZHA shows me the serial device path of the interface, which I select. After that I choose “ZNP” and it seems like Home Assistant starts to add it. However, in the end this final step fails and I get the message “Failed to connect”.

Does anyone know what I might be missing?

Kind regards,

Samnang

1 post - 1 participant

Read full topic

Hello,

I have a question about how to best configure the following
I have a wall switch with 2 buttons and a wifi dimmer bulb.
both flashed with tasmota.
Now in HA I want to have them working together, so Something with the light entity.
but the status and toggle action should be overruled with the one of the wall switch.

this way, I would still be able to always tun on of the bulb using the swicht, If I don’t have my phone with me.

Now I have them configured as 2 separate entities, but when I accidentally turn off the bulb I won’t be able to turn it on using the wall switch.

does anyone has any suggestions for me for how to approach this?

1 post - 1 participant

Read full topic

Hi, the check says:

Error loading /config/configuration.yaml: while parsing a block collection
  in "/config/configuration.yaml", line 17, column 5
expected <block end>, but found '?'
  in "/config/configuration.yaml", line 30, column 5

My yaml file:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
sensor: !include sensors.yaml
discovery:

waste_collection_schedule:
  sources:
    - name: ics
      args:
        file: "www/Heichelheim.ics"
      customize:
        - type: Gelber Sack
          alias: GelberSack
          icon: mdi:recycle
        - type: Hausmüll
          alias: Restmuell
          icon: mdi:trash-can
        - type: Altpapier
          alias: PapierTonne
          icon: mdi:trash-can-outline
    fetch_time: "7:00"
    day_switch_time: "7:30"

So whats wrong with it?

1 post - 1 participant

Read full topic

I have added one of my ESPHome powered sockets to the energy dashboard. ESPHome v2021.11.1.

Added the ‘platform: total_daily_energy’ sensor defined in ESPHome to my energy dashboard in HA.
Everything with energy metering and energy dashboard worked as expected. Until the end of December.
On 12/26/2021 I disconnected the socket from mains. And reconnected it again on 01/12/2022.

But no I get negative readings for this energy sensor.

I have checked data in database statistics table. Last sum value stored in 2021 before disconnect from mains is for 12/26/2021 (value is around 9.96… kWh).
The next row in database statistics table is for 01/10/2022 (after connecting the socket to mains). But sum value from than on is 0.00 kWh.

And energy dashboard is starting with negative value of -9.96 kWh. And is counting towards zero with new energy readings added to the database.
So if I have a consumption of 9.96 kWh in 2022 the energy dashboard will show a total consumption of 0.0 kWh.

Why is the sum reset to zero after connecting the socket?
Is there a way to fix the energy meter without loosing all stored data?
And what could I do to prevent this?

Here is a short excerpt from the statistics database table:

id,created,metadata_id,start,mean,min,max,last_reset,state,sum
719084,2021-12-26 21:00:22.245360,260,2021-12-26 20:00:00,,,,,0.0,9.96099999999984
806669,2022-01-10 18:00:20.175615,260,2022-01-10 17:00:00,,,,,0.0,0.0

the next rows with a sum value are:

810163,2022-01-11 06:00:20.926270,260,2022-01-11 05:00:00,,,,,0.001,0.001
810454,2022-01-11 07:00:21.180125,260,2022-01-11 06:00:00,,,,,0.109,0.109

Ulrich

1 post - 1 participant

Read full topic

I installed DuckDNS following the official guide and tried to set up SSL with Let’s Encrypt
But when I open my DuckDNS URL in a browser the page doesn’t load (err_connection_timed_out)

Image may be NSFW.
Clik here to view.
Image may be NSFW.
Clik here to view.

Eero config:

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

No error in the logs:

Image may be NSFW.
Clik here to view.

SSL certificate is invalid?
Image may be NSFW.
Clik here to view.

1 post - 1 participant

Read full topic

Hello Guys,
i would love to get your help and the Devs help here with something, long story short, i just bought a water heater switch (Switcher V4) which i found the integration for it, the problem is that its very limited,
also, i have a Service called switcher_kis.turn_on_with_timer but i cant use it in the lovelace card.

Image may be NSFW.
Clik here to view.

can you guys help setting this up please ?

1 post - 1 participant

Read full topic

Hi,

I configured an OpenMQTTGateway to handle RF2 codes of my remote
My remote ( flamingo sf-501) has 4 rows of 2 buttons (and one “master” row with 2 buttons):

Image may be NSFW.
Clik here to view.

When I press a button, following information in coming in

{"unit":2,"groupBit":0,"period":267,"address":52166656,"switchType":1}

• address: the ID of my remote (I have multiple remotes, they all have different ID’s)
• unit: number from 1-4, depending on the button I pressed
• switchType: 1 = on, 0 = off

I managed to create a simple automation:

  - id: omg_rf2tomqtt_52166656_1_1
    alias: omg_rf2tomqtt_52166656_1_1
    trigger:
      - platform: mqtt
        topic: "home/OpenMQTTGateway_ESP8266_RF2/RF2toMQTT"
        payload: "52166656"
        value_template: "{{ value_json.address }}"

    condition:
        condition: template
        value_template: "{{ trigger.payload_json['unit'] == 2 }}"

    action:
    - data:
        entity_id: light.my_n00_p01_light_l23_marokko
        transition: 0
      service_template:
        homeassistant.turn_on

Now my question is: what’s the best way to handle multiple conditions and actions:

I need an automation that does something like

case address == 52166656 AND unit == 1 AND switchType == 1
  turn on light A
case address == 52166656 AND unit == 1 AND switchType == 0
  turn off light A
case address == 52166656 AND unit == 2 AND switchType == 1
  turn on light B
case address == 52166656 AND unit == 2 AND switchType == 0
  turn off light B

etc…

What’s the best way to implement this?
Do I need multiple automations? Multiple conditions?
Can anybody point me to a simple example for this case?

kind regards,
Bart

1 post - 1 participant

Read full topic

Whenever I restart HA or reload the ZHA integration, I get the following two errors in my log (the other lines are what come immediately before & after the warnings):

2022-01-17 15:09:49 DEBUG (MainThread) [zigpy.appdb] Current database version is v7
2022-01-17 15:09:49 DEBUG (MainThread) [zigpy.appdb] Loading application state
2022-01-17 15:09:49 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57344
2022-01-17 15:09:49 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57345
2022-01-17 15:09:49 DEBUG (MainThread) [zigpy.appdb] [0xc43c:1:0x0000] Attribute id: 4 value: Securifi Ltd.

I am thinking it started after I unplugged a zigbee smart plug midway through an OTA firmware update. I had a Securifi Peanut Plug that I attempted to upgrade firmware on but it was taking way too long (I forgot to move it closer to my controller). I unplugged it midway through flashing, and attempted to flash it again several times but it stopped at 59% every time. I thought the cluster 57344 might be the cluster it kept failing at, but I don’t remember now and those logs are gone. When I attempt to reflash the plug now it won’t even initiate. For what it’s worth, I flashed 3 other peanut plugs successfully after that problem.

Anyway, I don’t care about the plug. The problem is that even when the plug is removed from the zigbee network and unplugged from the wall, and my HA is rebooted, I still get those two warnings in my log upon restart. I don’t know how to get rid of them, and I don’t know if they are causing any issues or not.

1 post - 1 participant

Read full topic

Hi,
one of my sensors on the gas meter was offline for one day. I know what’s missing since I can read the meter manually.

Is there any possibility to add the lost data in energy management?

1 post - 1 participant

Read full topic

I’m getting an “uncaught” error every time HA boots up. Anyone have any idea what this might mean or how I would go about getting more information on it? Since this is a front end issue, should I be looking at my lovelace dashboards?

Logger: frontend.js.latest.202112291
Source: components/system_log/__init__.py:189
First occurred: 4:09:54 PM (1 occurrences)
Last logged: 4:09:54 PM

http://192.168.1.100:8123/config/server_control:0:0 Uncaught

1 post - 1 participant

Read full topic

Hi all,

I have been racking my brain and I am new to this however I have got several things working and this one baffles me.

In short i have a internal motion sensor connected a shelly 1, the sensor goes ‘on’ and my automation begins, the light turns on for 13 seconds and then turns off. It also has a condition being that if the switch on the dashboard is turned on then the automation wont work, essentially creating a master override for permanent light on.

The problem is the shelly 1 has a binary sensor which confirms if the ‘input sensor’ has received power from the motion sensor, creating the ‘on’ and ‘off’ status which stops my automation for staying on for longer. Say i pass through the hallway the sensor lights up the hallway for 13 seconds, brilliant but just in case i am in the hallway vacuuming then the light still turns on after 13 seconds. I need to somehow incorporate a line that says 'if the sensor is ‘on’ then the light will stay on until the sensor goes to ‘off’ when no motion is detected. so walking through hallway 13 seconds is acceptable but longer time in the hallway means the light should turn off after i leave, say 13 seconds after or even 3 seconds to be perfect.

here is my code below, i have used the automation section via configuration not coding so please understand my knowledge around coding is limited.

alias: Master Downstairs Hallway
description: ‘’
trigger:

• platform: state
  entity_id: binary_sensor.shelly1_cx_input
  from: ‘off’
  to: ‘on’
  for:
  hours: 0
  minutes: 0
  seconds: 0
  milliseconds: 0
  condition:
• condition: device
  type: is_off
  device_id: DELETED THIS AS NOT SURE IF IT IS SAFE TO DISPLAY
  entity_id: switch.shelly1_cx
  domain: switch
  action:
• type: turn_on
  device_id: DELETED THIS AS NOT SURE IF IT IS SAFE TO DISPLAY
  entity_id: switch.shelly1_cx
  domain: switch
• delay:
  hours: 0
  minutes: 0
  seconds: 13
  milliseconds: 0
• type: turn_off
  device_id: DELETED THIS AS NOT SURE IF IT IS SAFE TO DISPLAY
  entity_id: switch.shelly1_cx
  domain: switch
  mode: single

any help would be appreciated, i end up in the dark sometimes and then have to walk to another room turn on the light via an ipad dashboard.

Thank you in advance.

1 post - 1 participant

Read full topic

I have a light group setup in the configuration.yaml and it works as expected except for one thing. I want the group to be “on” only if ALL the lights in the group are on. Currently, if I separately turn on 1 or 2 of the lights in the group, then the whole group already shows “on”. Is there a way to change this?

light:
  - platform: group
    name: Lamps
    entities:
      - light.bar_lamp
      - light.can_lights_dimmer
      - light.dining_room_lamp
      - light.entryway_lamp
      - light.kitchen_lamp
      - light.living_room_lamp
      - light.piano_room_lamp

1 post - 1 participant

Read full topic

I am having trouble with 1 of my internet radios (Sangean). When Home Assistant “discovers” the radio, it causes their app to crash (disconnect). This happens ever 3-6 seconds… I sent Sangean my logs and they see HA connecting. Pretty sure it’s the DLNA integration that is the cuprite because it’s sees the Sangean, my Yamaha’s (even though I am using the music cast integration) plus my Logitech radios. I have told HA to ignore, tried enabling then disabling, yet it keeps polling Is there any way to disable this?

Thanks

1 post - 1 participant

Read full topic

Hi Im trying to use DialogFlow with my HA, and its kinda working, but…there is a wierd problem. Nabu Casa Cloud is just to glitchy. Some time it works, some time it dont. Thats why I manualny add my google assistent integration (I have Nabu cass subscription active). So my question is:
Where can I find correct fulfillment url that I need to put in google DialogFlow? Dialogflow HA integration only points me to Nabu casa one, I want to use my duckdns.org link. Any Ideas? Thanks

EDIT:
Sorry found my error, forgot to add :8123 to URL Image may be NSFW.
Clik here to view.

1 post - 1 participant

Read full topic

I have an automation that access the stored png image in the /media/local/ folder, but every time Home Assistant restarts, the token changes.

https://10.0.1.100:8123/media/local/camera/image/image.png?authSig={long_lived_token}

I tried using a long lived token I created, but it gives me a 401 unauthorized error. I actually don’t need need a token for this as my Home Assistant is not accessible outside the network.

Is there a way to get this working? How do I use this long lived token that doesn’t work with the png link? Or is there a way that I can just access the link without using any token?

I tried whitelisting, but this doesn’t work.

allowlist_external_dirs:
  - "/media"

1 post - 1 participant

Read full topic

Hi all. It is possible to update a card from time to time. Being able to enter a template from time to time to be able to verify something?

1 post - 1 participant

Read full topic

Hi everyone, I have EnvisaLink 4 attached to my DSC panel. Would like make changes…

1. How I can have sensors icon changed based on state? Right now I defined manually in the card
2. For each sensor, now it show’s the last update. Every time I restart RAAS it will reset. Is it possible to put last updated time by tagging hour/date

Image may be NSFW.
Clik here to view.

1 post - 1 participant

Read full topic

Hi,

I am trying to mount an Android wall tablet near the front door which can have the alarm panel displayed as well also have few other dashboards from Home Assistant. Currently I have a MPD player working on another Ubuntu machine but it is little far from the front door so I had the bright idea of installing MPD on the Android tablet ( From Android store ).

After MPD installation on the Android tablet, I tried executing following under Developer Tools => Services:

service: tts.google_translate_say
data:
  entity_id: media_player.tablet_mpd
  message: Hello!

There is no sound on the tablet for above commands and I also see following errors on the Android Tablet:

Image may be NSFW.
Clik here to view.

Seems like the MPD on the tablet is receiving some input from HA but not sure why it is not working. If anyone has any insights on this then please point me in the right direction.

Thanks.

1 post - 1 participant

Read full topic

I am new to HA and have successfully added several ZigBee devices through the Tuya cloud based integration. Those devices were automatically discovered from my Smart Life account that I had setup using my phone. Yesterday I received 2 new devices: a ZigBee light dimmer, and a WiFi power meter (PG-01). After adding both devices to Smart Life, the dimmer showed up in HA by itself, but the power meter didn’t, even after several hours. The power meter was the first device that Smart Life didn’t find by scanning, I had to add it manually. I am thinking that this is some type of WiFi problem. Please point me to a guide for troubleshooting this type of problem. This is my second WiFi device. The first was an LG washing machine (ThinQ integration) which was added without any issues.

My WiFi network doesn’t have many devices connected to it: 3 laptops, 1 printer, 2 routers running dd-wrt that are connected to each other by Ethernet cable through a switch, ISP supplied fiber modem/router connected to our main router, washing machine, ZigBee router, and this new WiFi power meter. My son configured our WiFi and it runs two networks: the one provided by the ISP, and one that he had setup. We generally use the one he had setup. Forgot to mention that HA is running on my laptop in a Virtual Box VM. I had been using a VPN on my laptop, which I just turned off a few minutes ago to see if that makes a difference. Any recommendations would be greatly appreciated?

Is there a place in Smart Home where I can find more details about the WiFi device (power meter) that I have added? I can see it in the Tuya IoT web page in my account/project. It shows up as “Smart power monitor - PG-01 Wifi” where it shows a device ID number and an IP address.

1 post - 1 participant

Read full topic

Been observing some truely weird behaviour with the tts that has apparently changed overnight.

I use tts.google_cloud_say, set to a male german WaveNet voice. The required .json file is in the config directory, and everything was working fine last night.

This morning, I sent a voice message to my kids room, using the context menu in the media player card for his Google Home Mini, as usual, only to here the voice pronounce the german message in American English with a female voice.

I did some exploring and here’s what I noticed:

• Restarting HA didn’t change anything.
• Changing the parameters of the tts (pitch etc.) to force a refresh didn’t change anything
• Clearing tts cache didn’t help either

Next, I set up a test card with a click action of calling the tts.google_cloud_say service.

• If I use a Google Nest Hub as the target, everything works fine, the correct german voice is used.
• If I use a Sonos Roam as the target, I get the following error:

Error calling SonosMediaPlayerEntity.play_media on media_player.ecke: UPnP Error 714 received: Illegal MIME-Type from 192.168.86.33

Which makes me wonder if this is fallout from the Google/Sonos trouble.

However, using the context menu from a media player card in lovelace, even for non-Sonos devices, still defaults to the American English voice.

Any ideas what is going on here? Suggestions of how to get more clues?

1 post - 1 participant

Read full topic