larryllix

Maybe. I have had to factory reset one thermostat 8.or 9 times before it would link properly. I would not give up yet, and factory reset it. Then use restore.

The links can change who it talks to but flashing is an internal firmware problem and shouldn't be link related.

IIRC he would need V5 for nodelink also.

You are looking for solar noon, which most PV fans are familiar with. Your formula is right on, but you will find it never varies, season to season. The longitudinal angle of the sun is always the same for the same time of day while the latitude angle changes. Calculate it once and use it for a time trigger. For DST you may need to use a seasonal condition or two programs based on calendar calcs. Easy in v5.

Just right click on the device and select Restore. Sometimes there is a link that is temporarily changed. Don't understand it completely, but it doesn't cause problems. Restore will fix it, even if just for looks.

No. Stu is attempting to lead you through a diagnostic process to find the problem,not for keeps. and... are all your jumpers on only one pin except for the number 5 pins? I don't think MSes have beepers in them.

V5.x has been out for over a year but all versions are in alpha release status. They have bugs. None combine protocol scenes yet. If you have no Zwave, v5.0.4 or v5.0.7 well with minimal problems

Different brand protocol devices will never actually interact, as in Insteon scenes. ISY 'combination scenes' will just be hidden programs, called scenes or some other label.

I flash a corner bulb red while the garage door is open. If the lights go out and my bedroom light goes on I flash it full brilliance until the garage door is closed If the car leaves I send notifications.

No but Hues do not have scenes in ISY as they are not Insteon. Scenes can be operated from programs and so can NRs

You trigger a program that turns on the scene and send out NRs also. I use a variable with a bank of programs, each triggered off a different value in the state variable. Value = 0 = off Any program can stuff a value into the variable and it all happens behind the scene automagically. After flashing a bulb or any temporary usage of a bulb or LED strip the whole room can be reset back by restoring the value to the variable in a few lines of ISY code. Your dup post can be deleted.

Zones will be normally closed electrical loops for security of system detection If you have no device connected you may need to short out the input or bypass the zone in the setup.

Sorry I told you wrong. Do NOT use the linking mode. Tap the same button, 7 times quickly, and the MS will send the dark/light report immediately and it will not need the 3 minutes to adjust to the dark and light. You will see any change in the Admin Console on the dark sensor.

Put the MS into linking mode again. Now tap the same button 7 times quickly and the MS will send the dark/light report immediately.

Many companies do that, especially on ebay and aliexpress adverts. It's just plain scamming using people's confusion and lack of knowledge against them to sell product. Who is going to take them on legally, when they live on the ther side of the world.

This may be a weak communications problem. Place a dual-band device (like OnOff or LampLinc) close to the motion sensor and try again. bon chance!

How do the links inside a device get inside ISY? How would users use a Hub and an ISY without ISY filling up with errant links to the existing Hub?

Excellent, unbiased, information!

He is complaining about errant links inside ISY.

If the links are showing in ISY it is because your scenes and basic connections to the device demand them to be that way. If the links inside ISY are wrong then you may need a new ISY. In three years, I have never heard of this happenning before, so it isn't very likely the links are wrong. Links in devices contain one for each node going to the PLM and one for each scene that ISY knows about and has created from link management inside ISY. A thermostat will have many links to accomodate the setpoint, heat output and cooling output. each one takes a link as well as links back from the PLM to control nodes inside the device. If you have links inside your devices that only link to another controller/hub/automation computer, they will not be showing in ISY. ISY does not absorb links from devices, only put them into devices. This sounds like you have migrated from an Insteon Hub, where unmanaged links are reported to be a problem for some. If the link tables match perfectly, what is not working, from ISY, in your devices? What device are your referring to?

I assume you have the Portal installed by your comments but if not Admin Console | Help | Purchase modules. You must have an amazon.com account for the Echo registered to a valid US address with proper ZIP code. If you are not in the US you may need to have a virgin computer with no google ID installed. I found it constantly grabbed my google info, and the app is not available to outside US residents. Once all accounts with google, registered outside the US, are disabled, and removed from the computer, then the app may become available. Sideloads for the app are available, but be cautious with Version 2 adverts as they are just phishing hoaxes to lure you into giving personal information. Then follow the wiki link above, although I found it very confusing, as account references never state which one is being discussed. A few different accounts are involved.

Variables can use substitutions, for the value of the variable in the notifications, but not text strings, yet. One way would be to set up a variable for each lock, $sFrontDoor $sBackDoor $sPatioDoor So when kidA enters via the backdoor, the kid's code number is put into the $sBackDoor variable. If ... BackLock_code is not 0 Then ...$sBackdoor = back_door_accessCode When the master program sees any of the variables is changed from 0, it send a notification (State variables required) and then resets the variables to 0 again.(last line in the program) If ...$sBackdoor is not 0 or ...$sFrontdoor is not 0 or ...$sPatiodoor is not 0 Then ...send notification to you, kid_home ...Wait 5 seconds ...$sFrontDoor = 0 ...$sBackDoor = 0 ...$sPatioDoor = 0 Inside the message you have a nice title, with a time marker, and a list of doors, showing the value of each variable with a proper title, like this One of the kids just entered @ hh:mm:ss Front Door: 0 <--------really looks like "Front Door: $(var.2.65)" to use variable value substitution Back Door: 3 Patio Door: 0 People: 1= kidA, 2=kidB, 3=kidC Making sense? 1 program per each door 1 state variable per door 1 master notification program 1 notification NOTE: This may take v5.xx as I am not sure if the access codes can be stuffed into a variable in earlier versions.

You should never need to edit a link table inside a device.ISY provides tools to examine the link table, compare it to ISY's image of what should be in the device, and to restore the device's link table, in the device, back to what ISY has for it. Just right click on the device in the admin console device tree and click restore...fixed. If it is a battery device the linking mode will need to initiated usuall by pressing the linking button on the device for about 5 seconds. Devices do not take XML code.

All zeros is a terminator entry. It tells the CPU involved to stop reading the m into a program.

IIRC there is a trick to extracting the Insteon address that I think you need. You manually link the MS to another device like a SwitchLinc or plug-in module. This is done Insteon style without any help from ISY. Run the Event recorder in admin console and then activate the MS. Look for the Insteon address used for the MS. Factory reset both devices and restore the catalyst unit. Use the MS address in the new device menu (lightbulb icon)