@jwelvaert wrote:

When trying to make the zha-network-visualization-card I get this:

Custom element doesn’t exist: zha-network-visualization-card.

I installed this through HACS

Added zha_map: to my configuration.yaml file.

Verified that the zha_map is in my custom_components folder

Added
type: module
url: /hacsfiles/zha-network-card/zha-network-card.js to my resources in the Raw Configuration Editor
Thought that url looked odd so tried url: /community_plugin/zha-network-card/zha-network-card.js

Using Panel Mode

When I try to scan through Developer/Services/zha_map.scan_now I get nothing

What am I missing here?

Posts: 1

Participants: 1

Read full topic

@sender wrote:

All topics I search on I find the othr way around, how to update your ubuntu server with HA on it.

What I want is to have an option to kick a remote ubuntu server to start sudo apt-get update and upgrade etc. to be able to simply “manage” remote ubuntu servers to install their latest patches.

Any direction?

Posts: 7

Participants: 3

Read full topic

@brian1917 wrote:

How come scene editor in the GUI only allows device selection and not all relevant entities? For example, I can add Hue bulbs and Zwave switches to a scene but not Lurton Caseta switches. I can do it from the YAML, but don’t know why it wouldn’t be in the GUI editor.

Related - why aren’t Lurton Caseta switches identified as devices?

Posts: 1

Participants: 1

Read full topic

@Jeroen_Vermeulen wrote:

Hello,

i have a question about my mqtt automation.

when i leave out the payload in the automater the automation works
but if i put in the payload (and i really need to do this because i work with the sonoff/tasmoto wifi hub) then the action doesnt work

like you can see below hassio is recieving the messages when i go to developer tools - mqtt- listen to a topic

Message 0 received on tele/hub/RESULT at 2:14 PM:
{
“Time”: “2020-03-06T14:14:05”,
“RfReceived”: {
“Sync”: 7560,
“Low”: 270,
“High”: 730,
“Data”: “92D3B8”,
“RfKey”: “None”
}
}

below is my automation.yaml :

id: ‘1583497473605’
alias: motion gang voor
description: ‘’
trigger:

• payload: “92D3B8”
  platform: mqtt
  topic: tele/hub/RESULT
  condition: []
  action:
• device_id: 929eecf9a0df45f991bb3bd57bda9362
  domain: light
  entity_id: light.gang_voor
  type: turn_on

so without the payload filled in it works but thats no option.
if i fill in the payload with or without the “” it doesnt work.

Any one know an eassy way to fix this… ?

Posts: 8

Participants: 4

Read full topic

@nasgul wrote:

Using HA 0.106.1
How can this happen… or removed

image855×716 31.4 KB

Posts: 4

Participants: 4

Read full topic

@devilkin wrote:

I’ve got a reflective sensor on an arduino nano (with serial-usb) that gives me a pulse (basically an X) over serial input every time it’s triggered.

This is linked to a sensor as

sensor:
  - platform: serial
    serial_port: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
    baud_rate: 115200

Now, I get the things into HA … but how do i properly count this stuff?

Posts: 3

Participants: 2

Read full topic

@ResinChem wrote:

I’m trying to determine the best way to handle changing my WiFi password. I currently have 60+ devices from a variety of flavors (ESP8266, Lutron, Wink, Hues, Shelly, Sonoff (Tasmotized and not) ESPHome, RaspPis, etc. etc. etc… Some have fallback APs, some don’t. If I change my home WiFi and these devices drop off the WiFi due to the password change, how can I access them to update to the new password? The last thing I want to do is have to perform factory resets or delete and re-add the devices, as some like the Shellys are not readily accessible. In addition, if the device is reset/recreated, there is a strong possibility that the entity or device name will change/be rediscovered in HA, leading to a plethora of broken scripts, automations, etc. Obviously, devices like smart TVs, game consoles, etc. are not a problem because they have a local display interface to update the password. But for devices that are only accessible via WiFi, what is the best way to handle changing the WiFi password (and/or the SSID)? The semi-good news is that nearly all my devices are assigned static IP addresses and I have also recorded all MAC addresses… if that’s helpful. And my HA server is on a wired connection, so no changes have to be made for the HA or MQTT server connections.

I’ve come up with two possible routes…

1. First move all the devices, one by one, to a secondary guest network (different SSID). This will require all sorts of script updates and reflashing (but hopefully OTA in most cases like Tasmota, WLED and ESPHome). Each device will temporary drop off the current Wifi upon reboot, but should (hopefully) still be accessible via the guest WiFi. Once all devices are moved to the guest wifi then change the original SSID password and move each device back again (once again reflashing/rebooting).

2. On the current WiFi (still old password), access each device and change the password to a new password (again, reflashing where needed). Each will drop off the Wifi and will temporarily be unreachable via normal WiFi. Once that is done, the WiFi password can be changed, each device rebooted and “hope” that everything comes back online. This has the advantage of only updating/reflashing devices once, but runs the risk of leaving a device inaccessible if it doesn’t come back online, requiring a potential factory reset, reflash, changing entity name in HA, etc.

So, are there other options here? Again, I don’t need to worry about HA itself since it is on a wire connection. It is just the best way to approach a WiFi password/SSID change with a large number of various edge devices without a method of accessing other than WiFi and without breaking all the scripts, automations, etc. in HA.

Any advice greatly appreciated!

Posts: 3

Participants: 3

Read full topic

@amaximus wrote:

Is there a way to define yaml variables (even with yaml anchoring) that become available across the whole HA env? Something similar how secret file works.
How do you store your alert limits, payloads, etc.? Are they hardcoded in the automations or sensor files? I’d group all such values in one file and make them available across HA.

I know there are custom components like [1], but a set of simple key:value definitions would be enough.

[1] https://github.com/rogro82/hass-variables

Posts: 2

Participants: 2

Read full topic

@doubleUS wrote:

Since of today the coinmarketcap sensor platform isn’t working anymore. Anybody any idea what could be the problem?

I’m using HassOS on Proxmox:

arch	x86_64
dev	false
docker	true
hassio	true
os_name	Linux
python_version	3.7.6
timezone	Europe/Amsterdam
version	0.106.5
virtualenv	false

Lovelace

mode	storage
resources	11
views	10

The logfile contains this error.

2020-03-06 15:50:10 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 400, in _async_add_entity
    suggested_object_id or entity.name or DEVICE_DEFAULT_NAME
  File "/usr/src/homeassistant/homeassistant/components/coinmarketcap/sensor.py", line 98, in name
    return self._ticker.get("name")
AttributeError: 'NoneType' object has no attribute 'get'

Posts: 1

Participants: 1

Read full topic

@VMCosco wrote:

As I am sure many other are, I am running multiple services on my LAN. Many of them juts run on a local IP at a specific port (i.e. Sonarr, Radarr, etc). I would love to be able to add the online status for each of these to HA somehow. I know that ping does not with on specific ports. Is anyone doing something like this?

Posts: 1

Participants: 1

Read full topic

@Skye wrote:

I used the hub for burglar alarm, though now it does not play any ringtone anymore (since 0.106 I guess?)

I see in the services tab:

Play a specific ringtone. The version of the gateway firmware must be 1.4.1_145 at least.

Not sure what fw I am on, why has this changed? Can I safely update the device without losing the debug connection?

To test I’m doing:

xiaomi_aqara.play_ringtone

gw_mac: 'GW_MAC_HERE'
ringtone_id: '3'
ringtone_vol: '5'

It used to work fine for months, the LED ring still works OK.

I don’t see anything of errors or such in the log

Posts: 1

Participants: 1

Read full topic

@leonardpitzu wrote:

i have a PTZ foscam which is exposed in a picture-elements card (similar to what the documentation also offers). It works as expected - the lovelace card shows a live stream from the camera and the buttons move it around. I just can’t figure out how to make a bigger pop-up of the camera stream when i click the image in the card (i want basically the same behaviour as when clicking the picture-entity).
does anybody have a clue how to achieve this?

Posts: 1

Participants: 1

Read full topic

@giygas wrote:

Specifically, i’d like a card that would show the last 24 hours, with markers for every time a certain thing happened (eg an automation was triggered)

bonus if this could simultaneously show the state of a certain switch/sensor/etc, along the same timeline

Posts: 4

Participants: 2

Read full topic

@RichardU wrote:

I’m using this in a picture-element to highlight when a PIR is violated

              - type: image
                entity: sensor.0_office_pir
                image: /local/PIR01.png
                state_image:
                  'Violated': /local/PIR10.png

What I’d really like is make this a “heat map” so a violated PIR would switch to a bright image for 1 minute, then a medium image for 1 minute, then back to a dim image.

Any ideas on how to do that?

Thanks, Richard

Posts: 1

Participants: 1

Read full topic

@Jaques-Ludwig wrote:

Hi,

I have configured my HmIP-BSM in Home Assistant and power on / off works great. Now I wonder if it’s possible to react on long press up and long press down? I want to use it to dim my Osram lightify lamps.
Does someone know if it’s possible and how?

Thanks,

Jaques-Ludwig

Posts: 2

Participants: 2

Read full topic

@maurizio53 wrote:

Since the update to 0.106.5 i get these errors about the alexa media integration:

2020-03-06 19:58:33 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 46, in async_entity_state_listener
    hass, smart_home_config, alexa_changed_entity
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 79, in async_send_changereport_message
    properties = list(alexa_entity.serialize_properties())
  File "/usr/src/homeassistant/homeassistant/components/alexa/entities.py", line 264, in serialize_properties
    for prop in interface.serialize_properties():
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 231, in serialize_properties
    prop_value = self.get_property(prop_name)
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 674, in get_property
    current = math.floor(int(current_level * 100))
TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'
2020-03-06 20:02:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 46, in async_entity_state_listener
    hass, smart_home_config, alexa_changed_entity
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 79, in async_send_changereport_message
    properties = list(alexa_entity.serialize_properties())
  File "/usr/src/homeassistant/homeassistant/components/alexa/entities.py", line 264, in serialize_properties
    for prop in interface.serialize_properties():
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 231, in serialize_properties
    prop_value = self.get_property(prop_name)
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 674, in get_property
    current = math.floor(int(current_level * 100))
TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'
2020-03-06 20:02:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 46, in async_entity_state_listener
    hass, smart_home_config, alexa_changed_entity
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 79, in async_send_changereport_message
    properties = list(alexa_entity.serialize_properties())
  File "/usr/src/homeassistant/homeassistant/components/alexa/entities.py", line 264, in serialize_properties
    for prop in interface.serialize_properties():
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 231, in serialize_properties
    prop_value = self.get_property(prop_name)
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 674, in get_property
    current = math.floor(int(current_level * 100))
TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'
2020-03-06 20:02:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 46, in async_entity_state_listener
    hass, smart_home_config, alexa_changed_entity
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 79, in async_send_changereport_message
    properties = list(alexa_entity.serialize_properties())
  File "/usr/src/homeassistant/homeassistant/components/alexa/entities.py", line 264, in serialize_properties
    for prop in interface.serialize_properties():
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 231, in serialize_properties
    prop_value = self.get_property(prop_name)
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 674, in get_property
    current = math.floor(int(current_level * 100))
TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'
2020-03-06 20:07:37 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 46, in async_entity_state_listener
    hass, smart_home_config, alexa_changed_entity
  File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 79, in async_send_changereport_message
    properties = list(alexa_entity.serialize_properties())
  File "/usr/src/homeassistant/homeassistant/components/alexa/entities.py", line 264, in serialize_properties
    for prop in interface.serialize_properties():
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 231, in serialize_properties
    prop_value = self.get_property(prop_name)
  File "/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py", line 674, in get_property
    current = math.floor(int(current_level * 100))
TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'

Anyone else has this and how to fix?

Posts: 1

Participants: 1

Read full topic

@Ben_Barker wrote:

Hi,
I have soldered up an rfLink gateway, which seems to be seeing my devices OK. However, I am running into trouble adding them to home assistant:

configuration.yaml:

rflink:
  port: /dev/serial/by-id/usb-Arduino__www.arduino.cc__0042_55736323239351311150-if00

light:
  - platform: rflink
    automatic_add: true
sensor:
  - platform: rflink
    automatic_add: true
type or paste code here

logs

2020-03-06 19:40:26 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'acuritev3_0097_hum', 'sensor': 'humidity', 'value': 65, 'unit': '%'}
2020-03-06 19:40:26 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: []
2020-03-06 19:40:26 DEBUG (MainThread) [homeassistant.components.rflink] device_id not known and automatic add disabled

The last line seems to be why I can’t see any devices…but I am unclear at the moment as to why discovery is disabled…

Posts: 1

Participants: 1

Read full topic

@needhelpbad wrote:

Hi guys!
So i have a couple of sonoff plugs and Philips Hue lights. My intention is to get a Sonoff RF Bridge and sensors that i can use with both the Hue lights and the Sonoff plugs, but i don’t want to pay for the HA cloud. So is there a way that i can still use the plugs with Amazon Alexa (i thought of wemo simulation, but haven’t flashed any sonoff yet) and integrate them into Home Assistant? Philips Hue still works with Alexa without HA being connected to Alexa.

Posts: 1

Participants: 1

Read full topic

@Hs82H wrote:

I try to pass a variable to a script. I want my Google Home lower it’s volume when my son is sleeping, based on a input_select. Unfortunately I get an error and I am not that experienced with variables. I think I messed up some examples I found on the forum.

I got this automation and script:

alias: change volume when son is sleeping
trigger:
  platform: state
  entity_id: 
    - input_select.niek_status
action:
  service_template: >-
    {%
      if (
        is_state('input_select.niek_status', 'sleeping')
      )
    %}
      service: script.set_volume_googlehome
      data_template:
        variables:
          volume: '{{ 30 }}'
    {%
      elif (
        is_state('input_select.niek_status', 'awake')
      )
    %}
      service: script.set_volume_googlehome
      data_template:
        variables:
          volume: '{{ 70 }}'
    {%- endif %}

set_volume_googlehome:
  alias: 'Set volume Google Home'
  sequence:
    - service: media_player.volume_set
      data_template:
        entity_id: media_player.home
        volume_level: '{{ volume }}'

The error I get:

2020-03-06 15:32:44 ERROR (MainThread) [homeassistant.components.automation] Error while executing automation automation.change_volume_when_son_is_sleeping. Invalid data for call_service at pos 1: Service service: script.set_volume_googlehome
  data_template:
    variables:
      volume: 70 does not match format <domain>.<name>

Posts: 3

Participants: 2

Read full topic

@chezpaul2 wrote:

So my HA won’t boot up anymore. the log shows 0 errors and I already took out the only change I did from my config file. I still have samba access to it of course.
I did a snapshot 2 days ago. So I see them but how do I activate it so that it reboots to the last snapshot?

Thanks

Posts: 2

Participants: 1

Read full topic