larryllix

From your first statement the success of the program running is intermittent. If this is the case, and I think oberkc gave some good troubleshooting techniques, is the running of the program recorded in the program summary tab when the program appears to fail from manually changing the variable? If the summary shows it ran by time synchro, and the program did not run then something is turning it off again, suggesting variable negative feedback or defective ISY engine processing. At that point, with absolute proof, I would do an ISY factory reset and test again, then UDI contact. Bad SD or contacts? Did you state which ISY revision you are using?

Have you manually changed the value of the variable to divide the problem into output or input from the variable value? Does the variable state have any dependency on the state of the humidifier? Creating a negative feedback loop. Is your program triggers enabled? Have you checked and compared the links in the output module? factory reset it and restored?

Really cool device but it seems very new and therefore no support for it would be installed in ISY994, yet. May be worth requesting support in the feature request thread to UDI.

I was going to become one but maybe later.

It was some debugging/testing process the code writer went through, that left some French residue in most of our voicebases by accident. Glad your working again!

The main problem is... ISY cannot parse inputs. Sent from a tiny keyboard. Response may be brief.

Once somebody brightens one light in a scene involving 20 devices, is the scene now on or off? Varying scenes is an oxymoron. Sent from a tiny keyboard. Response may be brief.

SH cares a lot about quality. Some indicators are there. They just have extremely poor management that don't understand how to effect it. Quality Assurance will never make good customer relations. Somebody is reading the failed 1970's management playbook,still, proven unworkable for so many years.

The temperature range given in the spec. is a conservative range for the electronics. The range I posted is from actual testing, as mentioned in my post. Look at the data stream in the Admin Console events and it soon will become apparent the data values, 0-255 counts, are 0 - 127.5 degrees C. Each binary increment is 0.5C. For 22.5C reading you will see a 55 value in the data stream. For 15.0C, the data stream will read 30. Humidity reads one for one percent. BTW:When external is selected on the stat, the value sent is one degree C for each count so the resolution is only 1.0c instead of 0.5c for the internal selection. The negative values are interpretations using standard signed 8 bits values. A value of 254 eauates to -1.0 degree C. This was never intended to happen and ISY does not interpret it as such as the value would also represent 128.0C, which would be the correct interpretation. Also, accuracies are probably out to lunch at these points, outside the stated range allowance.

That's 0 to 127 degrees Celsius in 0.5C increments. 0 to 254 counts on the binary transmission scale, the capability of one byte of data. I ran tests on one of my 2441ZTH units and it sent temperatures to ISY down to about -2.5C but the temperatures were not interpreted by ISY correctly, as they are sent as two's complement negative numbers, which ISY doesn't interpret. At that coldest temperature the stat electronics failed and resumed later, when the stat was warmed up.

Use some hot breath or a few seconds with a hairdryer to initiate a temperature change update. There is no other way except to wait for a temperature change of a few degrees. Query won't do it.

Just access the STATE variable tab in admin console. Type in a name for a variable and hit save. Write a test program to save a value into the variable. Check the variable page again to see your value stored there. Write another test program with an IF line using your variable testing if the variable is equal to 5. In the then section write lines to turn a light on or off as an indicator. Manually change the value of the variable, hitting enter each time and watching the indicator you wrote. You're using variables. Play, play, play. Sent from a tiny keyboard. Response may be brief.

Wc8 is web control board by CAI. A small controller board with inputs, outputs, and anslogue inputs and can shoot values into isy's variables via the test interface. Sent from a tiny keyboard. Response may be brief.

Many of us have isy slave RPis and or wc8 boards feeding data into our isy. It would be a simple job to detect the local LAN system and router is functioning inside isy. Sent from a tiny keyboard. Response may be brief.

I confess. I haven't tried it with v5.0.8 But the 2441zth can only send one. Sent from a tiny keyboard. Response may be brief.

Isy just ignores the external data that is sent. We proved it is sent in another discussion Sent from a tiny keyboard. Response may be brief.

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.