@murmusbahnus wrote:

Hi,
I have a simple automation which sends me a message to my phone when the battery_level of an entity is below 15. As trigger for this automation I have inserted a list of all the entities. Did someone know if i can template this entity list? All entities have “battery_level” in their name.

Here is the code for the automation:

- alias: 'Notify Battery'

  trigger:

    platform: numeric_state

    entity_id: sensor.hue_motion_sensor_wohnzimmer_battery_level,

               sensor.hue_motion_sensor_esszimmer_battery_level,

               sensor.motion_sensor_arbeitszimmer_battery_level,

               sensor.motion_sensor_schlafzimmer_battery_level,

               sensor.arbeitszimmer_dimm_battery_level,

               sensor.button_tim_battery_level,

               sensor.button_kitchen_battery_level,

               sensor.rechtes_fenster_schlafzimmer_battery_level,

               sensor.arbeitszimmer_tuer_battery_level,

               sensor.wc_guests_door_battery_level,

               sensor.lumi_sensor_smoke_battery_level,

               sensor.linkes_fenster_schlafzimmer_battery_level,

               sensor.wohnzimmer_dimm_battery_level,

               sensor.esszimer_fernbedienung_battery_level

    below: '15'

  action:

  - service: notify.ios_devices

    data_template:

        title: "Batterien"

        message: "{{ trigger.to_state.attributes.friendly_name }} benötigt eine neue Batterie!"

        data:

         push:

          thread-id: "Batterie"

  - service: persistent_notification.create

    data_template:

        title: Batterien

        message: "{{ trigger.to_state.attributes.friendly_name }} benötigt eine neue Batterie!"

        notification_id: Batterien

Posts: 6

Participants: 3

Read full topic

@rajan wrote:

I have a bunch of Xiaomi Aqara temperatur sensors connected via deconz to Hassio.
Is it possible to change the icon color of battery_entity when it goes low.
The icons are in ’ Horizontal Stack Card’
Appreciate to know how to proceed …

Posts: 3

Participants: 3

Read full topic

@JamesMatthew wrote:

I just had some pretty weird behaviour after trying out my ConBee II.

My setup

• home assistant version: 0.108.9
• environment: Synology Virtual Machine Manager, ConBee passed via virtual USB controller
• other integrations: HomeMatic connected to a RaspberryMatic, HomeKit

First I set up deCONZ, everything working fine inside, no errors in the logs, but I had some problems pairing a switch, so I reset the conbee from inside phoscon and tried it with zha.
I then disabled start on boot for deCONZ, restarted Home Assistant, and set up zha.
All worked fine again and I was able to pair the switch too, but its events had a huge delay. Thought a restart might help, but after restarting from the UI, the UI didn’t become available again; also ssh didn’t work anymore, both stating “Connection refused”. Home Assistant was pingable.

To solve this, I tried the following to no avail:

• reboot the VM
• disable the USB controller and reboot the VM
• enable the controller but don’t pass the ConBee
• wait about half an hour
• empty caches (though this wouldn’t explain the ssh unavailability)

What solved the issues was using the “core check” command from the cli.
From its description, I thought it would only ‘check’ the configuration and not actually repair anything, but after running the command the UI became immediately available again just like ssh.
Everything kept working as expected after some reboots too.

My issue seems solved, however I would be interested in what went wrong with my setup, as I hadn’t made any changes to the configuration before the problematic restart (apart from some automations with lights which I checked with Check Configuration).
Also, why did core check solve the issue? Does the “validates” in its description in this case include repairing if something erroneous is found too?

Posts: 1

Participants: 1

Read full topic

@bvdbergh wrote:

After an update (fo almost 1 one year) my shutter won’t work. I do not know what is wrong
this is my configuration:

• platform: mqtt
  name: “Zonnescherm_open”
  availability_topic: “tele/Zonnescherm/LWT”
  payload_available: “Online”
  payload_not_available: “Offline”
  position_topic: stat/Zonnescherm/SHUTTER1
  position_open: 100
  position_closed: 0
  set_position_topic: “cmnd/Zonnescherm/shutterposition”
  command_topic: “cmnd/Zonnescherm/backlog”
  payload_open: “SHUTTEROPEN”
  payload_close: “SHUTTERCLOSE”
  payload_stop: “SHUTTERSTOP”
  retain: false
  optimistic: false
  qos: 1

Posts: 1

Participants: 1

Read full topic

@thehocrba wrote:

Hi,

I am trying to migrate to HA.
I am using rpi3+ zme_uzb1 stick.
After adding a fibaro relay with success ( node50:complete), and adding a button to lovelace dashboard, i can see the button changes it’s state when using the physical button.
but when I try to use the button on the dashboard nothing happens, and there is a line in the log “node presumed dead” even though it is still getting information from the device.

I have tried troubleshooting it with a different relay and i am getting the same result.
i will appreciate any kind of advice

log:

2020-04-29 17:00:30.372 Info, Node050, Response RTT 7093 Average Response RTT 5092
2020-04-29 17:00:30.372 Info, Node050, Received SwitchBinary report from node 50: level=Off
2020-04-29 17:00:30.372 Detail, Node050, Refreshed Value: old value=true, new value=false, type=bool
2020-04-29 17:00:30.372 Detail, Node050, Changes to this value are not verified
2020-04-29 17:00:30.372 Detail, Node050, Notification: ValueChanged
2020-04-29 17:00:30.438 Detail, Node050, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x32, 0x03, 0x25, 0x03, 0x00, 0xd8, 0x00, 0x3f
2020-04-29 17:00:30.439 Detail,
2020-04-29 17:00:30.439 Info, Node050, Response RTT 7159 Average Response RTT 6125
2020-04-29 17:00:30.439 Info, Node050, Received SwitchBinary report from node 50: level=Off
2020-04-29 17:00:30.439 Detail, Node050, Refreshed Value: old value=false, new value=false, type=bool
2020-04-29 17:00:30.439 Detail, Node050, Changes to this value are not verified
2020-04-29 17:00:30.439 Detail, Node050, Notification: ValueChanged
2020-04-29 17:00:30.503 Detail, Node050, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x32, 0x03, 0x25, 0x03, 0x00, 0xd7, 0x00, 0x30
2020-04-29 17:00:30.503 Detail,
2020-04-29 17:00:30.503 Info, Node050, Response RTT 7224 Average Response RTT 6674
2020-04-29 17:00:30.503 Info, Node050, Received SwitchBinary report from node 50: level=Off
2020-04-29 17:00:30.503 Detail, Node050, Refreshed Value: old value=false, new value=false, type=bool
2020-04-29 17:00:30.503 Detail, Node050, Changes to this value are not verified
2020-04-29 17:00:30.503 Detail, Node050, Notification: ValueChanged
2020-04-29 17:00:30.526 Detail, Node050, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x32, 0x03, 0x25, 0x03, 0x00, 0xd7, 0x00, 0x30
2020-04-29 17:00:30.526 Detail,
2020-04-29 17:00:30.526 Info, Node050, Response RTT 7247 Average Response RTT 6960
2020-04-29 17:00:30.526 Info, Node050, Received SwitchBinary report from node 50: level=Off
2020-04-29 17:00:30.526 Detail, Node050, Refreshed Value: old value=false, new value=false, type=bool
2020-04-29 17:00:30.526 Detail, Node050, Changes to this value are not verified
2020-04-29 17:00:30.527 Detail, Node050, Notification: ValueChanged
2020-04-29 17:00:30.574 Detail, Node050, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x32, 0x03, 0x25, 0x03, 0x00, 0xd7, 0x00, 0x30
2020-04-29 17:00:30.574 Detail,
2020-04-29 17:00:30.574 Info, Node050, Response RTT 7295 Average Response RTT 7127
2020-04-29 17:00:30.575 Info, Node050, Received SwitchBinary report from node 50: level=Off
2020-04-29 17:00:30.575 Detail, Node050, Refreshed Value: old value=false, new value=false, type=bool
2020-04-29 17:00:30.575 Detail, Node050, Changes to this value are not verified
2020-04-29 17:00:30.575 Detail, Node050, Notification: ValueChanged
2020-04-29 17:00:30.601 Detail, Node050, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x32, 0x03, 0x25, 0x03, 0x00, 0xd5, 0x00, 0x32
2020-04-29 17:00:30.601 Detail,
2020-04-29 17:00:30.601 Info, Node050, Response RTT 7322 Average Response RTT 7224
2020-04-29 17:00:30.601 Info, Node050, Received SwitchBinary report from node 50: level=Off
2020-04-29 17:00:30.601 Detail, Node050, Refreshed Value: old value=false, new value=false, type=bool
2020-04-29 17:00:30.601 Detail, Node050, Changes to this value are not verified
2020-04-29 17:00:30.601 Detail, Node050, Notification: ValueChanged
2020-04-29 17:00:30.627 Detail, Node050, Received: 0x01, 0x0b, 0x00, 0x04, 0x10, 0x32, 0x03, 0x25, 0x03, 0x00, 0xd5, 0x00, 0x22
2020-04-29 17:00:30.627 Detail,
2020-04-29 17:00:30.627 Info, Node050, Response RTT 7348 Average Response RTT 7286
2020-04-29 17:00:30.627 Info, Node050, Received SwitchBinary report from node 50: level=Off
2020-04-29 17:00:30.628 Detail, Node050, Refreshed Value: old value=false, new value=false, type=bool
2020-04-29 17:00:30.628 Detail, Node050, Changes to this value are not verified
2020-04-29 17:00:30.628 Detail, Node050, Notification: ValueChanged
2020-04-29 17:00:33.280 Error, Node050, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-04-29 17:00:33.280 Detail, Node050, Removing current message
2020-04-29 17:00:33.280 Detail, Node050, Notification: Notification - TimeOut
2020-04-29 17:00:33.284 Detail, Node050, Query Stage Complete (Session)
2020-04-29 17:00:33.284 Detail, Node050, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2020-04-29 17:00:33.285 Detail, Node050, QueryStage_Dynamic
2020-04-29 17:00:33.285 Detail, Node050, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchBinaryCmd_Get (Node=50): 0x01, 0x0d, 0x00, 0x13, 0x32, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x25, 0x02, 0x25, 0x13, 0xa9
2020-04-29 17:00:33.285 Detail, Node050, Queuing (Send) MultiChannel Encapsulated (instance=2): SwitchBinaryCmd_Get (Node=50): 0x01, 0x0d, 0x00, 0x13, 0x32, 0x06, 0x60, 0x0d, 0x01, 0x02, 0x25, 0x02, 0x25, 0x14, 0xad
2020-04-29 17:00:33.285 Detail, Node050, Queuing (Query) Query Stage Complete (Dynamic)
2020-04-29 17:00:33.285 Detail,
2020-04-29 17:00:33.285 Info, Node050, Sending (Send) message (Callback ID=0x13, Expected Reply=0x04) - MultiChannel Encapsulated (instance=1): SwitchBinaryCmd_Get (Node=50): 0x01, 0x0d, 0x00, 0x13, 0x32, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x25, 0x02, 0x25, 0x13, 0xa9
2020-04-29 17:00:33.294 Detail, Node050, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-29 17:00:33.295 Detail, Node050, ZW_SEND_DATA delivered to Z-Wave stack
2020-04-29 17:00:34.307 Detail, Node050, Received: 0x01, 0x05, 0x00, 0x13, 0x13, 0x01, 0xfb
2020-04-29 17:00:34.308 Detail, Node050, ZW_SEND_DATA Request with callback ID 0x13 received (expected 0x13)
2020-04-29 17:00:34.308 Info, Node050, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-04-29 17:00:34.308 Warning, Node050, WARNING: Device is not a sleeping node.
2020-04-29 17:00:34.308 Detail, Node001, Expected callbackId was received
2020-04-29 17:00:38.320 Detail, Node050, Received: 0x01, 0x05, 0x00, 0x13, 0x13, 0x01, 0xfb
2020-04-29 17:00:38.320 Detail, Node050, ZW_SEND_DATA Request with callback ID 0x13 received (expected 0x00)
2020-04-29 17:00:38.320 Warning, Node050, WARNING: Unexpected Callback ID received
2020-04-29 17:00:42.343 Detail, Node050, Received: 0x01, 0x05, 0x00, 0x13, 0x13, 0x01, 0xfb
2020-04-29 17:00:42.343 Detail, Node050, ZW_SEND_DATA Request with callback ID 0x13 received (expected 0x00)
2020-04-29 17:00:42.343 Warning, Node050, WARNING: Unexpected Callback ID received
2020-04-29 17:00:43.286 Error, Node050, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-04-29 17:00:43.286 Detail, Node050, Removing current message
2020-04-29 17:00:43.287 Detail, Node050, Notification: Notification - TimeOut
2020-04-29 17:00:43.290 Detail,
2020-04-29 17:00:43.290 Info, Node050, Sending (Send) message (Callback ID=0x14, Expected Reply=0x04) - MultiChannel Encapsulated (instance=2): SwitchBinaryCmd_Get (Node=50): 0x01, 0x0d, 0x00, 0x13, 0x32, 0x06, 0x60, 0x0d, 0x01, 0x02, 0x25, 0x02, 0x25, 0x14, 0xad
2020-04-29 17:00:43.299 Detail, Node050, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-29 17:00:43.299 Detail, Node050, ZW_SEND_DATA delivered to Z-Wave stack
2020-04-29 17:00:50.314 Detail, Node050, Received: 0x01, 0x05, 0x00, 0x13, 0x14, 0x01, 0xfc
2020-04-29 17:00:50.314 Detail, Node050, ZW_SEND_DATA Request with callback ID 0x14 received (expected 0x14)
2020-04-29 17:00:50.314 Info, Node050, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-04-29 17:00:50.315 Warning, Node050, WARNING: Device is not a sleeping node.
2020-04-29 17:00:50.315 Detail, Node001, Expected callbackId was received
2020-04-29 17:00:53.291 Error, Node050, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-04-29 17:00:53.291 Detail, Node050, Removing current message
2020-04-29 17:00:53.291 Detail, Node050, Notification: Notification - TimeOut
2020-04-29 17:00:53.295 Detail, Node050, Query Stage Complete (Dynamic)
2020-04-29 17:00:53.295 Detail, Node050, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2020-04-29 17:00:53.295 Detail, Node050, QueryStage_Configuration
2020-04-29 17:00:53.295 Detail, Node050, QueryStage_Complete
2020-04-29 17:00:53.295 Warning, CheckCompletedNodeQueries m_allNodesQueried=1 m_awakeNodesQueried=1
2020-04-29 17:00:53.295 Detail, Node050, Notification: NodeQueriesComplete
2020-04-29 17:01:09.057 Info, Node050, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2020-04-29 17:01:09.057 Info, Node050, SwitchBinary::Set - Setting node 50 to On
2020-04-29 17:01:09.057 Detail, Node050, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchBinaryCmd_Set (Node=50): 0x01, 0x0e, 0x00, 0x13, 0x32, 0x07, 0x60, 0x0d, 0x01, 0x01, 0x25, 0x01, 0xff, 0x25, 0x15, 0x51
2020-04-29 17:01:09.057 Detail, Node050, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchBinaryCmd_Get (Node=50): 0x01, 0x0d, 0x00, 0x13, 0x32, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x25, 0x02, 0x25, 0x16, 0xac
2020-04-29 17:01:09.058 Detail,
2020-04-29 17:01:09.058 Info, Node050, Sending (Send) message (Callback ID=0x15, Expected Reply=0x13) - MultiChannel Encapsulated (instance=1): SwitchBinaryCmd_Set (Node=50): 0x01, 0x0e, 0x00, 0x13, 0x32, 0x07, 0x60, 0x0d, 0x01, 0x01, 0x25, 0x01, 0xff, 0x25, 0x15, 0x51
2020-04-29 17:01:09.070 Detail, Node050, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-29 17:01:09.070 Detail, Node050, ZW_SEND_DATA delivered to Z-Wave stack
2020-04-29 17:01:15.074 Detail, Node050, Received: 0x01, 0x05, 0x00, 0x13, 0x15, 0x01, 0xfd
2020-04-29 17:01:15.075 Detail, Node050, ZW_SEND_DATA Request with callback ID 0x15 received (expected 0x15)
2020-04-29 17:01:15.075 Info, Node050, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-04-29 17:01:15.075 Warning, Node050, WARNING: Device is not a sleeping node.
2020-04-29 17:01:15.075 Error, Node050, ERROR: node presumed dead
2020-04-29 17:01:15.075 Detail, Node001, Expected callbackId was received
2020-04-29 17:01:15.075 Detail, Node001, Expected reply was received
2020-04-29 17:01:15.075 Detail, Node001, Message transaction complete
2020-04-29 17:01:15.075 Detail,
2020-04-29 17:01:15.075 Detail, Node050, Removing current message
2020-04-29 17:01:15.075 Detail, Node050, Notification: Notification - Node Dead
2020-04-29 17:01:15.079 Error, Node050, ERROR: Dropping command because node is presumed dead
2020-04-29 17:01:15.079 Detail, Node050, Removing current message
2020-04-29 17:03:31.245 Detail, Node050, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x32, 0x03, 0x25, 0x03, 0xff, 0xc9, 0x00, 0xd1
2020-04-29 17:03:31.245 Detail,
2020-04-29 17:03:31.245 Error, Node050, WARNING: node revived
2020-04-29 17:03:31.245 Info, Node050, Received SwitchBinary report from node 50: level=On
2020-04-29 17:03:31.245 Detail, Node050, Refreshed Value: old value=false, new value=true, type=bool
2020-04-29 17:03:31.246 Detail, Node050, Changes to this value are not verified
2020-04-29 17:03:31.246 Detail, Node050, Notification: Notification - Node Alive
2020-04-29 17:03:31.249 Detail, Node050, Notification: ValueChanged
2020-04-29 17:03:31.310 Detail, Node050, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x32, 0x03, 0x25, 0x03, 0xff, 0xd7, 0x00, 0xcf

Posts: 1

Participants: 1

Read full topic

@SKAL wrote:

Hello everybody.
I’ve just recived an aqara motion sensor.
I’ve noticed that apart the binary motion sensor and the lux one, it has also a temperature one.

The problem is that the last one has a completely uncorrect value since it says there are 29° C when a aqara multisensor gives me 19°C (which is more correct).

Am I the only one who has this difference of 10 degrees?

Posts: 1

Participants: 1

Read full topic

@robbie.huffman wrote:

I’m working on something to send TurnTouch remote info via MQTT. Right now, the topics look like this:

turntouch/battery 80
turntouch/mode lights

I’ve set up two sensors as such:

sensor:
  - platform: mqtt
    state_topic: 'turntouch/mode'
    name: turntouch_mode
    unique_id: turntouch_mode
    value_template: '{{ value_json }}'
  - platform: mqtt
    state_topic: 'turntouch/battery'
    name: turntouch_battery
    unique_id: turntouch_battery
    unit_of_measurement: '%'
    value_template: '{{ value_json }}'
    device_class: battery

The battery info works great! But the mode sensor is either blank or ‘unknown’.

I can see the data coming in the debug log:

2020-04-29 10:43:31 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on turntouch/battery: b'31'
2020-04-29 10:44:44 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on turntouch/mode: b'media'
2020-04-29 10:44:48 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on turntouch/mode: b'lights'

So I think I’m missing something conceptual here. I was hoping the sensor would show changes in the mode. I’ve tried mode both with and without the RETAIN flag. The end goal is to be able to trigger changes based on the current state.

Is there some smarter way I should be trying to accomplish this?

Thank you for your help!

Posts: 1

Participants: 1

Read full topic

@Porzioev wrote:

Hi, I’m newbie. So sorry if I’m writing wrong section.

My question is about the automation.

I would know if an automation start with the trigger and wait for the condition, or start only when the trigger is on the condition event.

In both cases how to get the other way working?

For example:
I want that a trigger is read only after 2 hours of working condition.

Shut down my deumidificator socket (Shelly) only if, after 2 hours of working condition above 200watt, it fall under 50watt.
It would mean that the sensors of full-tank switch off the compressor and it is beeping noise in the night (so only between 00:00 and 08:00)
So in that case I want to shoot it off.

Any suggestions on how to concatenate trigger and/or/waiting/ conditions?

Thanks you very much!

Posts: 1

Participants: 1

Read full topic

@hikingguy43 wrote:

Need some direction/ideas in how to setup an automation and then the Alert to SMS as I have read a number of posts and tried a number of ideas but just cannot seem to figure out what I need to do. I have a number of freezers and the below template gets me any that have temperature in the name and are above a set temp but when I add it to the message section of the automation it either does not work or is automatically removed by the editor.

Template:
{%-for state in states.sensor
if (state.entity_id.find("temperature") | int>=0) and (state.state == 'unknown' or (state.state | int>=20))%}
{{state.name}} :: {{state.state_with_unit}}
{%-endfor%}

Current Automation:
- id: '1580850664300'
alias: Freezer Notification - Run every 10 min
description: ''
- minutes: /10
platform: time_pattern
seconds: '00'
condition:
- condition: or
conditions:
- above: '20'
condition: numeric_state
entity_id: sensor.freezer_one_temperature
- above: '20'
condition: numeric_state
entity_id: sensor.freezer_two_temperature
- above: '20'
condition: numeric_state
entity_id: sensor.freezer_three_temperature
- above: '20'
condition: numeric_state
entity_id: sensor.freezer_four_temperature
- above: '20'
condition: numeric_state
entity_id: sensor.freezer_five_temperature
action:
- data:
message: >
{%if(state.entity_id.find("temperature") | int>=0) and (state.state == 'unknown' or (state.state | int>=20))%}
{{state.name}} :: {{state.state_with_unit}}
{%endif%}
title: Freezer(s) reporting temperature issue
service: notify.sms

Posts: 1

Participants: 1

Read full topic

@didivava wrote:

I have issue with ffmpeg, after hours of debug, I try to bring it out

1. Environment: Window 10 64bit, install using pip3, run use hass --open-ui
2. ffmpeg installed, set path, test running stand alone ok
3. Now add a very simple ffmpeg like this to configuration

camera:
  - platform: ffmpeg
    input: https://file-examples.com/wp-content/uploads/2017/04/file_example_MP4_480_1_5MG.mp4
    name: valies

4. Add picture entity card, thumb image show up
   
   image958×413 76 KB
5. Play video, get error

2020-04-29 21:48:27 DEBUG (MainThread) [haffmpeg.core] Start FFmpeg with ['ffmpeg', '-i', 'https://file-examples.com/wp-content/uploads/2017/04/file_example_MP4_480_1_5MG.mp4', '-an', '-c:v', 'mjpeg', '-pred', '1', '-f', 'mpjpeg', '-']
2020-04-29 21:48:27 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback _ProactorReadPipeTransport._loop_reading()
Traceback (most recent call last):
  File "c:\users\XX\appdata\local\programs\python\python37\lib\asyncio\proactor_events.py", line 274, in _loop_reading
    self._read_fut = self._loop._proactor.recv(self._sock, 32768)
  File "c:\users\XXX\appdata\local\programs\python\python37\lib\asyncio\windows_events.py", line 423, in recv
    self._register_with_iocp(conn)
  File "c:\users\XXX\appdata\local\programs\python\python37\lib\asyncio\windows_events.py", line 650, in _register_with_iocp
    _overlapped.CreateIoCompletionPort(obj.fileno(), self._iocp, 0, 0)
OSError: [WinError 87] The parameter is incorrect

You can see above ffmpeg command I dump out, I have tested this in cmd and everything run fine, return ton of raw data

ffmpeg -i https://file-examples.com/wp-content/uploads/2017/04/file_example_MP4_480_1_5MG.mp4 -an -c:v mjpeg -pred 1 -f mpjpeg -

So issue is somewhat handling data return form ffmpeg, dont know what s problem. I never code python before so have no clue what s going on, just guess asyncio is like something similar to ajax call in javascript or socket call with ton of await async. Also confirm https of above mp4 do nothing to error because I have tested other url, my camera rtsp, etc…

Could anyone help. Tks

Posts: 1

Participants: 1

Read full topic

@Lemmings23456 wrote:

Hi there,
I’m running HA 0.108.9 on Synology Docker and every few seconds I can see something like this in the log files:

Bildschirmfoto 2020-04-29 um 17.20.462872×1438 962 KB

All components of Homematic work like they should, but the logfile reports these infos.
The continue without end and I can’t see certain components, nearly all of Homematic.

What can I do to get rid of that ? Am I in trouble ?

Greetings,
Oliver

Posts: 1

Participants: 1

Read full topic

@Lemmings23456 wrote:

Hi there,
I’m running HA 0.108.9 on Synology Docker and have HACS installed. But after a reboot it seems, that HACS is running for the first time although it was initialized before.

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 216, in async_setup
    hass, self
  File "/config/custom_components/hacs/__init__.py", line 85, in async_setup_entry
    startup_result = await hacs_startup()
  File "/config/custom_components/hacs/__init__.py", line 164, in hacs_startup
    await setup_frontend()
  File "/config/custom_components/hacs/setup.py", line 103, in setup_frontend
    require_admin=True,
  File "/usr/src/homeassistant/homeassistant/components/frontend/__init__.py", line 190, in async_register_built_in_panel
    raise ValueError(f"Overwriting panel {panel.frontend_url_path}")
ValueError: Overwriting panel hacs

Any suggestions…?

Thanks,
Oliver

Posts: 1

Participants: 1

Read full topic

@revelare wrote:

Hi, I cannot change the orange colour of the top screen .
Where can I change this one? I am trying to switch between the themes - but still orange is there…

Posts: 1

Participants: 1

Read full topic

@agilani wrote:

I am new to the home assistant. I am trying to create an automation to turn the light on using a sonoff switch when the motion is detected but only when the blink is armed. If the switch turns on then turn it off after 10 minutes. I am not able to find how to check the state of the system.

- id: '1588172004740'
  alias: Front Door Light Turns On When Motion Detected
  description: Front Camera Motion Detected Front Door Light Turn on
  trigger:
  - entity_id: binary_sensor.blink_front_motion_detected
    from: 'off'
    platform: state
    to: 'on'
  condition:
  - condition: state
    entity_id: binary_sensor.blink_front_camera_armed
    state: 'on'
  action:
  - data: {}
    entity_id: switch.sonoff_100057c411
    service: switch.turn_on
  - delay: 00:00:10
  - data: {}
    entity_id: switch.sonoff_100057c411
    service: switch.turn_off

Can an experience person tell me where i am wrong.

Posts: 1

Participants: 1

Read full topic

@mike.hughes wrote:

Hi everyone,

I’m currently in the process of adding all my various smart home devices into HA, but I have run into an issue which I have got completely stuck on.

I have a lot of different integrations which i am then using homekit component to pass into homekit.

Tradfri is currently integrated into homekit directly. The issue i have is that I want to use my tradfri devices in HA for Automations, so i setup tradfri integration in HA. I then obviously don’t want the tradfri devices to then be duplicated in homekit via the homekit component.

I have read about using filters on homekit to exclude domains etc however I cannot work out how to make the component to block all the tradfri devices and nothing else.

I don’t have the option to leave tradfri running only through HA as I have over 100 tradfri devices, bringing the total of entities to 185.

Can someone please tell me how to use the filter to exclude all tradfri devices?

Thanks,

Mike.

Posts: 1

Participants: 1

Read full topic

@Lemmings23456 wrote:

Hi there,
I’m running HA 0.180.9 in a Docker on Synology.

As you can see in the screenshot, the log files show different timezones.

Bildschirmfoto 2020-04-29 um 17.36.351712×1632 515 KB

The correct time is in the log file, the container is wrong and two hours behind.
I’ve tried many docker starts like these:

sudo docker run -id --name=home-assistant --restart=always -v /etc/TZ:/etc/timezone:ro -p 8123:8123 -e “TZ=Europe/Berlin” --net=host -v /volume1/docker/home-assistant:/config homeassistant/home-assistant:latest

sudo docker run -id --name=home-assistant --restart=always -v /etc/timezone:/etc/timezone:ro -p 8123:8123 -e “TZ=Europe/Berlin” --net=host -v /volume1/docker/home-assistant:/config homeassistant/home-assistant:latest
docker: Error response from daemon: Bind mount failed: ‘/etc/timezone’ does not exists.

All these starts have no effect. Still wrong. You could say it doesn’t matter here but the main problem is, that the data in the database is wrong, too.
I’m using MariaDB on Synology, but not I docker, I use the package. The Timezone in MariaDB is set to “System”.

Whenever I query for some data from HomeAssistant.states ´, I have to add the correct amount of hours compared to UTC-Time.
Really annoying.

Automations or trigger DO have the right time.

Any idea ?
Greetings,
Oliver

Posts: 1

Participants: 1

Read full topic

@ob2s wrote:

In the UI I have this card with Wyze entities on in

If I click an entity, I get this information.

The battery information is not exposed as a sensor, but I’d like to access it. The only way I found is to turn on debug, and go trip the sensor, then log scrape, essentially the opposite of automation. Is there anyway I can run some sort of script to extract this information ? I am not interested in displaying it, just processing it. Thanks

Posts: 1

Participants: 1

Read full topic

@fabio.bocchini wrote:

Hello every one I have a problem with gpio on Home assistant, someone can help me? my installation is on rspberry pi 3b and when I try to modify the configuration. yaml file nothing apper on the main page of home assistant.

this is my code:

Example configuration.yaml entry

switch:

• platform: rpi_gpio
  ports:
  11: Fan Office
  12: Light Desk

Posts: 2

Participants: 1

Read full topic

@varyamereon wrote:

Hi there folks, first post here…

I am trying to set up a custom chart card for my Dyson fans where the colour changes according to the air quality levels (as it does in the Dyson app). I am wondering if anyone has found where those thresholds between levels are listed?

Many thanks!!
Will

Posts: 1

Participants: 1

Read full topic

@david_b wrote:

2020-04-29 16:56:29 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.2754213200] Error handling message: required key not provided @ data[‘category’]. Got None

Can anyone point me in the right direction as I dont know where to start with this error as it’s a bit vague.

Thanks
David

Posts: 1

Participants: 1

Read full topic