@haddood if that configuration worked in 0.110 I woudl first try and restart you Hub. The likely scenario is that the local connection to the Hub froze and HA cannot connect to it. If that does not work let me know but it should work.
@teharris1 ā upgraded to 111 and removed my insteon2 customcomponent, but only a handful of insteon devices were found after rebooting. I tried insteon.load_all_link_database for all devices, but it had no effect. There are a couple log messages related to my thermostats which were found, but nothing else of interest. Do i need to clear out a database or cache after the upgrade?
further color ā my insteon_devices.json is full of devices from the insteon2 customcomponent days and those entities are still in my config, reported as ārestoredā:
Hi, I did it today and no more config errors but only one light (the only light) was added to HA, 5 switchās and a cover didnāt appears.
I did a load_add_link and nothing.
I erased the database and restart HA and nothing.
I try to link as a new device and nothing.
I donāt think it was clear until the last few posts that insteon2 is now insteon. Thanks. For those of us that are new to this, it was hard to follow along. It might be good to update the readme on the github repo.
@bob_banks I just posted an update to HA to fix the X10 sending messages issue. It should be merged into HA in the next few days.
@teharris1, I did recycle the power of the hub multiple times, and restarting HASS after, with no luck. I can log in locally to the hub, Alexa Insteon skill working all the time ā¦
Any suggestions?, is there logs somewhere I can check?
update:
I found that this error happens before the forementioned errors
Logger: pyinsteon.protocol.http_reader_writer
Source: __main__.py:356
First occurred: 12:27:24 PM (1 occurrences)
Last logged: 12:27:24 PM
An aiohttp timeout error occured during test connection.
Thank you! As @elitemike mentioned, I to was confused on the config side as ha website said to use insteon and github docs said to use insteon2. Also saw no mention of the code being included in HA builds on the HA releases until the .111 release notes that mention thermostat updatesā¦ Someone confusing for a n00b like myself. In the end, config on website works after reboot. I got the switch responding and now to start linking the rest.
Is there any way to keep the modem in linking mode? It seems to pair 1 switch and then stop blinking. I have dozens to link and this is going to be a chore taking the computer around everywhere.
Unfortunately no way to keep the modem in linking mode.
I realize the code today cannot do that, but perhaps a future āfeatureā. I know the ISY-944 does do this. Perhaps, it has the software re-engage linking mode after device is linked until user pushes button? Or have another developer service to disable the linking loop?
Resolved ā thanks for the feedback. Turned out everything was functioning, but I had ādisabledā the insteon entities a couple months back when i enabled the insteon2 customcomponent. On startup, all of the insteon entities were already found and linkedā¦ just disabled and hidden from view (except for the few i added new while we were testing).
Alls good so far. Upgrade complete, entities all renamed to match my rules and lovelace configsā¦ Iāll wrap this BETA update as successfully transitioned to the release candidate. If i have any issues, Iāll start a new thread in the community or post out to github for you.
No need to walk around. Just use insteon-terminal using the command āenterLinkingModeExtendedā. It is little bit of work I just prep by building/preparing my commands in a text document and paste them into insteon-terminal
Check out https://groups.google.com/forum/#!topic/insteon-terminal/d2NdJhDXnhg. There are a few other postings in the same group as well
2020-06-18 09:11:47 ERROR (MainThread) [homeassistant.setup] Setup failed for insteon: Unable to import component: No module named 'custom_components.insteon2'
The beta went well for me but now it seems i cannot get rid of insteon2. I am using latest HA 111.3 on a Pi4 on a SSD using Raspbian Supervised install. I have restored comfiguration.yaml to say insteon not insteon2 and have moved ā¦/custom_components/insteon2 to insteon2.saved. The error message is above. Any hints welcome.
I would try 2 things:
- Make sure your
configuration.yamlfile does not still contain a reference toinsteon2 - Remove the
insteon2.savedfolder all together from thecustom_componentsfolder. (Or rename thecustom_componentsfolder if you have no other custom components.)
Did 1 and 2. No insteon2 in configuration.yaml. Moved insteon2.saved directory to my home directory. And IT WORKED!!. Now all I have to do is fix up configuration. Your item 2 was the cure but I have no idea why. Thanks, Wes
update: insteon Hub 2
most of the time insteon ends up being unavailable. with the following errors in the log
2020-06-23 05:59:29 ERROR (MainThread) [pyinsteon.protocol.http_reader_writer] An aiohttp timeout error occured during test connection.
2020-06-23 05:59:29 ERROR (MainThread) [homeassistant.components.insteon] Could not connect to Insteon modem
2020-06-23 05:59:29 ERROR (MainThread) [homeassistant.setup] Setup failed for insteon: Integration failed to initialize.
if I strip down my setup, removing integrations for HASS to start faster, it works again.
when I upgrade or reinstall, it works for couple of times then these errors start happening again
is there a way to increase the time limit for
[pyinsteon.protocol.http_reader_writer] An aiohttp timeout error occured during test connection.
?
anybody else having this issue ?
How many other integrations do you have? It is possible that the other integrations are taking time slices causing the Insteon integration to time out.
Iām also having the same issue;
I was previously having some intermittent issues with connection to the Insteon Modem (2245), but always fixed by a reboot. Things looked OK initially after installing 0.111, but stopped working for unknown reason a few days later. Now it always fails.
2020-06-23 06:41:18 ERROR (MainThread) [pyinsteon.protocol.http_reader_writer] An aiohttp timeout error occured during test connection.
2020-06-23 06:41:18 ERROR (MainThread) [homeassistant.components.insteon] Could not connect to Insteon modem
I did try disabling another broken integration, and now, the insteon one works. Not sure what exactly is going on.