ih574

Thank you. In my search for a solution, I was coming to that conclusion. Thank you for confirming. It also appears that the Eisy and Polisy devices will also replace my existing ISY994. If that's the case, I would only need one device to run both my ISY automation devices (Insteon, Network Resources, Email notifications) and my Polyglot node servers. Is that true? If so, I will do more research on those and find a place to purchase the device that does not require me to use cloud services (except for the weather feeds). Thanks again for the confirmation. r- Tom C.

Hi all. Its been a long time since I last posted. Was a ISY 4.x user until weather module deprecated. Went to 5.x upgrade and then Polyglot v2 on a Rasberry Pi. Then put on WeatherflowPGC. Worked well (except for having to manually restart the Polyglot Weatherflow node at least weekly. But now, the Weatherflow node server no longer connects to a station - any station. It just stopped working. I didn't change a thing. I looked around to see if I could see anything that indicates that version is no longer supported, but couldn't find anything. Another v2 node server (AVR Remote) is working fine. I'm happy to update to v3 if that what it takes, but I can't find clear instructions on upgrading or installing v3 on a Rasberry pi. Current version is: Version 2.2.11 Status: Connected Frontend Version: 2.2.9-5 ISY Version: 5.0.16C Uptime: 1 Day(s) 19 Hour(s) 6 Minute(s) 14 Second(s) (c) 2023 UDI Any help or advice appreciated. Tom C.

I had the same problem after going to Version 7 Build 51 today (Jan 18,2014). Error had something to do with security permissions. I went to the Control Panel | Java settings, then to Security tab. Then I added my ISY's IP Address and port number (e.g., http://10.1.1.8:8335) to the exception list and that fixed the issue. r- Tom C. http://www.outcropacres.com

Teken, Thanks for the shout out. Didn't think anyone ever saw that stuff. Thanks for noticing. r- Tom C.

That's interesting. I made my own water leak detectors back in 2010 using what were called "TriggerLincs" and the $11 water sensors (http://www.smarthome.com/79633/United-S ... sor/p.aspx). I wired the sensors to the little I/O port inside the Trigger Link. It worked well, except had exactly the same behavior as the OP mentioned above. For the TriggerLinc (now called a "Wireless Open/Close Sensor"), the ISY defined the states as Open and Closed. Out of water, it showed as Closed. In water, it would momentarily go to Open and then back to Closed. So I watched for the change and took action on that. Here is a picture: http://www.outcropacres.net/images/ha-watersensor.jpg. r- Tom C. http://www.outcropacres.net/pasttimes/homeauto.htm

I use the ISY network resources to force a PC running EventGhost to ping my phone every few minutes. Eventghost executes a REST command based on the ping result (runThen if ping was successful and runElse if not) which sets an ISY state program (or variable) true. I then compare that with other program states (or variables)to determine whether the device is gone, just got here, or has been here longer than 20 minutes. I take action on any one of these states, usually generating a greeting. This is only useful for taking global actions since the ping is not sensitive to different rooms or floors. But its fun to have the house greet me when I arrive. r- Tom C.

I have about 350 programs. The way I count them is to go into the console under Programs | Summary. I sort the list the way it is most useful to me (usually by path). Then I select the first line, hold down shift and select the last line. Then press CTRL + C to copy. Then I go into Excel and paste the lines in, followed by a tiny bit of formatting to add a header row and get column widths correct. Then I can set Excel's Autofilter and sort and search to my heart's content. The 350 programs breakdown as follows: General Controls 14 Timers 35 Occupancy Check 21 Voice Announcements 69 Garage 17 Weather 51 Building Status 46 Web Control 68 Archive 28 The Programs tab loads in 35 seconds, on a very slow client computer. I have 191 Network Resources, more than half of which are commands to the voice server. While most programs act on Insteon events, many are simple event processors that act on dates, times, PC or network events. r- Tom C.

I use a program called "http-ping.exe." It lets me send http commands from a command line. For example, this one executes the "runThen" of program 0115: http-ping.exe -n 1 http://userid:password@192.168.75.18:3968/rest/programs/0115/runThen In this case, fill in userid and password with your own and put in the right IP address and TCP port. The -n 1 causes it to run once. Full set of commands are shown with an "http-ping /?" command. I got http-ping from here: http://www.coretechnologies.com/products/http-ping/ r- Tom C. http://www.outcropacres.com

Michel, I did some traces on a successful and a failed Admin Console session, where failed means everything in the console comes up except for the device status and the latest version notification. I see the behavior you mentioned above, though it looks like the Console PC closes the session intended for reuse. I've sent a summary of what I saw to the support email below. r- Tom C.

I have always had the same problem. I agree that it is a firewall issue. Here are my experiences: My Configuration: I use a separate hardware based firewall between the home automation network and my general purpose network. I keep it pretty restrictive. On the machine I use for the console, I have Java caching turned off. Java version is V6 Update 33 and my ISY firmware is 3.1.17. Windows XP, SP3. All wired ethernet (no wireless). My Symptoms: This issue has occurred since I've had the ISY (almost two years). I do not have the problem when I load the console from a machine on the same IP subnet as the ISY. Interestingly, I never have an issue when I log into the ISY web services (HTML files stored on the ISY) or use any REST commands from any machine regardless of firewall type or whether it is inside or outside the ISY subnet, indicating the base IP communications and TCP ports are sound. Both the java ISY admin interface and the web services are configured for the same TCP port which is open in the firewall. The java ISY Admin console authentication is always successful indicating reliable communications with the ISY through the firewall. When the console loads, it always shows all my devices. However, when it fails (about 80% of the time), it loads the devices but will not show current status of the devices (i.e., on, off, %). Additionally, when it fails, it will not show the notification in the top right that there is a newer version available. Nothing changes if I query devices or let the console sit for 30 minutes. When it loads successfully, it will show device status and the notification for the later version. My Attempted Solutions: At first, I thought maybe the ISY admin console (using something in the Java implementation) was trying to get an ICMP response (ping, traceroute, etc.) or something similar from the originating address which I may be blocking. Maybe the ISY tries to originate a separate connection to the console machine, which I block. I've tried lots of firewall changes (one at a time) such as opening up ICMP, not NATing, creating a reverse proxy rule, and skipping forward proxying. I also tried pinging the ISY through the firewall before I start the console (always successful since I pass pings) so the ISY would already have ARPed the correct MAC address for the return conversation. Nothing has proven to be predictably effective. The only thing that works is to try a few more times. The next thing I'll do (and I haven't yet cause I'm lazy) is to look at some wireshark traces. I had hoped I would stumble on the solution by randomly guessing like I described above. So if anyone has any more ideas about what we could do to correct this, I'll give them a try. r- Tom C.

My area shows current light and light rate. Current light is never more than about 11% and that seems to be around 1:00pm if its very sunny. Its 0% up to about 9:00am in the morning and after about 5:00pm (in May). If its cloudy or raining, it shows 0%. I expect these readings are specific to my location's sensor or the location's station has the sensor inside or without a broad sky view. I don't think there are many applications for which this is a useful trigger. I agree with iostream that a motion sensor dusk trigger could be more useful and possibly more reliable. r- Tom C.

Ok. I think I get it. Time based conditions are deterministic and device status/control are events. Any time based "If" condition will show up in the program summary as a "next scheduled run." For some reason, I was mistakenly thinking it would act like a nested condition. Thanks. r- Tom C.

I have a bunch of programs that check the status of various devices and, depending on status, make voice announcements about their state. I want these programs to run only during specified time frames, which I have in the IF statement. I also use "Last Run Time" parameters instead of "Wait" statements so that I don't have all these programs running in the background for several hours. If From 9:00:00PM For 2 hours And Status 'GR - GrgBay1 - Sensor' is On And Time is Last Run Time for 'Check - Garage Bay1' + 10 minutes Then Resource 'Voice-Announce-CheckBay1' Else - No Actions - (To add one, press 'Action') Use of the "Last Run Time" causes the program IF to run every ten minutes, even when the time is outside the 9:00pm to 11:00pm window. I see this in the Program Summary tab where these programs' Next Scheduled Run time is always in the next few minutes. I would prefer if these programs were only executed in the time window specified. I recognize there is no issue with these running every 10 minutes, cause they will always fail the IF until the time window is true. However, I would like to have these programs active only during the specified time window to keep the history stats consistent (and to soothe my OCD characteristics). I'd also like to do this without Wait statements. Any ideas about how I can force these programs to run only within the specified windows while not using Waits? It seems like Last Run Time trumps the other schedule parameters. I expect I could put them in a folder that was only active during the window, except that I have different time frames for the checks. r- Tom C.

Paauto, I could have led with this, but the network stuff is more fun to troubleshoot. I have an old IBM PC in the garage that is configured to Power On after Power Loss in the BIOS. The BIOS option is under Power and under the "After Power Loss" setting. It is set to Power On. I then have that PC along with a couple of AV Receivers powered by an Insteon ApplianceLinc. When the ApplianceLinc turns on (by a program or a few KeyPadLincs around the house), the PC starts up and starts playing music. I think that's what you are after. r- Tom C.

I wanted to clarify some ideas from my post above. When I said "If you have a router between the LAN of the target and the LAN of the originator," I meant a device which routes packets from one Layer 3 (IP) network to another. In other words, I consider a router a device that connects two or more IP subnets (e.g., 192.168.5.0 to 192.168.8.0 or 172.16.0.0). Typically, folks have only one true router in their home networks and that is the one that connects the ISP provided network (on the Internet or WAN side of a home router) to your home network (typically 192.168.x.0). The rest of the Cat 5 ports (and all wireless "ports") on a home router are typically switch ports, which should act as the Layer 2 (ethernet) network. There is no "routing" going on between the switch ports - those ports are "switching." Additionally, all switch ports should be in the same broadcast domain, meaning that if any broadcast packet is sent from one port, it will be repeated on all switch ports, including wireless ports. If you connect one home router to another by its switch ports and they are all part of one IP subnet, then the WOL packets should be broadcast on all ports. Where I have had issues with low cost home routers is with their ability to actually broadcast packets on all switch ports. For example, DHCP requests that come from wireless devices are either not forwarded to other switch ports (where the DHCP server is) or the reply from the DHCP server is not forwarded to the wireless ports. The same thing may be happening with WOL broadcast packets. A Wireshark sniff will let you know. r- Tom C. http://www.outcropacres.com