Cqc vs homeseer11/6/2022 ![]() While they are often lumped into "IoT", the Z devices don't use IP or TCP so it's really hard for those Ts to be on the I. I still count that as one of my "geek" milestones. Tar, gzip, gcc, sources, libraries, binaries, I compiled and recompiled so many times.Įight hours, hundreds of MAN pages, a large pizza and 4L of carbonated sugar water later, I had a recompiled kernel running XWindows in my monitor's native resolution & refresh rate (score!) with the soundblaster (SB16 maybe.) able to play Torvald's "I pronounce Linux." file and a web browser (Netscape 1.0b I think). About the time I figured out what I should do, a package was downloaded. #Cqc vs homeseer downloadThe 128k ISDN (bonded channels!) and using two sessions let me download in one session while reading man pages and make my next action plan in the other. #Cqc vs homeseer PcI used it to boot my 75Mhz AMD PC and was able to connect to the LAN and (via ISDN) the internet. I started with a 1.44Mb floppy disk with a "router" build of slackware. I'd been using linux in the labs or at work since '91 so I wasn't a total neophyte but I'd never done an install. So thanks for sharing your thoughts.Back in the mid90s, I set up my first linux box. Your 20+ years of HA experience should be of great value. Even though intended for storing credentials, it should also be possible to store such things as the host of a HUE bridge or echo device.Īgain, HASS is still in a rather early stage of development. And exactly those entity IDs are what you reference to in automations, scenes, templates, pretty much anything.Īnother form of constants would be the usage of secrets. That’s why we can assign friendly names to devices. HASS has entity IDs, which usually are constant. I’m not sure if I understand what you mean by the constants. So making the things easy the users do most often. In that regard I personally would prioritize UI-based automation creation (or rule engine for that matter) much higher than the basic setup of the environment. Especially when setting up the components often is something you only do once, and afterwards only consume using automations etc… #Cqc vs homeseer softwareA first step has to be taken somewhere, and focussing on something as generic as grouping entities seems thoughtful compared to something as complex as setting up specific hard- and software that heavily depends on the users environments. Fairly recently (about two versions ago I believe) the first step in this direction was taken by optionally providing GUI-driven configuration for groups. Would be interesting to see how HA was done back then.Īs for the rest: so what you are actually asking for is a GUI based configuration utility? I’m pretty sure we’ll have that in HASS even before we reach version 1.0. Just out of curiosity: could you provide some information on the HA systems you were using 20+ years ago? Back then I was still playing games on my Win95 machine with no Wi-Fi in sight. If HASS ever changes its back-end, as long as it still uses the Constant method, updating code/configs is automatic, no user intervention needed. if you change a constant (like you change IP addresses, or friendly names) HASS automatically changes it in all placesĬ. use same constant in multiple configs, add/change anything in seconds, in multiple places/configsī. ![]() #Cqc vs homeseer modThis could be dynamic, loaded on start so if a constant changes, all you do it mod it, and restart HASS.Ī. When you pull up a config to add to HASS, you could simply link that config a constant, and HASS could define all items. To make things potentially even more flexible - HASS could create User Defined Constants (systems and devices that could be referred to within any config), the user could choose to ‘link’ the constant to one of more configs, as needed.Ĭonstant Name (aka Friendly Name) : Living Room Echo In the HASS GUI, users could select them and they are loaded into the yaml automatically- then the GUI could show on screen the specific items that need to user input. HASS could have a repo with these configs. ![]() #1 & #2 … should be easier to add to HASS as many items are already documented in the wiki and tell you what sections to update. ![]() But, this is also the most critical item to have in the GUI. #3… a rules engine is not super easy to implement but many apps do it well (Homeseer, ISY, Elve, and several others).
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |