larryllix

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.

Read this thread from the beginning but.... The Hue bulbs need a hub as a bridge between Etherenet and whatever the Hue protocol is. The ISY can use the Network resource module to access the Hub/Bridge. Start building resources to send URL codes out. See the previous post two back for sample screen shots. IIRC Polyglot has Hue support built into it for the RPi.

Very easily done. Create a program say "IamHome" and disable it so that no triggers in the ISY If section can trigger it. In the Then section that Alexa will cal on default to with the spoken "On", use a program line to call program (If) IamHome.2 In another proram "IamHome.2" disable it also, so no ISY triggers can trigger it. Set a condition time frame in the If section for your time frame you want bracketted. In the Then section turn on all the devices you want during that time frame. In the Else section turn on all the devices you want outside of the time frame. Go to ISY.io.com and enable voice control of the first program "IamHome" You will have to say "Alexa. Turn on I am home"

Examine ISY logs and compare with your SMS/email notification times. I have seen texts come in hours later and emails come the next day, in some cases. If texts take more than an hour or so they are sometimes dumped and never delivered.

I had some trouble also. IIRC mine showed I was linked to a registered account but it was linked to the wrong email account. Details are fuzzy at this point, but I installed the opposite end's email address....ie. ISY instead of Amazon or vice versa.

I has seemed to get slower as I use it...not sure, but right now I would say variable response times. I vocally use almost all ISY programs, no scenes, and a few single lights/devices. I'll keep an eye on it for speed and see if I notice a pattern. The not understand and then did it anyway happenned twice, IIRC.

Not enough plosive sounds? I had a few instances where Alexa reports she doesn't understand but still turns on/off the lights. I have only used "turn on" and turn off" so far. They seem to work about 99% of the time.

What would the vapour barrier be doing there? In colder climates, we use vapour barrier to keep the interior moisture out of the insulation so it can't freeze, and nullify the insulation properties, conducting heat out. Injected solid foam insulation doesn't require a vapour barrier to protect it from condensation. An outer membrane just under brick or siding to allow the moisture out of the insulation and framing but not allow water into the framing.

The Mycroft project should attract a few with it's stated "open source" claim. time will only tell how this pans out and "open source" is NOT just another trade mark. These companies go into these projects gung-ho and usually come out with their tails between their legs, as the task can be much bigger than they bargained for, and the job (competitive products) doesn't stand still. Many find by the time they get out a competitive product, it is now obsolete technology in the market. Very nice to see some competition for Echo. The intercom betweeen units is a nice feature.

Although Xathros has a black belt in ISY logic, I like to add an all-else-fails timer to that logic. Pendants Override If Control 'Kitchen / Kitchen Pendants' is switched On And Control 'Kitchen / Kitchen Pendants' is not switched Off Then Disable Program 'Pendants Timer' Wait 4 hours Run Program (else) Pendants Override Else Enable Program 'Pendants Timer'

My Tekmar stats have a programmable time out delay but default to two hours if a tap on the temperature up or down is done. My old HoneyWell non-WiFi stats did the same thing with a two hour default, non settable. I only use two setpoints per day on cooling so that would all day and not wanted to wait for the next setpoint. My $29 unit in my shop building waits until the next scheduled time point to fall out of temporary hold.