ErikN

Thanks for the ideas. I switched out the PLM and the issue has gone away. Soooo.... could be the PLM failed (caps were replaced not that long ago but who knows) or perhaps that one was more susceptible to power line noise. I will have to experiment to see if any recent holiday plug-ins are causing an issue. Thanks for the tips to help track it down. Erik N

Hi I am running current releases of IoP with just Insteon (no PG2 or 3 modules etc.) I am looking at the event viewer and ever second to two it says it is receiving a status message, reads as follows over and over non-stop: Wed 12/14/2022 09:50:39 PM : [X10-RX ] 02 52 FF 80 Wed 12/14/2022 09:50:39 PM : [ X10] J/Status = off (2) Wed 12/14/2022 09:50:40 PM : [X10-RX ] 02 52 FF 80 Wed 12/14/2022 09:50:40 PM : [ X10] J/Status = off (2) Wed 12/14/2022 09:50:42 PM : [X10-RX ] 02 52 FF 80 Wed 12/14/2022 09:50:42 PM : [ X10] J/Status = off (2) Wed 12/14/2022 09:50:43 PM : [X10-RX ] 02 52 FF 80 I don't seem to have any devices with ID 02 52 FF 80 so not sure where this could be coming from unless it's a failed device. If I understand correctly, this is X10 traffic but I have no X10 devices plugged in (I have 2 but unplugged them to eliminate them as source if this). Anyone have any thoughts on this? If it's a failed device and suggestions on how to track down which device? Thanks ErikN

@Michel Kohanim thanks for posting a quick summary of the current priorities. For the record I never complained about lack of information but it is helpful to have a peek at the big picture, and I think we all recognize that priorities can change and evolve as can timelines. One thing regarding the focus on having the future configuration interface being via the App, my only concern with that is whether there will continue to be a desktop web interface option, as having to type everything out via an app on my ipad can be a bit of a pain at times. I know, it seems like one can't win for trying since I get that the current desktop interface relies on Java and that has its own challenges etc. But thanks for listening. New eisy loos nice (although I loved the blue Polisy colour too) and will probably migrate to that sometime next year (that FOMO thing I previously mentioned). Personally I would probably go with a short USB extension to plug in the ZMatter/ Zwave card/box so I can mount it separately and less risk of being bumped and wrecking a the port. Erik

Thank you Techman. I was a little slow to migrate to Polisy (which I did earlier this year) because for a while I didn't really understand what it was all about in comparison to ISY, and I also didn't want to jump on the bleeding edge right away either. That said I do tend to like to have latest(ish) and greatest(ish) when it makes sense so I am interesting in learning more about eisy and will probably jump on board at some point.

For the record, I am NOT bitter at all and I can see how not wanting to say much about future plans helps to avoid people being upset if those plans don't work out. I love the ISY platform and believe Polisy was move in right direction to provide support for other protocols and broader devices. I find some of the implementation slightly confusing but I think that's just 'cause it's relatively new to me. Was just surprised because it was not that long ago that I migrated from ISY994 to Polisy but I can understand if there were challenges getting stock for the platform (too bad since it looks really nice). I have no concerns as long as Polisy platform will continue to be well supported and I don't have to move to yet another platform in the short term (or medium term for that matter, since return on investment is a consideration). I'll have to read more to understand what specific improvements it will have over Polisy -- see how much FOMO may set in

Sorry, joining this discussion very late. I am confused as I thought Polisy was the future. So what is the purpose of EISY? Why would one chose one over the other? (apologies if this has been answered already and I didn't see it when I scanned through this thread)

Thank you everyone this has been very helpful. Erik

Hi folks. I have been watching with interest the developments around Polisy for the last few years. At first I didn't quite understand it but I think I do now but hoping for some clarification and advice. I have a basic ISY994 that has served we well for some time. Almost all INSTEON devices plus a couple very old X10. It is interfaced with an iPhone based remote control system (roomieremote.com) and the two generally work well together. However, with the decline in availability and range of INSTEON devices available, I am looking at expanding into using Z-Wave+ (and maybe more?). This leads me to consider, whether I should upgrade / replace the ISY994 with an ISY994i ZW PRO to provide more capacity and Z-Wave capability, or for a few (well a little more than a few) dollars more make the bigger jump to Polisys with the ZW dongle, which it sounds like is evolving quickly and of course there's always some bugs to but mostly ready for mainstream use now. Just to clarify, in addition to running on a much more powerful UNIX based platform and the capability to add node interfaces to a virtually limitless array of other devices, it is my understanding that Polisys also hosts essentially the same event/device/node-based programmable application with essentially the same interface that runs on the ISY994, and I can basically import a backup of devices, scenes, scripts, network resources, etc. from my existing ISY (or I can re-develop them manually). So I can basically start by replacing my existing ISY994 and port over pretty much everything as is, and then from there expand and start looking at ways to use the new Polisys functionality. Is my understanding correct? Is there anything critical on the ISY that won't port over or won't work at all in this ISY on Polisys environment? The existing ISY994 API / REST interface that my remote control software uses to collect the manifest of devices and to send commands, control devices, run scripts, and receive device status updates, does that still work the same and use the same command string formats? Would you recommend making the jump to Polisys +ZW now, or perhaps just getting the ISY994i ZW+ PRO for now, and consider Polisys once it settles in even further? I am an old-school software developer but have been out of that business for many years and don't have time to join the effort to develop additional node interfaces etc. so I would be paying the full price for Polisys so there is a cost differential between them. Any clarifications or advice would be much appreciated. Erik

Anyone know if there are any plans to support some kind of basic text/string variables? Would be nice for example to set a variable contacting IP/Mac address for devices called using the network module.

Help! I just purchased an ISY-99i/IR (with the PLM + 1 access point) plus 3 Insteon dimmer devices. I am a long-time X10 user, and looking forward to migrating over to Insteon and greater control with the ISY. I am having some difficulties though: I had no trouble linking and controlling 2 dimmer devices (2476DH and2486D) with the ISY, but have not been able to link the 3rd dimmer (2476D). The automatic linking that worked easily for the first 2 devices did not work at all for the 3rd (no error, nothing) so I tried the manual linking it (i.e. "New INSTEON device") and entering the address, but get back an error "Failed writing the Highwater mark" and "Node not added - failed removing links". The event log contains a message ""Failed getting engine version, reverting to i1", not sure if that is relevant. I have tried moving the ISY/PLM to another location. What is really odd is that all 3 dimmer devices are located side by side in the same electrical gang box, and 2 work but 1 doesn't, so it seems hard to believe that there is an interference problem. I even switched the problem dimmer with one that is working and it still doesn't work with the other device still works fine. I tried a factory reset on the device, but did not help. The LEDs seem to indicate that it is going into controller linking mode rather than linking as a responder when I hold down the button to link. Note that it works fine as a stand-alone dimmer but won't link to the ISY. Could this dimmer be faulty? On an unrelated note: How do I unlink a device from the ISY? According to Insteon device doc, to unlink I need to put the controller into unlinking mode, but can't figure out how to do that in the ISY console. Thanks for any help Erik