The I/O Linc has a green light that goes on when the door is shut and the sensor magnet is near the sensor. Then when I open the door, the green light goes out until the door is shut again and then it comes on.
So the state of the light on the device is always consistent and is not reflected in the HA I/O Linc relay/sensor status.
I’m kind of stumped. It would make me feel better if someone else with the device could say it worked or didn’t work for them and how they have it connected up (though admittedly mine is different because I have the output of the I/O Linc connected to the remote and not the garage door (because that doesn’t work with this door).
Looking at https://cache.insteon.com/pdf/2450qs.pdf you should be connecting to sense and ground. If it is reverse what you would like, you would need a normally closed magnetic sensor.
Yep, that is what I figured. I have the full 2450 pdf document. I was hoping there was something that I missed. It was a LONG time ago when I set it up with the Insteon app. I was also hoping that maybe HA would do better, but it looks even more unpredictable.
I wonder if the sensor that came with the Insteon garage kit had a normal closed switch and that is what is confusing HA on the state. (but there seems to still be something odd about the sensor state getting updated.
I might see if I can find the code and figure it out. But not today…
And I’m still struggling with the %^#%%^^ 2450 I/O Linc and HA. The relay portion of the IO Linc always works, and the sensor part works 95% of the time. When it does work, it’s backwards. There are examples on this forum and others of how a “custom button” can be programmed in the configuration.yaml to make a custom garage door “button” that opens/closes the door AND reverses the sensor output to be correct. Pretty colors, red open door, green closed door, nice text… My issue is cutting/pasting the code then changing the Insteon address to match my units ALWAYS give some type of syntax error in the blasted *.yaml file. The syntax is “correct” in the editor and online checkers, but there is some error(s) that I can’t seem to fix when the modified configuration.yaml file is loaded in HA.
All I know to do is trial and error to get the syntax correct, but the indents, spaces, no-tabs, colon rules in the code are killing my efforts. Cutting/pasting seems to introduce syntax errors, too. I’m reading up on this yaml code, but I really don’t want to have to learn a new programming language to get this I/O Linc going. I keep hoping someone will post the exact method to get the garage doors going, what files to edit, what code to add, what to change in the code, how to add the button to the overview, etc. There are examples out there, but for a newbe to HA the examples are not complete enough to solve the problem.
Yes, I’d love to do what you suggested. But, where do you add this code? I assume if it’s added in the right place, I can add to the overview just like any other insteon sensor.
I cut and pasted from your example from “template:” on into the configuration.yaml file with the add-on File Editor. All the syntax was correct. Then, under Developer Tools/YAML, the file was Valid so I was able to Restart and load the new configuration.yaml. Finally, the new “Garage Door” could be found just like an Insteon entity and added to the Overview Pane underneath the IO Linc Relay Switch. Thanks! That’s a big step forward.
Now, I’ll try to modify to say “closed” instead of “on” and show a garage door open/closed as needed.
Thanks. I cut/pasted this text into the configuration.yaml file and it is good in editor check. “Check Configuration” under Developer Tools/YAML states “Configuration invalid.” Four errors and Restart of configuration not available.
Integration error: entity - Integration ‘entity’ not found.
Integration error: type - Integration ‘type’ not found.
Integration error: tap_action - Integration ‘tap_action’ not found.
Integration error: state - Integration ‘state’ not found.
I’m probably missing something somewhere… If it makes a difference, I’m running HA on a RasPi4.
It is a card, it does not go in config.yaml It goes in a dashboard card. Add the repository above then go to a dashboard and choose edit. Then add card → choose custom button card → add the above code → change the entity.
I go to Settings, then Add-ons, then +Add-on Store, Click on three dots in upper right, then Repositories, then “Manage add-on repositories” window opens. What goes on the ADD line? I’ve copied the URL (GitHub - custom-cards/button-card: ❇️ Lovelace button-card for home assistant), and get “Invalid Add-on repository.”
Jez… I need to start drinking to do this. This is my first jump into HA, but HA has got to be one of the most confusing systems with which I’ve ever dealt. Get this from here, add with that from there. I guess that’s a product of cobbling together code from many sources. I’d like my garage door to work without learning another language, but I’ll start digesting the directions. Maybe Universal Devices will purchase the Insteon rights before I finish and restart the Insteon Servers. At the rate of my progress with HA, that could really happen.
I do appreciate and am very thankful for the help.
Not sure what you are confused about. The only thing I found a little confusing was the figuring which version I should use, but once I saw a docker install for my synology nas, things have been pretty smooth. 40 insteon devices all working with my hub without any external server required. PLUS it found computers, rokus, denon receiver, tvs, and phones. None of that happened with insteon alone. I just have a minor problem with the garage door opener. Don’t give up.
All my Insteon items (except the IO Linc) are working well through the Insteon Hub using the Hub Schedules. And that’s OK with me; all HA is doing for me now is turning on/off Insteon switches from my phone as needed. Loading HA on the RasPi, adding Insteon, making the Dashboard, adding the cards took 2-3 reformats of the Memory card to wipe out any errors I may have inadvertently left while making HA something I liked. I thought the entire process was very tedious. HA doesn’t seem to be an out-of-the-box, plug-and-play product. That’s OK, too. I’m sure HA will be less frustrating when I dig into it a little more. All that’s left is the Garage Door Sensors, and that’s just going to take some time and trial-and-error to get it where I like it. Hopefully, in the process of getting the Garage Doors working, I’ll learn my way around HA enough to really do some helpful automation.
Ah, I could see where having to reformat memory cards on a pi could be annoying. I run HA on my Synology NAS and it was a fairly nice experience and I’m really glad to get additional mileage out of my NAS. I DID have to figure out a little about Docker which I have never used before. Maybe I am just more tolerant of any difficulties/complexities since I have been doing programming since 1966.
Plus, nowadays, there is SO much more help in the form of documentation, videos online, and user forums plus vendor support that it seems easy compared to the past.
I can also see that HA has come a long way in putting together a UI instead of configuring everything in the yaml. Now THAT would have been annoying except for the programmers and tinkerers. I much prefer the UI way of doing things.
Not exactly. Add-on’s are like separate programs, like a file editor. Some addons supply an integration for home assistant to interact with it.
Integrations tell home assistant how to communicate with other devices or programs(addons). Integrations that are officially supported come packaged with home assistant. The home assistant community store or HACS also has integrations that can be added as well.
Integrations are in HACS for various reasons. They’re new, often officially supported intgrations start off in HACS and are merge later on. The ability to push an update in HACS is almost instant, where the official needs to update the entire core and get approval from various people.
That approval is also why something may be in hacs, less popular items can often spend an eternity waiting for approval. This is a volunteer program so oversight resources are limited.
FWIW, I went into the Insteon panel “All-Link database” and deleted all the things that weren’t direct connections between the device and the hub or the between 2 devices. That got rid of the HUB scenes/schedules. Then I easily created even better scenes/schedules managed by HA using automations and scenes and groups. I now have much easier to understand and manage insteon devices than I had with the insteon app.
I think the plan is to improve this “All-Link database” interface with time. I’m just glad it was available when I needed it when Insteon disappeared.
… time passes …
Oh, on re-reading the thread, I see all the things that you “cobbled” together to get what you want. The I/O Linc doesn’t currently work correctly (my opinion) and so that is why different cobbles were being recommended to get around the problems. Me, I’m probably just waiting till it gets fixed. I can open or close the door if I want. And I have a camera set up in the garage, so I can just look to see if I’m unsure of its state.
The good news is that you CAN cobble things together if necessary. With the old app Insteon provided, if you didn’t like it, too bad.
