![homeseer forum insteon homeseer forum insteon](https://s3.manualzz.com/store/data/023111976_1-e4664f75e34fa3292b6f001a91a911dd.png)
I personally find Homeseer to be a nice bridge between all kinds of technologies and interfaces. Mike, looks like you will get the answers to all those how and why questions you posed (hopefully).Īs to the value added question, I may be able to answer that one. Old thread, but interesting to see this actually happening. Maybe it would be better if a third party were to take this on? I'm not saying there is no case to be made for an ISY plugin for Homeseer, but I think some of these things need to be analyzed before UDI can justify the development and support effort.
![homeseer forum insteon homeseer forum insteon](https://bithead942.files.wordpress.com/2014/06/3-way-wiring.jpg)
A direct ISY plugin might make this a little more direct but is it really worth the significant development and support effort from UDI as well as the added complexity to the end user of keeping the two systems in sync? There is perhaps some value in being able to trigger Homeseer events with Insteon triggers, but I think there is already a way to do that if you use the Elk M1 interface. If you have other triggers interfaced to Homeseer you can easily use an X10 transmission or an Elk M1 rule to facilitate Insteon operation. Putting Homeseer into the middle of either of these situations does not add any value. If you want to trigger from motion sensors, you can use X10 translation for X10 RF stuff or the existing Elk M1/ISY integration for hard wired detectors. how much of a pain is it going to be to re-sync the two system's device tables that often? How much editing of Homeseer scripts and events will have to happen each time you change devices around with your ISY? (or any other link management tool)Īlso what is the value added from having a Homeseer plugin? Once you have an ISY, you will want to put any scheduled or sunrise/sunset Insteon stuff directly into the ISY. I know I make changes to my Insteon environment at least once a week. Managing your environment with an ISY and then using an ISY plugin as the gateway from Homeseer to Insteon would likely solve those problems but would the cost of developing such a plugin be of sufficient benefit to UDI for it to be worth pursuing? Even if you and some others would purchase an ISY based on the availability of this plugin, how many other Homeseer/Insteon folks would be willing to do so?Īlso how would such an animal work? Homeseer maintains a device database that needs to be coordinated with the ISY device database. Homeseer does not want to provide a general tool for managing the Insteon environment and yet they let their plugin blunder around in the link tables of individual Insteon devices causing potential conflicts with whatever is used to manage the device to device link structure. I'm curious how you are currently managing your device to device links with Homeseer? Are you also using something like PowerHome? Are you trying to manually tap-tap manage them? I ask because I think this is the weak part of the current Homeseer plugin strategy. Is a Homeseer plugin for the ISY something that UDI would consider writing?