Thanks for the clarification. I’ll let all that soak in and simmer for awhile, but I’m feeling pretty good now that I’ll be able to set up my security system after i get my envisalink Ademco Vista keypad emulator delivered.
Im still miffed why there is not a State object created for my Flirc keyboard. It seems an obvious state for it would be something like keyboard-key: pressed/unpressed and key-up and key-down are transitions between the key state. But hey it works great, so won’t be losing sleep over it.
Who ever made that integration just made it as events that can be used for automations. Not sure why they made it the way they did. It’s possible that it was made way back in the day. It was the wild wild west and any integration could get added.
What is more, I suspect that the reason that what are now called integrations are found under Integrations - Home Assistant because otherwise every second link in the forum would break if they were suddenly renamed to Integrations - Home Assistant
I dont know about this site but i think apache or nynix is being used. Ive worked with server side PHP enough to know its easy peasy to redirect urls with directives.
This document explains how the Apache HTTP Server uses the URL of a request to determine the filesystem location from which to serve a file.
In fact Im thinking about doing a real request to split the components directory to at least two separate directories named Integrations and Domains and what is left to Modules I think it could be done in less than a day.
Thanks to @petro here are the exact files I would move to Domains:
automation
binary_sensor
camera
device_tracker
fan
group
image_processing
input_number
input_select
input_text
light
media_player
person
remote
script
sensor
sun
switch
weather
zone
zwave
I don’t think you’ll get anywhere with that request. Personally, I think you’re overthinking domains. You should just treat them like a ‘way to organize things’ in your head. Because other than that, they don’t really serve any purpose.
It’s not that so much as wanting a clean list of valid Integrations that are available to help me decide which Devices are supported. I know there is a web page here showing a list icons, but it didnt really help and the search feature never found what I was looking for.
For example: Im working right now on my security system and was looking for a list of siren, door bell, motion sensor and window sensor devices for me to research then purchase. But I didn’t have much luck finding any sort of list and ended up buying a siren that turns out to be unsupported.
I’ll admit that maybe I’m just not doing something right but I just didnt have much luck with my search.
The “integrations” page on the website is a complete list of all the things that are supported by home assistant. The URL says it’s components. It’s the same thing.
If something isn’t supported directly, get something that’s hackable and put your own esp8266 chip on it and make it work with your system.
Thanks, just to be clear, my example in the previous post is what I was doing before you steered me to a way to reuse my old Honeywell Vista system. Now I’m doing it you’re way.
I went back to the Integrations and tried again, but still dont think i would have ever found the EnvisaLink 4 without your help.
Searching for Honeywell just brought some sensors and going directly to EnvisaLink describes it incorrectly as a controller board. Where the mfg. calls it a “DSC & Honeywell Compatible Internet Interface Module”
Even though the three I circled qualify as items of interest, my eyes just glazed over and only locked on to the Honeywell card. As far as I was concerned, EyesOn and AlaramDecoder were other alarm system brands, so I ignored them as well as all the other cards except for the Honeywell card.
With a good filter I think with just looking for things related to Honeywell I would have found all the items plus a view sensors and other things.
For AlarmDecoder I would have found:
users who own either a DSC or Honeywell alarm panel to leverage their alarm system
For EyesOn:
users who own either a DSC or Honeywell alarm panel to leverage their alarm system and its sensors to provide Home Assistant with rich information about their homes
For Honeywell:
The totalconnect platform provides connectivity with the Honeywell TotalConnect alarm systems used by many alarm companies.
Ironically it turn out im extremely interested the first two cards but not the Honeywell.
Got a feeling Im not making my point but im trying
