Everything posted by macjeff
-
New or Old PLM
only reason I really have it is the locks. what do you use (sorry I know we are getting off topic)
-
New or Old PLM
believe me I have felt the pain. And sometimes scenes dont work. So this makes it easier. So sounds like this will not be that bad to switch until I get to Z-wave. My two issues there are the Yale locks fail 9/10 times when installing or uninstalling. Once they are installed they are pretty flawless. My other issue is I have a large house and had to put in about 12 repeaters and i have dog crates in one room and they seem to absorb the signal so I had to put repeaters in the 4 corners of that room. I have perfect coverage now but probably 16-20 devices so get rid of each one and adding again is a few hour job. I guess I could leave on OLD ISY for a while.
-
New or Old PLM
I have a brand new unopened PLM I bought last time my PLM died so I would not have to be down. moving to ISY on Polisy with lots of Insteon from a 994i Should I use the existing PLM from the 994i or leave that and use a new PLM. I think the only difference is you have to do the procedure for a new PLM once you finish the backup restore of the ISY. I am thinking if it saves time (and potential headache) I should use the old PLM for now
-
Web page for ISY on Polisy
would be nice but not the end of the world. I am just beta testing and reporting what I find. I am about to go to ISY on Polisy (soon). Right now I just have it up and running but with nothing in it. I think a z-wave conversion built in would be more important!!!
-
Web page for ISY on Polisy
yes worked for me too thanks
-
PGC not working ? Is it down?
Me too and actually I am happy to not use it. Now everything is on Polisy. as of now my ISY is not but working on it. yes being ported now but not ready yet
-
Error Log formatting
yep but I am sure that can be fixed
-
Migration with Z-Wave
I have seen some posts about upgrading the firmware on Zooz stick. I have tried on PC and Mac using their Simplicity Studio. cant figure it out. Did it work for you? now back to the original question- So I exclude from ISY 994i, and then include on the IOP? Will take a while but I can do it. Jeff
-
Migration with Z-Wave
So I see there is no migration but if I move everything from old ISY Zwave to zoo stick and then do the ISY migration to polisy shouldnt it work. My issue is resetting these devices is a pain (some are locks and they dont reset easily) Would appreciate it if anyone could write up step by step to migrate z-wave without an official migration. If its not easy I may hold off on moving to ISY on Polisy
-
Error Log formatting
The error log is pretty hard to read. Maybe a future version could format it better.
-
Web page for ISY on Polisy
on my 994i Pro if I go to the URL in a web browser it pulls up a web page Not that i use it much but a quick way to see if my ISY had crashed. When I try this on 8080 or 8443 I get the UD favicon so i know its connecting but the page is blank white. Is this correct behavior? If so are they going to add a webpage?
-
Get Started (v1.3)
Got it working. My pg2 was on 8443. I changed that port to 4000 and instantly the pg2.
-
Get Started (v1.3)
Thats my IP range. The URL you gave me brings up the Pg2 interface. Change port to 3000 and you get Pg3 interface. My issue is getting ISY on Polisy. The Launcher wont find it. on 8443 or 8080 OS is at 13 rev p6. I dont think the ISY is running even though it says it is or if it is something is wrong.
-
Get Started (v1.3)
I am trying this for first time. I have ISY running but the status command does not seem to work sudo service status isy Password: status does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable [admin@polisy ~]$ sudo service isy enable isy enabled in /etc/rc.conf [admin@polisy ~]$ sudo service isy start isy already running? (pid=1234). [admin@polisy ~]$ sudo service status isy status does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable [admin@polisy ~]$ sudo service status isy status does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable [admin@polisy ~]$ And when I try to add in launcher at http://172.16.1.226:8080 it says not found. and I am sure thats my correct IP address. Do I have to enter some data into the Polisy? I tried going to http://172.16.1.226:8080 in a browser and it goes nowhere. I have another ISY 994i thats working fine. I was just going to give this a try. So my pg2 and pg3 points to old ISY.
-
PGC not working ? Is it down?
You will have to go to Polisy.
- Holidays?
-
Evapotransporation Bug?
I see you changed it in 2.04 to in/day. Thanks!!
-
WeatherBit PG3 Forecasts not showing in ISY
so far so good. It seems to be updating now. I will leave Pg2 and pg3 versions installed for a bit. as far as the other bug I posted about the Evapotransporation I will update that post next Will post here later with final OK!!
-
PG3 multiple weatherflows
so I hope you will add that. Meanwhile see the posts I put in Weatherbit. Had to revert to pg2 version. Actually have them both installed with two different API's. Pg2 version keeps on ticking. Pg3 I cant keep up for more than 30 min and only way to get it going again seems to be to delete the nodeserver and reinstall. Restarting it (or stop and start) does not get it working again.
-
PG3 on Polisy
Point well taken. I was told when I move to ISY on polisy I wont see as much of the speed issue. and with #7 maybe have it ask for login when it needs it. for now you have to click on the purchases tab and see that its not logged in and log in.
-
PG3 on Polisy
If it was part of the instructions I missed it. I thought it had to be in the ISY for the upgrade to see that you are running it. At least it was only one of the nodeservers and not all of them,. I can afford to lose one slot but not a dozen of them!!!
-
PG3 on Polisy
Here are my thoughts after spending some time doing the upgrade......This is FYI only. I know its beta (maybe alpha) and I love the challenge so please dont take this as an attack. 1. Upgrade needs some work. It did a few of them but then got stuck and failed. I posted the info. I am almost 100% sure due to the failure both Pg2 and pg3 dont have a nodeserver installed but they both show something is in the old slot which says managed. Posted on that too. 2. Installing nodeservers is a LOT slower. 3. It seems updating on the physical ISY is a lot slower after restart of ISY or Polisy. My pg2 things are updated way before my pg3 things. 4. I like the interface but wish there was a restart polisy option (at least I dont see it) to reboot the entire polisy. I do from command line or Pg2 has the option. 5. Updates need some work. As pointed out by Jimbo, no notification but they are coming. 6. Would be nice to be able to roll back to old versions if you have an issue. A lot of my things I run on pi have a menu you can install back versions. 7. Randomly and it could be after I reboot my computer or Polisy I have to login to Portal again. Wonder why its not auto logging in? 8. Love the new store and purchase options but every time I click on Store the first time I log in, it says error getting purchases. I have to then click on purchases and usually they pop up but as in #7 sometimes I have to log in again, and then go back to store and all is well. To summarize- THANK YOU for your work. Its a very good and mostly stable beta. Needs some work, but overall its usable. I hope the developers get rewarded for their hard work,. Again THANK YOU
-
PG3 on Polisy
Its climacell but tI dont think the issue is the nodeserver. Its the fact that Pg2 and Pg3 sees something in a database saying its still installed but its not. I assume the issue was caused by pg3 but both show it as managed so I cant do anything. ISY sees it but wont delete it. Tried running on a PC and two macs to make sure it was not some sort of local JAVA issue
-
PG3 on Polisy
I mentioned this on earlier post and after some PM with some developers I was told to email UD tech support so I did but I want to post basically what I sent them here. A nodeserver got screwed up in PG3 upgrade It was both in Pg3 and Pg2 after the install I did not realize it at first so I configured the Pg3 stuff. Then I realized it, So I deleted it from pg2 but the Pg3 one deleted at the same time. I checked and Both pg2 and pg3 show it as managed now Then I went to reinstall but the slot is still taken. I went into ISY and its there in nodeserver list. I go to configure and delete and get a Socket Error. Rebooted ISY and Polisy and same thing It is not in either the nodeservers (pg2) or ns (PG3) directory when I ssh. So it must be in a database. Any way to fix or am I out a slot?
-
Hue Nodeserver
I agree but I hope someone takes it on. I am buying Pg3 nodeservers so supporting the guys doing this. And reporting bugs too.