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

Mode: restart automation broken after 2021.4 update

$
0
0

Automations with the mode: restart configuration seem to have broken in 2021.4.x. The new debugging tool shows the automation stuck between the trigger firing and the first step executing.

The context is that I have an automation that detects when I’m working from home (in the study no less), which I use to boost the heating in my study when it fires. It’s been very reliable for months. One element is figuring out whether my work laptop is actually active; I’ve found that I need to add some additional logic to the macOS companion app to make sure it is active right now. I’ve found that the companion app sensors can become stale, which leads to misfires. Usually this happens when my Mac is asleep connected to my docking station.

To do this, I use an automation that tracks whether the companion app has updated a sensor in the last 6 minutes. If it has, we can trust that the companion app is active and the companion app sensors are not stale.

I do this with a simple automation that triggers when one of two frequently updated sensors are updated by the companion app. The automation sets an input_binary and then clears it again 6 minutes later. I configure the automation with mode: restart, so that every time a sensor updates, the 6 minute timer is reset. Something of a watchdog timer.

input_boolean:
  nicks_workbook_app_alive:
    name: Nick's workbook app alive
    icon: mdi:laptop-mac

automation:
  - alias: Nick's workbook app alive
    id: 20884583-caa5-4f4b-979a-a0733783b2cf
    trigger:
    - platform: state
      entity_id: sensor.nicks_workbook_pro_last_update_trigger
    - platform: state
      entity_id: sensor.nicks_workbook_pro_storage
    mode: restart
    action:
    - service: input_boolean.turn_on
      data:
        entity_id: input_boolean.nicks_workbook_app_alive
    - delay:
        minutes: 6
    - service: input_boolean.turn_off
      data:
        entity_id: input_boolean.nicks_workbook_app_alive

The working at home sensor, by the way, is as follows. The sensor considers whether my Mac is active, whether the macOS companion app can be trusted (the relevant automation at hand) whether I’m at home, whether I’m connected to my home wifi network (my Mac is at home), whether my docking station is connected (something is active in the study), and whether it is in work hours.

binary_sensor:
  - platform: template
    sensors:
      nick_working_at_home:
        friendly_name: Nick working at home
        delay_on: 00:05:00
        delay_off: 00:20:00
        value_template: >
          {{ 
            states('binary_sensor.nicks_workbook_pro_active') == 'on'
            and states('input_boolean.nicks_workbook_app_alive') == 'on'
            and states('person.nick') == 'home'
            and states('sensor.nicks_workbook_pro_ssid') == 'mySSID'
            and states('device_tracker.docking_station') == 'home' 
            and states('sensor.time') >= '08:00'
            and states('sensor.time') <= '21:30'
          }}

1 post - 1 participant

Read full topic


Hassio just stops working!

$
0
0

I have the latest version of Hassio loaded.
Tried both Pi 2B and 3B+
Different Ethernet Cables
Different Power Supplies
Different SD Cards (32GB)
It runs for a few days and then NOTHING. No errors, nothing. It either stops responding to web requests and SSH logins, or says
Unknown Error
RELOAD UI
Which doesn’t do anything.
I have to unplug power and then plug it back in. And then it works again for a few days.
This has been going on for Months and I’m getting really frustrated.
What is wrong?

PS. The Addons I am running (all current are):
File Editor
MariaDB
Mosquitto Broker
Samba Share
Terminal & SSH

On this latest reboot, I have disabled File Editor; Samba Share and Terminal & SSH just to see if it makes any difference

1 post - 1 participant

Read full topic

Zwave via ZWaveJStoMQTT - what the heck - I had everything looking great and then - no more add or remove

$
0
0

So I was excited to migrate my Z-wave stuff from ST over to my HA server. After reading some posts and clearing up the addon vs integration confusion (I believe), I had the ZWaveJStoMQTT addon installed, Z-Wave integration, and not the Z-Wave JS addon. One by one I removed almost 10 of my Zooz and Inovelli switches and my Schlage lock and moved them over and everything looked great. I got excited and just removed the remaining dozen or so devices from my ST hub and powered it down, as most everything it had done I already do or can do with HA. Next I ran out to do some errands.

I came back 2 hours later and started trying to add devices again. All had been properly excluded. Nothing worked. Tried resets. Nope. Rebooted, still nada. Removed the addon and integration and rebooted. I even tried removing my Zooz S2 Z-wave 700 controller that had been working fine to start over. Nothing has fixed it.

Logs don’t show anything I can ID as obvious issues. There were some ingress error messages now and again, but the reboots and resets seem to have eliminated those - for now, at least. I do see messages now that Node 1 (my USB stick controller) doesn’t support group associations, and I don’t recall seeing that warning before, but maybe I just missed it. At this point I literally have no idea how to proceed as I have nothing paired and nothing that will add. Slowly leaning towards a reinstall, but that seems like crazy overkill. I thought I’d ask the smart folks here for help first…

1 post - 1 participant

Read full topic

Experience Migrating 35+ Z-Wave devices from SmartThings to Z-Wave_JS

$
0
0

This weekend I decided to take the plunge and migrate all of my Z-Wave devices from SmartThings to a new instance of Home Assistant (HassOS running on RPi4 with a Nortek-branded HUSBZB-1 Z-Wave USB stick). The devices included Homeseer dimmers and switches (WS-100+, WD-100, WD-200+), Inovelli switches (LZW30), a Yale Lock, and a handful of sensors. All devices were working correctly in SmartThings prior to migration. I thought I’d share my experience so far, and ask a few questions of the experts.

I was careful to make sure to go through the exclusion process for each device in SmartThings prior to including it into Home Assistant. I was worried this would be difficult, but it was actually very easy in SmartThings.

I found the “add node” inclusion process in the Z-Wave JS integration to be very temperamental. After hitting Start Inclusion and hitting the button on the device, the UI would return to the “Start Inclusion” screen as soon at the inclusion process began. If I hit “Start Inclusion” again, it would fail and the “Start Inclusion” button would then fail to function until I restarted the Z-Wave JS Add On. I ultimately found I could track the progress by looking at the Z-Wave JS Add-On logs, and keep reloading until I saw “Node ready for use”. Then I could move on to the next one.

Despite the fragile nature, I was able to get almost everything to include. My Yale Assure lock took by far the most effort, it didn’t work in HA after the first 5 attempts to include, but on the 6th attempt it came in and worked correctly. I also have a Ecolink Garage Tilt Sensor that has yet to integrate correctly, but I’ll keep trying (this one is cumbersome to include as the battery has to be removed).

First impression: Responsiveness is so much faster than SmartThings. Hitting the entity switch in HA instantly actives the switch, where it could be five or six seconds in SmartThings to respond (and even longer when piping those to HA via the SmartThings integration). Also, not needing any custom device handlers or special setup was great. Thanks to to the Blueprints here, I was able to easily use multi-tap actions on the switches and even change the switch LED color based on device state. While possible in SmartThings, this is already so much easier in HA.

I do have some issues. I have seven Homeseer WD-100 switches in my house, and none of these are working now in Home Assistant. All of them appear to be added without issue (all properties appear in the device page), but none of them are functional, or report status in HA. I have tried excluding and re-adding them, and even factory resetting the switches themselves, and rebooting HA, but no luck. Some of these switches are within 5 feet of the USB stick, so I don’t believe it is a signal issue (other devices far away are working fine). I also have other switches from Homeseer, WD-200+ dimmers, and some WS-100+ on/off switches. These are all working fine, only the WD-100 is failing.

The verdict: I’m not going back to SmartThings. I’m hopeful that my WD-100 switch issue can be solved, and I fully expect inclusion will become more robust over time as the platform continues to evolve.

I have also opened a GitHub issue for my challenges here: Zwave JS+HUSBZB-1 issue with Homeseer WD-100 dimmer switches · Issue #49397 · home-assistant/core (github.com)

Questions I have:

  • Should I have used the ZWaveJS2MQTT Add-On instead of ZWaveJS? Any chance this would work better for inclusion? I wanted to bet on the platform that looked like it would be official in the long run to avoid any future migrations if possible.
  • If ZWaveJS2MQTT would solve my issues, can I switch to it without rebuilding my zwave network? This seems unlikely.
  • Is there anyway to diagnose whether my challenges are related to my USB Zwave stick rather than the ZWave JS services?

Thanks for reading!

1 post - 1 participant

Read full topic

Lifetime statistics of a sensor using something similar to the "utility_meter"?

$
0
0

Hi there.

I use “Local Tuya” to track the usage statistics of my Gosund SP111 smart socket. It works pretty fine with the configuration I made:

sensor:
  - platform: integration
    source: sensor.socket_1_power_consumption_local
    name: socket_1_energy_spent_kwh
    unit_prefix: k
    round: 6
    method: left # prevents big jumps
	
  - platform: template
    sensors:
      calculated_energy_hourly_socket1:
        unique_id: calculated_energy_hourly_socket1
        icon_template: hass:calendar-clock
        friendly_name: Socket 1 - Hourly Energy
        unit_of_measurement: kWh
        value_template: "{{ (states('sensor.hourly_energy_socket1') |float ) | round(2) }}"
        
      calculated_energy_daily_socket1:
        unique_id: calculated_energy_daily_socket1
        icon_template: hass:calendar
        friendly_name: Socket 1 - Daily Energy
        unit_of_measurement: kWh
        value_template: "{{ (states('sensor.daily_energy_socket1') |float) | round(2) }}"
        
      calculated_energy_weekly_socket1:
        unique_id: calculated_energy_weekly_socket1
        icon_template: hass:calendar
        friendly_name: Socket 1 - Weekly Energy
        unit_of_measurement: kWh
        value_template: "{{ (states('sensor.weekly_energy_socket1') |float) | round(2) }}"
        
      calculated_energy_monthly_socket1:
        unique_id: calculated_energy_monthly_socket1
        icon_template: hass:calendar
        friendly_name: Socket 1 - Monthly Energy
        unit_of_measurement: kWh
        value_template: "{{ (states('sensor.monthly_energy_socket1') |float) | round(2) }}"
        
      calculated_energy_yearly_socket1:
        unique_id: calculated_energy_yearly_socket1
        icon_template: hass:calendar
        friendly_name: Socket 1 - Yearly Energy
        unit_of_measurement: kWh
        value_template: "{{ (states('sensor.yearly_energy_socket1') |float) | round(2) }}"

localtuya:
  - host: 192.168.1.X
    device_id: x
    local_key: x
    friendly_name: Socket 1 (Local)
    protocol_version: "3.3"
    entities:
      - platform: binary_sensor
        friendly_name: Socket 1 (Local)
        id: 1
        device_class: power
        state_on: "true" # Optional
        state_off: "false" # Optional
        
      - platform: sensor
        friendly_name: Socket 1 Current (Local)
        id: 4
        scaling: 0.1 # Optional
        device_class: current # Optional
        unit_of_measurement: "mA" # Optional
        
      - platform: sensor
        friendly_name: Socket 1 Power Consumption (Local)
        id: 5
        scaling: 0.1 # Optional
        device_class: power # Optional
        unit_of_measurement: "W" # Optional
        
      - platform: sensor
        friendly_name: Socket 1 Voltage (Local)
        id: 6
        scaling: 0.1 # Optional
        device_class: voltage # Optional
        unit_of_measurement: "V" # Optional
        
      - platform: switch
        friendly_name: Socket 1 (Local)
        id: 1
        current: 4 # Optional
        current_consumption: 5 # Optional
        voltage: 6 # Optional

utility_meter:
  hourly_energy_socket1:
    source: sensor.socket_1_energy_spent_kwh
    cycle: hourly
  daily_energy_socket1:
    source: sensor.socket_1_energy_spent_kwh
    cycle: daily
  weekly_energy_socket1:
    source: sensor.socket_1_energy_spent_kwh
    cycle: weekly
  monthly_energy_socket1:
    source: sensor.socket_1_energy_spent_kwh
    cycle: monthly
  yearly_energy_socket1:
    source: sensor.socket_1_energy_spent_kwh
    cycle: yearly

The only thing left would be “lifetime” statistics of “socket_1_energy_spent_kwh”.
utility_meter will reset the yearly statistics on 1st of January 2022. What other integration can I use to measure the lifetime statistics in the same way as it’s done in utility_meter? I read about the history_stats and such, but it also requires “recorder” and some other things that would take a lot of time to figure out. Is there maybe some easier solution? I’d very appreciate an example code.

1 post - 1 participant

Read full topic

How to store PV power at 15mins interval in own computer

$
0
0

Dear Altruists

Can anyone guide or recommend how to get and store Modbus registers data w.r to time to my computer?

I am using SunnyBoy 2.5. ethernet is available with IP and port 502.

I wish to use python script.

Thanks in advance
Rabiul

2 posts - 2 participants

Read full topic

Tuya LED Strip Rainbow Effect

$
0
0

Hi,

How can I make tuya led strip do rainbow effect? I able to do that in tuya app but not in home assistant.

1 post - 1 participant

Read full topic

The automations that I had already deleted were still working

$
0
0

I have set up the automation through the configuration.yaml file And it worked fine.

But time passed, the time came when I had to delete it.

So I commented out the automation as shown in the photo.

And I rebooted without any errors, but the automation was still working.

(automation 2 can no longer be found in any of my settings!)

(Sorry, I can’t figure out how to change the language to English)
The photo above indicates that my automation is still working.
image

Is there a problem with my configuration.yaml file?

I couldn’t find any errors in the home-assistant.log file (log-level:INFO)

I apologize if my explanation is insufficient. I am watching this topic in real time. Please ask me for a supplementary explanation.

Thanks in advance for your support.

1 post - 1 participant

Read full topic


PZEM_017 using Modbus and USR_DR302

$
0
0

Hi there.
I have a PZEM_017 and using the USR_DR302 I was able to connect from my Windows 10 computer using the oficial software and USR-VCOM.
Now, of course I’m asking here because I need to connect this unit to my Home Assistant.

I’m already using the EPEver Solar Controller with rtuovertcp with another USR_DR302, so I have this configuration:

modbus:
  - name: hub1
    type: rtuovertcp
    host: 172.16.10.98
    port: 8088
    timeout: 2
  - name: hub2
    type: rtuovertcp
    host: 172.16.10.99
    port: 8088
    timeout: 2
  - name: hub3
    type: rtuovertcp
    host: 172.16.10.100
    port: 8088
    timeout: 2

It works fine for my EPEver. This is my modbus.yaml file:

- platform: modbus
  scan_interval: 30
  registers:
    #Solar Registers
    - name: EPEver_Solar_Voltage #3100
      hub: hub1
      unit_of_measurement: V
      slave: 1
      register: 12544
      register_type: input
      scale: 0.01
    - name: EPEver_Solar_Current #3101
      hub: hub1
      unit_of_measurement: A
      slave: 1
      register: 12545
      register_type: input
      scale: 0.01
      precision: 2
    - name: EPEver_Solar_Power_Instant #3102
      hub: hub1
      unit_of_measurement: W
      slave: 1
      register: 12546
      register_type: input
      scale: 0.01
      precision: 2
      reverse_order: true
    - name: EPEver_Solar_Status #3201
      hub: hub1
      slave: 1
      register: 12801
      register_type: input
      #Discovered status: 11 == 'Cut Out'
    - name: EPEver_Device_Temperature #3111
      hub: hub1
      unit_of_measurement: °C
      slave: 1
      register: 12561
      register_type: input
      scale: 0.01
      precision: 2
##########################Modbus Config Test for pzem-017##########################
- platform: modbus
  scan_interval: 30
  registers:
    - name: PZEM_Voltage
      unit_of_measurement: V
      slave: 1
      register: 0
      register_type: input
      scale: 0.01
    - name: PZEM_Current
      unit_of_measurement: A
      slave: 1
      register: 1
      register_type: input
      scale: 0.01
      precision: 2
    - name: PZEM_Power_Instant
      unit_of_measurement: W
      slave: 1
      register: 2
      register_type: input
      scale: 0.1
      precision: 1
    - name: PZEM_Energy
      unit_of_measurement: Wh
      slave: 1
      register: 4
      register_type: input
    - name: PZEM_High_Voltage_Alarm_Status
      slave: 1
      register: 6
      register_type: input
    - name: PZEM_Low_Voltage_Alarm_Status
      slave: 1
      register: 7
      register_type: input

Using the EPEver config as example I tried to setup a modbus config for the PZEM-017, and as you can see, I don’t really know anything about modbus nor serial communication, so I’m on a try-and-error manner here, but after spending many hours of my weekend without luck, I stopped and decided to ask for help.

Using a software called Modbus Poll I was able to find that this address works for getting the values of Voltage, Current, Power, Energy, High-Voltage and Low-Voltage from the PZEM-017 with Slave ID: 1.

ModBus_poll

As you can see on the screenshot, I was able to get raw data from the unit, but I’m unable to transform that into something home-assistant will understand.

RTU Request on Modbus Poll

01 04 00 07 00 08 40 0D 

Can anybody help me get this config right? I don’t really know anything about coils or registers. If someone helps me with this, probably many people will benefit from using this configuration. I searched all over the internet and was unable to find how to do this.

This is the error I’m getting on home-assistant logs:

2021-04-19 00:24:26 WARNING (MainThread) [homeassistant.components.modbus.sensor] Sensor configuration is deprecated, will be removed in a future release
2021-04-19 00:24:26 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up modbus platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 205, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/modbus/sensor.py", line 178, in async_setup_platform
    hub: ModbusHub = hass.data[MODBUS_DOMAIN][discovery_info[CONF_NAME]]
KeyError: 'modbus_hub'

Here’s the PDF for the PZEM-017 where I found the addresses for voltage, current, power, energy, low-voltage and high-voltage alarms:
https://www.solar-thailand.com/pdf/PZEM-003-Manual.pdf

Thank you!
And if I need to buy a coffee for someone, I’ll be glad to do it, just ask!

2 posts - 1 participant

Read full topic

BUG? File Editor Starts On Boot even if set NOT to

MQTT Event Trigger on Home Assistant Startup but device is OFF

$
0
0

I have OctoPi on all my 3D printers, and they are running MQTT.
I have OctoPi set to send MQTT event messages either if it disconnects from the printer or there is an error.
In Home Assistant, I have this set up in /config/automations.yaml

MQTT

Which tells the Sonoff switch to turn the power off, thus shutting down the printer.

However, when Home Assistant Boots up, I’m getting these events in the LogBook, even when the printer and OctoPi is OFF:

And the BAD part is, if that printer actually is ON and printing, this ‘fake’ event happen anyway when Home Assistant restarts and it shuts down the power to the printer in the middle of a print job!

Any ideas how to fix this and/or why its happening?

Thanks!

1 post - 1 participant

Read full topic

Attempted access from criminalip.com

$
0
0

Hi
From time to time, I get this warning message in HA:

Login attempt or request with invalid authentication from security.criminalip.com (89.248.168.138). (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36)

2fa is on, and it doesn’t look like they’ve succeeded getting in.
What is security.criminalip.com? Their “web site” says that they’re good guys and not much else.
Their IP changes as well. The last two times it’s been 93.174.93.76 and 89.248.168.138.
What’s going on? Should they be blocked, or is there anything else that needs to be done?
Helge

1 post - 1 participant

Read full topic

Legrand Home + Control Integration

$
0
0

Hello, good to see that Legrand Home + Control has been added to the Core Integrations. But unfortunately I wasn’t able to get it working yet. Authentication process seems ok and I can see the Integration in the list but there is no Entities, nothing can be seen in the integration. Any ideas ?

1 post - 1 participant

Read full topic

Why is Person home?

$
0
0

I can’t really rely on the presence of person. The person isn’t home and shouldn’t be home according to the statuses, at least that’s what I think :thinking: Did I do something wrong?

All stationary trackers have status not_home and all updated, in this example, an hour ago.
GPS device tracker has status home but is last update 12 hours ago.

device_tracker Wifi: platform: nmap_tracker / consider_home: 90
device_tracker Bluetooth: platform: bluetooth_tracker / consider_home: 90
device_tracker GPS: Home Assistant Companion app

I’ve added screenshots for proof :grimacing:

2 posts - 2 participants

Read full topic

Beckhoff ADS stop working

$
0
0

Goodmorning,
I have a problem with communication between home assistant and my PLC with twincat3.
After some hours, I get this errors in HA:
First this error:
2021-04-19T01:28:44+0200 Error: read frame failed with error: Connection reset by peer
2021-04-19T01:28:44+0200 Info: connection closed by remote

And than, when I try to use HA I get this error:
2021-04-19T07:21:48+0200 Error: write frame failed with error: 32
2021-04-19 07:21:48 ERROR (SyncWorker_14) [homeassistant.components.ads] Error writing Global_Variables.OutputModule.LMP_bagno1P.bHMI_Attiva: ADSError: Unknown Error (-1).

HA version:
core-2021.3.4
supervisor-2021.04.0

Any suggestion?

1 post - 1 participant

Read full topic


One of my Lovelace tabs not displaying after update

$
0
0

After updating to 2021.4, one of my Lovelace dashboard tabs stopped working (it worked since 2019 versions up to 2021.3.x without issues). It shows nothing, just empty space.

Sometimes I see it for a second and then it disappears again so I think it’s some kind of web rendering issue.

Problem persists up to the latest, 2021.4.5.

I see nothing relevant in the log so far but I’m not sure. How would I go about troubleshooting this? Thanks.

1 post - 1 participant

Read full topic

Adding RTSP-Stream from ESP32-CAM into Frigate

$
0
0

Hello,

has anybody successfully integrated a RTSP-stream from an ESP32-CAM into Frigate? I flashed GitHub - geeksville/Micro-RTSP: A RTSP video server intended for very small CPUs (ESP32 etc) on my ESP32 and I am able to watch the video in VLC (via RTSP) and in the webbrowser. Frigate however is not able to receive the stream:

frigate.yml:

cameras:
  back:
    ffmpeg:
      input_args:
        - -avoid_negative_ts
        - make_zero
        - -fflags
        - nobuffer
        - -flags
        - low_delay
        - -strict
        - experimental
        - -fflags
        - +genpts+discardcorrupt
        - -r
        - '3'
        - -use_wallclock_as_timestamps
        - '1'
      inputs:
        - path: rtsp://192.168.188.127:8554/mjpeg/1
          roles:
            - detect
            - rtmp
    width: 600
    height: 800

Log output:

frigate.mqtt INFO : MQTT connected
watchdog.back INFO : No frames received from back in 20 seconds. Exiting ffmpeg…
watchdog.back INFO : Waiting for ffmpeg to exit gracefully…
frigate.video INFO : back: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
frigate.video INFO : back: ffmpeg process is not running. exiting capture thread…
frigate.watchdog INFO : Detection appears to have stopped. Exiting frigate…
frigate.app INFO : Stopping…
frigate.record INFO : Exiting recording maintenance…
frigate.object_processing INFO : Exiting object processor…
ffmpeg.back.detect ERROR : [udp @ 0x16111c0] attempted to set receive buffer to size 393216 but it only ended up set as 360448
ffmpeg.back.detect ERROR : [udp @ 0x1621510] attempted to set receive buffer to size 393216 but it only ended up set as 360448
ffmpeg.back.detect ERROR : [rtsp @ 0x16095a0] UDP timeout, retrying with TCP
ffmpeg.back.detect ERROR : [rtsp @ 0x16095a0] Could not find codec parameters for stream 0 (Video: mjpeg, none(bt470bg/unknown/unknown)): unspecified size
ffmpeg.back.detect ERROR : Consider increasing the value for the ‘analyzeduration’ and ‘probesize’ options
ffmpeg.back.detect ERROR : Output file #0 does not contain any stream
frigate.events INFO : Exiting event cleanup…
frigate.events INFO : Exiting event processor…
frigate.watchdog INFO : Exiting watchdog…

Has anybody a suggestion? I think tweaking the ffmpeg parameters is the way to go but I am clueless which parameters propably work.

1 post - 1 participant

Read full topic

Homeassistant as a Wireguard client

$
0
0

I have an rpi running wireguard. Now I want to setup my hass installation to connect as a client to this wireguard.

I am aware of (and using in other places) the wirequard add-on from Frenck, but this is for running a wireguard server, not a client (as far as I know).

Anyone any pointers on how to do this ? Thanks !

1 post - 1 participant

Read full topic

Are Philips Hue bulbs supported repeaters?

$
0
0

Hello,

I’ve read here that Philips hue bulbs are terrible repeaters:

Avoid adding Zigbee lightbulbs to your hub in combination with other Zigbee devices, since the lightbulbs will try to act as routers, but unfortunately they only perform this role properly with other lightbulbs. The exception we have found are Sengled Zigbee lightbulbs, which do not try to take on the role of repeating other Zigbee devices. Zigbee light bulbs do not have issues routing among themselves, therefore a good alternative is a separate Zigbee network via a compatible bridge such as the Philips Hub Bridge, or a second Hubitat Elevation hub with only Zigbee lightbulbs paired to it. This will avoid this issue of bulbs attempting, and subsequently failing to repeat signals for other devices, by establishing two separate and stable Zigbee networks.

I would like to know if someone indeed experienced issues using philips hue bulbs on its network, among other zigbee devices (aqara for instance).

I use a Deconz Conbee II, and when I look at my network map, it looks quite strange because my Aqara switches & sensors are not connected to anything, but they work though.

Maybe it’s related to my deconz and I should switch to something else ?

Any suggestions are welcome :relaxed:

1 post - 1 participant

Read full topic

Zigbee2MQTT: re-pair IKEA outlet does not work

$
0
0

Last night I have the z2m pluging installed and paired successfully the Tradfri outlet and a button to z2M and got corresponding sensors, sw etc… in HA. But today morning I see the button works perfectly but the outlet cannot be recognized by z2m

Zigbee2MQTT:error 2021-04-19 10:53:09: Publish ‘set’ ‘state’ to ‘ikea-socket01-e1603’ failed: ‘Error: Command 0x5c0272fffe6273dc/1 genOnOff.on({}, {“timeout”:10000,“disableResponse”:false,“disableRecovery”:false,“disableDefaultResponse”:false,“direction”:0,“srcEndpoint”:null,“reservedBits”:0,“manufacturerCode”:null,“transactionSequenceNumber”:null,“writeUndiv”:false}) failed (Data request failed with error: ‘No network route’ (205))’

tried to reattach my zigbee coordinator (Slaesh CC2652RB stick), restarted z2m pluging, re-pair the outlet … nothing helps… at the same time the switch Tradfri e1743 works perfectly.
What else I can do?

1 post - 1 participant

Read full topic

Viewing all 107764 articles
Browse latest View live


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