Thanks for all that youāve shared already! Your examples have given me and Iām sure others a nice base and some cool things to chase after. I can say that Iām guilty of peeking back from time to time to see whether youāre at a place where youāve shared your code as there are plenty of sticking points, but thanks for considering it anyway and sharing your progress.
As a specific example, do you mind to share a snippet or two as to your implementation of the sidebar card for your tablet/expanded view?
Replaced the Ultrasonic for another and working now, Can you share your calls with me? my salt bin max is actually around 37cm but the sensor is 43cm from the bottom.
What is everyone doing for their door locks and door sensors? I canāt come up with a good way to combine the lock card and door open/closed sensor card together for a cleaner look. I canāt stand how this currently looks.
esphome:
name: salt_level_sensor
platform: ESP8266
board: d1_mini
# WiFi connection, replace these with values for your WiFi.
wifi:
ssid: xxxxx
password: xxxxx
# Enable logging
logger:
# Enable Home Assistant API
api:
# Enable over-the-air updates.
ota:
# Enable Web server.
web_server:
port: 80
# Sync time with Home Assistant.
time:
- platform: homeassistant
id: homeassistant_time
# Text sensors with general information.
text_sensor:
# Expose ESPHome version as sensor.
- platform: version
name: salt_level_sensor ESPHome Version
# Expose WiFi information as sensors.
- platform: wifi_info
ip_address:
name: salt_level_sensor IP
ssid:
name: salt_level_sensor SSID
bssid:
name: salt_level_sensor BSSID
# Exposed switches.
# Switch to restart the salt_level_sensor.
switch:
- platform: restart
name: "salt_level_sensor Restart"
sensor:
# Uptime sensor.
- platform: uptime
name: salt_level_sensor Uptime
# WiFi Signal sensor.
- platform: wifi_signal
name: salt_level_sensor WiFi Signal
update_interval: 60s
- platform: ultrasonic
trigger_pin: D1
echo_pin: D2
name: "saltlevel_in_percent"
update_interval: 12h
filters:
# Calculates in %
# MARK: Subtract depth reading from total height of hopper and divide that by max usable height of hopper to give total capacity percentage. Multiply by 100 to give %
- lambda: return ((0.46-x)/0.35)*100;
unit_of_measurement: "%"
- platform: ultrasonic
trigger_pin: D1
echo_pin: D2
name: "saltlevel_in_cm"
update_interval: 12h
filters:
# MARK: Exact distance of sensor to bottom of hopper, with x output * 100 to change m to cm
- lambda: return 46-(x*100);
unit_of_measurement: "cm"
- platform: ultrasonic
trigger_pin: D1
echo_pin: D2
name: "raw_sensor_in_cm"
update_interval: 12h
filters:
# MARK: Raw distance output * 100 to get m to cm - only used for validation.
- lambda: return x*100;
unit_of_measurement: "cm"
I combined the two cards using a template card and the lock card so that it only takes one card, I have indicators on my home page to show if the doors are open and unlocked as well so this is more than enough for my needs
Mine isnāt quite the same as the poster to whom you replied, but similar concept I think. Hereās my code if youāre interested and if it helps at all. Clicking will trigger the lock since itās the controlling entity.
I looking for while but canāt find the answer. I tried to set the hide_state and more but none of them works. Or is there a way to use the type: template to show only the icon.
Could you use the template card and have the icon show the status of the lock then use badges to show the status of the sensors? Then have the card toggle the lock status.
Anyone knows how to make a Mushroom Template Card āreactiveā (change color or icon), same as the HA Button card that change color when pressed.
I am trying to use a Template Card as a ābuttonā for a script or shell command, but I have not find a way of visually knowing the template card was indeed being pushed. (tap_action:)
I know I can use the date stamp for when the script was executed and have that change the color/icon of the template card, but I was hoping it was a more straight forward approach? Appreciate anyoneās suggestions or ideas. Thanks
These are very beautiful words. Really. Thank you very much.
Lately I have decided to get rid of some third party add-ons because of the dependincies to them may cause problems in future updates. As for sidebar it has some bugs at the moment especially with the the bottom bar not displaying things properly. So I decided to delete that as well.
Currently I am still working on my mobile view. I will share the code if I can manage to complete sooner. And after that I am also planing to do something for the tablet view.
This is what Iām trying to learn hereā¦ the concept of using variables such as ā[[entity]]ā
Not sure how thatās done.
Care to perhaps share a little insight on that if you would.