Flex

I believe I have found the answer to the Net Module Rules. It's simply the ID number of a given network resource as you create them. It became obvious to me once I started working on another test ISY, that had just a few network resources in it. Thanks Techman, I will look this up and see if this sheds any light on my issue. It is however, exactly what is happening, but hopefully I can figure out why. Jerry

The reason for this question is that , I am trying to establish a response from a Control by Web x410 via a network resource. While with the Control by Web x310 this works, with the x410 not so much . I feel this is a first step to get the Control by Web x410 to respond to the ISY with data. So I would like to know what some of these error messages mean so I can perhaps figure out a way to establish communications between the two. If this will not work then trying to establish communication using DevLink or other node server to be developed is likely to be futile. FYI the x410 is a newer version of the x310. I am sending them both this command, just a different IP address and different passwords via Network Resources test: GET /state.xml HTTP/1.1 Host: 192.168.1.132:80 User-Agent: Mozilla/4.0 Connection: Close Content-Type: application/x-www-form-urlencoded Authorization: Basic "base64 encoded password" The one that works returns this; HTTP/1.1 200 OK Cache-Control: no-store Content-Type: text/xml Content-length: 707 <?xml version="1.0" encoding="utf-8" ?><datavalues><input1state>1</input1state><input2state>1</input2state><input3state>0</input3state><input4state>0</input4state><relay1state>0</relay1state><relay2state>0</relay2state><relay3state>0</relay3state><relay4state>0</relay4state><units>F</units><sensor1>81.9</sensor1><sensor2>77.2</sensor2><sensor3>x.x</sensor3><sensor4>x.x</sensor4><s1Alrm>0</s1Alrm><s2Alrm>0</s2Alrm><s3Alrm>0</s3Alrm><s4Alrm>0</s4Alrm><count1>0.000</count1><count2>0.000</count2><extvar1>0.00</extvar1><extvar2>0.00</extvar2><extvar3>0.00</extvar3><extvar4>0.00</extvar4><vin>10.59</vin><vinAlrm>0</v The one that doesn't work returns "TCP client read response failed" followed by "Net Module Rule: 59" in a dialog window. Now even though an error is returned both the x410 and x310 will execute a command to energize or de-energize one of their relays or other output..This is a command that works "GET /state.xml?relay1State=1 HTTP/1.1" So I can send from the ISY to these devices but not from them to the ISY So these are some of the errors I received and would like to know what they mean? Sat 2019/07/20 12:38:34 PM System -140005 Net Module Rule: 56 Sat 2019/07/20 12:39:09 PM System -140005 Net Module Rule: 59 Sat 2019/07/20 12:42:09 PM System -140005 Net Module Rule: 55 Sat 2019/07/20 12:43:02 PM System -140005 Net Module Rule: 4 Sat 2019/07/20 12:43:16 PM System -140005 Net Module Rule: 5 Sat 2019/07/20 01:11:12 PM System -140005 Net Module Rule: 60 Sat 2019/07/20 01:11:57 PM System -140005 Net Module Rule: 60 A search on this forum on -14005 returned no results. Any information would be appreciated. Thanks, Jerry

I do not have a windows computer the could be running 24/7 where this is going. I think the Pi would be easier to keep running unattended over the the winter when the location is not occupied. Will this run on a Pi? If so what OS needs to be installed to the PI? I am just starting out with the PI. I have a webcontrol board at the location mentioned. I have four of these, three wc8's and one wc32 and only the oldest has been reliable enough, but it only has 1 one wire temperature sensor on it. And it is at home where I can work with it if neededI have mentioned webcontrol issues in other topics. I just haven't had the success with the webcontrol boards others have had. I find that my version is not all that reliable for an unattended application. This is why I like the Control by Web products, one of which is watching my sump pit and pump, which is why I would like to integrate the Control by Web products into my application. Jerry

I am not sure where this topic belongs since I am not sure which direction this will take. I believe this is where a Node Server and a Pi would come in. And I may be getting in over my ability level, since I am not a programmer but rather one who configures devices. I have been following the forum regarding ISY version 5, node servers, Polyglot, and etc. and feel the technology has advanced to point where what I would like to do is doable without me trying to do expert level programming. The Control by Web family of products will respond to "get requests" via what I believe is a rest protocol. And have been able to send commands from the ISY to both my Control by Web x410 and x310. I like these products because, though expensive for home projects, they simply work. They are rugged, reliable, run without reboots, accurate, packaged well, and easy to configure to get them to do what I want them to do. This said, If I send a 192.xxx.xxx.xxx/state.xml via a browser the x410 or x 301 will return XML formatted something like this; <datavalues> <digitalInput1>0</digitalInput1> <digitalInput2>0</digitalInput2> <digitalInput3>0</digitalInput3> <digitalInput4>0</digitalInput4 ><relay1>1</relay1> <relay2>0</relay2> and so forth until it gets to <datavalues> As such, should I seek to utilize a node server with a PI solution, or is there another method that would be easier and require less hardware? Is this something that can be done with the latest ISY version 4 firmware or would this require moving to version 5. I am generally a late adopter and wait for the releases to become official before upgrading my ISYs, although I believe 5 is now far enough along to implement. I just received my Raspberry Pi this week but haven't started to experiment with it yet. Thanks,

I was never able to achieve that degree of success with my older WC8 boards. I would like to know what values you use for the resistor and capacitor at the one wire input at the board. Maybe that will also reduce the lockups and reboots I experience with my WC8 board. It would be worth a try. My problems with Webset packets being sent too quickly wasn't at the ISY end but rather to keep my WC8 board from locking up. I have a watchdog in the ISY to alert me and counter to keep track of the WC8 and to have the ISY cycle power to the WC8 as needed. This ISY is still at the 4.7.3 revision. Both of these operate at a remote location three to four hours away. The home WC8 monitors a sump pump and has just one one-wire temperature and a one-wire humidity sensor and it has never had a problem. And I have never had either ISY lockup to the point where they stopped running their programs. PLM problems and losing the ability to communicate with the remote ISY from home is another matter. What I have found to be reliable for my sump monitoring (at the home location) is the Control by web family of products but they are Modbus only, with the exception that the ISY can send output requests to their relay outputs via network resources. This way the WC8 and the Control by web backs up each other. Once a version 5 release for ISY becomes official I would like to try the node server solution to get an input from the Control by web products to the ISY. I want to keep the component/device count at the remote location as low as possible to keep the reliability at an acceptable level. Then I will plan to look at the node server topics to try to figure that out and likely ask questions there.

Just a word of caution, to save some frustration, when using the WC8 Webcontrol board. Please note the WC8 board from a "practical" standpoint only supports one digital "one-wire" temperature device and the humidity one wire device if you are using the WC8 to "webset" variables to the ISY, as described earlier in this thread, and have it doing other logic besides. If you wish to use multiple one-wire temperature sensors you should either add additional WC8 boards, or reduce the programing in the WC8 to the minimum required to get the task done. I have been using two of the WC8 for well over three years and have found them to be the only simple practical way (besides perhaps a PI) to get digital and analog I/O points into the ISY. I have found that using more than one wire temperature device will cause board lock ups and the failure of all, or all but one, of the one wire temperature points. I also recommend sending "webset" variables to the the ISY at one minute or longer intervals to reduce load on the WC8 board. Hope this helps with the planning and setup of your project. Please note earlier topics, (CAI Web Control loses Temperature Configuration along with other topics on the "CAI Web Control to ISY Integration" section of this board) about getting digital and analog inputs into the ISY.

Apostolaski: I went to ebay to look at the enclosure, but I still need the plug and ribbon cable, which I looked up on the web, That said, it still leaves the issue as to how best to connect the ribbon cable to the switch which is 50 feet away from where the Webcontrol board would be located. Do you or anyone else know of any ready made cable that would plug into the board and terminate into a screw terminal type block. It looks I will have to roll my own enclosure as I would like to the connections enclosed in the same enclosure as the Webcontrol board. I'll have to check to see if Phoenix contact would have anything. Once the cable is obtained it will be modified to connect to a DIN mounted terminal block or similar, unless a ready made solution is found. Which Webcontrol board do most people use, the PLC firmware or the BRE version?

I figured as such, but if the PLM fails I believe the ISY goes into safe mode. So if the ISY goes to safe mode, will it still send an email or text message? I have looked at the Webcontrol board again and will likely buy one while Smarthome still has their 22% off sale. I would still like to enclose it in some way. With sump level switches hard wired to the Webcontrol board I may just rely on the Webcontrol to do the notifications via text or email. Other contact inputs could then be communicated to the ISY to perform other tasks. I wouldn't want the PLM on a UPS anyway as that would open up at least a few UPS questions, let alone dealing with the removal of a key ISY to Insteon communications route, I was looking primarily to keep the ISY from going to safe mode thus possibly affecting the ISY's ability to send a message.

Thank for your replies, If the PLM is supplied with UPS power and queued events start to back up, would the ISY still be able to send an email message based on a data from a RaspberryPi or other device? If not, another solution may be nessesary. I want to be notified if the backup sump pump is operating, or if the pit is filling up potentially flooding the basement. I have looked at webcontrol and think I like that solution better than the PI, not having any experiance with either. I am looking for a solution with a short learning curve. I'll look at Beagle Bone as I have not heard of that before. I have looked at cell phone based sump alert systems, but they require a monthly or yearly fee.

I have a fairly active sump pit and currently use an Insteon 2450 I/O Linc and a float switch. There are issues of reliability with the 2450 and Insteon in general. Mostly in a power fail situation. While Insteon is fine for monitoring door opening and closings, for the sump pit I want something more robust. What I would like to do (short of purchasing an Elk system, which is an expense I would like to avoid) is to find a way to input to the ISY that is not Insteon dependent. In other posts I have seen references to networked I/O boards that can serve as two or more digital I/O points and communicate them to the ISY. But from what I have seen, the packaging leaves a lot to be desired as most are just open boards for which an enclosure is needed. Also they do not seem to be commercial or industrial quality. What I would like is something like “Digital Loggers” “Ethernet sender” It has 8 inputs and can be located anywhere on the network. Does anyone know of anything like this that will interface nicely with the ISY 994i, with the network module? In addition will the ISY send messages while it and the network is on UPS power while the PLM is not? If not is there something that can be done to work around that? If not, it would seem the Elk is the only answer, as it could perform the notifications. I am not interested in Smartenit solutions due to reported reliability and other issues with them. Any Suggestions? Thank You for your consideration.

I run the Show Device Links Table followed by a Compare as suggested. I got; [identical] 0FF8:E2 01 1B.FB.A2 FF 1F 01 [identical] 0FF8:E2 02 1B.FB.A2 FF 1F 02 [identical] 0FF8:E2 03 1B.FB.A2 FF 1F 03 [ignore] 0FF8: 00 00 00.00.00 00 00 00 And it just reported an "OFF" Put back in its box and waited the 3.5 minutes or so and just reported an "ON" I don't know what caused it to start working unless the Show Device Links Table followed by a Compare trigged something. PLM Links first pass counted 148, second pass also counted 148 links. Thank-you Lee G.

On both the non-working and working sensors the Dusk/Dawn light level set to 128 which I believe is the default. On both the non-working and working sensors the jumpers are set; Jumpers 1-4 off and Jumper 5 on. While the working sensor reports Dusk/Dawn to the ISY as being "ON" or "OFF" the non-working sensor reports nothing, the box on the ISY interface shows a blank space rather than an "ON" or "OFF". I have held the non-working sensor to a two-tube four-foot fluorescent fixture and placed it in its box for well past the 3.5 minute time it takes for the Dusk/Dawn light level to register a status. When I remove the non-working sensor from the box registers motion-sense "ON" and replacing in the box registers motion-sense "OFF" after its timeout period, which is set for two minutes. But the Dusk/Dawn-sense still reports a blank.

I purchased one motion sensor 2842 which works well with no issues. So I purchsed another and have been working with it off and on for a day or so. However, the motion-dusk.dawn does not report back to the ISY. The motion-low Batt and the motion-sensor both work fine. Should I assume the photocell is bad and request replcement or would it be worthwhile to look into this further. Is there anything that can be done besides deleting (unlinking) it and relinking it?

Michel, I checked the error log again and I am not recieving that error, at least not for now. I will mention that even though the error was occuring the ISY was able to perform its tasks. That is, the programs ran according to schedule, at least some of them did. The ISY and the PLM are about six to eight months old now. I checked the history pior to clearing the log, I had saved it, and yesterday, as far as I could see, was the only occurance of the " UDQ:Queue Full: PWRIT" error. That said, I will continue to watch to see if the error "UDQ:Queue Full: PWRIT" re-occurs. If there is a next time I'll know to look toward the PLM and its cable to the ISY. And I thank you for your response and assistance regarding this issue. This is the most recent error log now, for about the last 24 hours or so. Time User Code Message Sat 2012/11/10 06:31:45 PM System -5 Start Sat 2012/11/10 06:31:46 PM System -110022 /CONF/INSTENG.OPT Sat 2012/11/10 06:31:46 PM System -110012 /CONF/INSTENG.OPT Sat 2012/11/10 06:31:47 PM System -170001 [Network] Established Sat 2012/11/10 03:32:05 PM System -10011 n/a Sat 2012/11/10 03:32:07 PM System -10011 n/a Sat 2012/11/10 03:32:08 PM System -170001 [Auth] 192.168.1.20:2521->80, Num=3 Sat 2012/11/10 03:32:08 PM System -10011 n/a Sat 2012/11/10 03:32:11 PM System -170001 [Auth] 192.168.1.20:2522->80, Num=4 Sat 2012/11/10 03:32:11 PM System -10011 n/a Sat 2012/11/10 03:32:12 PM System -170001 [Auth] 192.168.1.20:2529->80, Num=5 Sat 2012/11/10 03:32:12 PM System -10011 n/a Sat 2012/11/10 03:32:14 PM System -170001 [Auth] 192.168.1.20:2530->80, Num=6 Sat 2012/11/10 03:32:14 PM System -10108 Check log Sat 2012/11/10 03:32:14 PM System -10011 n/a Sat 2012/11/10 03:32:16 PM System -170001 [Auth] 192.168.1.20:2531->80, Num=7 Sat 2012/11/10 03:32:16 PM System -10108 Check log Sat 2012/11/10 03:32:16 PM System -10011 n/a Sat 2012/11/10 03:32:20 PM System -170001 [Auth] 192.168.1.20:2532->80, Num=8 Sat 2012/11/10 03:32:20 PM System -10108 Check log Sat 2012/11/10 03:32:20 PM System -10011 n/a Sat 2012/11/10 03:32:21 PM System -170001 [Auth] 192.168.1.20:2533->80, Num=9 Sat 2012/11/10 03:32:21 PM System -10108 Check log Sat 2012/11/10 03:32:21 PM System -10011 n/a Sat 2012/11/10 03:32:21 PM System -170001 [Auth] 192.168.1.20:2534->80, Num=10 Sat 2012/11/10 03:32:21 PM System -10108 Check log Sat 2012/11/10 03:32:21 PM System -10011 n/a Sat 2012/11/10 03:32:22 PM System -170001 [Auth] 192.168.1.20:2535->80, Num=11 Sat 2012/11/10 03:32:22 PM System -10108 Check log Sat 2012/11/10 03:32:22 PM System -10011 n/a Sat 2012/11/10 03:32:22 PM System -170001 [Auth] 192.168.1.20:2542->80, Num=12 Sat 2012/11/10 03:32:22 PM System -10108 Check log Sat 2012/11/10 03:32:22 PM System -10011 n/a Sat 2012/11/10 03:32:23 PM System -170001 [Auth] 192.168.1.20:2543->80, Num=13 Sat 2012/11/10 03:32:23 PM System -10108 Check log Sat 2012/11/10 03:32:23 PM System -10011 n/a Sat 2012/11/10 03:32:23 PM System -170001 [Auth] 192.168.1.20:2544->80, Num=14 Sat 2012/11/10 03:32:23 PM System -10108 Check log Sat 2012/11/10 03:32:23 PM System -10011 n/a Sat 2012/11/10 03:32:24 PM System -170001 [Auth] 192.168.1.20:2545->80, Num=15 Sat 2012/11/10 03:32:24 PM System -10108 Check log Sat 2012/11/10 03:32:24 PM System -10011 n/a Sat 2012/11/10 06:36:22 PM System -5 Start Sat 2012/11/10 06:36:23 PM System -110022 /CONF/INSTENG.OPT Sat 2012/11/10 06:36:23 PM System -110012 /CONF/INSTENG.OPT Sat 2012/11/10 06:36:23 PM System -170001 [Network] Established Sat 2012/11/10 06:38:44 PM System -5 Start Sat 2012/11/10 06:38:46 PM System -170001 [Network] Established Sat 2012/11/10 06:38:56 PM System -60006 n/a Sat 2012/11/10 08:46:56 PM System -5012 26 Sun 2012/11/11 06:38:49 AM System -100 [DHCP] state=RENEW

In order to install the update I had to do a factory reset on the ISY, then restore the backup. I then made the addition to the scene and the update occured in good time and most importantly, finished. Again thanks, LeeG for your help.

Thank you for your response. I tried clearing the cache. I also have rebooted from the user interface and then when that didn't work also powered down and restarted after about 30 seconds. I still have system busy message. Makes it to 99% complete then starts over it has been like this for over an hour now. It won't let me update till the ISY frees up. A portion of the error log reads, Sat 2012/11/10 02:23:46 PM System -170001 UDQ:Queue Full: PWRIT Sat 2012/11/10 02:23:56 PM System -170001 UDQ:Queue Full: PWRIT Sat 2012/11/10 02:24:06 PM System -170001 UDQ:Queue Full: PWRIT and so forth over and over about every ten seconds Sat 2012/11/10 04:25:38 PM System -170001 UDQ:Queue Full: PWRIT till the last entry, complete with out of place time stamp, which is, Sat 2012/11/10 04:11:29 PM System -5 Start

I am a newer user to the ISY 994i firmware version 3.2.4 and UI version 3.2.6 and first post. I just added a keypadlinc 6 button dimmer button to a scene. All looked good so I went to test the operation of a new program using that scene. When I got back to the computer I found the system busy dialog bar looping. The prompt says "Please do not power off/unplug the system or make adjustments to linked/attached devices." The progress bar will reach up to 99% complete before restarting again. This can last hours if not days. My system consists of the ISY, two keypadlincs, two Icon switch dimmers, one 2430 controLinc, a couple of lamplincs, and a few x10 devices. This is about the third time this has happened. I have about 20 programs Is there anything one can do to regain the ISY's attention? What would happen if I were to try and reset it, that is power it down and restart. I would like to know why updating a small setup like mine takes so long?