Please forgive the newbee nature of this question: Just starting into HA Rpi with the 2413U PLM. Been running HomeSeer for like 15 years. I’ve got the PLM detected and now trying to figure out how get HA to be aware of my (30 or so) Insteon devices. Here’s where my screen sits now. Hoping you can let me know how to get to where you are in this video and/or point me in the right direction for HA/Insteon/Rpi tutorials (Haven’t been able to find a forum subcategory for us yet. Thanks!
I’m also just starting and wanting to migrate from HomeSeer!
Normally it take a hour or 2 after you first get it loaded to scan your hardwired devices in. Did anything show up? If nothing is scanned in make sure you have the port write and check your logs for any errors. It should read the DB on the PLM and scan the devices and bring them in.
For now i have been using Mark’s insteon Plugin for HomeSeer to program my PLM and devices then plug the PLM into HA for controling. First time i plug it in i had a few issues and had to look into the logs only to find i had the wrong port. Then after that i had a device that the plugin didn’t know and it would cause the discovery to stop.
@teharris1 - I see this didn’t make into the next release (2021.06) Is there a way we can merge this into our own local copy. I see how to do it to the with the API pull request, I just don’t understand how to merge on the frontend pull request?
If you can follow the instructions to set up a frontend dev environment I would be happy to help load my code into it. But I will say, setting up a frontend dev environment is not for the faint of heart.
Frontend development | Home Assistant Developer Docs (home-assistant.io)
Very interested… following.
Great news! One of the two pull requests has been merged into Dev. Now we just need the second PR to get reviewed. Halfway there.
I’m excited for this - thanks for your continued work!
I have been everyday refreshing the Pull Requests and watching the drama. I can’t wait for this and to say good bye to HomeSeer. Now if we could get detached load support on KPL in a future update i would be in heaven.
Is there still a chance this could be in the August releases if it gets approved?
I don’t think so. I believe the August release candidate has been set. I could be wrong but I don’t think so.
Wow I feel like they are giving this update the cold shoulder!
I didn’t see this in 2021.9 either. Any estimate on when it might make it in?
So it doesn’t look like the HomeAssistant Admins seem to want to review and get this change in and even made a comment on if this should be part of the core. You can read the comments about the change and make up your mind but I feel they are unfairly making a grave misjustice towards all the hard work teharris1 has made
After reading the PR, it sounds to me like they are just busy.
No sure but should this be checked by teharris??
Yeah i gave them the benefit of the doubt on that but then i check that persons activity log and they have been approving other PRs and making code changes since they posed that and was on go live video chat for the September HA release and still hasn’t gotten back to teharris. There were alot of other PR that have been reviewed while this has been skipped over since April.
There are 2 things going on here… The 1st is that they are very busy for sure as there are a limited number of people that do work on the front end versus the back end. The 2nd is an architectural question of whether they want every component to have their own control panel for component specific configuration. This is a very valid and important question since insteon represents the 1st component to post this type of change that isn’t contributed by one of the moderators.
I have started to work on an alternative front end while the architecture question is being thought through.
I personally feel it would be better and easier for Is the front end to develop a generic config option similar to what has been done for the installation of integrations. This would mean developers would not have to put in their own front end work but rather would do everything in the back end and the user would get a consistent experience across all integrations.
another set back it appears here is the comments on the PR which was closed:
balloob commented yesterday
I think that it’s better to not move forward with the insteon panel. Insteon is used by 0.2% of the users, Home Assistant Analytics, and it’s not an official integration or open home automation standard.
This code can still be made available to users via a custom integration registering a custom panel, similar to how the Supervisor panel works.
That’s too bad. This looked very interesting and I was waiting for it to become available.