matapan

The kind of analysis I'm thinking of does not require the device to self report a failure. That would be nice, but the devices are not designed with this in mind yet. It is to look at communication event transactions to see if any fail, then pattern match on known problems or failures to pattern match. On an ISY, a diagnostic could take an event log at the most granular level as input for analysis. The idea would be to find pattern matches of communication events which fail because a response was not received.

With all the discussions around self driving and AI, doesn't it seem like there is enough of a knowledgebase developed now to identify Insteon issues as they occur? use cases: on demand - identify a problem adding a new device, communication issue between controller and device real time monitoring: looking for potential device failures - notify user/administrator of potential failure and provide steps for replacing device, including PLM What do you think? After all, we're on the precipice of robotaxi services becoming a reality. How hard can it be to capture all the collective knowledge amassed on these forums?

I want to write an automation script to notify me when my dryer load is completed. To do this, I think I'll need a plug for monitoring the load change on the dryer. Does anyone on this forum know a ZWave plug for this purpose that works with the ISY994? Or, if I'm barking up the wrong tree, is there a better way to accomplish this task?

Looking for three paddles, or two kits. Please PM me if you have any for sale. Thanks!

I’m looking for three Switchlinc paddle color change kits, part number 2400GY. Parts are no longer available from Insteon. Any chance anyone has a few to sell? : )

Can you using a 2413U USB PLM with a USB to serial converter in place of a 2413S Serial PLM with either an ISY994 or eisy?

Like any complex endeavor in life we individually or collectively engage in, keeping organized, well written documentation that is easily accessible is paramount. The documentation needs to be useful to its intended audience and address the central concerns one would have when placed in their role. With respect to an Insteon setup, inventorying the devices in the house with specific details like the hardware version and date code, along with the device relationships (like scenes) and references in programs can be useful to someone unfamiliar with the system. Documenting scenes and programs and what they do or how they function can also be useful to a new homeowner. All this could be stored in an online repository (think Google Drive or Microsoft’s equivalent) with a unique username only tied to the house. Keeping documentation like pdfs of user manuals in the repository can be helpful, especially if any external web source for that documentation were to suddenly disappear. It’s important to make it a habit to update the repository as things evolve with one’s HA setup to maintain the information’s accuracy and integrity. Documenting troubleshooting and maintenance steps in the repository, along with a main webpage for the repository can provide enough information for someone unfamiliar with the system, be it a new homeowner, electrician, or handyman to make educated guesses on any work they may have to perform on the system sometime in the future. when you sell a house you can give the new owner the keys to the repository and have some comfort you are not leaving the owner in the lurch. If the setup was professionally installed, all any professional Home Automation installation outfit worth their salt would provide that documentation as a badge of integrity. Unfortunately, sometimes it’s human nature to hold on to that information in attempt to lock in future business - maintenance. That’s fine if the company is there to provide the service and the owner is willing to pay for it, but often times companies go belly up or disappear or some owners aren’t willing to cough up the asking price for service or maintenance. After all, isn’t this why companies like Insteon exist in the first place, to cater to the DIY crowd in addition potentially to installers?

Perhaps someone with great hardware knowledge can answer this question: 1. What is the rated lifespan of Lutron branded switches? I personally have seen none fail in the 4-5 installations I've seen over 20 years. Personal anecdotes can't be used to generalize product reliability. 2. If the answer to #1 is a very long time, how are their switches engineered to last that long? 3. is the design of the Insteon switches inherently good, and the short lifespan of early assemblies due to low quality parts used in the switches? Or, is it more than that? In other words, will a really good set of electrolytic capacitors and contact switches make for a high quality, reliable switch? Just asking. I believe this is the question that every Insteon setup owner will be asking.

If you're asking how to future proof your install, consider this: 1. Are the Insteon devices failing of a certain age and version? Have the newer ones been more reliable for you? 2. After reviewing the landscape of alternatives available now, do you see anything promising that is worth the cost and effort of migrating? My take on existing technology and how it will be incorporated into some new and amorphous, yet to be fully designed standard and associated products is that the current product landscape outside of Insteon all have their own problems. I personally don't see anything that jumps out as being worthwhile to drop your Insteon investment. Unless you're investing in some pricey and closed system like Lutron, I don't see any system out there that is fully qualified and free of road bumps and road blocks. The current trend is to consolidate or aggregate disparate protocols under a single platform or application so that everyone plays nice with each other. I think the best way to future proof given this reality is to see which platform does the best job of aggregating the ecosystem of devices you have and plan to have. I don't own an eisy, but that seems to be the approach they are taking as well for future proofing.

Precision Logic in New York apparently carries it. precisionlogicinc.net.

I believe if you run the Airport Utility on your Macbook Pro, you can see your router and see all of its clients attached to it. You can look for the MAC address of your ISY to find its IP address and try manually adding it to the Launcher using the Add option.

Just curious for those who have purchased i3 devices. How well are they working? They look very nice. Pros, cons? Do you think they're better quality overall, including the longevity of the electronics? I know that's not a question that can be answered until they been around for a couple of years. But I was wondering if these devices have risen from the poor build quality pool and they are reasonably reliable. You can only hope....

I think the easiest way to get the correct lights is to set up a test bench where you can connect a keypadlinc to a plug and run the load to the cans for test. There aren't any standards for dimmers and led lights to be compatible with each other, unless the manufacturer specifically tested it with their product. Of course, that usually means you are dealing with a well known product like Lutron and some large lighting manufacturer that has the $$$ to test specific dimmers like Lutron with it.

Home Assistant seems to have a good model for this. If the update doesn't work, there appears to be a feature allowing rollbacks. I have no experience with that, as I have thankfully never had HA not comeback from an upgrade. But their model seems pretty sensible.

If you're concerned about the ramifications of using this node server, you can always use an IO Linc with your setup to generate the momentary contact necessary to open and close the gargage door, then use a door sensor to monitor if the garage door is open or not. I have a magnetic contact sensor mounted on the floor of my garage and the other component mounted to the door. Use a program to trigger the necessary contact to open and close the door and monitor the state of the sensor. This works pretty well.