uix-view-yaml: |
grid-layout:
$hui-grid-card:
$: |
#root {
flex: inherit !important;
}
if youre using card-mod, replace uix to card-mod instead
uix-view-yaml: |
grid-layout:
$hui-grid-card:
$: |
#root {
flex: inherit !important;
}
if youre using card-mod, replace uix to card-mod instead
For automations using Wake-On-LAN, the MAC address now needs to be used in the actions code. Refer to the integration documentation for Samsung Smart TV. There is a section titled Turn On Action that gives a great example of using an explicit Wake-On-LAN automation.
Iāll second Keymaster. It works well installable through HACS and allows syncing between lock, time and date enables of codes, and notifications.
Agreed that core cards should remain as-is by default.
New features should be handled with new (optional) parameters.
Some of those parameters should:
It is insane that Home Assistant can integrate with AI blah blah, but you canāt make two core cards look similar. These are fundamental issues and like the bricks at the bottom of a house wall, they should be sorted before you start putting gargoyles on the roof.
If only we had a way to preview new features or say updated core cards prior to being release, gain feedback and decide if they should be rolled out, I donāt know we could call it āHome Assistant Labsā or something like that? ![]()
⦠or BETA.
Fair point, but I still think we could take more advantage of the Labs feature.
I donāt think that itās a good use of developer resources to create a Labs feature every time UI changes are applied (which is every month, so we can also test this with the regular beta).
Set up a VM with an HA instance with a few fake cards (the same ones youāre using in your productive system) or simply crate a backup when the beta cycle starts, update to beta and revert (+give feedback in the discord beta channel) in case of problems you canāt live with (which is what I do).
That is also what I do, well almost. I run the beta on a second environment and provide feedback in the discord channel (all be it infrequently). If the effort on developers is too great to use the Labs feature, could it be made simpler�
That said my tongue-in-cheek comment seems to have gone further than it should have! ![]()
Input numbers defined to use input field as opposed to sliders, the up/down adjustment arrows have gone�?
I just want to say I love the changes to Home Assistant automations. Being able to add a new device, then go to add an automation for that device or add it to automation Iāve already made is so much easier or much more user friendly. Being able to search the device/entity name in the trigger, condition, and/or action sections is amazing! I love that they added the background color for sections but wish they would add a way to change the card colors. I know there are HACS for that but itād be so much better if it was part of Home Assistant. Iām so looking forward to infrared AC unit controls. Having a fully local none-HACS way to control my window AC units is gonna be so useful! Just gotta find some infrared devices thatāll work. Anyways, I just want to say thank you for your hard work to all the contributors for all they do and I look forward to whatās coming.
Anyone with an issue around SkyConnect after the latest update?
Mine is not being recognized anymoreā¦
āFailed setup, will retry: The device is not plugged inā
I use SkyConnect for zigbee. Z2M in particular. Still working like a champ, but Iāve kept it updated to its latest stable firmware.
Anyone else?
A fix has been made for this, should show in the next frontend patch release ![]()
Your issue was probably caused by the OS update to 17.2, not the 2026.4 Core update which this thread refers to.
Thereās an open issue about it here - your best bet is do downgrade the OS back to 17.1 as explained at the bottom of the first post.
How is this new IR support compared to SmartIR integration? It was quite versatile and supported multiple transmitter hardware platforms. I am still using it with battery powered zigbee transmitter.
As explained in the Blog post, built-in IR support is only just starting to roll out & only the LG infrared integration supports it natively for now. Itās gonna take a while until it can go head to head with all the devices SmartIR supports.
OK, thanks. I just hope this new IR-support will at least be useful for more convenient IR code detection/conversion to improve flexible solutions like SmartIR.
Would be great if the team could also check/fix the HACS panel issue on mobile..
Updating has been a challenge ever since that occurs
Aware itās been a month only but Hacs resources update quite frequently;-)