search

twrecked / lovelace-hass-aarlo

Lovelace card for hass-aarlo integration.
75 stars 23 forks source link

The device options: bell , bell2 get mixed up and don't display correctly #104

Open sdrapha opened 3 years ago

sdrapha commented 3 years ago

When using more then one doorbell entity/icon, they get mixed up and just one of them shows.

example card:

type: custom:aarlo-glance
entity: camera.aarlo_front_door
name: Front Door
image_click: recording
image_view: smart,direct
library_view: smart,download,duration
library_sizes: 3,4,2
image_top: name|status,onoff
image_bottom: motion,library,stream,snapshot,battery,door,bell,bell2|date
door: binary_sensor.front_door_wyze_sensor_2
door_bell: sensor.aarlo_motion_my_doorbell
door2_bell: binary_sensor.aarlo_ding_my_doorbell

image

Obs: What I really wanted to achieve, is an icon for the doorbell motion, and another for the doorbell pressed. An option to represent this better ( different icon?) would be awesome. Thank you for the awesome aarlo component!

twrecked commented 3 years ago

There is a bug stopping the bell2 icon from appearing. I'll fix that.

But would a bell_motion and bell2_motion option help? That way we'd get the correct icons.

sdrapha commented 3 years ago

Thanks for having a look at it. Honestly I'm not sure what could be the best way of representing it,.. Just thinking about it now... I'm coming up with this logic.. What if: the bell and bell2 could be left alone as is. ( I will use that for my "ding/press the button sensor") and them for the bell motion sensor, there could be a motion2 icon, a generic one not tied to the doorbell. I say that because I can use it anyways for my scenario, but also I can envision people using the 2nd motion icon with a generic pyr sensor. So in the end we will have a motion sensor coming from the arlo camera ( which is not much reliable, arlo to blame ) and then a second motion icon for anything you could use extra, like a zigbee pyr sensor (or the doorbell motion sensor in my case).