November 30, 2019, 1:17 pm
@WolfsW3lp3 wrote:
Hey guys,
I have a little problem with some entity pictures:
![Screenshot_2]()
In a glance card the person has an image but when I click on it or place it as a badge in lovelace
the image is not there.
I customized the person like that in customize.yaml
person.kevin:
entity_picture: "local/Bilder/Kevin.jpg"
And here is the glance card:
- type: glance
title: Familie
entities:
- person.marco
- person.sonja
- person.kevin
And even if I click on the person there is no picture:
![Screenshot_1]()
Someone know why ?
Posts: 1
Participants: 1
Read full topic
↧
November 30, 2019, 1:43 pm
@kol wrote:
Time to time I got this error
[locationsharinglib.Service] Received response code:429
According to google it is:
Too Many Requests - Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space…
What does it mean exactly? What is the optimal scan_interval for this integration?
Posts: 1
Participants: 1
Read full topic
↧
↧
November 30, 2019, 1:49 pm
@jsnyderman wrote:
I have a RasPi3 and an Aerotec Z-Wave Plus USB stick, along with an Aerotec door sensor.
I am having a lot of trouble getting this all to work. I think it may be a permissions issue, but honestly, this is new ground for me.
The Z-Wave config page shows the stick but shows no entities. I finally for the sensor to show, but that was by pairing them while the stick was disconnected. The device seems to move between ACM0 to ACM1, but I am trying to user the serial usb ID instead. This is a printout from an SSH session…
core-ssh:~# hassio hardware info
audio:
"0":
devices:
- chan_id: "0"
chan_type: digital audio playback
- chan_id: "1"
chan_type: digital audio playback
name: bcm2835_alsa - bcm2835 ALSA
type: ALSA
disk:
- /dev/mmcblk0p1
- /dev/mmcblk0p2
- /dev/mmcblk0p4
- /dev/mmcblk0p3
- /dev/mmcblk0p8
- /dev/mmcblk0
- /dev/mmcblk0p6
- /dev/mmcblk0p7
- /dev/mmcblk0p5
gpio:
- gpiochip128
- gpiochip0
- gpiochip100
input:
- Lenovo ThinkPad Compact USB Keyboard with TrackPoint
serial:
- /dev/ttyAMA0
- /dev/serial/by-id/usb-0658_0200-if00
- /dev/ttyACM1
core-ssh:~# sudo usermod -aG dialout homeassistant
-bash: sudo: command not found
core-ssh:~# ls -l /dev/serial/by-id/usb-0658_0200-if00
crw-rw---- 1 root audio 166, 0 Nov 29 21:40 /dev/serial/by-id/usb-0658_0200-if00
core-ssh:~# ls -l /dev/ttyACM1
ls: /dev/ttyACM1: No such file or directory
core-ssh:~# ls -l /dev/ttyAMA0
crw-rw---- 1 root audio 204, 64 Nov 29 21:40 /dev/ttyAMA0
core-ssh:~# ls -l /dev/ttyACM0
crw-rw---- 1 root audio 166, 0 Nov 29 21:40 /dev/ttyACM0
core-ssh:~# sudo
-bash: sudo: command not found
core-ssh:~# chgrp dialout /dev/ttyAMC1
chgrp: /dev/ttyAMC1: No such file or directory
core-ssh:~# sudo chgrp dialout /dev/ttyAMC1
-bash: sudo: command not found
core-ssh:~# groups homeassistant
groups: unknown user homeassistant
core-ssh:~# groups root
root bin daemon sys adm disk wheel floppy dialout tape video
core-ssh:~# sudo chgrp dialout /dev/ttyAMC1
-bash: sudo: command not found
It seems that the stick can not communicate to the other device because of dialout permissions?? But I am not sure how to resolve.
Any help or guidance would be hugely appreciated. Ive been fighting with this all day and it seems like it is pretty straightforward for others.
Thanks!
~Jon
Posts: 1
Participants: 1
Read full topic
↧
November 30, 2019, 1:51 pm
@eyalco wrote:
Hi,
I have an MQTT sensor which get multiple sensors data (attributes). How do I send it to InfluxDB? Do I need to define for each attribute a sensor of its own? InfluxDB gets entity id so I am not sure is there other way beside defining sensor for each attribute.
Thx
Posts: 1
Participants: 1
Read full topic
↧
November 30, 2019, 2:33 pm
@Mariusthvdb wrote:
so wanted to revive an older HA Pi to dedicate it to a Z-wave usb stick… Older as in 100.1.
Some of the add-ons worked out, but 2 important ones, SSH and Samba error out. Just as trying to update Hassio itself:
19-11-30 22:30:35 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.102.3
19-11-30 22:30:35 INFO (SyncWorker_2) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.100.1 to homeassistant/raspberrypi3-homeassistant:0.102.3
19-11-30 22:30:35 INFO (SyncWorker_2) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.102.3.
19-11-30 22:30:37 ERROR (SyncWorker_2) [hassio.docker.interface] Can't install homeassistant/raspberrypi3-homeassistant:0.102.3 -> 500 Server Error: Internal Server Error ("readlink /mnt/data/docker/overlay2/l: invalid argument").
19-11-30 22:30:37 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
and the same error for the ssh add-on:
19-11-30 22:34:16 INFO (SyncWorker_6) [hassio.docker.interface] Update image homeassistant/armv7-addon-ssh:6.4 to homeassistant/armv7-addon-ssh:7.0
19-11-30 22:34:16 INFO (SyncWorker_6) [hassio.docker.interface] Pull image homeassistant/armv7-addon-ssh tag 7.0.
19-11-30 22:34:18 ERROR (SyncWorker_6) [hassio.docker.interface] Can't install homeassistant/armv7-addon-ssh:7.0 -> 500 Server Error: Internal Server Error ("readlink /mnt/data/docker/overlay2/l: invalid argument").
what could be the cause of this, and, more importantly, how do I solve this?
Please have a look? thanks!
Posts: 1
Participants: 1
Read full topic
↧
↧
December 1, 2019, 7:50 am
@pasoad wrote:
Hi everybody,
I have the same issue with all dark themes i tried… when I’m going to the to configuration/integrations/ and for example deCONZ, i can not read correctly the list… the most efficient one is “dark_cyan” like the screenshot below :
Can you tell me what to do to change this? I try to take care of my eyes ![:sweat_smile:]( ":sweat_smile:")
Thanks ![:slight_smile:]( ":slight_smile:")
Posts: 5
Participants: 3
Read full topic
↧
December 1, 2019, 8:06 am
@Lasse_Hedeby wrote:
Hi
In an action in my automations I am calling this service;
- service: climate.set_temperature
data:
entity_id: climate.baggang_gulvvarme
temperature: "{{ states('input_number.gulvarme_stuen') | float }}"
If I test the template {{ states(‘input_number.gulvarme_stuen’) | float }} it returns 26.0. But when I call this service with this automation I get this error;
Invalid data for call_service at pos 2: expected float for dictionary value @ data[‘temperature’]
But the template is returning a float, so I cannot see where it whent wrong.
I am running HA 0.102.3 in Docker.
Posts: 3
Participants: 3
Read full topic
↧
December 1, 2019, 8:07 am
@yakox wrote:
I have a Xiaomi robot (Gen1) with Valetudo integrated with Home Assistant (0.101.3) using MQTT discovery.
Everything is working perfectly except one thing. When the vacuum has a problem and sends an error state I do not see this reflected in any way in Home Assistant as far as I can see.
I can see the error status is reported in MQTT:
{"battery_level":82,"docked":false,"cleaning":true,"charging":false,"fan_speed":"max","error":"Clean main brush"}
but the robot status in Home Assistant remains “on” and there is no indication of an error in attributes:
status: Cleaning
battery_level: 82
battery_icon: 'mdi:battery-80'
fan_speed: max
fan_speed_list:
- min
- medium
- high
- max
cleanTime: '354.4'
cleanArea: '18773.6'
cleanCount: 660
last_run_stats:
startTime: 1575201583000
endTime: 1575203734000
duration: 61
area: '1.0'
errorCode: 0
errorDescription: No error
finishedFlag: false
mainBrush: '289.6'
sideBrush: '140.8'
filter: '131.9'
sensor: '19.6'
friendly_name: rockrobo
supported_features: 2045
Shouldn’t the error status be reflected somehow in the state of the vacuum sensor in HA or do I need to create a separate senor for that?
Posts: 1
Participants: 1
Read full topic
↧
December 1, 2019, 8:23 am
@Mariusthvdb wrote:
using a regular entities card for the climate entity has the text flow out of the card when resizing the window:
![30]()
anyone else seeing this?
Posts: 5
Participants: 2
Read full topic
↧
↧
December 1, 2019, 8:25 am
@DkAutomater wrote:
Hi guys, i have some issues with this Roth Touchline Component in the latest hassio release, i mean the latest in 1 year.
Link: https://www.home-assistant.io/integrations/touchline/
I got 7 climate thermostat out of 10 available in my setup.
I see this error in logs in my hassio:
touchline: Error on device update!
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 292, in _async_add_entity
await entity.async_device_update(warning=False)
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 450, in async_device_update
await self.hass.async_add_executor_job(self.update)
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/homeassistant/homeassistant/components/touchline/climate.py”, line 52, in update
self.unit.update()
File “/usr/local/lib/python3.7/site-packages/pytouchline/init.py”, line 60, in update
response = self._request_and_receive_xml(request)
File “/usr/local/lib/python3.7/site-packages/pytouchline/init.py”, line 128, in _request_and_receive_xml
return xml(content)
File “/usr/local/lib/python3.7/xml/etree/ElementTree.py”, line 1315, in XML
parser.feed(text)
File “”, line None
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 1, column 186
Posts: 1
Participants: 1
Read full topic
↧
December 1, 2019, 8:29 am
@joernborup wrote:
Hi Team
The question:
-using a NUC with proxmox, should I use hassio image or a ‘Ubuntu image with docker with Hassio ?
Just got hold of a NUC and would like to install proxmox and then an image with HA.
This image, should that be a HASSIO image directly ? or should I install Ubuntu, with docker, and then add Hassio ? Guess the end result would be the same (one just ubuntu based, and the other …. What ever HASSIO is build on).
But somehow I feel with the ubuntu setup, I can use the Docker setup for other stuff. But could I do the same with the HASSIO image ?
Option is also, that since I will be using proxmox, just to add another image, with docker for the rest of the container…
What do you recommend ?
Regards Jørn
Posts: 1
Participants: 1
Read full topic
↧
December 1, 2019, 8:49 am
@weswitt wrote:
I’m running HomeAssistant 3.5 on a Raspberry Pi 3B+.
I’m having problems getting a simple template sensor to work. I’ve read the docs but cannot seem to make this work.
I have a sensor that is a discovered MQTT sensor. It has a JSON payload as the state value. In my tests the JSON state value is: { “temp”: “78.494003”, “humidity”: “24.537109”, “pressure”: “100561.515625”, “timestamp”: “2019-12-01T00:26:49Z” }.
I’m then trying to create a template sensor to extract the temperature value.
Using this properly yields the JSON string, which tells me that the template can access the value.
sensor:
- platform: template
sensors:
upstairs_temp:
friendly_name: "Upstairs Temperature"
value_template: "{{ states('sensor.upstairs') }}"
Now if I do the following I get the “unknown” value.
sensor:
- platform: template
sensors:
upstairs_temp:
friendly_name: "Upstairs Temperature"
value_template: "{{ state_attr('sensor.upstairs', 'temp') }}"
This also yields “unknown”:
sensor:
- platform: template
sensors:
upstairs_temp:
friendly_name: "Upstairs Temperature"
value_template: "{{ sensor.upstairs.temp }}"
How do I make this work?
Posts: 3
Participants: 2
Read full topic
↧
December 1, 2019, 8:51 am
@cameron wrote:
This happens on all my devices.
The font colour is black when I go to any Config page then goes white.
Posts: 1
Participants: 1
Read full topic
↧
↧
December 1, 2019, 8:52 am
@getut wrote:
I’m having trouble getting my home assistant accessible from the outside, but I’m trying to do it in what I though was a much easier route than that what the official documentation instructs to do. But I can’t figure out why it isn’t working.
I have a Nethserver (all in one email, fileserver, nextcloud, webserver, etc) that is already set up with letsencrypt and working with my domain and it is already listening on ports 80 and 443. It supports reverse proxy to other hosts in my network and I set up a reverse proxy to http://:8123 from my Nethserver at https://my.registereddomain.com/ha.
It’s not working but the forwarding to my ha instance seems to be working. Does anyone know what I can do to get this going?
Posts: 1
Participants: 1
Read full topic
↧
December 1, 2019, 9:14 am
@smith.james0 wrote:
Hi,
Please go easy I am new to HA (less than a month) and new to WLED (about 2 days!) and I am struggling with an automation.
I am trying to configure that when triggered if my LED’s are on (I have an automation to turn them on at sunset) LED’s will do the Random pattern in WLED for 5 min.
So far I can do the trigger and the condition but I have no idea how to do the ‘do random’ for 5 min.
Can anyone help / point me in the right direction.
Regards
James
Posts: 2
Participants: 2
Read full topic
↧
December 1, 2019, 9:18 am
@mudit182 wrote:
I wanted to inquire about the rgb_color attribute available in the light component. In the docs it says
A list containing three integers between 0 and 255 representing the RGB color you want the light to be. ..."
However, in reality the numbers need to be between 0 and 100. This seems to be a recent modification as previously 0 - 255 worked perfectly.
The biggest problem, as far as I see, is that internally HA still stores rgb values between 0-255. So for instance when I get the current state using “state_attr(‘light.my_light’, ‘rgb_color’)” I get a list of values between 0-255, but when I need to set the same state, I need to convert it to 0-100.
So does anyone have any idea as to which is/will be the standard? Is it a bug and rgb_color will be reverted to the range of 0-255 or do the docs need to be updated and 0-100 is the new standard?
Ps. I have a script that randomly generates rgb values for my light. It’s more like a random walk around the color wheel, so the color change is not too jarring. Anyway in case anyone wishes to know how I did it, I’d be happy to share that later in this post.
Posts: 1
Participants: 1
Read full topic
↧
December 1, 2019, 9:23 am
@jjross wrote:
I’m using some Wemo switches and they are working great. They are automatically discovered and automatically added to my lovelace home page (I’m still playing with things and have left lovelace to manage itself) which is amazing.
The issue is that when I go to the “Integrations” panel under configuration there are no devices listed under the Wemo integration which means that I can’t add the switches to an area (adding to an areas causes automatic lovelace to place the device into a panel with other devices in that area).
Is this expected? Anything I can do to force the devices to an area or is that support just not built into the wemo integration?
Posts: 2
Participants: 1
Read full topic
↧
↧
December 1, 2019, 9:26 am
@111 wrote:
Well I recently upgraded to Home Assistant 0.102.3 and Philips Hue stopped working and since i tried to connect the bridge it give me the message that fails to connect anyone aware of that?
Posts: 1
Participants: 1
Read full topic
↧
December 1, 2019, 10:06 am
@jhart003 wrote:
I’m close but I can’t seem to figure out this automation.
I have a PLC that provides the hourly runtime of my sump pump. This value appears in HA as sensor.current_hour_runtime. It resets to zero at the start of each hour.
I have an input number that I want to use to track how long my sump pump has run each day (input_number.cumulative_sump_pump_runtime).
I wrote a small automation that adds the current hour runtime to the cumulative runtime at 59 minutes and 30 seconds past the hour. This seems to be working well.
I want to reset the daily runtime value at 11:59:30 each day. I can’t seem to master how the reset value should be configured in the automation. I get these errors in my log:
Error while executing automation automation.update_sump_pump_daily_runtime. Invalid data for call_service at pos 2: extra keys not allowed @ data[‘value_template’]
Here is the automation as I currently have it:
- alias: update sump pump daily runtime
initial_state: True
trigger:
platform: time_pattern
minutes: 59
seconds: 30
action:
- service: input_number.set_value
data_template:
entity_id: input_number.cumulative_sump_pump_runtime
value: "{{ states('sensor.current_hour_runtime')|int + states('input_number.cumulative_sump_pump_runtime')|int }}"
- service: input_number.set_value
data_template:
entity_id: input_number.cumulative_sump_pump_runtime
value_template: >
{% if (now().hour == 23 ) %}
0
{% endif %}
I’ve tried Value: 0 and {{ states(‘input_number.cumulative_sump_pump_runtime’) = 0 }} but neither seem to work even though they pass the built in configuration validation.
Thank you in advance for your help formatting that if/then in the Value_template section.
Posts: 9
Participants: 3
Read full topic
↧
December 1, 2019, 10:19 am
@kayser21 wrote:
Is it possible to set start value of utility meter? I want to have some value at the beginning instead of “0”.
Posts: 1
Participants: 1
Read full topic
↧
