I got into trouble with my wife this morning because the automation to turn my Christmas tree lights didnt turn the socket off. For some reason the socket had disconnected from the network. I will use Retry and it will save my marriage 😂
The HACS retry has changed since this was released. Now, after HACS install we need to: Add Integration - Retry This is because the retry service can be created in an automation/scripting GUI rather than manually typing the yaml :)
An amazing list of HACS components, I will be checking out retry for sure as it could replace my own states tracking and device online tracking automations
Hey BT! I signed up for membership today. Hope it helps you as I always look forward to your videos and have gleaned a lot of useful tips along the way! I definitely like the expander card better than the collapsible card that I've been using. It looks much easier to setup and more intuitive. Merry Christmas to you and your family! 🎄🎅 ✝️
Welcome aboard! I've seen in notifications one other message from you - not sure if you've deleted it or RU-vid just removed it (happens from time to time), I'm ashamed that most of those cards are available on my recording and test systems - while my main setup hasn't been freshened up in years....
Recommended for future video... Thermal Comfort. I use it for three things, outdoors for frost warning, indoors for relative summer comfort and inside my filament storage for showing absolute moisture levels (rather than humidity which is affected by the temp of room) It's just been updated so you can do all the config in the UI and not in code 🎉
thanks BT for the Network Scanner HACS tip , nice NMAP integration, really love the HACS diamants you find ;-) I hope there is way to manually edit/insert the Custom Name and Custom Description somewhere so I can name my found known devices. Maybe someone already found this ?
Not that I know of at this time. Only way to add is to remove existing and add once again. That will show the configuration screen where you can add up to 24/25 names and mac addresses
Thanks. The expander card looks especially useful, I’ll be installing it now. Do you know if there’s a way to do something similar horizontally, a swipe right/left to see more entities ? Maybe a walkthrough of the base Lovelace components, how and where to use them (and key HACS extras) would be useful 👍
Thanks for the Network Scanner HACS reference. 1. I haven't managed to get the custom name / manufacturer to work for my (known) device(s) eg 'B0:xx:56:xx:yy:xx;Orbi_Router;Netgear' is the 'devices' entry needed before the device list?- may try restart & see.. 2. Wondering now if there is a way to detect the IP address of a device (non static IP) from the MAC, then assign that discovered IP to an HA parameter for use in other HA scripts / automations that depend on device IP (thinking LGTV integration for example)?
I try Network Scanner, but it has couple of bugs. It has limited count of MAC specification for known devices, scanner did not works well for all of my devices and did not found them, all devices behind WiFi range extender had same MAC address of that extender. For example my router show me that I have connected 27 devices but "Network scanner" shows me only 19.
Haven't cough this one as I've removed all my extenders and replaced them with wired APs. The other is probably limitation of library used. You can try to ask author on GitHub about this one.
I tried expander cards; installation worked but when I try to make new sheet for testing, my HA screen is updating continuously and I cannot create anything. I also installed Retry -service and update my Christmas lights -automation because sometimes automation didn't change all lights on/off. Let's see how it work.
About that issue - I've seen it on one of my test systems. Need to figure out if that's conflict with one of other hacs components. On other systems it works ok. Hoping retry works for your case. It should...
HA told that my automation is using unknown service, retry.call. Here are the automation rows: default: - service: retry.call data: service: homeassistant.turn_on expected_state: "on" target: entity_id: light.group_autotie At first I tested it only one place but it didn't work 😐 My system is: Core: 2023.12.1 Supervisor: 2023.11.6 Operating System: 11.2 Raspberry Pi 4
I missed that when I checked your video. Now I have added retry as a new integration, not in configuration.yaml. Any way, it was my bad and now retry -service seems to work and I will add it to all my automations because I have had some problems with Zigbee -lights and I trust this will fix all problems. Also that HA screen updating problem has gone without any changes. It seems that 2-3 restarts fixed it.
I love the retry service! Works beautifully! As for the Stardate sensor, I'm not a fan of the calculation based on the Stardate today would be in a current TNG episode if it were still filming so I created my own which I think is more realistic and gives today's Stardate based on Stardate 00000.0 being Friday, July 5, 2318 around noon (Starfleet Command time which is USA CDT). Right now it is Stardate 270457.5 BT which is -270457.5 "Before Trek" (not BeardedTinker!). The template is: {{ ((as_timestamp(states('sensor.date_time_iso')) - as_timestamp("2318-07-15 00:12:00.0-05:00")) / 34367.0564 )|round(1,'floor') |string}} BT
