larryllix

The thermostats will send either remote or internal sensor temperature dependant on the setting in the thermostat. However, ISY will not intetpret or display the received data unless marked as internal sensor. Sent from a tiny keyboard. Response may be brief.

V5 variable features haven't changed any since decimals were added. AFAIK. I have asked for small additions like an Integer function to tear off fractions. An exponent function would be nice for windchill calculations now but I haven't asked yet. Sent from a tiny keyboard. Response may be brief. On a bad forum browser right now but my Xmas programs are all in a folder that is enabled from Dec 1 to Jan 11 each year. I need to add a detailed yearly notification describing the X10 and Insteon addresses of each light string so I know which ones are reserved for what task.

Like jtara above, fixing your ip address indide of most devices on your LAN is a bad idea. The fixing of ip addresses should be done inside your router. A fixed ip address inside a device may work forever but one day the router can assign that address to something else and suddenly the whole LAN can hang and be really hard to diagnose. Sent from a tiny keyboard. Response may be brief.

No batteries required. Check the other thread for details You have to drop some code into the kumoapp website and modify to match your isy variables you set up. That's the easiest way. It will self prompt and save your isy credentials for you automatically. Sent from a tiny keyboard. Response may be brief.

Search for another thread where people are raving about them. I find them fabulous for temp. Humidity. BattV. XYZ angle position not explored yet. Out of range. I can't walk that far. 1000 feet to each end of the street and I couldn't trigger loss of signal. Inside double cookie tins didn't do it either. Most reliable HA stuff I have so far. The other thread has code for kumoapps that Michael wrote and I rearranged to make easier ISY user access. Also added decimals. The prices started about $15 each and have steadily increased as features get added. Sent from a tiny keyboard. Response may be brief.

Shoot! Thanks for reminding me too late. I usually carry a few X10 plug-ins and key fob remotes while on vacation. I forgot this time. It's always nice to turn out that lamp in a hotel room from the bed, even if you have to chisel the epoxy out of the receptacle holding the plug in. Sent from a tiny keyboard. Response may be brief.

Just add a Wait in front of the notification. Everytime a heartbeat signal is received the timer will start over and never notify you. Make the timer at least 10% longer than the heartbeat period. Sent from a tiny keyboard. Response may be brief.

Each line contains an address (link) of another Insteon device. Minimum you have to have a link to your PLM or ISY would be blind. You will also have a line for each scene the device contains. At the end you will have a terminator line with all 00s. If you have a multiple node device like a stat you will have more links due to setpoint, temp, humidity, fan etc,,,, If the compare disagrees this indicates a disagreement between ISY's records and the links inside the device. The Restore is the fix for that. I can't tell you much more without getting into the bit twiddling nitty-gritty and I can't say I have spent enough time on it myself to understand it all. As per Paul above, it's not something to pursue, at this point or hopefully, even forever.

In the admin console, device tree, right click and select to view the device links. After the upload completes, (you will see a 00 00 00 record) click on the compare button to check if the links installed in each device is the same as ISY thinks they should have will all the scenes and PLM connections. If they disagree, try a right click and select restore on that device to correct the links. Test again.

As per Paul's advice I like to do load links from the device, itself, and then click on compare to find the offending link, so I know who to spank, first.

I started with BSR Canada, devices in the early 1990s. I have some Stanley Canada devices, also. Later, BSR was purchased by a company named X10 and also sold under the Radio Shack Plug'n Power brand. Just looking in my junk box I still have a sealed Universal Interface Module, never opened. Insteon is just new for me at about three years now.

Looks perfect! Controls only true when it calls the CPU to execute the logic evaluation. This means when the sunset trigger gets attention for evaluation the control is always False. Whenever you want to use the time frame logic only as a filter you need another program or use Control for the trigger element. With variable values as triggers, a second trigger disabled program is necessary for the time frame not to trigger Then at the start node and Else at the termination node.

Did you happen to install a KPL about the same time?

Welcome to the forums! Revival for an old thread!

Wow! The CAO Tags are like that too. I can't make them drop signal at either end of my street about 1000' each way. One in the glove compartment triggers about 2km away from home. Scary! The higher frequencies are usually line of site as they don't bend or reflect off things well. What is the ZWave frequency?

I kind of figured the OP may be referring to the ISY programmer/user's point of view but he did post. ..."architecture of the internal system." and the reason I posted "maybe". While UDI has never really released the hidden secrets of the ISY execution engine I see a few ways of doing what they have done. 1) On a time clock basis you scan every line of code and see if any factors have changed. Not likely and maybe the way the antique v4 and earlier versions worked. 2) Every time any event occurs you scan every logic line to see if anything is affected and run accordingly. Maybe? 3) Each time any event occurs, ISY scans a specific and particular link table for that event/device. From there you branch out to evaluate those and only those logic lines or programs involved. Much more economical for CPU cycles and I believe this is the major change to the ISY v5.x event logic engine. Reading this UDI is probably doing some hidden snickering behind the scenes (not Insteon scenes). So while the ISY user / program writer, only sees the ISY magic, behind the scenes the "little ISY engine that could", is polling and scanning at high speed constantly, so the user doesn't have to. This is why I laugh when people suggest linear languages would be so much easier and simpler. I know they haven't written an event based trigger OS yet and most likely will bog down somewhere around the two to three year mark, doing it "My Way". There is always somebody that wrote the code, and doesn't believe in the magic, so that we can.

1) Maybe. The ISY engine evaluates any logic statement containing the element if the element changes value. 2) Yes. Programs voluntarily give up CPU control at Wait, and Repeat statements. 3) NO. It's a multi tasking system that continues with or without ACK / NAK 4) See all above

In another life with X10, or wired security light MSes whifts of snow coming aroud the soffits would set off my lights regularly.IIRC some of those, from the old days, where dual element sensing made to eliminate most of these probelms but they couldnt handle it. Car lights and lightning were handled well but the snow dust in the air swirling around always seemed to be a problem from my experiences. Location is key.

I tried it in one small room but I thought it was slowing down the response. It did seem to make a difference for response speed and I never put the jumper back on. In a small room the reach range shouldn't make any difference. As an aside: I had one report motion while I wasn't home again. Then my webcam didn't connect to verify anything. Suspecting problem I forgot about it until I got home to find a 9v battery testing at 4.5 vdc. No LowBatt signal...and I record them (lowBatts) in ISY in a variable that hold three unit's records at a time.

Mine is up OK also. Perhaps your ISY connection has changed addresses or something ISY related has changed?

It may give some problems with direct scene links between devices but a simple program can alleviate and logic reversals needed. Is it important to not have a 1 second delay between garage door starting to open and the KPL LED coming on/Off?

No hardware or wiring changes are needed. Just take out the Reverse Trigger option and reverse your code logic. THis is easy. First change you device node to read the correct status like "Garage door open" or "garage door closed" ...whichever is correct when On. Then change your If section logic to the reverse logic like... Garage Door Open = On instead of Garage Door Open = Off or Garage_door closed = On instead of Garage door closed = Off...etc. There is a reason that ISY is programmable.

Since you found a changed setting, without a reasonable explanation, I would factory reset the stat and start again. This may cure other problems also.

Is there an Insteon clinic? Did I miss something? Sent from a tiny keyboard. Response may be brief.

Sure. Blame it all on us! Sent from a tiny keyboard. Response may be brief.