I’ve converted all of my insteon devices over to home assistant and I’m happier with HA than I was with the Insteon app. But I have one device that doesn’t seem to be working correctly. My I/O Linc 2450. I have it hooked up to operate and sense my garage door opener. Because my opener has a rotating code, I can’t just hook up the I/O Linc to the door opener. So I cracked open the remote control and figured out what the microswitch inside does. Then I made the output of the I/O Linc operate the remote which operates the door.
For the sensor, I had some burglar alarm magnetic sensors for the windows and doors and I hooked one up so that when the garage door is closed, the magnet and sensor indicate the status of closed.
I have the wires that connect to the remote on the N/O and COM screw terminals. And the sensor is hooked to the GND and S(ense).
I’m confused about the sensor state because, at the least, it can say open when closed and vice versa. Although I think sometimes I’ve seen it saying closed when it is closed.
So I thought maybe I didn’t have it configured right in the device. So I re-read the documentation for the 2450 and I found a section that I just don’t understand (after reading it several times). Here is the section:
A latching relay when switched will stay in that position until it receives another signal. Normally a relay will switch but will require power to stay in a switched position, a latching relay doesn’t.
A momentary switch when it receives a signal will switch and then wait a predetermined period of time before switching back.
You would want to attach it to the normally closed terminal.
Are you saying I need to switch to N/C for the signal to the remote to solve the sensor state? Or are you saying that I should switch to that in one of the 2 cases you described?
It sounds like I DON’T want latching mode as it should just “press” the remote button each time. I think it is doing momentary because when I turn it “on” in the HA UI, it toggles itself back off after a few seconds.
And is the “normally closed” referring to the type of sensor or the state of the sensor. The sensor I have used shows continuity when the magnet is near and infinite when the magnet is not near. I thought that meant “normally open” for the sensor, but of course, when the door is closed the magnet is near so the circuit is closed in that case.
So I’m not sure what changing the wiring for the relay operating the remote will do. Does that mean that it will be “closing” the switch in the remote all the time except for a brief opening when HA triggers it? That doesn’t sound right to me. It should be a momentary press on the remote.
… time passes …
I see from using the Insteon Panel that the I/O Linc is set to “Momentary C” which I think I want.
Does the N/O or N/C just indicate what the I/O Linc will send back to HA depending on whether the sensor has continuity or not?
… time passes …
From the document again:
Momentary C
1) Set the sensor to the desired on state (meaning an ON command will not trigger the I/O Linc relay when the
sensor is in this state). For example, if you want an ON command to open the garage door and an OFF
command to close it, open the garage door in this step
I think I want to trigger the relay each time I click the HA UI. So it does that. It turns it on, and then it goes off (after a 2 second delay according the Insteon Panel). But the first “on” should open it, and the second “on” should close it. And I guess when it turns off after 2 seconds, it doesn’t re-trigger an OFF relay according to what that is saying, correct?
… time passes …
Nope, N/C for the relay is wrong. I could see that remote light continuously blinking. I don’t want that…
Normally closed/open refers to the power in the circuit. Normally open means the circuit is open or no power is making it to the other end. The magnetic switch can either be N/O or N/C some are both and have 3 connections.
The magnetic switch when the door is open sounds like it closes the circuit in your case meaning that when you move the unwired portion of the switch away it closes the circuit.
When the magnet is near, there is continuity (measured with a volt-ohmmeter). When it is not near, no continuity.
And when the door is closed, that is when the magnet is near. Yeah, it doesn’t make sense to me either. And I could swear that sometimes, the sensor state shown by HA is different at different times, but I haven’t been able to reproduce that behavior.
I do see that when the door finishes opening, the HA UI shows open for a moment and then it switches to closed.
Maybe I’m wrong, but I thought the I/O Linc only put out power when the 5V and GRD were connected to something. Otherwise, I just thought it was either sensing continuity (on GRD and Sense) or causing continuity (on N/O and COM).
Nope. I’ll go out and measure as it is operating. It does slam shut pretty hard. (that is how the professional adjusted in when he replaced the broken springs)
But when it goes OPEN, the magnet isn’t involved and that is when it goes from OPEN momentarily and then CLOSED.
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.”
