Thanks for your feedback. That is really great view - from the other side of HACS... BTW - I really need your help. Your component has been on my list to do for VERY long time, but can't get my head around where to start, what to get, so I can do video on it . loving the ide of using ePaper. We can continue on Discord or mail - mine is inquiry@beardedtinker.com Really would love to do video, but no idea what I need to get to get it working.
@@BeardedTinkerMaybe this could be a starting point: ua-cam.com/video/Etonkolz9Bs/v-deo.htmlsi=YOKaVTiV87q544LL Looks like a lot of work, but it is explained quite well and understandable. I use several Epaper displays myself, but they are all driven by ESP8266 and ESP32 with Esphome. Thank you for your videos. I love your precise explanations.
Unfortunately, as much as I'd love to avoid HACS, some of my most used integrations are ONLY available through HACS. examples are Frigate, Tesla, and SolarEdge Modbus.
The 2GB RAM on the "flagship" HA Yellow was the major reason I ended up getting the kit version and supplied my own 4GB CM4 module. the 4GB made a huge difference as my restart speed is about 45 seconds, for a restart and about 90 seconds on a full reboot. I have around 40 integrations that load, with 10 of them being custom integrations. I guess it depends on the integrations you use, but I did swap with a 2GB CM4 I used with another project, and my start up time was double at 90 seconds and 180 seconds. I never thought 4 GB RAM would be needed, but even if it doesn't use it, it makes a difference. I am also using a NVMe drive not the eMMC on the CM4. Now the other two reasons I didn't get the 2GB flagship model was because I wanted PoE and I wanted to use the onboard bluetooth of a CM4 with radios. :) That said, admittedly the RAM is the bigger thing. Even the HA Blue I had previously had 4GB and 128GB eMMC. I really feel the shortage of components caused Nabu Casa to kind of "cheap out" by getting the 2GB / 16GB CM4 module. It really would have been better as a 4/32 module.
Yeah, that's a topic for a long video - HA crew would probably cry over the whole thing - no matter how enthusiastic you are or how great your ideas are if "world" hits you or real life happens. They are really disappointed with Yellow, not as product but everything around it. They wanted versatile and simple device for masses that would be cheap, and it simply spiralled out of control. Prices gone up, delays, availability of CM4 module with again, prices going up - plus some other issues that are stil not fully public as multi-pan issues and discontinuing of it, plus post release issues with Google coral TPU with M.2 slot etc.
Almost all of the 'frontend' stuff is Javascript code, which runs client-side and thus will not affect your HA-instance (but will affect any clients connecting to it).
I use it a lot, some things critical to my core house functionality like the Tuiss blinds integration and other nice to have like battery notes and presence simulation.
This is the risk in HACS though. If those "critical" custom components stop being updated and become incompatible with new versions of HA, you are either stuck on an old version forever or you lose that functionality. I admit I use HACS, but more for local weather services and things of a less critical nature.
@@EsotericArctos absolutely agree, I always grab a copy of the repo as well to my GitHub so I have it but it’s a risk. Using the blinds example if I lose the functionality I have to go back to using my remote control instead or hope it becomes an official integration. It’s a risk I have to take as they are the blinds I have and they are not cheap to replace
I really hope I managed to get that across the video. We all have at least some components that we really depend on. Being aware of the risk is already 50% of the job done - maybe you haven't prevented it but you are aware of it.
@@EsotericArctos Which is better: Having a "critical" custom component that might stop working sometime in the future, or not being able to have it at all? That's the choice here. having the "critical" functionality, without having the risks is simply not an option, so is a somewhat false choice.
You can select it via Integration page - but 4 out of 5 times I did it on test systems it didn't work. Ludeeus (dev) is stating that same procedure - check it here (if you have Discord account): discord.com/channels/606225571898327139/1201810560434311198/1201811972430249994
Yeah, I'm guilty of using HACS a lot. Maybe 5-7 custom integrations, 2 AppDaemon components and too many Lovelace components to count. 😅 Actually started considering moving my setup from my HA Yellow to a small but powerful mini PC. Would love some extra speed, since my system seems very slow at times.
Hear hear! 👏🏻 True, but mine is still under 1 GB. Had a major issue last year which corrupted my old database beyond repair. (And I somehow missed that my auto backup had stoppet working even long before that even happened.) So I'm pretty sure it's not that. 😉
Instead of moving to a PC that uses more power, maybe look for a CM4 that has more RAM and maybe also move to an NVMe drive instead of using the CM4 MMC. I use a 256GB NVMe and a 4GB CM4 and I have, last I checked, 4 AppDaemon apps, 30 odd integrations and a few of them are custom from HACS (though I don't ever do anything mission critical from HACS) and I don't get any lag during operation and the boot times from cold are less than 3 minutes, and a restart less than 2 minutes. Much better than 6 years ago when I use to run on a Lenovo mini PC and took 20 minutes to reboot :)
@@EsotericArctos Triple check on all of that. 8GB of ram and 1 TB NVME. It is not that I get proper lag, it's more that the system sometimes feels underpowered. One of the worst things is when I try to update my 16 ESPHome devices. It takes forever to compile and flash everything.
I only update 3 of my ESPHome devices on each update. Rest are on firmware that's probably 3, 6 and some even 12 months old. If it works... ON my main setup, on Synology, it took up to 10 minutes to reboot. That's after replacing 4TB with 12TB drives. But I've added 2 NVME read/write cache drives and now it really flies.
8:50 - the new HA 2024.02 brings a huge performance upgrade by implementing the new python version. The front end is much faster at least on Pi 4 with 4 GB that we run here with a 100 GB SSD. That is a big benefit most over look. I have heavy apex charts that use 5 entities while also the experimental preview / zoom is active aka as brush. You could literally watct that chart drawing each line and it took 5 or 8 seconds to update the chart, but now it is a lot faster, instantly there. My whole dashboard has become a race horse compared to the snake I had before.
I've stopped using NodeRed long time ago. Didn't want to have separate system to run things I could do internally. NR is good as it's very visual tool, but...
I have 50+ integrations/lovelace components and yesterday I started to use HACS 2.0. First impression is that it is imrovement but let's see. When component will be changed how new HACS shows it?
Not sure on that. I'm still not sure if the new "update" feature is something I like or not. If you've noticed, that's moved to the updates section in Home Assistant.
@@BeardedTinker I haven't seen yet. But it would be good to collect all updates to same place. Those HACS component updates will come weekly, so I should see something during next few days
I was using the UA-cam custom component from HACS until recently, but now that there is an officially supported one that uses the UA-cam API, I've removed it.
@@BeardedTinkerTrue, but it's a lot harder to add new entities to the one in HACS since YOutube rolled out the custom channel names and hid the older style ones.
As a custom component Dev(OpenEpaperLink), I really like Hacs because it allows you to generate HA release independent releases of our component.
Thanks for your feedback. That is really great view - from the other side of HACS...
BTW - I really need your help. Your component has been on my list to do for VERY long time, but can't get my head around where to start, what to get, so I can do video on it . loving the ide of using ePaper. We can continue on Discord or mail - mine is inquiry@beardedtinker.com Really would love to do video, but no idea what I need to get to get it working.
@@BeardedTinkerMaybe this could be a starting point: ua-cam.com/video/Etonkolz9Bs/v-deo.htmlsi=YOKaVTiV87q544LL
Looks like a lot of work, but it is explained quite well and understandable.
I use several Epaper displays myself, but they are all driven by ESP8266 and ESP32 with Esphome.
Thank you for your videos. I love your precise explanations.
@@SciBee thank you - just checked it out. Nice video and explanation of HW/firmware setup!!!
Thanks for the information on the HACS update. Updated nicely!
Any time! Thanks for the comment!
Thanks BT! I was a little nervous about deleting HACS, but your instructions were perfect. Running the new UI now! I like it better. 👍
Great to hear! That's why I have few test systems - allows me to randomly push buttons to see what they do 😂
@@BeardedTinker thank you for being a willing crash test dummy for all of us! 😂
Unfortunately, as much as I'd love to avoid HACS, some of my most used integrations are ONLY available through HACS. examples are Frigate, Tesla, and SolarEdge Modbus.
The 2GB RAM on the "flagship" HA Yellow was the major reason I ended up getting the kit version and supplied my own 4GB CM4 module. the 4GB made a huge difference as my restart speed is about 45 seconds, for a restart and about 90 seconds on a full reboot. I have around 40 integrations that load, with 10 of them being custom integrations. I guess it depends on the integrations you use, but I did swap with a 2GB CM4 I used with another project, and my start up time was double at 90 seconds and 180 seconds. I never thought 4 GB RAM would be needed, but even if it doesn't use it, it makes a difference. I am also using a NVMe drive not the eMMC on the CM4.
Now the other two reasons I didn't get the 2GB flagship model was because I wanted PoE and I wanted to use the onboard bluetooth of a CM4 with radios. :) That said, admittedly the RAM is the bigger thing. Even the HA Blue I had previously had 4GB and 128GB eMMC. I really feel the shortage of components caused Nabu Casa to kind of "cheap out" by getting the 2GB / 16GB CM4 module. It really would have been better as a 4/32 module.
Yeah, that's a topic for a long video - HA crew would probably cry over the whole thing - no matter how enthusiastic you are or how great your ideas are if "world" hits you or real life happens. They are really disappointed with Yellow, not as product but everything around it. They wanted versatile and simple device for masses that would be cheap, and it simply spiralled out of control. Prices gone up, delays, availability of CM4 module with again, prices going up - plus some other issues that are stil not fully public as multi-pan issues and discontinuing of it, plus post release issues with Google coral TPU with M.2 slot etc.
Almost all of the 'frontend' stuff is Javascript code, which runs client-side and thus will not affect your HA-instance (but will affect any clients connecting to it).
Yes, that's correct. But integration part is mostly backend and can affect HA.
It’s suuuper minor, but if it may be of interest, it looks like there’s a very minor typo in one of the chapter titles, “chek” (→ “check”).
Thank you! Fixing it ASAP :)
I use it a lot, some things critical to my core house functionality like the Tuiss blinds integration and other nice to have like battery notes and presence simulation.
This is the risk in HACS though. If those "critical" custom components stop being updated and become incompatible with new versions of HA, you are either stuck on an old version forever or you lose that functionality.
I admit I use HACS, but more for local weather services and things of a less critical nature.
@@EsotericArctos absolutely agree, I always grab a copy of the repo as well to my GitHub so I have it but it’s a risk. Using the blinds example if I lose the functionality I have to go back to using my remote control instead or hope it becomes an official integration. It’s a risk I have to take as they are the blinds I have and they are not cheap to replace
I really hope I managed to get that across the video. We all have at least some components that we really depend on.
Being aware of the risk is already 50% of the job done - maybe you haven't prevented it but you are aware of it.
@@EsotericArctos Which is better: Having a "critical" custom component that might stop working sometime in the future, or not being able to have it at all?
That's the choice here. having the "critical" functionality, without having the risks is simply not an option, so is a somewhat false choice.
Am I missing something completely? Can't you just select Configure and enable or disable the Experimental mode without removing it and reinstalling?
You can select it via Integration page - but 4 out of 5 times I did it on test systems it didn't work. Ludeeus (dev) is stating that same procedure - check it here (if you have Discord account): discord.com/channels/606225571898327139/1201810560434311198/1201811972430249994
You have to clear your web browser cache when changing HACS modes.
Yeah, I'm guilty of using HACS a lot. Maybe 5-7 custom integrations, 2 AppDaemon components and too many Lovelace components to count. 😅
Actually started considering moving my setup from my HA Yellow to a small but powerful mini PC. Would love some extra speed, since my system seems very slow at times.
Everyone should use HACS :)
Slow system can also be database. Mine is currently at 6GB 😂
Hear hear! 👏🏻
True, but mine is still under 1 GB. Had a major issue last year which corrupted my old database beyond repair. (And I somehow missed that my auto backup had stoppet working even long before that even happened.) So I'm pretty sure it's not that. 😉
Instead of moving to a PC that uses more power, maybe look for a CM4 that has more RAM and maybe also move to an NVMe drive instead of using the CM4 MMC. I use a 256GB NVMe and a 4GB CM4 and I have, last I checked, 4 AppDaemon apps, 30 odd integrations and a few of them are custom from HACS (though I don't ever do anything mission critical from HACS) and I don't get any lag during operation and the boot times from cold are less than 3 minutes, and a restart less than 2 minutes.
Much better than 6 years ago when I use to run on a Lenovo mini PC and took 20 minutes to reboot :)
@@EsotericArctos Triple check on all of that. 8GB of ram and 1 TB NVME. It is not that I get proper lag, it's more that the system sometimes feels underpowered. One of the worst things is when I try to update my 16 ESPHome devices. It takes forever to compile and flash everything.
I only update 3 of my ESPHome devices on each update. Rest are on firmware that's probably 3, 6 and some even 12 months old. If it works...
ON my main setup, on Synology, it took up to 10 minutes to reboot. That's after replacing 4TB with 12TB drives. But I've added 2 NVME read/write cache drives and now it really flies.
8:50 - the new HA 2024.02 brings a huge performance upgrade by implementing the new python version.
The front end is much faster at least on Pi 4 with 4 GB that we run here with a 100 GB SSD.
That is a big benefit most over look. I have heavy apex charts that use 5 entities while also the experimental preview / zoom is active aka as brush.
You could literally watct that chart drawing each line and it took 5 or 8 seconds to update the chart, but now it is a lot faster, instantly there. My whole dashboard has become a race horse compared to the snake I had before.
That's really big change. Thanks for post!!!
Only time I have seen a huge hit on cpu and memory was when I was running Node Red with a few automation running.
I've stopped using NodeRed long time ago. Didn't want to have separate system to run things I could do internally. NR is good as it's very visual tool, but...
thanks for the good info 👌
Glad it's interesting! Thank you!!!
I have 50+ integrations/lovelace components and yesterday I started to use HACS 2.0. First impression is that it is imrovement but let's see.
When component will be changed how new HACS shows it?
Not sure on that. I'm still not sure if the new "update" feature is something I like or not. If you've noticed, that's moved to the updates section in Home Assistant.
@@BeardedTinker I haven't seen yet. But it would be good to collect all updates to same place. Those HACS component updates will come weekly, so I should see something during next few days
I was using the UA-cam custom component from HACS until recently, but now that there is an officially supported one that uses the UA-cam API, I've removed it.
I'm still using HACS version. Need to check internal one, but if I remember correctly, it's missing some of the attributes compared to HACS one.
@@BeardedTinkerTrue, but it's a lot harder to add new entities to the one in HACS since YOutube rolled out the custom channel names and hid the older style ones.
Thank you sir.
Most welcome Ron! Thank you!!
Yes I am.
And that's very very good :D
I use HACS for a few card types.
Nice! I have few of them as hey really nicely extend and improve internal ones.
Until home assistant sucks in many functionality HACS is the only way. Its almost most important HACS than the core home assistant.
Did you try make any suggestion on suggestion forum or maybe tired pull request if you can program?