I have a CBUS system, which I integrate via Home Bridge and into HA. I’m a new HA user (less than a week) but already I can see it has so much potential to work with my systems. So, the piece above works flawlessly.

What I want to do is trap the level of the incoming CBUS device into HA (0-255 as a dimmer) then be able to tell a script or automation to set another device to the very same level, in this case some Shelly dimmers.

I have looked and excuse my noobness, I’m struggling to see how I can trigger an action to say ‘set the Shelly level to the level of this other device’. This is my most important automation, the critical reason to act to moving to HA. Hoping for some hive mind help.

Thanks!

1 post - 1 participant

Read full topic

After upgrading to 2021.11 (Hassio) - Supervisor tab does not load for me
I get a screen with:

Troubleshooting
If you just started, make sure you have given the Supervisor enough time to start.
Check the Observer
Try a reboot of the host
Check System Health
Ask for help

Observer - shows all positive signs
System Health - showing “error unknown”

the logs are full of [homeassistant.components.hassio.handler] /<<>> return code 403

for example (but much more):

2021-11-04 17:23:16 ERROR (MainThread) [homeassistant.components.hassio.handler] /homeassistant/options return code 403
2021-11-04 17:23:16 ERROR (MainThread) [homeassistant.components.hassio.handler] /supervisor/options return code 403
2021-11-04 17:23:16 ERROR (MainThread) [homeassistant.components.hassio.handler] /info return code 403
2021-11-04 17:23:16 ERROR (MainThread) [homeassistant.components.hassio.handler] /ingress/panels return code 403
2021-11-04 17:23:16 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can't read panel info: 
2021-11-04 17:23:16 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Supervisor for hassio
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 304, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 623, in async_setup_entry
    coordinator = HassioDataUpdateCoordinator(hass, entry, dev_reg)
  File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 702, in __init__
    self.is_hass_os = "hassos" in get_info(self.hass)
TypeError: argument of type 'NoneType' is not iterable

How do I diagnose and work it back to normal ?

1 post - 1 participant

Read full topic

hello,
I am running HA on version 2021.9.6.
It runs smoothly for a long time and without problems. Apart that, I have attached an Amazon tablet to my wall with Fully Kiosk Browser.
It works smoothly too without problems for a long time.

Yesterday, I decided to update to version 2021.11.0.
Update was completed successfully without problems.

Since then, the tablet on the wall stuck on loading data.
All the rest of our devices (my pc, our mobiles) are working properly.

I tried everything without success.
At the end I had to restore version 2021.9.6

Any ideas why this is happening ?

1 post - 1 participant

Read full topic

Hi guys… I was following a guide on a lock code for my schlage lock and everything was going well except for this part. I can’t figure out what is wrong. I get an error on line 20 col 16. “can not read an implicit mapping pair; a colon is missed at line 20, column 16”

What am I missing? Thanks in advance.

alias: Front Lock - Lock Code
description: ''
trigger:
  - platform: event
    event_type: zwave_js_notification
condition:
  - condition: template
    value_template: '{{ trigger.event.data.device_id == ''1e972ghrdjkfhskjafdffkdsajkfhkasd' }}'
  - condition: template
    value_template: '{{ trigger.event.data.event == 5 }}'
action:
  - service: input_number.set_value
    data_template:
      entity_id: input_number.last_front_door_code
      value: '{{trigger.event.data.parameters.userId | int}}'
  - service: input_text.set_value
    data_template:
      entity_id: input_text.front_lock_user
      value: >
'{% if states('input_number.last_front_door_code') | int == 1 %}
  Code1
{% elif states('input_number.last_front_door_code') | int == 2 %}
  Code2
{% elif states('input_number.last_front_door_code') | int == 3 %}
  Code3
{% elif states('input_number.last_front_door_code') | int == 4 %}
  Code4
{% elif states('input_number.last_front_door_code') | int == 5 %}
  Code5
{% elif states('input_number.last_front_door_code') | int == 6 %}
  Code6
{% elif states('input_number.last_front_door_code') | int == 7 %}
  Code7
{% elif states('input_number.last_front_door_code') | int == 8 %}
  Code8
{% elif states('input_number.last_front_door_code') | int == 9 %}
  Code9
{% else %}
  Error
{% endif %}'
mode: single

1 post - 1 participant

Read full topic

Hello !

I’ve just added Homekit integration to my working Home Assistant setup.
My garage door, in Home Assistant is a MQTT device (it is Wemos D1 with Relay shield):

light:
  - platform: mqtt
    name: "garagea"
    state_topic: "stat/wegaragea/POWER"
    command_topic: "cmnd/wegaragea/POWER"
    payload_off: "OFF"
    payload_on: "ON"
    qos: 1

The device is sync with Homekit like this :

homekit:
  filter:
    include_entities:
      # inter
      - light.garagea # jag

On Lovelace, I can ask a confirmation when I trigger this switch (to avoid false opening).
Can I have the same behaviour with Homekit on my iPhone ?

1 post - 1 participant

Read full topic

Stuck with some jinja2 coding to get the index value for a highest value in a list.
What i am trying todo is the following:
I have 4 rooms with heating and a valve in each room, i’m using opentherm for the boiler.
For the opentherm to work correctly i need to input the setpoint and actual temperature, but i need to send the highest difference to the boiler. Otherwise it will start to lower its output temperature when the actual temperature reaches the setpoint.

So if the first room is set to 21 and actual is 20,8 the output could be 34 degrees.
But room 2 is set to 21 and is 19, so that room while the valve is open it wont heat up quickly.

So my thinking was to calculate all the differences and then decide with that what gets send to the boiler using the index value of the list i made with those differences

From my basic python skill i could do something like:

room1_delta = 4
room2_delta = 3
room3_delta = 1

delta_room = [room1_delta,room2_delta,room3_delta]
min_delta = min(delta_room)
x = delta_room.index(min_delta)

But no clue how todo that with jinja. Any ideas which direction is should look at?

1 post - 1 participant

Read full topic

Greetings,
i have one device that reads this data

modbus:
  - name: hub1
    type: tcp
    host: 192.168.6.3
    port: 502
    binary_sensors:
      - name: "q1"
        address: 8192
        scan_interval: 30
        slave: 1
      - name: "q2"
        address: 8193
        scan_interval: 30
        slave: 1
      - name: i3
        input_type: discrete_input
        address: 2
        slave: 1
        
    sensors:
      - name: vm12
        slave: 1
        address: 12
      - name: vm50
        slave: 1
        address: 50
      - name: vm55
        slave: 1
        address: 55

The thing is that if i wan to add new but identical device i would want to change only one thing lets say a name of the whole device but keep all the sensors lets say like this:

modbus:
  - name: hub2
    type: tcp
    host: 192.168.6.4
    port: 502
    binary_sensors:
      - name: "q1"
        address: 8192
        scan_interval: 30
        slave: 1
      - name: "q2"
        address: 8193
        scan_interval: 30
        slave: 1
      - name: i3
        input_type: discrete_input
        address: 2
        slave: 1
        
    sensors:
      - name: vm12
        slave: 1
        address: 12
      - name: vm50
        slave: 1
        address: 50
      - name: vm55
        slave: 1
        address: 55

But obviosly this will not work as it would have the same name of sensors.
Is it possible to somehow group and use it lets say like this?

hub1.binary_sensors.q1
hub2.binary_sensors.q1
hub1.sensors.vm12
hub2.sensors.vm12

Or if you have any recomendation pls let me know. Thank you.

1 post - 1 participant

Read full topic

Hello,

I’m using a binary sensor to retrieve the cycles of my gasmeter via gpio. You can find the config of the corresponding sensors below.

I’ve tried to add the device_class: gas to my sensor, but this will be rejected by HA.
Is there any possibility to enable energy management for this type of sensor?
What do I need to add/change?

sensor 1:
  platform: template
  sensors:
    daily_gas_in_m3:
      unit_of_measurement: 'm³'
      #state_class: total_increasing
      #device_class: gas
      value_template: "{{ (states('sensor.daily_gas') | float / 100) }}"

utility_meter:
  daily_gas:
    source: counter.gascounter
    cycle: daily

binary_sensor:
  - platform: rpi_gpio
    invert_logic: true
    ports:
      18: GASZAEHLER

Best regards
Stefan

1 post - 1 participant

Read full topic

I configured the google Assistant configuration manually. Everything is going well so far.
But, when I want to switch something, it takes a short time for it to be carried out and Google says that it has been carried out.

So when I say “Hey Google, turn on the room lamp” it takes 5-8 seconds for the lamp to turn on.

Can I optimize something there?
Or is it normal that it takes so long?

Some time ago I used FHEM as a smart home. The switching process was carried out within 2 seconds.

Is it faster with NabuCasa?

1 post - 1 participant

Read full topic

Hi,

I’m not sure where to post this as I do not have any clue on how to investigate.
So I’m just spitting out what I see and hope for the best.

Background: I have a digital gas meter and I’ve added this meter to the energy dashboard.
When I take a look at the graph of the meter, it is looking ‘fine’ as far as I can tell

But when I take a look at the energy dashboard, it tells me I used 70m³ of gas on the 2nd of November

That does not feel like it is correct.
Taking a look at the entries in the database it ‘jumps’ all of a sudden with that same value of 70

My question is 2 parted:

• Does anybody know what might have triggered this?
• Does anybody know on how to correct it?

Thanks a lot for your replies.

2 posts - 2 participants

Read full topic

Hi all,

My HA / Odroid N2+ / zzh! (50 devices - Lidl / Ikea / Philips / Sonoff) + ESPHome + TP-Link setup has been working pretty stably for a while now with just a few glitches that I feel are more ESPHome / WiFi based than HA itself.

And it was whilst trying to upload some new code to an ESP8266 that I ended up in a right mess around lunchtime and I’m still not back 100% yet. ;-(

I think what could have happened (if such a thing is possible) is that I attempted to upload some ESPHome / ESP8266 code to the Zigbee coordinator (port) by mistake (USB connection / Linux terminology and a PC that was running very sluggishly at that moment) and that screwed up the coordinator? I had to re-flash it with the TI Windows program and then re-pair all the devices (an Ikea LED Tradfri lamp and a remote) which don’t seem to want to play again but were working fine last night)?

All the other things seemed to pick up their original names so I didn’t have to re-assign all the ID’s in the automations at least. (Then the whole Automation area disappeared and I had to edit the .yaml manually to get it back again … I think it was Blueprint that got messed up). ;-(

So, not wanting to be in that sort of position again, where are we re ‘duplicating’ coordinators so that in the even of one failing or getting screwed up, it can be swapped out quickly and everything just work please?

FWIW I do have two zzh!'s and I saw mention of backing up the non-volatile memory but I wasn’t sure if that would have been a good idea after the crash and not sure I’d know how to do so in any case. ;-(

Cheers, T i m

1 post - 1 participant

Read full topic

I have a thermostat, configured in home assistant. Everything works but the thermostat’s screen is dim and I can’t see if it’s turned on or off. I want an rgb led change color depending on the state (“off”= blue, “heat”=orange)

I created an automation that changes the led color when the state changes from “heat” to “off” (and other way around), but apparently it sometimes misses the change, so the led color is wrong…
I want to make an automation so it checks the state every minute and then change the color accordingly.
(don’t know if this asks much from the system? )

what is the easiest way to achieve this?

1 post - 1 participant

Read full topic

Hi all! My first post here, hopefully i didn’t miss anything.

My situation is the following:
Aqara E1 switch, when being paired, sometimes don’t recognized as having double rocker, only one switch is available, and it works both ways (HA to switch and back). When i’m trying to pair it once more, second switch shows up in HA, but it only works form HA to switch, and rocker presses on the second gang don’t get reported to HA.

If I try to read clusters manually OnOff @ 0x0006, endpoint id 2 (2nd rocker), value changes from Bool.false to Bool.true, which tells that HA can in fact receive rocker state, but it foesnt happen automatically.

Please, help me with trying to understand who’s fault is it at this point, and what i can do.
Thanks in advance!

Config is:
Sonoff zbBridge flashed with Tasmota 10.0.0
ZHA integration
Aqara E1 switch QBKG39LM - no neutral, double rocker, QBKG39LM
Home Assistant 2021.11.0, hassio, Raspberry Pi 3b+

Pairing log (failed pairing - only 1 gang active):

[0x6113:1:0x0406] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=189 command_id=Command.Report_Attributes>
[0x6113:1:0x0406] ZCL request 0x000a: [[Attribute(attrid=0, value=<TypeValue type=bitmap8, value=bitmap8.1>)]]
[0x6113:1:0x0406] Attribute report received: occupancy=1
[0x6113:1:0x0500]: Updated alarm state: 1
[0xf844:1:0x0500] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=124 command_id=0>
[0xf844:1:0x0500] ZCL request 0x0000: [<ZoneStatus.Alarm_1: 1>, <bitmap8.0: 0>, 0, 0]
[0xF844:1:0x0500]: Updated alarm state: ZoneStatus.Alarm_1
New device 0x6984 (54:ef:44:10:00:17:e9:2a) joined the network
[0x6984] Scheduling initialization
Tries remaining: 3
[0x6984] Requesting 'Node Descriptor'
Tries remaining: 2
[0x6984] Extending timeout for 0x36 request
Device 0x6984 (54:ef:44:10:00:17:e9:2a) joined the network
[0x6984] Scheduling initialization
[0x6984] Canceling old initialize call
Received frame on uninitialized device <Device model=None manuf=None nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=False> from ep 0 to ep 0, cluster 19: b'\xd3\x84i*\xe9\x17\x00\x10D\xefT\x80'
[0x6984:zdo] ZDO request ZDOCmd.Device_annce: [0x6984, 54:ef:44:10:00:17:e9:2a, 128]
Tries remaining: 3
[0x6984] Requesting 'Node Descriptor'
Tries remaining: 2
[0x6984] Extending timeout for 0x38 request
Received frame on uninitialized device <Device model=None manuf=None nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=False> from ep 0 to ep 0, cluster 2: b'\xd4\x00\x00'
[0x6984:zdo] ZDO request ZDOCmd.Node_Desc_req: [0x0000]
[0x6984:zdo] Unsupported ZDO request:ZDOCmd.Node_Desc_req
Received frame on uninitialized device <Device model=None manuf=None nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=False> from ep 0 to ep 0, cluster 32770: b'6\x00\x84i\x02@\x80_\x11\x7fd\x00\x00,d\x00\x00'
[0x6984:zdo] ZDO request ZDOCmd.Node_Desc_rsp: [<Status.SUCCESS: 0>, 0x6984, NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)]
[0x6984:zdo] Unsupported ZDO request:ZDOCmd.Node_Desc_rsp
Received frame on uninitialized device <Device model=None manuf=None nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=False> from ep 0 to ep 0, cluster 32770: b'8\x00\x84i\x02@\x80_\x11\x7fd\x00\x00,d\x00\x00'
[0x6984] Got Node Descriptor: NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)
[0x6984] Discovering endpoints
Tries remaining: 3
[0x6984] Extending timeout for 0x3a request
Received frame on uninitialized device <Device model=None manuf=None nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=False> from ep 0 to ep 0, cluster 54: b'\xd5\xb4\x01'
[0x6984:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_req: [180, <Bool.true: 1>]
Received frame on uninitialized device <Device model=None manuf=None nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=False> from ep 0 to ep 0, cluster 32773: b':\x00\x84i\x03\x01\x02\xf2'
[0x6984] Discovered endpoints: [1, 2, 242]
[0x6984] Initializing endpoints [<Endpoint id=1 in=[] out=[] status=<Status.NEW: 0>>, <Endpoint id=2 in=[] out=[] status=<Status.NEW: 0>>, <Endpoint id=242 in=[] out=[] status=<Status.NEW: 0>>]
[0x6984:1] Discovering endpoint information
Tries remaining: 3
[0x6984] Extending timeout for 0x3c request
Received frame on uninitialized device <Device model=None manuf=None nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=False> from ep 0 to ep 0, cluster 32772: b'<\x00\x84i\x1a\x01\x04\x01\x00\x01\x01\x07\x00\x00\x02\x00\x03\x00\x04\x00\x05\x00\x06\x00\t\x00\x02\n\x00\x19\x00'
[0x6984:1] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=1, profile=260, device_type=256, device_version=1, input_clusters=[0, 2, 3, 4, 5, 6, 9], output_clusters=[10, 25])
[0x6984:2] Discovering endpoint information
Tries remaining: 3
[0x6984] Extending timeout for 0x3e request
Received frame on uninitialized device <Device model=None manuf=None nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=False> from ep 0 to ep 0, cluster 32772: b'>\x00\x84i\x12\x02\x04\x01\x00\x01\x01\x05\x00\x00\x03\x00\x04\x00\x05\x00\x06\x00\x00'
[0x6984:2] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=2, profile=260, device_type=256, device_version=1, input_clusters=[0, 3, 4, 5, 6], output_clusters=[])
[0x6984:242] Discovering endpoint information
Tries remaining: 3
[0x6984] Extending timeout for 0x40 request
Received frame on uninitialized device <Device model=None manuf=None nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=False> from ep 0 to ep 0, cluster 32772: b'@\x00\x84i\n\xf2\xe0\xa1a\x00\x00\x00\x01!\x00'
[0x6984:242] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=242, profile=41440, device_type=97, device_version=0, input_clusters=[], output_clusters=[33])
[0x6984] Extending timeout for 0x42 request
[0x6984:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=66 command_id=Command.Read_Attributes_rsp>
[0x6984] Read model 'lumi.switch.b2lc04' and manufacturer 'LUMI' from <Endpoint id=1 in=[basic:0x0000, device_temperature:0x0002, identify:0x0003, groups:0x0004, scenes:0x0005, on_off:0x0006, alarms:0x0009] out=[time:0x000A, ota:0x0019] status=<Status.ZDO_INIT: 1>>
[0x6984] Discovered basic device information for <Device model='lumi.switch.b2lc04' manuf='LUMI' nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=True>
Device is initialized <Device model='lumi.switch.b2lc04' manuf='LUMI' nwk=0x6984 ieee=54:ef:44:10:00:17:e9:2a is_initialized=True>
Checking quirks for LUMI lumi.switch.b2lc04 (54:ef:44:10:00:17:e9:2a)
Considering <class 'zhaquirks.xbee.xbee_io.XBeeSensor'>
Fail because endpoint list mismatch: {232, 230} {1, 2, 242}
Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'>
Fail because endpoint list mismatch: {232, 230} {1, 2, 242}
Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
Fail because endpoint list mismatch: {1} {1, 2, 242}
Considering <class 'zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor'>
Fail because endpoint list mismatch: {1} {1, 2, 242}
Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
Fail because endpoint list mismatch: {1} {1, 2, 242}
Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'>
Fail because endpoint list mismatch: {11, 13} {1, 2, 242}
Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
Fail because endpoint list mismatch: {1} {1, 2, 242}
device - 0x6984:54:ef:44:10:00:17:e9:2a entering async_device_initialized - is_new_join: True
device - 0x6984:54:ef:44:10:00:17:e9:2a has joined the ZHA zigbee network
[0x6984](lumi.switch.b2lc04): started configuration
[0x6984:ZDO](lumi.switch.b2lc04): 'async_configure' stage succeeded
Error handling '_save_attribute' event with (54:ef:44:10:00:17:e9:2a, 1, 0, 4, 'LUMI') params: FOREIGN KEY constraint failed
[0x6984] Extending timeout for 0x44 request
[0x6984:1:0x0000]: finished channel configuration
[0x6984:1:0x0019]: finished channel configuration
[0x6984] Extending timeout for 0x46 request
[0x6984:2:0x0000]: finished channel configuration
Error handling '_save_attribute' event with (54:ef:44:10:00:17:e9:2a, 1, 0, 5, 'lumi.switch.b2lc04') params: FOREIGN KEY constraint failed
[0x6984:1:0x0006]: bound 'on_off' cluster: Status.SUCCESS
[0x6984] Extending timeout for 0x48 request
[0x6984:2:0x0006]: bound 'on_off' cluster: Status.SUCCESS
[0x6984] Extending timeout for 0x4a request
[0x6984:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=72 command_id=Command.Configure_Reporting_rsp>
[0x6984:1:0x0006]: Successfully configured reporting for '{'on_off': (0, 900, 1)}' on 'on_off' cluster: [ConfigureReportingResponseRecord(status=0)]
[0x6984:1:0x0006]: finished channel configuration
[0x6984:1:0x0006]: 'async_configure' stage succeeded
[0x6984:1:0x0000]: 'async_configure' stage succeeded
[0x6984:1:0x0019]: 'async_configure' stage succeeded
[0x6984:2:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=74 command_id=Command.Configure_Reporting_rsp>
[0x6984:2:0x0006]: Successfully configured reporting for 'set()' on 'on_off' cluster
[0x6984:2:0x0006]: Failed to configure reporting for '['on_off']' on 'on_off' cluster: [ConfigureReportingResponseRecord(status=193, direction=0, attrid=0)]
[0x6984:2:0x0006]: finished channel configuration
[0x6984:2:0x0006]: 'async_configure' stage succeeded
[0x6984:2:0x0000]: 'async_configure' stage succeeded
[0x6984](lumi.switch.b2lc04): completed configuration
[0x6984](lumi.switch.b2lc04): stored in registry: ZhaDeviceEntry(name='LUMI lumi.switch.b2lc04', ieee='54:ef:44:10:00:17:e9:2a', last_seen=1636060571.4203372)
[0x6984] Extending timeout for 0x4c request
[0x6984:zdo] ZDO request ZDOCmd.Match_Desc_req: [0xFFFD, 260, [25], []]
[0x6984:1:0x0003] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=76 command_id=Command.Default_Response>
[0x6984:1:0x0003]: executed 'trigger_effect' command with args: '(2, 0)' kwargs: '{}' result: [64, <Status.UNSUP_CLUSTER_COMMAND: 129>]
[0x6984](lumi.switch.b2lc04): started initialization
[0x6984:ZDO](lumi.switch.b2lc04): 'async_initialize' stage succeeded
[0x6984:1:0x0006]: initializing channel: from_cache: False
[0x6984] Extending timeout for 0x4f request
[0x6984:1:0x0000]: initializing channel: from_cache: False
[0x6984:1:0x0000]: finished channel initialization
[0x6984:1:0x0019]: initializing channel: from_cache: False
[0x6984:1:0x0019]: finished channel initialization
[0x6984:2:0x0006]: initializing channel: from_cache: False
[0x6984] Extending timeout for 0x51 request
[0x6984:2:0x0000]: initializing channel: from_cache: False
[0x6984:2:0x0000]: finished channel initialization
[0x6984:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=79 command_id=Command.Read_Attributes_rsp>
[0x6984:1:0x0006]: finished channel initialization
[0x6984:1:0x0006]: 'async_initialize' stage succeeded
[0x6984:1:0x0000]: 'async_initialize' stage succeeded
[0x6984:1:0x0019]: 'async_initialize' stage succeeded
[0x6984:2:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=81 command_id=Command.Read_Attributes_rsp>
[0x6984:2:0x0006]: finished channel initialization
[0x6984:2:0x0006]: 'async_initialize' stage succeeded
[0x6984:2:0x0000]: 'async_initialize' stage succeeded
[0x6984](lumi.switch.b2lc04): power source: Battery or Unknown
[0x6984](lumi.switch.b2lc04): completed initialization
None: polling current state
[0x6984] Extending timeout for 0x53 request
None: polling current state
[0x6984] Extending timeout for 0x55 request
[0x6984:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=83 command_id=Command.Read_Attributes_rsp>
[0x6984:2:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=85 command_id=Command.Read_Attributes_rsp>
[0x6984:zdo] ZDO request ZDOCmd.IEEE_addr_req: [0x0000, 0, 0]
[0x6984:1:0x0019] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=False disable_default_response=False> manufacturer=None tsn=77 command_id=1>
[0x6984:1:0x0019] ZCL request 0x0001: [0, 4447, 6664, 20, None]
[0x6984:1:0x0019] OTA query_next_image handler for 'LUMI lumi.switch.b2lc04': field_control=0, manufacture_id=4447, image_type=6664, current_file_version=20, hardware_version=None
[0x6984:1:0x0019] No OTA image is available

Zigbee signature:

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0100",
      "in_clusters": [
        "0x0000",
        "0x0002",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0009"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "2": {
      "profile_id": 260,
      "device_type": "0x0100",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006"
      ],
      "out_clusters": []
    },
    "242": {
      "profile_id": 41440,
      "device_type": "0x0061",
      "in_clusters": [],
      "out_clusters": [
        "0x0021"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.switch.b2lc04",
  "class": "zigpy.device.Device"

1 post - 1 participant

Read full topic

This template

{{ '{:0.2f}'.format(0.1) }}

Should return 0.10, but returns 0.1.

Likewise

{{ '{:0.3f}'.format(0) }}

returns 0 rather than 0.000.

This is using HA 2021.11.0 via Docker. Do others get the same behaviour?

1 post - 1 participant

Read full topic

The SmartThing integration I installed incorrectly supports the Samsung Dual Oven (model: NV75N5671RM). It gives me entities that only support the top oven and no bottom oven. Any hint on how to fix this?

1 post - 1 participant

Read full topic

Currently, my Tuya ceiling light has a brightness sensor set up:

sensor:
  - platform: template
    sensors:
      brightness_decke:
        friendly_name: "Brightness Ceiling"
        value_template: '{{ state_attr("light.ceiling", "brightness") * 1.5 }}'

This generally works… a second light (LED strip) is using an automation to change its brightness to match the ceiling light, but with a factor of 1.5, since I want it to be brighter than the ceiling light.

alias: LED Strip Brightness match
description: ''
trigger:
  - entity_id: light.ceiling
    platform: state
    attribute: brightness
condition:
  - condition: device
    type: is_on
    device_id: 6ef81025fd62944bce6a24193850779e
    entity_id: light.ceiling
    domain: light
action:
  - delay:
      hours: 0
      minutes: 0
      seconds: 0
      milliseconds: 10
  - data_template:
      brightness: '{{ states.sensor.brightness_decke.state }}'
    entity_id: light.led_strip_1
    service: light.turn_on
mode: single

However, my log is repeatedly showing this:
TemplateError('TypeError: unsupported operand type(s) for *: 'NoneType' and 'float'') while processing template 'Template("{{ state_attr("light.ceiling", "brightness") * 1.5 }}")' for attribute '_attr_native_value' in entity 'sensor.brightness_decke'

No matter if the light is on or not.
Any idea how to clean this up properly?

1 post - 1 participant

Read full topic

Hello.

I am trying to configurate some sensors of my electricity meter.

My hardware is a Carlo Gavazzi EM24… which is connected to a Modbus/TCP converter.

I need the modbus register of the EM24.

Is here somebody who has already installed it?

Thank you a lot.

1 post - 1 participant

Read full topic

Hello everybody,

so I managed to set up a RaspberryPi with HomeAssistant and started to add some sensors and lights and so on.

So today I installed a Shelly 1 in my house to use my normal wall switches for smart and dumb bulbs. In my living room I wanted to set the switches in detached and momentary mode.

And this is where I get completely stocked. I read a lot but I still can‘t figure out how to get things to work in HomeAssistant. I read that I need to set up shelly.click and so much more…

Is there anyone who can help me and explain in details to me how to get a shelly in detached mode to work for the first time?

The Shelly is already integrated and configured natively in HomeAssistant.

Thank you so much!!!

1 post - 1 participant

Read full topic

I have setup Home Assistant in hopes to get this Smart Light Bulb (LIFX) working with it.

I have Home Assistant setup on it’s own VLAN, and plan to have all IoT devices on their own VLANs.

Now my issue is, how do I actually connect this lightbulb to my network without using their proprietary app?
Like when you FIRST plug in the bulb to the socket out of the box, it gives itself some arbitrary IP like 172.0.35.21 and you are supposed to download their proprietary app and set it up. How do I add the bulb onto the network without using their app? Won’t it need the credentials to join the SSID somehow? Where would I enter this?

Once I get it onto the network, I presume it’s as simple as just giving my firewall it’s MAC address, and assigning it a static IP, and just forwarding the port it needs. I saw in docs and in previous forum history people state you can manually configure lifx in the configuration yaml file. But again, you need the IP of the device… or discover it. But again, I do not understand how you do this, when the device isn’t on the network yet.

I guess this question would not only apply to LIFX bulbs, but to any IoT devices really because they all want you to use an app to configure it seems which is annoying.

1 post - 1 participant

Read full topic

I seem some strange things about my disk usages after the latest update. Has something been changed dramatically with the recorder integration? I have nothing special setup, just local on my SD card and only excluded a bunch of entities. However, I all of a sudden see this dramatic increase in usage and apparently a lot more write actions to the SD card, which makes me worry a lot about SD Card life (and actually running out of space really soon…)

Any ideas what is going on here?

1 post - 1 participant

Read full topic