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).
Shake the door? Is wind possibly causing the mag switch to disconnect.
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.
Are you using one of these on your garage door?
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).
Not sure why I didn’t turn it up before when I searched, but just now I see someone else with what sounds like the same problems.
https://community.home-assistant.io/t/reverse-garage-door-cover-insteon/414113/3
This is a normally open magnetic sensor
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…
Thanks anyway.
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.
If getting the other type of mag sensor is not something you want to do, you could make another sensor that is the reverse of it.
template:
- binary_sensor:
- name: "Garage Door"
state: >
{{ is_state('binary_sensor.name_goes_here', 'off') }} ## Use other garage door sensor here
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.
FYI. This is the code I can’t get to run in my configuration.yaml file. It looks like a nice solution if I could get it to run.
You need to install the custom button card first
type: custom:button-card
entity: switch.adaptive_lighting_home
tap_action:
action: toggle
state:
- color: 'rgb(255, 5, 5)'
icon: 'mdi:garage-open'
name: Garage Door<br>Open
value: 'on'
- color: 'rgb(5, 255, 5)'
icon: 'mdi:garage'
name: Garage Door<br>Closed
value: 'off'
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.”
Follow the install instructions on GitHub - custom-cards/button-card: ❇️ Lovelace button-card for home assistant
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.