502ss

Starting last night my alexa integration stopped working. (alexa would make the tone like the command worked by the skill command to turn on a light didn't work. This morning I started looking deeper. From UD mobile everything works fine controlling my ISY as long as I am local, if I disable wifi and try to test remote connection from the app it times out. If I login to the isy portal it tells me my ISY is online with firmware 5.3.4. If I goto ISY information in the portal all it shows me is the UUID, all the other fields are blank. I also see nothing under logs, If I click on events or errors it just sits there saying retrieving. I also keep getting an HTTP error 408 from the Portal website. Is there a portal issue going on?

Ticket 2148 opened on July 8th Thanks for the response, I will open it up to see memory card capacity and order a new one!

about 1.5 weeks ago my ISY started acting up. alerts not working, variables not updating etc. This happened for a couple days before I was able to login to the admin console. When I did I noticed it was much worse. It looked like my ISY had reset to factory. All of my Insteon devices were there but all my programs, variables, configurations (even my password was reset). I assumed there was some sort of corruption so I performed a factory reset and attempted to perform a restore and I just get a bunch of errors like "unable to read config", "unable to clear config". I tried to open the error logs and get an error stating "could not open file /LOG/ERRORA.LOG". I then tried to format the SD card by telnetting into the ISY. While it looks like it formats, I never see the "goodbye" message in the terminal window like the documentation states and instead the session simply terminates. After preforming this I still cannot perform a restore. I did open a ticket with UDI when all of this started but I have not had much luck getting any progress on the ticket so I figured I could come here! Is it possible that the memory card has physically failed? Any way to test this in the ISY or what to look for if I remove it and put it in my computer? I haven't opened up my ISY yet but anyone know exactly what type of Memory card it takes and its capacity so I can get a replacement ordered online? FYI - I have an ISY 994i (1120) currently running Firmware 4.6.2 Any help would be appreciated! Thanks Jim

I opened a ticket! Thanks Funny how nothing on my end changes and yet I am the one having to open a ticket! Sounds like residual issues left over from the server failure a few days ago!

Power cycle did not work for me. ISY shows offline in the portal since 4:48pm today! Are there portal problems again?

Is portal down again? My ISY is showing offline as of 4:48pm today. Tried a reboot and no such luck. Everything was working fine until 4:48

Does anyone else find it weird that UDI doesn't have access to the documentation for new products from SH? I wouldn't consider UDI just any 3rd party developer, Christ, SH sells the ISY bundled as a starter kit with their products, wouldn't that make UDI some sort of tier 1 partner or something? I really hope this is not the beginning of the end! Michel - sorry to hear that this is a major hurdle for UDI. Hopefully things change! I have a ton of money invested in SH components and would hate to see things take a turn for the worse!

Sometimes a leak sensor shows up in the ISY as blank. It's not either on or off. It doesn't happen often but I want bullet proof notifications so anyone know how to test for this blank condition? I tried writing a program that tested for "if not on" or "if not off" but that program comes back as true. Any ideas? Thanks Jim

I bought a syncrolinc and spent 2 hours trying to get it to work with no luck. I can't even get it to consistently talk to the ISY never mind feel comfortable relying on it for monitoring my sewer pump! I have ordered a current sensing switch and will use it with a pi, a small bash script, and rest to update variables on my ISY. I will let you know how it works but overall I am extremely disappointed with the syncrolinc!

That starter kit is the way to go! Glad your having fun with this stuff! Sometimes it seems like an addiction!

Stan - No need to apologize. I think almost everyone of us here is here to learn! My suggestion would be spend the money and get a pi! They really are quite powerful. If you can learn some basic bash programming (and bash is pretty easy to learn with tons of examples on the internet) then it really becomes a device that can compliment the ISY. I do suggest though that you keep it pretty much behind your router. If you start making some of the pi services public facing (like a public facing web server, etc.) then I would suggest you think about hardening the pi. Thanks Jim

sorry for the confusion, let me try to answer some of the questions/comments and make things a bit clearer. 1) I guess I made some assumptions in my original post that the folks reading this thread would understand that when I posted bash code that any reference to a "program" was referring to the bash prog am and not an ISY program. My apologies. 2) the reason I am not using JS and restful on the pi to listen for the ISY to tell me when the variable changes was for simplicity. I have this functionality running on another pi to control the lowering of a motorized TV based on a command from the ISY and it works cool but I know some people on here are looking for simple integration and a simple looping bash program achieves that. 3) the reason for using geo fence and the bash script is really for two reasons. a) I don't want the door unlocking before I am physically in the yard (even if it's only 5-8 minutes) I have other events that are triggered off me physically arriving home which I also do not want to trigger prematurely (disabling camera recording, etc.) 4) I chose to use the variable from the ISY to trigger the arp-scans strictly because thats the way I wanted to do it. There are probably a dozen ways to achieve the same functionality. This is the way "I" chose to provide the functionality. Hopefully this clears thing up? Let me know if you have any other questions. Thanks Jim

I wrote this program a while ago but kept forgetting to post it. Another member sent me a PM asking about it so I figured no better time than the present! This has been running for over a year and has worked 100% of the time! Basically all you need for this to work is a raspberry pi (or some other device that can run bash, curl, etc) and the ability to assign a static IP to your mobile device(s). How it works: I have a variable on the ISY that changes from "140" to "150" when I cross a Geo fence and are within 5-8 minutes from home. The program is running through a loop constantly looking for the variable to be "150", if it's anything other than "150" the program does nothing, sleeps for 10 seconds and runs again. Once the program detects that the variable has changed to "150" it starts performing an arp-scan looking for the static IP of my mobile to show up on the WIFI. If it doesn't find it it breaks out of the loop, sleeps for 10 seconds and tries again. Once it finds the IP on the WIFI. It changes another variable on the ISY. This change of the variable in my environment triggers a morning industry door lock to unlock. The program then sleeps for 60 seconds and sets the variable back to "140" so the whole process could start over again. I whipped this script up really quick and could have made it cleaner by using variables to define ISY IP, username, password, etc. but I didn't feel free to modify as needed! Let me know if you have any questions. #!/bin/bash while : do curl -s http://isy_uname:isy_password@isy_ip:isy_port/rest/vars/get/1/19 | grep 150 > /dev/null if [ $? -eq 0 ] then #echo "found 150" while : do #echo "running arp command" sudo arp-scan <phone_ip> | grep <phone_ip> > /dev/null if [ $? -eq 0 ] then curl -s http://isy_uname:isy_password@isy_ip:isy_port/rest/vars/set/2/10/1 > /dev/null sleep 30 curl -s http://isy_uname:isy_password@isy_ip:isy_port/rest/vars/set/2/10/0 > /dev/null break fi sudo arp-scan <phone2_ip> | grep <phone2_ip> > /dev/null if [ $? -eq 0 ] then curl -s http://isy_uname:isy_password@isy_ip:isy_port/rest/vars/set/2/10/1 > /dev/null sleep 30 curl -s http://isy_uname:isy_password@isy_ip:isy_port/rest/vars/set/2/10/0 > /dev/null break fi done sleep 60 curl -s http://isy_uname:isy_password@isy_ip:isy_port/rest/vars/set/1/19/140 > /dev/null else #echo "found something else" sleep 10 fi done

oh god! cancel order...cancel order!

so did I read this right? As long as you are running 4.x or 5.x these new motion sensors will work? I realize dusk/dawn and low bat haven't been tested but the base functionality will work? So these new motion sensors have the same internal model number? Thanks Jim