@teharris1 – thinking about upgrading to 111, but I also plan to continue beta testing for your upcoming releases assuming you want some help there. Am i setting myself up for a lot of pain having to rename entitiess jumping back and forth between the merged production version and your custom component?
Perhaps i’ll just stay in custom land unless you advise a better way for testing…
I really appreciate all the help with testing and the offer to help further. The issue is that config flows cannot be in custom components so there is no way to test that outside of the core module. After that, I will be focused on frontend work which is also not something that can be tested using a custom component so the only way to help test is to set up a development environment, which is definitely not easy. (https://developers.home-assistant.io/docs/frontend/development)
Hello! i tested the custom component and now i’m trying to use the official one but when i change the configuration HA keeps calling the custom component in a kind of conflict cos can’t set it up.
HA says the component is “insteon” but is calling the Insteon2 files and init.py
What can be? any thought?
2020-06-13 10:07:40 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for insteon which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
| arch | armv7l |
|---|---|
| chassis | embedded |
| dev | false |
| docker | true |
| docker_version | 19.03.8 |
| hassio | true |
| host_os | HassOS 4.10 |
| installation_type | Home Assistant |
| os_name | Linux |
| os_version | 4.19.126-v7 |
| python_version | 3.7.7 |
| supervisor | 227 |
| timezone | America/Bogota |
| version | 0.111.1 |
| virtualenv | false |
insteon:
port: /dev/ttyUSB0
Hello new to HA, been trying to setup my insteon devices with no luck, tried the built in component and maybe everything was mostly right, all my insteon switches and stuff showed up as entities but none of them showed up as devices. Now maybe i needed to do the device over ride list thing, i didnt try that instead i decided to give the insteon2 beta a test. However i have not been able to get it to install i followed the instructions and have tried multiple times but it never seems to install the insteon2 component.
2020-06-13 14:08:38 ERROR (MainThread) [homeassistant.setup] Setup failed for insteon2: Integration not found.
Im running hassio on the raspberry pi 4, downloaded the 32 bit image from HA…
Any help would be great… and any help I can provide let me know…
just a side not under the current built in insteon component my 6 button and 8 button keypads were registering the opposite, and i even did a factory reset on the keypad and reprogrammed it in, but all of my 6 buttons create entities for an 8 button, and my 8 button creates entities for the 6 button. And again this was all with the original insteon component, cant get the new beta version installed.
@avgJoe the Insteon component does not create devices yet. That is the next change that is coming. If all your devices showed up as entities then it appears to be working. You should not try to use the insteon2 custom component. It was for test purposes only.
@Alfonsolsl Did you remove the insteon2 folder from the custom_components folder?
@bob_banks it is up to you if you want to setup automations now or after the config flow change that will introduce insteon devices. If you want to be able to see your automations associated to the devices the hold off but if your automations are few and/or simple there is no harm to doing it now. Any automations you setup now will still work later you just won’t be able to look at the device and see what automations are associated with it.
@avgjoe can you send me the category and subcategory of the KeyPadLinc devices you are using? Did you ever change the faceplates on those devices? Are they dimmers or switches?
@ teharris1 So I currently have 4 keypads installed, installed many years ago… I don’t know which one but I’m pretty sure I did change one of them from a 6 to an 8 or vice versa, or possibly even swapped a 6 and an 8??? I really don’t remember off hand its been many years. I have one keypad that’s not a dimmer, just an on off, and its in the 6 button configuration, that leaves 2 dimmer 6 buttons and 1 dimmer 8 button.
6 button dimmer
“cat”: 1, “subcat”: 66
“cat”: 1, “subcat”: 65
6 button On/Off
“cat”: 2, “subcat”: 44
8 button dimmer
cat": 1, “subcat”: 66
Also i think i found my problem with insteon2 not installing, i misspelled custom_components folder… but i deleted that out and just went back to orginal since everything was working there…
I am confused with what we should be using right now. I am running 111 and I could not get anything to work unless I added your repo to my custom_components folder.
I should mention that at this point I haven’t yet entered anything myself… The cat and sub cat numbers I got from the insteon_devices.json file… I was about to go into to the configuration.yaml and start entering device override information to see if then the switches show up as devices not just entities…From my understanding the insteon_devices.json is the data that what was pulled off of the PLM listing its links and stuff…
So ok after going back to the original insteon component I’m a bit confused… How do I get my switches and keypads and what not to show up as devices in HA? I see them as entities, but cant use those in automation. Also I tried to create a device over ride list in the configuration.yaml but that didn’t seem to make a difference… Not only do they not show up as devices in HA but also the 6 keypad I switched to an 8 and the 8 to the 6 still report incorrectly under entities even after changing their cat and sub cats in the device overirde list…
device_override:
- address: 32fc9d
cat: 0x01
subcat: 0x41
- address: 2bfd96
cat: 0x01
subcat: 0x42
First, thank you @teharris1, it is an incredible jump in speed for insteon and hass.
I am facing an issue, I can’t get inseton to work any more on 0.111.2 , I get
Logger: homeassistant.setup
Source: setup.py:212
First occurred: 7:41:28 AM (1 occurrences)
Last logged: 7:41:28 AM
Setup failed for insteon: Integration failed to initialize.
and
Logger: homeassistant.components.insteon
Source: components/insteon/__init__.py:121
Integration: insteon (documentation, issues)
First occurred: 7:41:23 AM (1 occurrences)
Last logged: 7:41:23 AM
Could not connect to Insteon modem
My config entry is:
insteon:
host: !secret insteon_lan
ip_port: 25105
hub_version: 2
username: !secret insteon_user
password: !secret insteon_pass
this same exact config worked on 0.110 !!!
second is there any chance that this will support morning link locks? look at this if you have a minute
@avgJoe The .111 release doesn’t include devices. Just entities. Those will be coming in a future release. If you want to use automations now, use the “Call Service” action with “light” or “switch” service and select the entity from the drop-down.
@teharris1 I may be the last one on the planet but I still have X10 device in play. Are they functional at the moment? I tried adding to configuration but not go. Via logging, I do see data being sent.
x10_devices:
# Curio Cabinet
- housecode: L
unitcode: 3
platform: "switch"
# Garage
- housecode: G
unitcode: 1
platform: "light"
2020-06-14 09:19:59 DEBUG (MainThread) [pyinsteon.topics] Topic: send.x10_send data: {'raw_x10': b'V', 'x10_flag': 0x00}
2020-06-14 09:19:59 DEBUG (MainThread) [pyinsteon.topics] Topic: send_message.x10_send data: {'msg': msg_id: 0x63, raw_x10: 0x56, x10_flag: 0x00, 'priority': 5}
2020-06-14 09:19:59 DEBUG (MainThread) [pyinsteon.topics] Topic: ack.x10_send data: {'raw_x10': 86, 'x10_flag': 0x00}
2020-06-14 09:19:59 DEBUG (MainThread) [pyinsteon.topics] Topic: send.x10_send data: {'raw_x10': b'\x05\x02', 'x10_flag': 0x80}
2020-06-14 09:19:59 DEBUG (MainThread) [pyinsteon.topics] Topic: send_message.x10_send data: {'msg': msg_id: 0x63, raw_x10: 0x0502, x10_flag: 0x80, 'priority': 5}
2020-06-14 09:20:07 DEBUG (MainThread) [pyinsteon.topics] Topic: send.x10_send data: {'raw_x10': b'V', 'x10_flag': 0x00}
2020-06-14 09:20:07 DEBUG (MainThread) [pyinsteon.topics] Topic: send_message.x10_send data: {'msg': msg_id: 0x63, raw_x10: 0x56, x10_flag: 0x00, 'priority': 5}
2020-06-14 09:20:07 DEBUG (MainThread) [pyinsteon.topics] Topic: ack.x10_send data: {'raw_x10': 86, 'x10_flag': 0x00}
2020-06-14 09:20:07 DEBUG (MainThread) [pyinsteon.topics] Topic: send.x10_send data: {'raw_x10': b'\x05\x02', 'x10_flag': 0x80}
2020-06-14 09:20:07 DEBUG (MainThread) [pyinsteon.topics] Topic: send_message.x10_send data: {'msg': msg_id: 0x63, raw_x10: 0x0502, x10_flag: 0x80, 'priority': 5}
2020-06-14 09:20:15 DEBUG (MainThread) [pyinsteon.topics] Topic: send.x10_send data: {'raw_x10': b'V', 'x10_flag': 0x00}
2020-06-14 09:20:15 DEBUG (MainThread) [pyinsteon.topics] Topic: send_message.x10_send data: {'msg': msg_id: 0x63, raw_x10: 0x56, x10_flag: 0x00, 'priority': 5}
2020-06-14 09:20:15 DEBUG (MainThread) [pyinsteon.topics] Topic: ack.x10_send data: {'raw_x10': 86, 'x10_flag': 0x00}
2020-06-14 09:20:15 DEBUG (MainThread) [pyinsteon.topics] Topic: send.x10_send data: {'raw_x10': b'\x05\x02', 'x10_flag': 0x80}
2020-06-14 09:20:15 DEBUG (MainThread) [pyinsteon.topics] Topic: send_message.x10_send data: {'msg': msg_id: 0x63, raw_x10: 0x0502, x10_flag: 0x80, 'priority': 5}
Thanks. Then I guess everything except my 2 keypads are working as it should… And I have to say the whole setup was much easier and quicker then the last time I tried HA about 1 -2 years ago. As for my keypads i’ll probably just switch them back to what they were when i got them and then physically swap their locations. I don’t remember why 10+ years ago I took a 6 button and made it and 8 and made an 8 into a 6, I probably didn’t want to have to switch out the physical switches or something, but I think that’s going to be easiest to get it to work right. Interestingly inside of the Universal Devices ISY program it treats the keypads correctly as either 6 or 8 button dimmer keypads but it also says that the 8 button is a 5 button and that the 6 button is an 8 button, so somehow it reports back to the PLM and to the ISY program that the keypad is an 8 button keypad being operated in the 6 button mode, and that the 6 button keypad is being operated in the 8 button configuration. So there must be some kind of second check or another data field or something…
Hi,
Are there instructions somewhere that I could use to install Insteon2. Tried searching add-on store and using links provided here to Github but not having any luck.
Thanks in advance!
@elitemike Not sure why the standard solution would not work. What does your configuration.yaml file look like when you try to run the standard solution?
@avgJoe This is what the insteon component will call your devices:
6 button dimmer
“cat”: 1, “subcat”: 66 => (0x042) 6 button dimmer
“cat”: 1, “subcat”: 65 => (0x041) 8 button dimmer
6 button On/Off
“cat”: 2, “subcat”: 44 => (0x2c) 6 button on/off
8 button dimmer
cat": 1, “subcat”: 66 = (0x42) 6 button dimmer
I have confirmed also that this is the same as 0.110 and prior. Not sure why they would be showing up different 0.111.
@brian_jankovich you should not need insteon2 since it is now the insteon component in 0.111. You can find information about how to install insteon here:
@Bob_Banks sending X10 commands has an issue at the moment. Receiving X10 commands should work. I have a fix coming in the next few days to address sending X10 commands.