larryllix

Everything needs to be tested. Even still, we all get caught while away sometimes. Put the sensor on the counter with a puddle of water and tap the button after drying off to clear the statuses.

Have you power cycled the PLM yet? Bad PS capacitors like to bid their final farewell or heal somewhat after a rest sometimes.

Welcome to the forums!! As per the usual database and spread sheet ordering in MS products, UDI has implemented the technique to mouse click on the top line where the titles of the columns are.

One thing to keepin mind is that the backwashing requires fast flow to "fluff up" the resin beads and break down any calcium clumping. A sensor that creates any restriction make damage your softener function, and in the latest case I saw last year, all the plumbing fixtures in the house. Insurance does NOT like to pay for home owner negligence replacing every clogged water fixture. It's mainly at the tee intersection restriction for the three hole fixtures and steam heads in showers may require replacement of all stall tiling to access. It can get complicated real quick.

I would have called support first. This is very rare.

As a matter of inerest here is how I got around the log usage with ISY. A simple calcualtion of %RH divided by a factor of 5 was offered elsewhere but the curve gets way off at one end of the range. Note how this line has been used as an inline If/Then condition to fudge any humidity over 45% ...Repeat While $Variable > 45 This is to bring dewpoint resultant at that end of the curve, closer to the actual conversion curves . I use three programs like this, for conversion of inside, outside and cold cellar %RH humidities to dewpoint humidity readings. Sync.DewPoint.in - [ID 0128][Parent 0101] If $sHouse.humidity <= 100 Or $sHouse.temperature <= 100 Then $House.dewPoint.scratch2 = 100 $House.dewPoint.scratch2 -= $sHouse.humidity $House.dewPoint.scratch1 = $House.dewPoint.scratch2 Repeat While $House.dewPoint.scratch1 > 45 $House.dewPoint.scratch1 -= 45 $House.dewPoint.scratch1 *= 0.7 $House.dewPoint.scratch2 += $House.dewPoint.scratch1 $House.dewPoint.scratch1 = 0 Repeat 1 times $House.dewPoint.scratch2 /= 5 $House.dewPoint.scratch2 -= $sHouse.temperature $House.dewPoint.scratch2 *= -1 $sHouse.dewPoint.in = $House.dewPoint.scratch2 Else - No Actions - (To add one, press 'Action')

Yeah. Dew point is only necessary where you compare two humidity levels. I calculate mine, dynamically, using ISY programs so Logs are not happenin' there. My usage is my cold cellar running at 10-18C degrees, and if you bring in warmer and lower RH% air, very often you will increase the humidity RH% as the temperature drops. Use SOAP RPN, I do not. To do the work for me, I like my computers.

There is a troubleshooting chart based on the LED pattern. Not sure where to find it but Google is your friend. First try a power cycle of the PLM and ISY. PLM gets powered up first for a few seconds, and then ISY. If that doesn't work, try a factory reset. Research how to do it, so you have better access to proper troubleshooting information. I hope you have a good backup file. If you factory reset it, you will need the factory password, reset the location information and then use your back up file.

That's awesome! Many people will have usage for that find. Softeners do a lot of clear water flushing at the end of the cycle but the salt could be a problem for some internal part maybe. Hopefully not, Price is excellent too. You da' man!

I use dew point to run exhaust fans now. It is more predictive of the desired resultant. I discovered by exhausting air with a higher humidity than the outside air, I may still be increasing the humidity, instead of lowering it, once the incoming air is cooled down to the room temperature. Dew Point comparisons eliminate this and it's easy to calculate.

Other than a multiple try or a better mail server I don't know. Repeat 2 times (Canuck = twice ) ...send X email notification to ES1400 ...send X sms notification to ES1400 ...wait 1 hour Repeat 1 times

It's upgradeable right from inside your ISY admin console.

hmmmm. I might have a screen shot somewhere here.... IIRC you are one of those apple guys and they only allow a single core

Try deleting all the java cache stuff and reloading the admin console.

This was reported by a previous poster about a year ago. Can't remember the fix though...sorry. I would try a factory reset of the ISY. You will have to fix your password and time zone options. Make sure you have a good backup image. I have had a few installation quirks in my time. The firmware was always great but the install got confused somehow.

Has the admin console worked OK from the same device when at home, via the same comm path? You haven't said what type of connection you are using (public, private, hotel, shopping mail) or what type type of device you are using. ISY has a soft reboot found on the System? Tab on the far right.

Sounds like a intermittent comm problem. I take it you are away from your LAN. The missing devices sounds like a hang during the data loading. My guess is ISY is fine. Do you have any anti-virus or firewall things on your remote device that have suddenly jumped into action, not liking your access? Some ports are not liked by public style access points.

ahhhhh.. This would fit in with the checkbox at the end of every line idea, to enable/disable it. It would have a slightly different function in the If section.

Probably all the same electronics and paddle but with one component missing that allows dimming to happen The paddles may put out Dim and Brighten also. Hey that could be useful for people controlling bathroom fans and other side jobs from the same switch. We know the light control can't respond to the strange paddle pushes. I don't have any On/Off Switchlincs. Are they relay contact or Triac?

V5 has comment lines but they take too much space vertically, so far. End of line remarks would be nice.

Sorry. I was totally confused in the thread and didn't start over reading. I guess I don't understand what the Fast On/Off have to do with the logic working. Do you think the switch is contact bouncing and sending those codes by mistake?

It's a syntax error (grammaro) that has existed since Repeat was added to the ISY repertoire. ....Repeat 1 times means execute once only. I was using it in a few programs only to find out it had some problems. I don't recall what the problems were now. The discussion was posted in a thread about a year back.

This hasn't come up for quite a while but just a thought..... Status devicename is On may not test true if the dimmer is 1-99% Try status devicename is NOT off

Control devicename is switched On is not ever false if it causes the re-evaluation of the logic in that program. Control devicename is switched On calls the attention of the ISY logic engine upon receiving the On signal from a device, so while the line is being evaluated it is always True = running Then. Statuses have two states, usually On and Off. Control devicename is switched ON has two states = active and not-active. Control devicename is switched Off has two states = active and not-active. Note two different signals to detect Now just to complicate things. If ...control devicename1 is switched On ...AND ...control devicename2 is switched On can never be True = never run Then. While one line is being evaluated, due to it triggering the evaluation, the other line will always be False (at that time) and the combo will run Else. So there are two ways to do this. If ...status of devicename is On Then ....set light On Else ....set light off If ....control devicename is switched On AND ....control devicename is NOT switched Off Then ....set light On Else ....set light Off

...Repeat 0 times may have undetermined results. You should use ...Repeat 1 times as a UDI documented method. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Action