I have a Universal Devices EISY with it’s PLM and want to slowly migrate to HA. I purchased another PLM and connected it to the HA. What is best practice for the addition of the Insteon HA Service to ensure that the PLM’s are seen as distinct and separate? In my first pass, I think that they were conflicting. Has anyone gone through this process without any conflicts?
A lot of people might not know what you are talking about. (Like me)…
A few more details and fewer TLA’s might be helpful. How to help us help you - or How to ask a good question
Sir_Goodenough
This is asked of people who understand the question…
It is for users of Universal Devices Integration and who have Insteon.
I personally dropped Insteon years ago, preferring Zwave, but I understand the question.
I recently migrated from eisy to ha. What worked best was a single cutover… move the existing fully operational PLM to ha insteon integration, let the insteon integration discover your insteon network and deal with functional automation conversions one at a time.
There are some device linking capabilities that the ha insteon integration can control, but not as good at setting up from scratch as eisy/994i are
Thanks.
I got the PLM connected, and one switch is attached to the Insteon service. However, the system does not recognize that it is a switch - it says “the device has no entries” under the Controls section. I am not sure how to add the controls to it so it knows that it is a switch.
SOLVED: → I deleted the device, and then added it through the Insteon code xx.xx.xx and it read the device and it knows it is a switch!