paulbates

Having used most insteon switches for many years, and i3 for over a year, I really like i3. Coms are great and they blend in visually versus stick out and drawing attention. A couple of gotchas that can be navigated around via awareness is that to implement them, each switch has 2 'nodes'. One is the traditional settings and one is advanced i3 paddles settings. This gotcha is that there are some of ones like 'disable wireless'. A few of mine came from the factory with that set The advanced node, also called flags, do not get updated when using restore device

I would download and reinstall Java, then reinstall the launcher

Can the installer tell you what brand/model the panel is? Can also go to the panel, see if you can find brand/model info on the cover, stickers or the main board behind the door. You could search the internet for its pdf manual and look through it. I had a panel at my last house and did that. It did have dry contacts capability. If your panel does have that ability, you might be able to talk your installer into enabling it, or maybe there's YouTubes out there describing how to do what you want. You could research and decide it you want to get your screwdriver out.... I ended up installing SimpliSafe, and it sent emails based on alarm status. I used gmail to make filters for those emails and update my ISY via IFTTT. A little clunky, but it worked

ADT's approach is to be the central controller to Home Automation and integrate a with google home and Amazon Alexa and zwave. ADT uses 4 different brands of panels, including their own brand. Knowing which one you have is part of the answer. If your panel has dry contacts capability, there's the possibility of connect it to an Insteon, zwave or zigbee io interface. Integrating with an alarm panel can be technical and specific to the panel you have. It would be best to talk to the alarm installer and ask them what's possible with a dry contacts controller.

If the client is present when "the scrape" is going on, tell them to expect random beeps from everywhere there is an Insteon device

I was going to ask which model of Venstar CT do you have, there are models with and without a humidistat

Double check the directions in the link I posted above. It's not necessary to clear the java cache unless there are specific symptoms. You can log on locally when you're there, or via the manual remote link you create per the directions when you're away. When remote, iox will use the portal as a proxy to initiate conversation with the eisy. Even though it's the same iox login screen, you have to use your udi portal credentials when remote. It took me a couple of times initially to get that right

You can run iox remotely by having a UDI Portal account. It provides a link that that can be used on a remote iox instance. Note the instructions on which login credentials to use

Advanced Insteon tasks need to be done in iox on java capable pc, etc

When you add an Insteon device from the linking menu, one you know the Insteon ID of like a wall switch or plugin module, there's and option to have it not delete existing links, and use the links table of that device as input to find the others. You'll need to spend time after it's done cleaning up and naming things as it can't know what function it is e.g "Kitchen Table". You'll have to turn on on the devices it's discovered to see what goes with what. It takes a long time so go get a coffee (or beer ) A couple of assumptions The "buried" devices are all linked to other devices that are being searched by this iox feature, so that they can be found The buried and other old devices weren't used in X10 mode that some older Insteon devices supported. The devices aren't dead This should get you most of the way there and point to what devices weren't found by virtue of you not being able to turn them on or off with the device table that is built from this feature. I tried this when I first moved to the ISY with about 30 devices and resultant list of devices looked like a mess and some of the scenes where hard to figure... but as I renamed devices to functional, meaningful names, it got closer to making sense, Some scenes didn't make sense and I deleted and rebuilt what i needed

Is the thermostat indicating correctly? The little water drop icon on the top icon bar will turn from blue to orange when the stat is calling for humidity. Same for the water valve on the humidifier, is going on and off in sync with the light and values from the stat? There's also a setting for humidity on demand, do you get that behavior on both heat calls and humidity calls?

Variable substitution, I believe it works in NRs too: https://wiki.universal-devices.com/ISY-994i_Series:EMail_and_Networking_Substitution_Variables

Once you create a scene in the ISY, you turn the scene on and off, not the device. This includes iox programs.But if you turn any one of the devices on at the switch, they'll all go on and off

A suggestion is to put all 3 switches in a scene as controllers. The switches will handle the required action for you and there will be not delay, and no program will be needed.

The node/plug-in environment, pg3x is the platform on which the yolink plug-in runs on. I believe that's policy/eisy only As stated above, some yolink devices say Ifttt compatible, which says it's plausible to run it on the isy. I would message yolink tech support and ask specifically about this device, Ifttt and how does Ifttt work with it. I have found them timely and meaningful in their help

I use yolink on eISY with the plugin. The integration is really good. I know, all things considered, it's a bad time to suggest upgrading to an eisy, but the integration is there. I haven't seen the mousetrap yet, but other Yolink products integrate with Alexa google home. Some of their products claim IFTTT integration, and I assume that the Yolink hub is the integration point for that. Yolink's support is very good, you could contact them.

Another option in yosmart / yolink. One of their features is reliable, long range (1/4 mile) communications. There's a great, well supported plugin for eisy. I use yolink temp/humid sensors in my fridges/freezers and also control venting for our master bath. I use a plug in module to monitor our dryer and turn on the fan when its on. I also use their smoke/co sensors tied to virtualarm.com monitoring. The also have switches and outlets, depending on what you're controlling as @Guy Lavoie asked Yolink is neither expensive or difficult to set up, maintain. It complements an ISY/Insteon where it does things like this better, yet still run by iox programs on the same eisy

There's some things to think about with multiple PLMs and eISYs: Insteon devices need to be on one or the other, but not both eISYs The 2 PLMs won't be aware of each other, the chance of traffic collisions will go up If you have Home Automation functions that will cross the 2 eISYs, it's a bit technical to get them to talk. The way I know how to do it is Network Resources that set a variable in the other eISY. Possible, but debugging can get tricky. It might be possible to solve the Insteon communications problems directly. Can you describe the buildings at a high level, how big, what they're made of and how far apart? I had a detached garage at my last house and I had a 2 band device like an appliance module plugged in on the house side of the garage that was in signal range of switchlincs in the house... I need that because I had iolincs in the garage that were single band. Maybe the same would work here.

A long time friend and mentor have me this phrase: Price, Quality, Time.... Pick 2. My ~ 10 years with UDI days it the first 2, and not many (non self inducted) problems as a result.

Do you use DHCP to assign IP addresses to devices?

You can manually enter a url that incudes the IP address of the policy into the ISY finder. Can you give that a try? Is there a chance that the IP address of the policy and eisy are identical? Depending how you use DHCP, eg router assigned IP to a MAC address, that could be one explanation.

There are a few moving parts and I think it's down to one of these: The switch is old and losing functionality.. how old is the switch? turn on the event viewer level 3 and double tap the switch, does iox have a record of that? The mechanical part of the switch could have failed due to frequent, vigorous double tapping. If yes to the above, something happened in iox. Does the program turn green when the double tap occurs? It would help to post the program If none of the above, probably something happened between eisy and homeseer and its plugin. Has it ever worked with eisy?

I forget and leave it open. The main thing I've seen, with both ISY and eisy, on different computers at 2 houses is: clicking the mouse causes the old windows to "blong" sound, with no visual change in the interface. Other times some things will work and some won't... then I remember... 🤪😂

The Admin Console/iox is not designed to be left running 24x7. It's the java app on the computer that freezes, not the ISY/eisy. Different users have different experiences with how long the AC/iox runs before freezing.

Let's start with the basics: Where is your PLM plugged in, to the EISY? Sometimes Insteon devices get "confused" after long periods (years) of use. If your PLM is connected to the EISY, Factory reset the 2477D Pull out the tab, wait a few seconds Press in all the way and hold until it beeps Restore old settings from EISY: Right click on the device Pick "Restore device" Retest If that doesn't help, then the PLM might be in question