larryllix

High tech stuff. When it works, it is great! When it doesn't, it sucks.

Typically you would create a program with a time trigger for each change of level desired. Out them all into a folder with an appropriate name and never have to look at them again.

Learn to read your Events Log where it tells you max hops and hops left. Unplug a dwvice and test again. One less hop left indicates a bypass happened. This won't indicate a parallel path if the counts do not change. Sent using Tapatalk

Yup! I was born before X10. I was born around the same time 60 Hz was.

Zwave devices are always in a state of flux. As long as the zwave devices tables are part of ISY firmware ISY v5. will always be considered beta. In 6.5 years, I have never heard of an ISY994 crashing it's firmware and I have run every version since late V3.x that my ISY came with.

No links can be adjusted in the MS, only settings in the responder(s). These MSes cannot be adjusted when not in the linking mode. UDI used a scene name that doesn't exist to differentiate between scene style controls. It was always a little weird but it works and makes scene adjustments available. I am not sure this will work properly using an MS II. If you link the MS II directly to a lamp the MS II will turn the lamp off as well, or if ON Only is selected, the MS II will never send another On trigger to restart the Wait statement until the MS II stops seeing motion for it's delay time, plus stops seeing motion for the length of it's Off time as well. Yeah, the MS II sucks. There may be a way to use this technique to just block the MS II and use both On and Off events sends.

I drive a 1960s car too. I don't need side mirrors or seat belts. Sent using Tapatalk

The first MS version was indoors only also. It didn't stop people from using it outdoors in protected environments though. @paulbates uses his MSes with some glue to seal the face, in northern US weather, protected from precipitation of course.

I use LEDenet RGBWW/CW controllers for my strips above cabinets. I don't use the CW output as the WW leds give off such a beautiful white colour, I like them everywhere. AFAIK these are completely compatible with MagicHome controllers except cheaper and 5 channel units. They take a 12vdc power supply to run the strips. For bulbs I use a Chinese knockoff that is 99 percent compatible with MagicHome. I wrote my own software to get around the differences and eliminate the popcorn effect of using 25 but I only paid about $8 per bulb fir them but the colours are not as strong as MiLight and some more expensive brands Sent using Tapatalk

My undercounter LED strips are not coloured, nor dimmable. I found a plug-in motion sensor and tucked it beside the fridge so it only shoots right down the counter. We have never touched a switch there in 12 years. You walk up and the counter lights up day or night. It's a dark corner far away from windows. Those LEDs probably cost me an extra 1 or 2 cents per year. Something like this..the original HA. https://www.amazon.ca/Télécommande-allumage-mouvement-intérieur-MLC4BC/dp/B009KSEE4G/ref=sr_1_6?dchild=1&keywords=plug+in+motion+sensor&qid=1594645067&sr=8-6 or better yet this https://www.amazon.ca/Westek-MLC12BC-4-Indoor-Activated-Control/dp/B009KSECO8/ref=sr_1_5?dchild=1&keywords=plug+in+motion+sensor&qid=1594645193&sr=8-5 Get the LED strips inside a silicone tube/sealed. You'll appreciate that when you try to wipe them down with a wet cloth.

Have a look here. If you install colour you will learn to like it. Just don;t install RGB equipment. Install RGBWW strips and 4 channel controllers. Likely cost you less than $50 for all equipment for up to 15.4 feet long. There are many compatible controllers but look for NS here that support MagicHome and other popular brands.

I use FileZilla Client to transfer files between polISY and Rpis and Win 10. It is updated frequently and works like a charm with many options. I don't know how to get files in or out of git-hub.

Insteon battery devices need to be in "linking mode" before they will allow any input to them. This is usually accomplished by holding a small button down for about 5 seconds until the device starts to blink slowly. After you program the device from the ISY admin console you tap the button a few time to take it out of linking mode again. Every device should be factory reset before linking to ISY, especially when new. That also involved that same button, and power cycling. Each device has it's own technique.

I can't remember all the details but IIRC you will need at least a wait of about 2-5 seconds or it can miss sometimes. @jfaiAlso it is not only the same routine trigger. Alexa will only allow a trigger every 30 seconds period. Now having said that this stuff is developing rapidly since I set these up and tested this. I found under 30 second hits may or may not work reliably at that time. I also noticed that leaving the variable value True caused some problems.(1-0-1) I think it had to be False for a few seconds before Alexa would clear it's allowance time???? and then your vocal would be delayed from the event. IIRC this was stated somewhere but I do not remember where...maybe the app?

@oberkc IIRC, we were originally told we had to only use a State variable to accomplish this. However maybe the emphasis was on "State" and not "variable". I cannot think of one application where I would want a raw sensing device to produce a spoken response, though. These inputs to Alexa routines are sensitive. If you do not observe the 30 second rule they will just ignore your requests. Programs and devices may not obey those rules nicely, and cause amazon to avoid talking. eg. If I created a routine using the status of my SynchroLinc on my dryer, it would attempt to say "The dryer has finished" every time my wife opened the dryer door. When loading the dryer with the door open, that would be a false statement. eg. When one garage door opens I report which door has opened. When one garage door is closed I report nothing unless they are both closed. That takes ISY logic, but I could use an additional program to trigger a vocal Routine, I suppose. Another thing that should be noted: Many times when amazon or ISY Portal makes an upgrade the connection between ISY Portal and amazon/GH can be broken. When you disable the account connection and re-enable the connection to re-synch devices, all your Alexa Routines will be forgotten as the trigger events did not exist for those few fleeting seconds. You must start from the beginning, rebuilding them again.

How did you manage to clear these write queues? My ISY is starting to display the busy box frequently again, and I have all delayed write programs deleted and battery write delay features all disabled. Last time, I had to factory reset my ISY before ISY events became very quick again as when ISY was new. AFAICT, with polyglot and a few other variable injectors going on ISY cannot seem to afford these extra CPU time or I/O burdens. I have had to add extra Wait times between NR sends again lately. Where I previously used Wait 1 second or no Wait line at all between NR sends, I have recently had to add Wait 3 seconds to avoid variable values being clobbered by the next NR call using those same variables. It seems that ISY's I/O processing of Insteon affects I/O processing of it's Ethernet port also.

Excellent. Just think of the memory on your calculator with a some sneaky mouse inside that watches for a piece of cheese. When you feed it, it squeaks out the phrase you taught it!!! ISY Forever! ASBRIL! VARIABLE KING!! ASBRIL! VARIABLE KING!! ASBRIL! VARIABLE KING!!

There won't be any mechanical gadgets or lights going on and off. It will be one speaker you test it on making sounds. Keep it close and the volume down. I would think GH would have the equivalent of Alexa Routines, but I can't confirm. My 3-4 units are all shut down now. Remember in any good computer programming, your device, variable and other thing naming is your documentation you may need two years from now. Use text name length generously. I like "camel case" style eg: $sSayGarageDoorsClosed. When you use it again a year from now there is no doubt what it does.

After you create the variable and create the link in ISY Portal you can see it in the Alexa app also. That should give you the confidence to keep going and you are almost done. It must be done in order from the ISY end, variable==> ISY Portal ==> Alexa App ==> Alexa app Routine ==> pick a speaker or All speakers. I was using All speakers for a while but the echo sound can make it unintelligible. Now I use a few key speakers only.

I tell people...it's fun, adventurous, and exciting but "if you haven't started, run away as fast as your can!" I'll give you a free sample for your birthday but once you are hooked, you are going to pay dearly! I found it fascinating with my three sons. "I don't want any! I don't want any" Next visit, I see 40 or 50 new devices in their homes, and they hide their faces.

Define a STATE variable with a nice name like $sSayBothGDoorsClosed, Save! In an ISY program insert lines $sSayBothGDoorsClosed = 1, Wait 30 seconds, $sSayBothGDoorsClosed = 0 In ISY Portal, in define Alexa table, find that variable $sSayBothGDoorsClosed and define as a Motion detector, make On from value = 1 Say "Alexa discover" to make it appear in Alexa app. In Alexa app on a cell phone (Win app does not allow Routine editing) define a Routine using sSayBothGDoorsClosed as a trigger, make the output a custom vocal and add "Both garage doors are closed" Routines can take a while to be effective on Amazon sometimes. Also Amazon may block Routine triggers faster than 30 seconds = don't use on fast changing events. Asbril...close your eyes, bang your fists, stamp your feet, sip a brandy, and then create a State variable. It will not hurt one bit and you'll like it!! Let me know if you get stuck! Then we are going to chant "Asbril...Variable King!" "Asbril...Variable King!"

Yes. We use Alexa boxes to control our lights, TVs, Roku sticks, and say things like "Both garage doors are closed", "Garage door one is open", "You have a low battery on a leak/motion detector", "The dryer has stopped". etc.. You will need the ISY Portal to make this easy. It acts like a translations table between ISY and the GH or Alexa devices. I don't define anything as a scene, only switches.

Getting more complicated but every pseudo device could use a scaling factor and a zero offset , then special use cases would be not special. C to F conversion could be done right in the pseudo device code... Scaling factor=1.8, Zero Offset =32.0

The values need to stay mathematically correct. Precision is not an arithmetic operator. It appears your Autelis box, like the WC8 board, does not understand precision and sends raw binary counts. This means 24.2 degrees is sent as 242 raw binary counts. Changing the precision shouldn't modify values. That would make it mathematically incorrect. If you want to shift decimal places it requires multiplication, or division, by powers of 10, not attempting to correct the deficiencies of equipment that doesn't support the protocol used. CAO Wireless Tags support this protocol just fine. If the precision used in ISY was to multiply values times 10^n, values from those devices would all be represented incorrectly. UDI implemented correct methods. Some equipment is using a different standard industry protocol. As a simple example....what if an end device was sending values where each count represented 0.05 degrees C? Should ISY multiply the received value times 20 to get engineering values? What if F degrees is wanted for display? The NS will require scaling factors, offsets, and clamping factors for each parameter. A clamping factor specifies the minimum change ISY programs would require for triggering, say on 0.0005C changes if not desired. SCADA master? Here we come! My ISY is already too busy with polyglot, to handle NSs properly without 3-4 seconds Waits between sends.

Look back about 5 posts. Sent using Tapatalk