apostolakisl

Thanks for the info. Looks like need to move positions 3,5, and 6 to 1, 7, and 8. My wires have different colors than the other post. I'll give it a try when I get home from work. EDIT: Still no luck. I am confident I have the wires moved correctly. I'll order the UD one and see if there is an issue with the console cable, but I just don't think there was.

This is the part that concerns me: If the panel was modified by an installation company, it may retain their custom codes even after a factory reset.

i can't even buy a usb plm right now, out of stock. I did check and indeed the Insteon box is checked. I think I will take my plm's to my church and plug it into the 994i there and confirm that ISY recognizes it before I waste a bunch of time. I guess the next step would to buy the rs232 adapter from UD, but I really don't think it is different.

I will probably end up going to ebay for a used 1832. Trouble is you have to make sure that it has the factory programming password or at least one that they know and tell you.

My eisy came today but I can't get it to connect to plm. My old plm got fried in the lightening strike but I have two spares and neither will connect. via SSH, eisy says the serial adapter is connected. The PLM's are old but I am pretty sure both of them work. I did factory resets on both of them and both do the normal factory reset sound. Ideas? I am using a USB to serial adapter that I already owned, I don't think it is any different than the one UD sells. I tried different ports and have rebooted and power cycled eisy as well as the plm multiple times. [admin@eisy ~]$ dmesg | grep -i usb xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0 usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 ugen0.1: <Intel XHCI root HUB> at usbus0 uhub0 on usbus0 uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Root mount waiting for: usbus0 CAM ugen0.2: <FTDI USB Serial Converter> at usbus0 ugen0.3: <vendor 0x8087 product 0x0026> at usbus0 uftdi0: <FTDI USB Serial Converter, class 0/0, rev 2.00/6.00, addr 1> on usbus0 ubt0: <vendor 0x8087 product 0x0026, class 224/1, rev 2.01/0.02, addr 2> on usbus0 [admin@eisy ~]$ Eisy says

Eisy comes today. I'll open it up and see if it uses the same msata drives. If so, I'll try putting the polisy one in and see what happens. Unless someone thinks it could somehow harm the eisy. And more fried stuff being found. Of course my plm is dead. But a curious one, I have a whole house sound system with 6 controllers that are hard wired back to the main unit. One of the controllers is dead. The rest of the system is working normally. That one controller is in a j-box containing a 2476d switch that is also dead. The j-box is a split jbox, so the low voltage side is decisively separate from the Insteon swtich side. Other Insteon switches controlling the same light and using the same hot wire are fine. How does this happen? To add the insult, the system I use is no longer made and I can't find any individual controllers on ebay. And my intercom system isn't made anymore and I can't find those on ebay, but I can't even figure out what is the faulty part(s).

Astonishing to me. Perhaps authorized installers are getting something to integrate with their own apps, I don't know. But this is infuriating. Everyone else is increasing interoperability and they just shut the whole thing down with their product. I had been using the eyezon unit for years with great success at my office with an 1832 and my church wanted to install an alarm on a new building, so, without thinking, I got a new DSC system since the older 1832 units are discontinued. Big mistake. Probably going to have to pull it all out. And that means all the zone expanders and keypads. The databus on the new is encrypted so nothing is cross compatible with the old system.

The DSC neo is a dead end. Don't buy it. No integration possible in the US. They encrypted the data bus and no one has the encryption but them and they provide zero remote monitoring/control of any sort in the US. Astonishing how they have moved backward 30 years with this.

I opened my polISY and found it has a baby SATA SSD, not an SD card. Not sure what I can plug that into. Perhaps eisy has the same and perhaps it will boot? And it isn't the power supply, I already tried that. Polisy is just dead, no noise, no lights, no nothing. The board has no physical evidence of any issues, don't have any idea what would be fried. Same thing with the two control boards I removed from two of my HVAC units. Both look normal. Replaced one of them already and got one of the two units functional again. So many issues to deal with. Hopefully Spectrum will get me my new modem today, it is also just flat out dead.

@IndyMike Thanks for all that info. Now I'm dealing with a dead polisy after a lightening strike. My eisy which I ordered before the strike is coming tomorrow. I seem to have neglected to make a recent backup of PG3, so now I have that headache as well.

Had what I believe to be a direct strike to the house, though I don't see any physical damage, but we had a flash bang simultaneous and now boat loads of stuff is fried, including my polisy. Won't power up at all, and yes, I tried multiple power supplies, just nothing, no lights, no sounds. As coincidence would have it, I already planned on upgrading to eisy and it was already ordered (lucky I didn't order it a week earlier). Anyway, I have recent backups of ISY, but my backups of PG3 aren't so new. Was wondering if I opened polisy, is there an sd card that perhaps would boot on eisy to get backups? Or other solutions? FYI, list of known "fried" Mind you, I had whole house surge suppressors on every panel and a lot of this stuff was on a UPS. Two of 3 HVAC units have fried circuit boards (one unit had outdoor circuit board die and another had indoor unit, so I was able to swap parts and get one of the two back online while waiting for parts). Elk M1G Elk XEP ? rest of Elk boards, can't test them Spectrum modem Pool Lights Several Insteon Switches (one of my outdoor switches was behind a popped gfci and when I reset it, the Insteon device literally had something explode inside. likely a cap) Luba lawn mower power supply PS5 Intercom System Many wall warts A couple of Security cameras Netgear switch GFCI Outlet Landscape lighting transformer . . .Still finding things Fortunately, all PC's survived as did my Ubiquiti stuff (Dream machine, switches, and several wifi AP's). Not sure if this is good design by ubiquiti or dumb luck. EDIT: Opened it up. See nothing physically wrong. I see that it has a small solid state SATA drive. Perhaps this can be plugged into eisy? Or something else?

You don't need parenthesis at all for this. There is no functional difference between either of the two options you showed as well as no parenthesis at all. Mostly you would use parenthesis when you have two sets of conditions not connected by the same and/or. ie. (1 and 2 and 3) or (4 and 5) (1 or 2 or 3) and (4 or 5) the following are all functionally identical (1 and 2 and 3) (1 and 2) and 3 1 and (2 and 3) 1 and 2 and 3 (1 and 3) and 2

I don't think you are mistaken.

Is there anyway to view programs in a backup without restoring the backup to an ISY unit? I deleted a whole series of programs about a year ago and want them back now. Restoring that backup, however would get rid of a bunch of changes I want. I suppose I could make a backup, restore the old one, copy the programs and the restore the backup I just made. However, I really don't want to do that. Seems like more opportunities for things to go wrong.

So it is odd that anything related to your network would be the issue, like the router booting up after the eisy. Connecting to the peripheral devices would go through the network. and that worked. Yet ISY doesn't connect to PG even thought they are both on the same machine, seems like networking shouldn't be needed. Perhaps all the com protocols still go through the network since originally PG was designed to be on a stand alone device (rpi).

It was not checked. But wouldn't it be better for it to poll the status of programs (or whatever) that are currently displayed? In this case, I need to set it to poll all my programs every time for something I only need 1 percent of the time.

@Javi Suggestion: I read through the instructions linked to the advanced config via the question mark bubble, and it didn't mention that setting this up is tied to the node, not the favorite. I think that is worth putting in there. I would consider that to be something you might want to put as the first note about setting up advanced config since someone might easily see that and just stop before wasting any more time if they only want it to apply to that favorite. EDIT: One more issue, on a different favorite, I am using advanced config to display the status of a program (true idle/true false). But it doesn't seem to poll the value, it only shows it after it changes. Otherwise, blank.

OK, the same name error message appears on all the fan speeds, fyi. And the radio buttons are working great now. thx. Fixed my pool fountain buttons as well.

@JaviUsing the blank space works to make it not show the word "on", but it still shows the word "off"

@Javi One issue, when the fan is off, and the "fan off" favorite icon is turned red, the button reports "on" when the fan is off. The button name is "fan off", so it literally says "fan off on" (over two lines), or "fan off off" when the fan isn't off. It isn't the end of the world, but it is a bit screwy. My goal here is to just work like a KPL. No need for words on/off, just the color change is all that is needed, much like a KPL tells you what is going on by backlighting the one button. In short, it would be nice to set a "display node" that actually doesn't display anything, but rather just gets you access to setting the advanced status configuration. I have this same issue with some of pool controls showing confusing or useless info in the display section when all I really want is to be able to set the favorite icon color. EDIT: Also, why does it say "UD-Mobile-Name-Error" in the display status section?

Well, there was an easy fix. I just set it to track the status of the corresponding KPL button which I already have working correctly via programs and Insteon scenes. So each favorite display node is the corresponding KPL button and when the KPL button is on, the advanced config turns it red. I see also that everywhere that node appears now also turns red when on, consistent with what you said.

Not wanting a bunch of colors, just two. Here is what I want to happen: 4 button: off, low, med, high Whichever one is the current state, is red, the others are blue. If the fan is off, the variable is 0 and the "off" button is red, the other 3 are blue. If I hit the "high" button, the variable changes to 6, the "off" button turns blue, the "high" button turns red. And so on with the other two buttons. Just your basic radio button type configuration. Same way the KPL controlling the fan only lights the button that is currently active. It works if I use 4 different variables, but things are already so cluttered. But I guess you are saying that advanced configuration is tied to that node and there is only one possible advanced config per node, you can't have advanced config on the same display node behave differently for different favorites . . . end of story?

I am configuring favorites with buttons on my phone with each speed of a fan. I am tracking the fan status using a variable through a link to Alexa since there is no ISY node for this fan. - I have 4 buttons in UD Mobile, one for Low, med, high, and off - I want the button that represents the current state of the fan to be a different color - The tracking variable is set to 0,2,4,6 for the various states of the fan. The issue is that when I set a custom color for one button at one variable value, the other 3 buttons configuration changes to match. I can't use the same variable at different values to make different buttons change color at different values. This is on Android. I tried closing the app and re-opening. No change. Is this a bug or just something that is going to be this way?

This is not fully working like I had hoped. Alexa can fully control the fan and can recognize what state the fan is in from the fan controller screen. However, when using the fan status as a trigger in a routine, there is only "on" and "off". So I can't synchronize back to ISY the current state of the fan aside from "off" and "on", or in other, speed zero, and some speed that isn't zero. So I guess I am left with just telling ISY that the fan is on high when Alexa reports "on".

This fan uses a tuya controller. It has its own app and it links to Alexa for full control through Alexa. It has 6 speeds, but I am happy to simplify that to 0,2,4,6. Or in other words, off, low, med, high. I am using a keypad link to control it. I have full control of it using network resources from ISY sent to Alexa and that is working fine. But, I would like ISY to know the status of the fan if it is set from the handheld remote it came with. Alexa sees the fan speed settings when set by the remote and I was able to have Alexa set a variable to 0,2,4,6 on ISY. So, I can do it this way, but I would rather streamline this to get rid of the webhooks and have it all synchronize via the variable. Life would be easier if someone wrote a Tuya node. I believe they have a public api. Tuya.com I wish I had the time to learn how to write nodes, but I just can't take on another hobby.