larryllix

Try a restore on each of the two devices. Perhaps a link has been lost in one.

2441ZTH was never shown in the pulldown devices list in ISY. i\I have two and both show the correct type after reading the device type and version. Both have different features that work and neither have all the controls work. Even some of the program lines do not work with them. eg. temperature increment/decrement sends nothing.

Factory reset and make sure it is complete then link it again. IIRC ISY does not have a definition for the 2441ZTH and will link to it as a 2441TH only. I have one that is controllable and one that isn't, different firwmares. Both will report temperature changes when it happens only and both report humidity on a heartbeat continuous basis.

Just remember in the summer you may pay twice for the wasted heat too. You pay to create the bulb and dimmer heat, and you pay again to take it out with A/C.

I have everything in my LAN pegged down with a static IP address dictated by my router. Guests are the only devices that get dynamic assignment. Each person's devices gets blocks of ten number groupings just to keep it easy to figure out who is doing what. Printers and common things get different ranges etc. Every device uses DHCP and the router reigns supreme.

Yup. Four buttons can produce 4x4x4x4x4x4 = 4096 combinations, if all combos use six key pushes. I settled on four and three keystroke combinations to operate things, though. My KPL is right over my inverters so it is not 100% reliable, all the time, taking a second try at the combo, when low light conditions put the inverters in the low load and noisy synthesizing mode. Less keystrokes makes it more reliable. http://forum.universal-devices.com/topic/16135-using-keypad-triggers-for-a-multiple-combination-locks/?hl=combination

We decided years ago, after a few scrapes, GD frame repairs and body jobs to never back into our garage again. When we built our new house the Chief Inspector said over my plans, "No, you aren't using the standard 8' wide doors, you aren't getting any younger". Best advise I ever got going 9' wide. Yeah you have to drive in forward. Mount it on the door but the cord would be a problem. These days with LEDs and MS built in batteries should last years.

I have a 6 key KPL. The major buttons act as a light control for the room. The four small buttons indicate garage door open, lights on upstairs, lights on downstairs. The four small buttons also act as a combination lock with multiple codes for security, as well as turning my washing machine, or well pump back on after a water leak is detected. Each function with a different four key sequence.

As a test I have a potlamp (not a grow op) over my desk that flashes every time a setpoint change is made on my thermostat to prove my stat programs are working correctly. If you have ISY v5.xx firmware you can stuff the temperature into a variable each time it changes. If you really want to find out you can assign 5-10 sequential variables to the task, and shift them all down one and shove the latest temperature into the top variable each time the temperature changes. Then you will have a record of the last 5-10 temperature changes for your examination. It's your ISY, your variables, and your time,,,play with it and have fun. costs nothing. If InsteonStat temp <9999 Then var10 = var9 var9 = var8 var7 - ..... ..... var2 = var1 var1 = InsteonStat Temp Else --

...and each button could still be used to acknowledge alarms or other related activities, like lighting scenes around each door that is indicated and labelled on each LED.

I haven't installed Polyglot so I can't say a real comparison but I feel sorry for newbies attempting to tackle anything on a RPi. I know this. I worked on a Unix work alike in the 80s for many years, writing my own drivers for FDD, HDDs, integer compilers, and many other pieces of software, but the Linux thing on the RPi is the worse piece of confusion I have ever seen. The documentation is not only bad, much of it is wrong and misleading. 90% of the software doesn't work due to incompatibilities with different versions of OSes, or implementations. Software and system code writers enjoy making things as cryptic as possible with no rhyme or reason for names given to app and utilities, Instructions are given out as a bunch of mumbo jumbo with no explanation of what any of it means. Standards are lacking, unless one considers having 30 different standards as a standard. It's a mess and most of it isn't even compatible with itself. Sure it will settle down into a few but it will most likely settle into another completely different base that will win out and obsolete the whole thing based on thinking the Rpi was cheap to start with but I can buy a bare CPU for $10 too, much cheaper. Don't get me wrong. I love the concept, and own two RPis, but without some real instructional documents most people are just going to be lost and scared off. My bet is 90% of RPis have not been powered them on within the last month and sit on a shelf or junkbox somewhere..

I haven't had any problem with my kpl. They do have some complex options that can be difficult to understand. Get an 8 key kpl though.

Oh geeesh! I hope the R on the shift lever isn't thought to stand for 'Race'. My wife went to jog the car up in the garage once and depressed the gas peddle trying to unhook her shoe from under the brake peddle. Luckily she stopped just before the freezer door in our 29 foot deep garage. If I would have known that it would have been built 32 feet deep. 'Gas peddle' should be have been referred to as 'acceleration request reostat'

I had one of those for awhile and my kids would bat it around the garage when the garage door was up. I had to take it out after l my tires were low, one time, and I my wife couldn't get past the front of the car. As far as I know she might still be there. Actually I moved and the darn thing couldn't track us. Then the LED missile guidance system took over.

A body man told me they have at least one vehicle with a damaged rear hatchback per week from garage doors coming down on the door after getting the groceries out. I use the LED laser markers for my garage. When the red dot just enters the windshield onto to dash I have 1 inch clearance behind my vehicle for the garage door to shut. Since my last unit I purchased was a dual unit and I already had one for my second bay, I used the two beams for "just in far enough" and "far enough to get the groceries out of the back, but still get past the front". You pick which LED occurrence you want when you drive into the garage. The beams are only defined to protect small children and toys from being crushed, not vehicles. I have raised mine to protect the side opening back door though. Not recommended in the mfg. instructions though. A crosshatch grid of beams would be good and somebody mentioned one here, quite some time back.

Yeah. See post #56 for the embedded Hue program lines, my style. http://forum.universal-devices.com/topic/19199-nodelink-support-for-milight-led-controllers/page-3 Note the colour is set with a Interger variable I use as constants, denoted by the $cXXXX. I define all my colours so I don't ever have to look up codes.

In certain Network Resources, I use {"on":true, "bri":${var.1.69}, "sat":${var.1.71}, "hue":${var.1.70}, "transitiontime":40} see the "transitiontime":40 ? That will make all your colour and level changes ramp and fade slower so that multiple bulb changes all look like they happen at the same time. The variable substitutions allow me to have only one "Hue Bulb Set Network Resource" that does everything, for each bulb, except Offs. Then you have to set the three variables to whatever colour, brightness, and saturation before each NR call. Once UDI makes the variable substitution buffering time an option (in V5), there will only need to be one Network Resource to set all bulbs to anything you want.

Take the "/" characters out of the IP address. Is that the IP address of your Hue Hub? The rightmost box should look formatted something like this "/api/isy994user/groups/0/action" for general setting action I use. A field sample from my same Resource looks like this (for format style) {"on":true, "bri":${var.1.69}, "sat":${var.1.71}, "hue":${var.1.70}, "transitiontime":40} I am not sure your final parameter should have delimiters around it. '"' Make sure you save everytime you open a resource, edited or not. Click the test button on the page.

Yeah, I just realised that when the Hue scene came up. I never use Hue scenes as I have ISY and can totally manipulate it easily. Thanks for the nudge though. Need to specify which one in Hue conversations for sure.

Looks correct AFAICT

Careful as "Program" is used to mean and ISY program here. You create "Network Resource". See post 18 and copy it, except to substitute in your own Hue hub IP address, and some numbers for the variable substitutions I used. The ones that look like this ${var,1,xx}. After you can make the bulb do something, start playing with different numbers. ALWAYS HIT SAVE!!!

Variables are 32 bit signed values. v5 also have a decimal precision parameter to indicate where the fixed decimal falls. I use MMDDhhmmss for some time stanps. With v5 seconds since midnite is a built in ISY parameter. Here I just used the seconds parameter from v5 ISY. http://forum.universal-devices.com/topic/17366-v5-tracking-fan-cycle-runtime/

Scenes are only an Insteon idea and done inside Insteon devices. Isy helps manage them, set them up, and control them. My non-Insten devices are all controlled in programs calling Network Resources to spit out Ethernet codes as just another inline program line in an ISY program. When everything has a nice 1-2 second ramp time differences are not noticed.

No. A Network resource send one line of command code out through your Ethernet connection from the ISY. Whatever the Hub can do with that command is what one Network resource can do

I have five Hue bulbs and these are the total Network resources I use to control them anything I want. Once ISY has the option to not cache parameters and evaluate them at resource call time these can be reduced to about four or maybe five for some convenient operations without setting up parameters. I make use of parameters for each call. Here is how I set up parameters for each call when dinning levels or special colours are needed. Colours.orange - [iD 00C6][Parent 00C5] If $sGathRm.colours is $cMOOD.ORANGE Then . $Hue.hue = $cHUE.ORANGE . $Hue.saturation = 254 . $Hue.brightness = 100 . Resource 'Hue.set(all)' Else - No Actions - (To add one, press 'Action') If you are not inclined to do a lot of program setup/learning the network resource method works well with complete control over every bulb, level, hue, and brightness.