Hey everyone,
so HydroQuebec has 2 different rates that apply to a house: The first 40 kwh are billed at one rate, and the subsequent kwh are billed at another. I figured I would create a template sensor to define the rate… but then I realized to this to properly, i would need to be able to get the value of the “grid” value on the energy dashboard, but it doesnt seem to be a normal entity.
Anyone know how to get this data?
1 post - 1 participant
Hi guys
i want to setup a sensor or something that shows the peak (highest) watts used for the day.
regards
Jeremy
1 post - 1 participant
Attempting to use the History_Stats sensor to derive daily rainfall measurements. Currently, the rain guage just keeps incrementing any time rainfall occurs. As the measurement is in mm, it is a floating point value with one decimal place. My current sensor definition always returns “Unknown value” and I suspect it has to do with the state: definition. I verified this definition returns that float value, using Developer Tools / Template. I’ve also tried both type:time and type:count but neither succeeds.
I would appreciate any suggestions from you great and infinitely more experienced HA wizards. Thank you! 
sensor:
- platform: history_stats
name: 'rain_mm_today'
entity_id: 'sensor.cotech_367959_121_rain_mm_today'
state: '{{ states("sensor.Cotech-367959-121-rain_mm") | float(1) }}'
type: time
start: "{{ now().replace(hour=0, minute=0, second=0) }}"
end: "{{ now() }}"
1 post - 1 participant
hi im trying to create a person group in yaml. so i can create some automations for myself and my wife. below is my code in my Config file. I get this error which is saying platform is an invalid option fo person
Invalid config for [person]: [platform] is an invalid option for [person]. Check: person->person->0->platform. (See /config/configuration.yaml, line 270).
person:
- platform: group
name: Brad & Lauren
icon: mdi-account-group
entities:
- person.lauren
- person.brad
4 posts - 2 participants
I am not sure if this is frontend or zigbee/zha related.
I have some zigbee blinds, the card for the blinds is always backwards (says open when it’s closed and vice versa).
In the attached screenshot, the blinds are up/open. The card says they are down/closed. So, it only allows me to click the up button; but since the blinds are already up, it doesn’t do anything. I can’t click the down button because it’s grayed out since the system thinks it’s already down/closed. Further, if I move the blue dot for the blinds location 1/4 inch from the left, the blinds start moving but the blue dot moves 1/4 inch from the right (the opposite side that I moved the indicator, and the blinds do move to the opposite state). If I put the blinds half way open and half way closed, I can then click either the up or down button, but the blinds do opposite of what the button indicates.
Is there anyway to reverse the blinds status in HA so it matches the actual status of the blinds?
2 posts - 2 participants
Please help my erudite friends!
A year ago approximately i set up many generic RGB bulbs and flashed them with Tasmota.
They were all working well, but were then removed and not used for well over 6 months.
Recently when i have tried to power them up they are all completely lifeless.
I am hoping someone here can help me to resurrect them.
i have tried the multiple powering on/off combinations, all to no avail.
Can they be re-flashed, have they lost their identities?
Thanks.
2 posts - 2 participants
Hi,
I would like to create a condition in an automation that compares energy usage before and after an action.
My scenario is that I’ve 433mhz plugs outside that I use to control the car heating in the winter times. It works 95% of the times, but sometimes the plugs just haven’t received the signal. It is extremely frustrating when you realize that the car didn’t get preheated when you plan to drive.
So to validate if the signal has gone through, I would like to create below logic by comparing my houses real-time energy usage. One aspect of the challenge is that I’m not recording the energy usage, as it would create a lot of entries. MQTT publishes energy usage every second.
The issue is which I don’t know how to solve or even if it is possible, is to store a value in a variable inside a flow and use it later in the flow to compare.
Thanks for the ideas for helping me to solve this.
2 posts - 2 participants
Hi,
So I installed HAOS, then the Let’s Encrypt addon, obtained my cert and private key from my DNS registrar, all is well.
Then installed NGINX Home Assistant SSL proxy, aaaand all it gives me in a browser is:
400: Bad Request
Then if I check the Home Assistant logs, it’s full of:
A request from a reverse proxy was received from 172.30.33.0, but your HTTP integration is not set-up for reverse proxies
Yes, I added these lines to my config:
http:
use_x_forwarded_for: true
trusted_proxies:
- 172.30.33.0/24
But it does not solve anything. Tried adding the various “magic” random IP addresses others suggested on these forums, even 0.0.0.0/0, but I still receive the same error every time.
Any ideas?
1 post - 1 participant
Hi folks,
I want to trigger an automation when the difference between two temeratures is above a specivic value.
How can I do this?
Thanks a lot
2 posts - 2 participants
Hello.
I’ve tried to find the reason why some of my bulbs and the oudoort Ledvantage light-poles are switched on over night while HA reported them as switched off.
Trying to play with the setup a bit, I’ve changed the transmit power value on the configuration page inside zigbee2mqtt. After a reboot the zigbee2mqtt did not start anymore…
That’s what happen in the log:
[06:44:15] INFO: Handing over control to Zigbee2mqtt Core ...
> zigbee2mqtt@1.24.0-dev start
> node index.js
Zigbee2MQTT:info 2022-03-21 06:44:17: Logging to console and directory: '/share/zigbee2mqtt/log/2022-03-21.06-44-16' filename: log.txt
Zigbee2MQTT:info 2022-03-21 06:44:17: Starting Zigbee2MQTT version 1.24.0-dev (commit #efe768d)
Zigbee2MQTT:info 2022-03-21 06:44:17: Starting zigbee-herdsman (0.14.20)
CREATED DECONZ ADAPTER
Zigbee2MQTT:info 2022-03-21 06:44:17: zigbee-herdsman started (resumed)
Zigbee2MQTT:info 2022-03-21 06:44:17: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":112,"product":0,"revision":"0x26700700","transportrev":0},"type":"ConBee2/RaspBee2"}'
Zigbee2MQTT:error 2022-03-21 06:44:17: Failed to start zigbee
Zigbee2MQTT:error 2022-03-21 06:44:17: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-03-21 06:44:17: Exiting...
Zigbee2MQTT:error 2022-03-21 06:44:17: Error: not supported
at DeconzAdapter.setTransmitPower (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:1025:15)
at Controller.setTransmitPower (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:380:29)
at Zigbee.start (/app/lib/zigbee.ts:138:33)
at Controller.start (/app/lib/controller.ts:100:27)
at start (/app/index.js:101:5)
There is NO value in /config/configuration.yaml or in the config with zigbee2mqtt add-on page. Therefore this transmit power value must be saved somewhere else… I simply want to remove this setting so that z2m can start again, but I can’t find the place where this value is stored and how to remove it.
Can anyone help me please?
Thanks,
Oliver
2 posts - 1 participant
Hi
Im new to home assistant, and I was wondering if someone could explain what integrations are and how I use them? A detailed explanation for a complete noobie would help alot 
Thanks !
Birk
3 posts - 3 participants
Hello, I am planning to migrate my MariaDB database running on the HA node to a Synology NAS (DS920+) to have the benefits of the NAS for data protection…
Anyone was succesful doing a similar migration ?
What were the steps to make sure the database was transferred keeping data integrity… (Stopping the recorder before executing a backup ? or redirect to the new database/restart HA/backup the old database (without having updates on it)/stop HA/restore the database on the new instance and restart HA)
Sofar I have MariaDB installed on the Synology NAS and remote access enabled… Quite simple… but for the rest…
Thanks !
2 posts - 2 participants
Hi, after my old HA crashed, i restore it from a backup.
Then i got a lot of lags, i try to reinstall Deconz. But the problem is the same. My Hue Dimmer maybe dont work some times, some times it works, some times it lags, so make the lights on 5-10 sek later, sometimes does nothing…
Can someone help me?
I have the Deconz on my Pi
here the logs from today:
08:37:51:442 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
08:37:52:385 Skip idle timer callback, too early: elapsed 944 msec
08:38:09:836 Bind response success for 0x001788010212cad8 ep: 0x02 cluster: 0x0406
08:38:09:838 skip configure report for cluster: 0x0406 attr: 0x0000 of node 0x001788010212CAD8 (seems to be active)
08:38:10:376 ZCL configure reporting rsp seq: 52 0x001788010212CAD8 for ep: 0x02 cluster: 0x0406 attr: 0x0030 status: 0x00
08:38:16:079 ZCL attribute report 0xF0D1B800001A1F18 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
08:38:18:813 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0006, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:38:18:941 ZCL attribute report 0xF0D1B800001A1F18 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
08:38:20:827 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0008, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:38:32:451 Device TTL 2921 s flags: 0x7
08:38:52:386 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
08:39:03:390 ZCL attribute report 0x0017880103289A06 for cluster: 0x0406, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:39:16:458 ZCL attribute report 0x0017880104F6CABD for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:39:26:221 ZCL attribute report 0x001788010212CAD8 for cluster: 0x0400, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:39:27:559 ZCL attribute report 0x0017880103CAB325 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:39:32:438 Device TTL 2861 s flags: 0x7
08:39:37:146 ZCL attribute report 0x0017880103289A06 for cluster: 0x0402, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:39:41:400 ZCL attribute report 0x001788010212CAD8 for cluster: 0x0406, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:39:41:459 Bind response success for 0x001788010212cad8 ep: 0x02 cluster: 0x0406
08:39:41:460 skip configure report for cluster: 0x0406 attr: 0x0000 of node 0x001788010212CAD8 (seems to be active)
08:39:42:000 ZCL configure reporting rsp seq: 128 0x001788010212CAD8 for ep: 0x02 cluster: 0x0406 attr: 0x0030 status: 0x00
08:39:52:386 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
08:39:54:386 Skip idle timer callback, too early: elapsed 941 msec
08:40:23:386 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
08:40:26:728 ZCL attribute report 0xF0D1B800001A1F18 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
08:40:31:003 ZCL attribute report 0x00178801021B226A for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:40:32:444 Device TTL 2801 s flags: 0x7
08:40:35:840 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:40:35:875 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:41:18:387 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
08:41:19:860 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:41:19:934 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:41:19:954 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:41:32:437 Device TTL 2741 s flags: 0x7
08:41:52:022 ZCL attribute report 0x001788010212CAD8 for cluster: 0x0402, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:41:58:386 Skip idle timer callback, too early: elapsed 817 msec
08:42:26:173 ZCL attribute report 0x0017880103289A06 for cluster: 0x0400, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:42:32:436 Device TTL 2681 s flags: 0x7
08:42:36:070 ZCL attribute report 0x0017880104AF1828 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:42:39:160 ZCL attribute report 0x0017880104F6B4F3 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:42:59:385 Skip idle timer callback, too early: elapsed 926 msec
08:43:14:182 ZCL attribute report 0xF0D1B800001A1F18 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
08:43:17:730 ZCL attribute report 0xF0D1B800001A1F18 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
08:43:17:875 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0006, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:43:19:889 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0008, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:43:32:465 Device TTL 2621 s flags: 0x7
08:43:47:610 Announced to internet https://phoscon.de/discover
08:43:47:612 discovery server date: Mon, 21 Mar 2022 07:43:47 GMT
08:43:47:613 local time seems to be ok
08:44:02:893 ZCL attribute report 0x0017880103289A06 for cluster: 0x0406, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:44:04:877 ZCL attribute report 0x00158D00067CE971 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
08:44:05:004 ZCL attribute report 0x00158D00067CE971 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
08:44:05:100 ZCL attribute report 0x00158D00067CE971 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
08:44:17:555 ZCL attribute report 0x0017880104F6CABD for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:44:25:631 ZCL attribute report 0x001788010212CAD8 for cluster: 0x0400, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:44:28:664 ZCL attribute report 0x0017880103CAB325 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:44:32:444 Device TTL 2561 s flags: 0x7
08:44:36:712 ZCL attribute report 0x0017880103289A06 for cluster: 0x0402, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:44:40:852 ZCL attribute report 0x001788010212CAD8 for cluster: 0x0406, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:45:26:244 ZCL attribute report 0xF0D1B800001A1F18 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
08:45:32:134 ZCL attribute report 0x00178801021B226A for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:45:32:441 Device TTL 2501 s flags: 0x7
08:45:34:934 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:45:34:953 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:46:03:386 Skip idle timer callback, too early: elapsed 939 msec
08:46:18:916 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:46:18:984 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:46:19:004 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:46:32:446 Device TTL 2441 s flags: 0x7
08:46:51:546 ZCL attribute report 0x001788010212CAD8 for cluster: 0x0402, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:47:03:386 Skip idle timer callback, too early: elapsed 945 msec
08:47:25:733 ZCL attribute report 0x0017880103289A06 for cluster: 0x0400, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:47:32:439 Device TTL 2381 s flags: 0x7
08:47:37:175 ZCL attribute report 0x0017880104AF1828 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:47:40:261 ZCL attribute report 0x0017880104F6B4F3 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:48:04:808 Skip idle timer callback, too early: elapsed 1 msec
08:48:05:386 Skip idle timer callback, too early: elapsed 578 msec
08:48:12:630 ZCL attribute report 0xF0D1B800001A1F18 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
08:48:16:958 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0006, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:48:17:329 ZCL attribute report 0xF0D1B800001A1F18 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
08:48:18:954 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0008, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:48:32:437 Device TTL 2321 s flags: 0x7
08:49:02:360 ZCL attribute report 0x0017880103289A06 for cluster: 0x0406, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:49:18:653 ZCL attribute report 0x0017880104F6CABD for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:49:25:130 ZCL attribute report 0x001788010212CAD8 for cluster: 0x0400, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:49:29:783 ZCL attribute report 0x0017880103CAB325 for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:49:32:441 Device TTL 2261 s flags: 0x7
08:49:36:088 ZCL attribute report 0x0017880103289A06 for cluster: 0x0402, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:49:40:349 ZCL attribute report 0x001788010212CAD8 for cluster: 0x0406, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:50:01:735 0x001788010226D0B0 error APSDE-DATA.confirm: 0xE9 on task
08:50:25:892 ZCL attribute report 0xF0D1B800001A1F18 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000
08:50:32:436 Device TTL 2201 s flags: 0x7
08:50:33:271 ZCL attribute report 0x00178801021B226A for cluster: 0x0001, ep: 0x02, frame control: 0x08, mfcode: 0x0000
08:50:34:000 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:50:34:019 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:51:00:746 reuse dead link (dead link container size now 5)
08:51:13:385 Skip idle timer callback, too early: elapsed 912 msec
08:51:17:993 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:51:18:012 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
08:51:18:045 ZCL attribute report 0x7CB03EAA0A078E1F for cluster: 0x0300, ep: 0x03, frame control: 0x18, mfcode: 0x0000
1 post - 1 participant
Hi folks,
I have the problem that iq_notify notifies only the first mobile_app in my group
notify:
- platform: iq_notify # the platform to use
name: familie # alias name for notify.{name}
time: 2 # time offset in which we assume someone "just left/arrived" or "is staying"
pairs: # a list of presence entities are corresponding notify services
- entity: device_tracker.pixel_4a_mob
service: mobile_app_pixel_4a
- entity: device_tracker.redmi_note_7_mob
service: mobile_app_redmi_note_7
- entity: device_tracker.patriks_handy
service: mobile_app_patriks_handy
- entity: device_tracker.pixel_6_pro_mob
service: mobile_app_pixel_6_pro
I trigger an alert by an input_boolean and the only app that’s notified is the first in the list. (in my case the pixel_4a)
alert:
terrassentuer_stosslueften:
name: Stoßlüften
title: Handlung nötig!
message: Die Terrassentür sollte geschlossen werden
entity_id: input_boolean.trigger_stosslueften
state: "on"
repeat: 15
can_acknowledge: true
skip_first: false
notifiers:
- familie
data:
mode: only_home
Does anybody have an idea what went wrong?
Last week everything worked quiet fine.
1 post - 1 participant
I have a house of about 35 devices (light dimmers in hard to reach places, wall switches and thermostats), all connected to a primary controller that is now out of production and the support is ending.
Therefore, I would like to switch the devices to a Raspberry Pi 3 with Aeotec Z-stick Gen5 that I just connected to the network as secondary controller.
Will there in any way be possible to remove the primary controller and change the Z-stick to primary? I have been told it is not possible and that I have to remove and re-add, re-configure and re-group all devices in order to make the switch. This would represent a lot of work and risk for me, being a total noob. Given all the options, functions, add-ons and scrips HA has to offer, I keep my fingers crossed there is a simpler solutions. Everything looks so promising and smooth in HA, I only need this last piece of the puzzle.
Any help would be highly appreciated!!
1 post - 1 participant
call me silly, but I just realized all automations show the last-changed in the more info popup. which is pretty useless isn’t it, as it gets reset on each restart, and, (in my config) really does nothing else but show that last restart?
Ofc I have the frontend configured to show last-triggered, which Is very useful. More-info also shows that, but the last_changed, well why is it there. Maybe the more-info could be remolded to replace the last-changed with the last-triggered and cut a line of space 
btw, it even shows last-changed on never triggered automations…
1 post - 1 participant
Hello ppl after update to HA 2022.3.x my dashboard stopped working properly
I have some input_select inside of horizontal-stack and It doesn’t open under elements, it opens up of and pushes everything down:
Closed:
Open
it becomes unusable
My YAML is:
- type: custom:vertical-stack-in-card
cards:
- type: horizontal-stack
title: Acções Rápidas
cards:
- type: custom:button-card
name: Fechar
icon: mdi:window-closed
tap_action:
action: call-service
service: cover.set_cover_position
service_data:
entity_id: all
position: 0
- type: custom:button-card
name: Entreaberto
icon: mdi:window-open
tap_action:
action: call-service
service: cover.set_cover_position
service_data:
entity_id: all
position: 20
- type: custom:button-card
name: 50%
icon: mdi:window-open
tap_action:
action: call-service
service: cover.set_cover_position
service_data:
entity_id: all
position: 50
- type: custom:button-card
name: Aberto
icon: mdi:window-open
tap_action:
action: call-service
service: cover.set_cover_position
service_data:
entity_id: all
position: 100
- type: custom:vertical-stack-in-card
cards:
- type: horizontal-stack
cards:
- type: entities
entities:
- input_select.estores_quartos_sala_actions
- type: entities
entities:
- input_select.estore_cozinha_actions
- type: divider
- type: horizontal-stack
cards:
- type: custom:button-card
entity: switch.carregador_tablet
name: Tablet
styles:
grid:
- position: relative
custom_fields:
notification:
- background-color: >
[[[
if (states['sensor.energia_entrada_power_2'].state >= 9)
return "#b3ffba";
return "#f08181";
]]]
- color: "#000000"
- border-radius: 50%
- position: absolute
- left: 60%
- top: 5%
- height: 30px
- width: 30px
- font-size: 11px
- font-weight: bold
- line-height: 30px
- visibility: >
[[[
if (entity.state >= "on")
return "visible";
return "hidden";
]]]
percent:
- color: --mdc-theme-on-primary
- position: absolute
- left: 39%
- top: 35%
- height: 30px
- width: 30px
- font-size: 11px
- font-weight: bold
- line-height: 30pxurn "hidden";
custom_fields:
notification: >
[[[ return states['sensor.energia_entrada_power_2'].state + " W"]]]
percent: >
[[[ return states['sensor.tablet_bateria'].state + "%"]]]
icon: mdi:tablet-android
- type: custom:button-card
entity: switch.computador_sala
name: PC Sala
icon: mdi:desktop-classic
- type: custom:button-card
entity: light.luzes_presenca
name: Luzes Presença
icon: mdi:floor-lamp-dual
- type: horizontal-stack
cards:
- type: custom:button-card
aspect_ratio: 4/1
layout: icon_label
label: Desligar tudo
show_label: true
show_name: false
icon: mdi:power
confirmation:
text: '[[[ return `Têm a certeza que deseja desligar tudo?` ]]]'
tap_action:
action: call-service
service: script.desligar_tudo
I think the problem came from this change
any help?
Thanks
1 post - 1 participant
I am trying to set a routine so it will only water the garden if there is no rain forecasted for the day.
I am using open weather map one day call and it provides me with an entity of: sensor.openweathermap_forecast_condition Looking at the Developers Tools I can see that the current state is cloudy.
However when I manually run this automation, not matter what i put the state as, the action always runs.
- id: '1647850116736'
alias: Morning Water
description: ''
trigger:
- platform: time
at: 06:00:00
condition:
- condition: state
entity_id: sensor.openweathermap_forecast_condition
state: rain
action:
- type: turn_on
device_id: 673882bd533d8f7187e39de46d43fec6
entity_id: switch.garden_watering
domain: switch
mode: single
What am I missing? Any help would be greatly appreciated.
2 posts - 2 participants
Hi,
I have a trigger which is based on the state of an input boolean. I change the boolean and a script runs. I have 5 of these, booleans, and 5 scripts. The object_id of each boolean matches the object_id of a script.
I would like to combine the automations in to one, such as:
- alias: "heating boost to a room"
trigger:
- platform: state
entity_id: input_boolean.heating_boost_james_room
from: 'off'
to: 'on'
action:
- service: input_number.set_value
data:
value: 5
target:
entity_id: input_number.heating_boost_upstairs
- delay:
seconds: 2
- service: "script.{{trigger.object_id}}"
This dosn’t appear to work and I am too much of an idiot to figure out why - can anyone help?
2 posts - 2 participants
Hey, so I had some problems with my router which ended up with that I factory reseted it. Then when I activated it again I couldn’t reach my HA instance but I also saw that the HA has gotten a new IP, so I changed it back to it’s previous static IP but I still can’t reach it.
I got the “Unable to connect to Home Assistant.”. All my sensors work though, so it’s running, it’s just that I can’t access the interface.
Any clues on how I can solve this?
1 post - 1 participant