@jfka18 wrote:

I am running HA on:

• Raspberry PI 4
• HA version 0.109.6
• ffmpeg version 4.1.4-1+rpt7~deb10u1
• I am running in a virtual Python environment with, hass --open-ui

I have tested my RTSP stream in vlc, and using ffmpeg and both are successful. I have replicated the arguments that HA passes to ffmpeg and it is successful streaming when outside of HA. I have tried about 10 different extra_argument configurations as well, basically whatever I could find through this forum and other googling that people have tried and all get the same result, which is no errors in HA but no picture or stream on my screen.

Configuration in YAML
ffmpeg:
ffmpeg_bin: /usr/bin/ffmpeg

camera:

• platform: ffmpeg
  name: Front Door Camera
  input: -rtsp_transport tcp rtsp://admin:password@192.168.0.21:554/ch01/1

Configuration in Lovelace
cards:
- type: picture-entity
entity: camera.front_door_camera
camera_view: live

On the screen, it shows:
Preview of the Front Door Camera camera
It also has the footer with an Idle state.

If I grep the log from hass --open-ui for ffmpeg.core, this is what I get:
2020-05-14 12:15:48 DEBUG (MainThread) [haffmpeg.core] Start FFmpeg with [’/usr/bin/ffmpeg’, ‘-version’, ‘’]
2020-05-14 12:15:57 DEBUG (MainThread) [haffmpeg.core] Start FFmpeg with [’/usr/bin/ffmpeg’, ‘-rtsp_transport’, ‘tcp’, ‘rtsp://admin:password@192.168.0.21:554/ch01/1’, ‘-an’, ‘-c:v’, ‘mjpeg’, ‘-pred’, ‘1’, ‘-f’, ‘mpjpeg’, ‘-’]

Any help would be greatly appreciated. Thanks.

Jeff

Posts: 1

Participants: 1

Read full topic

@At3 wrote:

Simple question for you guys I think. But I have a automation where the lights dim when the TV is playing (state playing). That works fine. But now it does that when playing anything. So I want to put a condition that it does only dim the lights when Netflix or Kodi is open and playing. So trigger when playing but condition only when kodi or Netflix is open.
So the entity is media_player.philips_tv
It has a attribute source which I want to use as condition. How do I put it in the condition?

Is it something like media_player.philips_tv.attribute.source? Or am I thinking it all wrong? The states of source are easy to find. Just need to know how to look in this attribute as condition.

Posts: 1

Participants: 1

Read full topic

@karldonteljames wrote:

Evening All,
I had an issue where new devices were not being exposed to my Amazon Echos, so today I cleared al of my previous devices in the Alexa app, and rescanned for devices.
Now no devices are now being exposed to Amazon.

I have tried to disable the home assistant skill, followed by enabling it, reconnecting my account and then running a discover.
I have tried to sign out of my Nabucasa account, and sign back in, within homeassistant followed by a discover.
I have tried the sync-entires button, followed by a discover devices in the app.

My nabucasa account is live and active
My password hasn’t changed recently.

Any ideas why my devices are suddenly not showing?

Posts: 2

Participants: 2

Read full topic

@f00dagi wrote:

Hi!

I would like to list (separated by comma) the friendly_name of all lights that are unavailable.

I got this far but then I got stuck.

{{ states.light|selectattr('state','equalto','unavailable')|list|join('\n') }}

It returns the text below where I can see the friendly_name, but I do not know how to extract it.

<template state light.portable_2=unavailable; restored=True, supported_features=40, friendly_name=portable 2 @ 2020-05-11T22:57:59.805573+02:00>
<template state light.sovrum_sangbord_daniel=unavailable; friendly_name=sovrum (sängbord daniel), supported_features=33 @ 2020-05-11T22:57:30.971928+02:00>
<template state light.sovrum_sangbord_ninni=unavailable; friendly_name=sovrum (sängbord ninni), supported_features=33 @ 2020-05-12T19:51:07.774874+02:00>
<template state light.tradfri_bulb_8=unavailable; restored=True, supported_features=0 @ 2020-05-11T22:57:59.811603+02:00>
<template state light.tyra_fonster_3=unavailable; friendly_name=tyra (fönster), supported_features=33 @ 2020-05-11T22:57:30.968700+02:00>

Thanks!

Posts: 1

Participants: 1

Read full topic

@aming-miyembro wrote:

They seem to be the result of some sort of glitch with a device entity. Or not?
They’re not stored in core.entity_registry – are they stored anywhere?
If not, how does Home Assistant know about them?

I have an “unnamed_device” that’s a doppleganger of an item in core.entity_registry – though that item entity is non-functional, and I can’t tell in the core.entity_registry why it’s broken.
Is there some typical/generic way to resolve unnamed_device entities?

A search run on the community forum shows many folks suffer from these. It would be helpful there be a way to repair them. If it’s already documented, please point me to it.

Thanks.

Posts: 1

Participants: 1

Read full topic

@schale01 wrote:

So I’m trying to get webhooks working to get information to Home assistant from IFTTT
I got the webhook deliverying data to the server but I can’t seem to get it to parse the data correcly.

I used the template provided at https://www.home-assistant.io/integrations/ifttt/ to create my webhook and Automation.
IFTTT Webhook

URL: https://MYDOMAIN.duckdns.org/api/webhook/LONG-API-TOKEN
Method: POST
Content type: Application/Json
Body: { “action”: “call_service”, “service”: “script.turn_on”, “entity_id”: “script.1579661587176” }

I pasted the following into the /config/automations.yaml (not sure this is where this is even suppose to go but it’s the only place I wasn’t getting a syntax error from the file editor)

- id: '1579661379561'
  alias: Webhooks
  trigger:
  - event_data:
      action: call_service
    event_type: ifttt_webhook_received
    platform: event
  condition: []
  action:
  - data_template:
    entity_id: '{{ trigger.event.data.entity_id }}'
    service_template: '{{ trigger.event.data.service }}'

When I could not get the above to work I tried creating the automation through the UI but couldn’t get all the syntax correct. I instead created a very simple automation that ignored all Body data from the post and just looked for a webhook received.

I was able to trigger the script with the following automation, but as you can see it ignores all data passed in body so any webhook will trigger the script which is not desired behavior but does it confirm that the server is receiving the post from the webhook and the issue is likely in the syntax/setup of my automation. Any guidance would be helpful.

- id: '1589415747273'
  alias: Test Webhooks
  description: ''
  trigger:
  - event_data: {}
    event_type: ifttt_webhook_received
    platform: event
  condition: []
  action:
  - data: {}
    service: script.1579661587176

Posts: 2

Participants: 2

Read full topic

@XxTexMex wrote:

Hi all
I have a Sonoff wich control a Gate, so i need to turn it on and than after some seconds turn it off.
The problem is that i don’t want to create a trigger for turning it off everitime it goes on, because sometimes i have to wait for another event before stopping it.
I want something that turn it on and than turn it off after clicking it like a button, for using it with the Siri assistant on HomeKit.
The expected final result should be a “Ehi Siri, open the gate” command that activates the sonoff by switching it off immediately afterwards.

Can you give me a code example for helping me out.
Thanks

Posts: 1

Participants: 1

Read full topic

@sirvictory444 wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic

@demi wrote:

At the moment im running hass.io on a Pi4 and have a cc2531 stick connected to it to be able to connect zigbee devices.
i have already installed both the zigbee2mqtt and the Mosquitto broker.
Whenever I try to pair my Xiaomi Aqara sensors with it the log shows the following:

zigbee2mqtt:info  2020-05-15 01:18:34: MQTT publish: topic 'zigbee2mqtt/0x00158d000446ce5a', payload '{"battery":100,"voltage":3055,"contact":true,"linkquality":115}'

so it does realize that there is something there, however it doesn’t add the sensors right away the zigbee2mqtt.io site states that to connect a device the log should show something along the lines of this:

zigbee2mqtt:info  2019-11-09T12:19:56: Successfully interviewed '0x00158d0001dc126a', device has successfully been paired

what am I doing wrong or how do I add the devices manually with the info provided form my log?

Posts: 1

Participants: 1

Read full topic

@dopecoder wrote:

I am a newbie and have HASSIO running on VirtualBox on a windows machine which is running fine.

I know it has portainer and home assistant is running in a docker within the HASSIO system. I need to install an app from github that needs to be in a docker. unfortunately docker-compose doesnt work in hassio it says command not found which is strange as i can see dockers for ha and other add ons.

Please let me know if i can create a new docker via ssh on HASSIO and how i can do that.

Thanks for your help

Posts: 2

Participants: 2

Read full topic

@mkanet wrote:

I am trying to convert bps to Mbps in a temple. However, the result state value is just “unknown”.

Could someone please tell me what I’m doing wrong in the below template?

      my_download_speed:
        friendly_name: 'My Download Speed'
        value_template: "{{ state_attr('sensor.my_network_0_bps_received') | multiply(0.0000001) | float }}"
        unit_of_measurement: "Mbps"

Posts: 5

Participants: 2

Read full topic

@fversteegen wrote:

I would like to create a bind mount for a hassio addon (in this specific case for Motioneye, but I believe the question is generic for all add-ons).

The only solution I have figured out thus far is by editing the add-on container in Portainer, but a new version of the add-on will undo these edits, so I believe there should be a way to do a bind mount in the add-ons config. Question is: how ?

Posts: 1

Participants: 1

Read full topic

@sithmein wrote:

I have some temperature sensors that - for whatever reason - produce short spikes every other hour where the measured temperature is around 0.5 larger for a single measurement (they send values every 30 seconds). So I thought, let’s try out filters. I tried the outlier filter, which seems to be a perfect fit, and also the moving average filter. However it seems the previous values they take into account are not the previously reported values from the sensors but the previous values where the last change occurred. This means if I set the radius for the outlier filter to 0.4 and the number of samples to 3 this does not mean I uses the values from the previous 1.5 minutes, which were constant and thus the 0.5 degree spike is classified as an outlier. Instead values from much longer ago are used and since they are resulting from changes the radius of 0.4 isn’t appropriate any more. Basically the same problem arises with the moving average. Either I’m missing something here or there is a serious design flaw in how filters are implemented.

Posts: 1

Participants: 1

Read full topic

@rspittle wrote:

Hi

I am new to Home Assistant & in the process of trying to change across from my Vera platform to HA.

I have a number of temperature sensors that are input via modbus. When the measured temperatures are under 0 degrees, the sensor value is 1000 less the actual temperature ( eg if the temperature is -1.2 degrees, then the sensor value is 1001.3.

I need a simple IF function that will return the raw sensor value for sensor values < 1000 and (- sensor value -1000) for values > 1000.

I think the way to go is to use a sensor template, but are completely lost on how to do this as the examples for templates seem to be based on states rather than state values

My sensor entity ID is sensor.outside_west_temp

Any help appreciated.

Posts: 1

Participants: 1

Read full topic

@beanbag wrote:

Hi all,

I’ve just switched from OpenHAB to Home Assistant and all has gone great aside from a couple of issues. Firstly, I’ve set everything up on a new Raspberry Pi. Originally I started with OpenHAB, transferring my Windows server setup to the Raspberry Pi with little difficulty, but continued to have trouble setting up the scripts and HomeKit integration.

So I took the plunge after reading all the reviews and switched to Home Assistant.

As I mentioned earlier, two issues are still remaining which I’m hoping you might be able to resolve.

Firstly and most importantly…Blink.

I have two Blink security cameras and I simply cannot get them to integrate into my system.

I’ve added the following code:

# Example configuration.yaml entry
blink:
  username: YOUR_USERNAME
  password: YOUR_PASSWORD

And entered my username and password as I’ve done with other integrations. I’ve checked the entries numerous times and confirmed they work on the Blink app, but I am not able to make this work.

In the logs I see the following:

Log Details (ERROR)
Logger: blinkpy.helpers.util
Source: components/blink/__init__.py:116
First occurred: May 14, 2020, 11:19:36 PM (1 occurrences)
Last logged: May 14, 2020, 11:19:36 PM

Endpoint https://rest-piri.immedia-semi.com/login failed. Possible issue with Blink servers.

Does anyone else have this issue and how can it be corrected? Have Blink blocked their API and is there even a solution?

Thanks!

Posts: 1

Participants: 1

Read full topic

@palengh wrote:

Have a look at this image:
The state is reported as home in the states view, but is localized (translated to Norwegian in the GUI, and history view.

I assume the states shown in the states view are to be used in automations and scripts. How do I check (visually read a log/states log for the correct states values for eg. a device_tracker or group throughout the day? Obviously the GUI shows different values than the states itself…

Skjermbilde 2020-05-15 kl. 10.09.141432×740 109 KB

Posts: 1

Participants: 1

Read full topic

@Antipiot wrote:

Hello everybody!

I’ve setup my home assistant installation to control my Pioneer SX-S30DAB.
Everything works fine but its really slow to apply settings (change source - volume - power on - power off ect…)

As a point of comparaison, i had it intergrated with Domoticz and it was near real time when sending command for it to be applied using onkyo-eiscp

With home assistant it may take 5-10 secs for a command to be applied.
I also have this kind of messages in logs:

image1113×481 114 KB

Is there anything i can do to improve response time? Do i have to change some settings?

Config. yaml looks like this:

media_player:
  - platform: onkyo
    host: fqdn
    name: Amp. Salon
    sources:
      bd: 'PC'
      TV: 'TV'
      bt: 'Bluetooth'
      strm-box: 'Switch'
      video2: 'Recalbox'
      cd: 'Moode-Audio'
      phono: 'Platine'

Thanks for your help
kind regards

Posts: 1

Participants: 1

Read full topic

@klib wrote:

I’m new to HA and am confused about entity naming.
I have a Hive system, and when I configure it, I get an entity (amongst others) called climate.heating. That’s fine if there is only one platform that creates a climate.heating entity, but if there are two or more, then whenever I restart the system, I get new climate.heating entities created as climate.heating_2, climate.heating_3 etc and the previous ones get orphaned and are inactive. This means I can never refer to any entity as it will be renamed come the next restart.

So what I thought was that if I named the entity in the configuration.yaml, this would solve the problem, like so:

hive:
  username: myusername
  password: mypassword

climate myzone:
  platform: hive
  name: My friendly name for my zone

But this doesn’t seem to work, I still get the entity created as climate.heating, not climate.myzone as I expected.
What am I doing wrong, and/or where is the documentation on how entity names work?

Many thanks

Posts: 1

Participants: 1

Read full topic

@zxman wrote:

Hello all
I have a server a thome that his outputting a JSON array of temperature sensors, like this:

{
  "Readings": [
    {
      "unit": "C",
      "status": "'OK'",
      "sensor_type": "Temperature",
      "temp": "27.00",
      "Type": "Temp 1",
      "ID": "14",
      "op_status": "Nominal"
    },
    {
      "unit": "C",
      "status": "'OK'",
      "sensor_type": "Temperature",
      "temp": "40.00",
      "Type": "Temp 2",
      "ID": "15",
      "op_status": "Nominal"
    }
  ]
}

(This is just an example, there are 20+ sensors).

Using the template in Developer Options I can extract a single temperature that Iw ant but I want to be able to make a group of sensors from all of the available readings.
How can I create this in my configuration file?
Soemthig like this

- group
  temp 1:
     name: '[{value_json.Readings[0].Type }]'
     value_template: '[{value_json.Readings[0].temp }]'

  temp 2:
     name: '[{value_json.Readings[1].Type }]'
     value_template: '[{value_json.Readings[1].temp }]'

Any help in getting this done would be much appreciated
Thanks

Posts: 1

Participants: 1

Read full topic

@iDontWantAUsername wrote:

Hi,

i am wondering if it is possible to show an input_select value as a name in the lovelace card for the generic thermostat.

I have an input_select called current_active_room which is the room i am current using as the target temperature and it would be good to show this as pain text in the thermostat card. i don’t want it to show as a dropdown just the text e.g. “Bedroom”, “Living Room”, etc.

  - entity: climate.heating
    type: thermostat
    name: {{ state('input_select.current_active_room') }}

Posts: 1

Participants: 1

Read full topic