bob123 Posted July 9, 2023 Posted July 9, 2023 I'm starting to plan my migration from isy to my polisy. Both are up and running, but given that the isy is 4.9 and series 300 zwave, I've decided to take it slowly. Breaking the migration into 2 parts- first, move zwave and ELK to the polisy and ensure I'm happy with behavior, then upgrade the isy to latest 5.x.x fixing all issues and then move insteon over. I will hand update the existing ELK and zwave programs after everything is on the polisy. To accomplish this, I want to utilize variables and the network module to control programs/state between the zwave/ELK on the polisy and the programs on the isy using insteon. I've tried to use the network module from both sides to set/get variables from the other side and cannot get it to work. I can go into Chrome and 192.168.1.206//rest/get/vars/1/1 works perfectly. This works to both the isy and the polisy. From the network module on the polisy, I try the same and get a 'TCP client request failed [Net Module Rule 1:715]'. I have it setup as follows I'm sure I have a setting incorrect, but have tried just about every one. If I put in an incorrect password for the authorization I get a different error with a 401 Error, so I know its talking to the isy. I have also tried different rest commands. These all work from Chrome. I have tried this also from the isy to the polisy. I used https and 8443 for the port - got the same type of errors. Any suggestions are welcome. Thanks
Solution Goose66 Posted July 12, 2023 Solution Posted July 12, 2023 You say you tried it in Chrome, do you mean you typed it into address bar and it worked? If so, then change your HTTP command here to GET. 1 1
bob123 Posted July 12, 2023 Author Posted July 12, 2023 Goose66 - thanks so much. Changing to an Http get did the trick. Thought I had tried that previously but guess not. Knew it was something simple. Much appreciated. 1
larryllix Posted July 12, 2023 Posted July 12, 2023 When I was in this process I set up a bank of state variables that were cloned in my polisy. I created a program triggered by any variable that changed and sent them allover to my polisy. With variable control over banks of lights in my home, it was so easy to setup and each program could be ported over to the new device without any interruption of any lighting controls or scenes. I was going to do the reciprocal to send any changes back to my ISY at which point I decided to commit and retire my ISY instead. It was a lot of fun synchronising the two boxes but it was time to walk away.
bob123 Posted July 12, 2023 Author Posted July 12, 2023 That’s very close to my plan. Modify existing isy programs to work on triggering from sets of state variables so that I can transfer functionality gradually over to polisy with little modification. As you said, it’s getting time to fade away from my trusted isy.
bob123 Posted July 13, 2023 Author Posted July 13, 2023 I spoke too soon on success. Using the http Get works great from the polisy to the isy. I cannot get a similar call working from the isy to the polisy to set a variable. The error I get is TCP client request failed. [Net Module Rule: 30:404]. I have tried both the secure and insecure port (8443 and 8080). I know it’s reaching the polisy because an incorrect login password gives a different error message. Works fine from Chrome. Any ideas? thanks
DennisC Posted July 13, 2023 Posted July 13, 2023 The ISY is much slower, have you tried increasing your time out as suggested above? 1
bob123 Posted July 13, 2023 Author Posted July 13, 2023 The timeout was not the issue. It was my own late night testing. I started from scratch with new entries and it worked. I had a typo in the actual isy test command. Entered /rest/get/vars/1/1. It should be /rest/vars/get/1/1. I tested different timeouts from 800-3000 and all worked. thanks everyone for the assistance 1
Recommended Posts