larryllix

I have found "away" and "vacation" to be different functions, completely. For Away I don't shut down my HRV ventilation or set my heating or humidifier back. They take many days to recover. Away runs off of 12 MSes and a few other components like SwitchLincs etc that can only be operated by humans inside the house. The Home / Away countdown timer stops during sleep hours and continuous in the morning. Each MS resets the timer to a different number of minutes remaining. Setting the ISY based security system from a KPL as a combo keypad, cancels the timer. I run my Vacation variable off my ecobee thermostats as the stats have detailed timers and preset-ability for future dates. Vacation runs more security home lighting faking etc.. and sets HVAC parameters back to save energy money. I gave up on automatic Vacation mode as I would get home the next day or two and the HVAC would be set back and we we sleep in a cold house for the night. Infloor slab heating is like that and can take days to get back to normal. YMMV.

Yeah. I am not sure I want a car that runs on 6216 pc. 16850, size A lithium cells. One of the nastiest chemicals on the planet, so far.

I use the Kumoapp server to directly inject my Tag values. It requires no extra hardware and is easy.

Thanks. That is what I did eventually, after trying to copy, rename programs, and re-update/edit every line. Perhaps I thought a Save failed before. MY ISY is now so busy with constant battery device writes and there doesn't seem to be a way out of it since it keeps turning itself back on and the scene modifying hits on the battery device now every program line. It would be nice to see this battery write dilemma/logical error fixed.

@Chris Jahn@Michel Kohanim New error for me during v5.3.0 save of a new program. I never found a way out and had to refresh my programs losing many edits. Hasn't done it since.

The internal zip file is too large to unzip. Use a better unzipper like 7-zip that can handle the size.

Unfortunately a two wire dimmer should be easy to manufacture with a small loading resistor and a larger power supply capacitor inside the dimmer, but most manufacturers do not do it. I guess the cost of a $1 capacitor and a $0.10 resistor is prohibitive in this money squeaking industry. There are dummy loads that can be installed behind light fixtures on amazon. Search old posts here for links. They are more expensive than they should be though but with all the USULC etc.. approvals required these days?

IIRC it only works correctly when people were still installing incandescent bulbs and IIRC it was released as one of the early Insteon modules about ten years ago.

v5.2.0 is right for everybody. Beta does not mean unstable firmware. It means there may be some quirks in the device handlers for newer devices, like Zwave devices. If you would like to expand into Ethernet/WiFi devices using polyglot, or use decimal variables, you will need V5. Make a good backup before and after and you can always return to v4. The upgrade is free.

As I posted before, the DHCP table is not related. The size of the WiFi, SSID count, or number of router or access points is not related either. Only the size of the memory space in the one router containing the DHCP server is important. I found not all devices were listed in the "Connected devices" listing of the DHCP router and they would change total counts occasionally, as devices took turns having a connection and then failing. Usually it was devices that didn't affect me much. Until it was my ISY994 and my polisy once I didn't spend much time on it. Power cycling the house gave me different devices connected each time, depending on what devices booted up last.

Isn't that little arrow supposed to point at the sensor? I would think that would be the side of the open magnetic field (horseshoe magnet format) and you have it across the steel hinge.

This has come up before where two variables are compared. What you see is a rounded off value based on the NS programmer's algorithm which may not be the same value the ISY rounds off to. 2.99999999 is not 3.00000000 The < should have worked though.

As per @garybixlerabove but take the time condition out of the If section, and then you can either wait for the value to change, or run the If section manually to your hearts content, until you have it figured out. Then replace the time restraint condition.

Ahhhh....My guess is you have the magnet and sensor enclosed in an almost complete ferrous loop that bypasses the magnetic field and weakens the magnet's strength.. You could try mounting it a wooden board or aluminum plate to isolate it from all the steel and iron surrounding it.

The program can only ever run true when the ISY clock runs the program at exactly 1:37 PM. I am not sure how you are testing it. The 2.8 volts will alarm with the batteries about 50% left, in cold environments, and almost dead in warm environments.

Speed usually doesn't matter but filed strength of the magnet does. However if the magnetic field is barely string enough, the speed may cause a mechanical vibration inside the device, or if you create some mechanical shock the contact inside may be jarred loose enough to make it transfer. I have seen many contacts that will not close with a weak field but work when some mechanical shock is added in relay work over the years. Are you sure your magnetic gap is wide enough to make the device sense "Open/off"? @Brian H may be able to tell us what type of contact is inside these devices. I assume they are sealed reed type contacts. May be a manufacturing defect where something sticky (oil?) was inside the sealed glass envelope or on the contact making it sticky.

I would think we can conclude it is happening inside the modules and not ISY. Also freezing and/or ice inside is not an issue. Possibly some rain got inside? But both is a snag in that logic. Can you test with another external magnet? Possibly the magnetic strength is too weak or too large of a gap? Have you tried wiggling the device (physical shock) after the first close, and it fails to update, to see if the contacts have some stickiness to them? Some devices have 3v AA lithium batteries. If you replaced them with a 1.5V AA battery, it could do strange things.

Did this happen in the warmer months also?

How many devices do you have connected to your router? Not just WiFi but your whole LAN count of devices? My ASUS AC68u (about 5 years old) would not handle more than about 52 devices. No errors, no complaints from the router. When I was running WRT-?? OEM firmware on that router the count allowance was even less. It threw NVRAM shortage errors for a long time once I crossed about the 45 device mark, but I didn't understand why and their suggestions were not helpful. It turned out they upgraded that model's NVRAM from 64MB to 128MB and I got an old model on sale. Three years of anguish was not worth a few bucks. Don't be confused by the range of the IP address table. It is not related. My problematic router could distribute 510 IP addresses easily, but couldn't actually remember that many. When you reboot all the devices compete for an IP address via the DHCP server. When mine finally disallowed my ISY994 and polyisy fro getting IP addresses while in the Caribbean, I wasn't too happy with it, and bought another $600 in routers in order to sleuth the problem and look for a fix. ISY was attempting to send out commands using a 0.0.0.0 address in the logs.

Did you know the admin console has a search engine to find anything by Variable name, program name etc?.... Right click on any program name and select "Search and Replace" option on the pulldown menu.

The Stop at the end of a section is useless anyway. Without Stop at the end of each section the program was going to end anyway.

A scene with 0% will not do it, as you are turning the switch Off which will turn any scene off also. A scene with Closet Light On as an output will not work as it would also turn on the closet light with the main room light turn on. You will have to use a program and no scene(s). What is the problem with a 1 second delay to turn the closet light off? An On delay can definitely be annoying but what is the problem with a slight Off delay due to Insteon comm delays?

I wondered about that combo colour also. I agree it sounds like a hardware problem now. Likely software colours are mixed up with hardware colours as well as two traces shorted together where the cut was made, or a connector doesn't line up with the traces on the LED strip. RGBW strips have at least 5 traces to connect to while RGB only has four traces to connect to. They cannot be interchanged. Things are not always solderless, just plug and play, in this world.

ISY is a self-triggering event driven language. When you manipulate an element's status within a program you usually suffer a repetitive oscillation in the program when the same program's "If" section detects the change. "Stop" only stops the current execution but the If section retriggers it and it starts again. You may have trouble getting control of your ISY if you run this program.

Welcome to the UDI forums!! I have a few dozen of these strips and many of them have different wiring. First when cut the opposite end has the wiring reversed. The ends of the LED strip may be marked RGBWC for Red, Green,Blue,White, and Common. First you need to find the common conductor on the strip and wire it to the C on the controller. Then turn on one colour only and touch the wires from each LED contact to it until the colour matches the selected colour. Repeat until all proper colours are wired.