apostolakisl

If you have a program referencing a program, or an outside network resource referencing a program and you delete the program, you get an orphan reference. The reference is not to a program name, but to a program ID slot. This allows you to name the program anything you want and later change the name without breaking the references. But if you delete a program, have an orphan reference, and then create a new program that then picks up that same ID, then it will now reference the new program. I have no idea how ISY picks what ID slot to put a new program in, I have tested adding new programs and they do not add to the end, they seem to pick up some random unused slot that presumably was an old deleted program's ID. Basically, it is the same thing as if you just changed the program and never deleted it. ISY ID's all programs in a sequential fashion using hex numbering. The ID is in the far right column of the program summary page. This ID is what you use when setting up an outside network resource calling the program. Also, if you delete a program and don't hit "save changes", the program will not actually be deleted even if though it will vanish from the tree, only to reappear when you next load the ISY admin console. This is a bad design issue that I don't know why UD doesn't fix and is related to the way they use Java. Should you delete a program that is the target of another ISY program, that program will now say "Not Specified" in the program where the name used to be. You can search for any orphan program links by searching the raw text "Not Specified" in your programs folder to hunt those down. While ISY admin console will always substitute the program ID with its given name, any reference to the program via the network (outside of ISY) will reference the ID only.

Could you have a network resource outside of Isy sending a runThen to Isy? As Javi mentioned, looks like that. It is very easy to search all your programs for any reference to this program to rule out a runThen origination from another isy program, but not so easy if it is from something like ifttt. There is a"find" function in Isy to search all rograms for any reference to that program. I forget exactly, but if you leave the event viewer open and set to level 3, i believe it will tell you the source of the trigger. In addition, you don't need a variable to trigger the program, just have whatever sets the variable instead directly trigger the program.

Good to hear. What you have designed is loaded with powerful features, but when it comes to just turning on a light, too many features get in the way. Need a dumbed down gui and an advanced gui. Most of the other guys out there just have a dumbed down gui appealing to the mass market I suppose.

Not sure if this has been discussed. But is there any plan to make UD mobile more intuitive on the GUI? It's fine for me, but it confuses most folks. Basically, can a light switch present as a light switch looking thing or a thermostat look like a thermostat?

Aha! I was just trying to figure this out and here it is. Thanks.

My personal experience is that an air compressor makes it very easy to remove components without damaging anything. I tape off the board with painters tape, then melt the solder with my iron and hit it with a pop from my air compressor and the solder goes flying leaving a perfectly clean hole with the wire lead loosely sitting in the hole. Super fast and easy. Just be aware of where the solder is flying so you don't short out something elsewhere on the board. Angle the air compressor gun such that your solder flies off onto the tape. If you do get some over spray on the board, it easily is removed with a fingernail or wooden q-tip handle. The solder spray will not bond when it lands, but certainly could create a short. though I have never had a short happen. I have replaced quite a number of capacitors on Insteon devices over the years and can repair an entire unit it just a couple minutes start to finish. Also, leave the wire leads long on the new ones until after soldered in. Once soldered in, I just bend it around a few times and it snaps off right at the edge of the solder.

"Recertified" is unlikely to mean that anything was done but testing. The PLM's are easily opened and inspected. There is a good chance you will be able to tell if it was recapped, even if the soldering was done by a pro as there will be subtle differences. Also, some of the recommended replacement caps don't fit in the orientation originally designed. If I were you, I would go ahead and buy a new set of caps for it now. You might decide to just let well enough alone until it fails, but seeing as failures like this always happen at the most inconvenient time, you might just recap it now.

You can factory reset the PLM and you won't lose anything. ISY has a "restore plm" command which will write all the links to a blank plm. I do believe your plm is quite old. Has it been recapped? PLM's from that vintage are like clocks. At exactly 2 years of being powered on, they die. The issue is bad capacitors which most people diy repair.

I have the Leviton units as well. I did have a lightening strike fry my well pump, but I suspect that surge did not go through the electric panel but rather directly through the Earth to the pump. Nothing else on that circuit was damaged and the pump is 3 phase. There is a single phase to 3 phase variable frequency drive controller that converts the single phase to 3 phase. So the pump motor doesn't see line voltage at all.

Sorry to hear. Might consider a whole house surge suppressor. I put one on each panel. I can't say if they work since it is hard to know what didn't happen that would have happened. Knock on wood, in 12 years, I have not had anything that I could blame on a surge. Easy to tell if the device is dual band. Just go to your ISY admin console main page and click on your root folder in the left tree and it will tell you what each device is and the firmware. The 20% thing sound like the triac is faulty, but I don't know. My failed devices (caps) wouldn't boot up or took a really long time to boot up. Also they would buzz and be erratic. Can't ever recall a device that would only ramp up part way.

I would say that maybe I had 10 of those dimmers fail and maybe had 6 or 7 come back to normal operation by replacing the caps.

Those old dimmers I had failures. The newer dual band ones I have never had a failure that I can recall. I decommissioned my entire single band setup years ago and replaced it with all dual band. I was able to fix a number of those older ones by replacing the capacitors. But I don't recall ever having one behave like you are describing. To open the switches, however, you have to drill out the rivet on the heat sink. When re-assembling, you need to have a rivet set.

You can open ISY Tools/Diagnostics/Event Viewer and set it to level 3. This will show all communications that ISY sees on the network. You have to have it open, though, it will not show you what happened before you opened it. So I would turn it on this evening around 9pm and see what you get.

I don't know about "no plm" firmware. But you can just run ISY with a plm then "delete plm" and it will no longer run in safe mode. This does not erase the plm, it just removes it from ISY. So you can just "borrow" your PLM from polisy then return it when done. I used a super old ISY 99i as the IR relay since it is otherwise useless. See my post on how to make an old ISY into a IR relay using network resources.

Not sure I can use this without some changes. I got my Tesla and then immediately went on vacation. I left the car with 90% charge but did not have it plugged in. About 10 days into my vacation I thought to see how my Tesla was doing. the battery was at 35%! It was losing roughly 5% per day just sitting there. I shut off the node server, and over the next 10 days it might have lost 1 or 2% more. In short, the node server seems to keep the car in a state of energy sucking that is pretty significant.

Odds are very high that, as mentioned, you just need to completely clear java. Just type " configure java" in your windows search box and the first choice should be just that. In the first window that opens, you'll see "temporary internet files", click on "settings" in that section. Then in the box that opens, click "delete files", in that box, check all 3 options, then click "ok". Now click on this link https://isy.universal-devices.com/start.jnlp to download the ISY launcher. It will install an icon on your desktop for future access. The first time you run it, it will open straight up. It should find your ISY. If it doesn't find you ISY, then something is up with your network. But you can still enter the IP manually and it should work unless you have it fire-walled. For example, I have to enter the IP manually when I am running over my VPN connection, but otherwise, it comes up on its own. If you do have to enter it manually for whatever reason, it will remember it the next time, so unless your ISY changes address, you are set. Downside is every time you do a windows update, soon to follow you will need to do a java update. At which point, you have to repeat the process. I'm not a fan of java, but once you realize what needs to be done, it isn't but 20 seconds or so.

@stevehoytThat smart splitter looks easy, but for $500 I think I could do it for free. I already have CAI webcontrol boards which I can hook up to my AC units to know when they are running and I can do that in the attic. At that point, assuming the node server can tell the car to charge or pause charging, I just need to write a program on ISY. I haven't seen the node server working yet since it seems as though I actually have to have the car before the nodes will install. So, I'm not 100% that the node server can start/stop charging. Can you confirm that the node server can do that?

Thanks for the info. Directly in front of my parking spot at the office are my AC units. When I bought the space, I re-did the AC and went from 4 units to 3 units. So I already have a 50 amp circuit just sitting there doing nothing. I don't actually drive that many miles. My current car is a CTS-V, is 11 year old and only has 65,000 miles on it. We have largely used my wife's car for the bulk of driving, but perhaps that will change after I get this car. Back in the day I thought 558 hp was impressive. Now it is 1000+hp or I'm going home. Anyway, I have always loved the wolf in sheep clothing car. . . the 4 day family sedan that kicks ***. Probably talking about a few bucks/month, but whatever, I have to charge it somewhere and being a HA junkie, I just want to do it. The cost of the car itself dwarfs the cost of the electricity, so it is kind of joke, but again, whatever. Basically, I just need the node server to give me control of the charging. To tell the car to start and stop charging. Not sure if you have to keep the car awake to do that. Doesn't seem like keeping the computers in the car on should have much power draw, but what do I know, I don't yet own it.

It would only matter on command, not response. The max kw is based on a running 15 minute average, so even if there were a short delay of something under a minute, it would not likely affect the 15 minute running average much. I need to figure out the best method for getting the trigger data into ISY. It is 3 phase and Sense, which I use at home, doesn't do 3 phase. So I need to figure out a different way. Right off, I know I could use a webcontrol board and just monitor the AC units with that and only charge when they are idle. Though I might never charge the car the way this summer is going.

My new Tesla is finally arriving next week after a 6 month wait. This is my first Tesla. I was looking at charging at the office where I am on a kw + kwh billing system. In other words, your worst 15 minutes of wattage during the month determines about 2/3 of the bill and kwh is only ~5c each. So, my thought was, to only let the Tesla charge when my wattage was low so it only cost me 5 cents/kwh and doesn't bump up my high watt level. It sounds like this node could help. Basically, I would like to tell the car to charge whenever certain conditions are met. Either I monitor my overall power usage, or just monitor the big draw items, like AC units, and only charge when they are idle. Anyone have thoughts on this?

I may be wrong on this. I swear it used to be that true/false status of a program would only trigger another program when it changes status. But I just checked in a very old 3.3.10 ISY firmware and it triggers every time regardless of whether the status changed or stayed the same. @larryllix

Yes, I just tested this and you are correct. Something has changed, a program used to only be a trigger upon changing status, now it is a trigger every time it runs regardless of if it changes. I just recently switched over to IoP and will need to look over my programs. I have had a few things happen that I wasn't sure why they happened and this might be a reason. But also, what Mr. Bill said. That fixes the problem and also solves hysteresis issues which very well may happen.

Mr. Bill addressed this as I would have. No need for a Boolean state variable ever because it just mirrors the state of the program and functions identically as a trigger for any program that references it. In your second post it looks like you stated you "couldn't do that". But you are mistaken. My guess is you need to put some hysteresis in there. Trouble likely is that temp is bouncing around. 79.9, 87.0, 79.9 etc. Each time it does that it will get you a new notification. Program 1 If temp is >=87 Then disable program 1 Else blank Program 2 If temp is < 79.5 Then enable program 1 Program 3 If program 1 is true Then do what you want Probably should do a "run at startup" on 1 and 2 as well. EDIT: After looking at this a second, I realized you don't need program 3. You can put your notification into program 1 then clause prior to the disable line.

If you restore from ISY and you still have incorrect behavior, that is a dead giveaway. Detecting orphan links is much more difficult since they don't create bad behavior, but they do take up space. Orphan links require a very good knowledge of how to read the links table. You could take a random sampling of devices, record their links, then delete/reinstall the devices and see if you get the same set of links.

Factory reset/restore PLM will make the PLM links the same as ISY's internal database. So bad links will only exist on the PLM if they exist in ISY, which can happen. The only way to get rid of bad links in ISY is to delete the devices that have bad links. This means starting over from scratch on those devices, need to manually put them back into programs and scenes.