brians

I applied update remotely from my work and that update fixed ability to reboot IoP from the administrative console. What was other bug that is fixed?

Issue with UD mobile. Noticed after updating that if I removed and added isy/Polisy again then it does not show status of devices. I have a isy994i that I can add/remove to my iPhone and works normally. i had my iPhone not working properly as above but iPad was fine which made me wonder. So I just removed the Polisy on iPad and added again and now is broken like the iPhone however sync didn’t affect it seems that I had to remove it first.

After update I went and looked at mine and the left LED was solid green. I did a reboot via ssh because I could not get it to reboot from admin console or Polisy web, but it did not come back so I went and looked and the right LED was flashing. I hard rebooted Polisy and came back but after that I had flashing fast left green LED. Pressing the button 6 times cleared LED blinking instantly and now is solid green. I see no indication of any change otherwise. Still cannot reboot isy from admin console. UD Mobile on my iPhone does not seem to get status updates of devices, I get an error sometimes and I cannot read it all but at top of screen: Starting Service ERROR <?xml version="1.0" encoding="UTF-8"?><s:Envelope... I set UD Mobile to point to my old ISY 994i in portal, which has some test devices on it, and it works correctly so there is a bug introduced in ISY on Polisy 5.4.0 or I did something else on ISY coincidentally that it doesn't like. I was able to make my iPad, which worked before, do same thing now - by removing the portal and adding it again then it has status update problem like my iPhone now. For those that just sync an existing setup would probably not notice this.

Updated no issues so far with ISY itself. One thing I noticed is that UD Mobile on iPhone does not seem to update/show current status of devices, and is not consistent controlling devices. I will post more on appropriate forums regarding this after I test more. Update - seems to work fine on my iPad when I checked last night but not iPhone. I’ll check later what difference is eg. if I am going through portal or not on iPad.

Ok after updating isy on polisy to 5.4.0 i left it alone and started seeing updates from my pg3 ecobee. I then did a query from isy and everything populated. So I guess that is how it worked and I didn’t realize before. Pg2 I left alone and haven’t seen it in isy yet .

This seems to be a bug, I have the same issue reported here: But both my PG2 and PG3 have the issue, unlike OP that only experience with PG2. If there is a power failure or Polisy has to restart, then I have manually restart PG2/PG3 for ISY on Polisy to update.

Ok I have done some tests on my Polisy with Z-Wave and Insteon. Test 1: With one Insteon 2477D and a GE/Jasco Enbrighten ZW4008 Z-Wave in wall paddle switch - both added to an Insteon scene: Control from ISY is near instant to either switch, Insteon maybe a bit faster. Control from the 2477D turns on/off the Z-Wave switch near instant. Control from the Z-Wave switch takes about 2-3 seconds to turn on/off the 2477D Test 2: I remove both from scene and wrote a program that controls the 2477D from the Z-Wave switch status: Control from Z-Wave switch takes about the same as scene, 2-3 seconds. Looking at ISY, the on/off update is also slow 2-3 seconds delay from physically turning on/off the Jasco ZW4008 However, I just started using these Jasco switches and I also remember not as much issue with some other Z-Wave I have.... for example a Zen17 relay I use to monitor a pump I remember was nearly instant when shorting the dry connections with a paperclip testing and watching ISY... so I investigate a bit further because most all of my wall switches are Insteon, and Z-Wave is just used for things like appliance modules, dimmers, water shutoff etc. I am just starting to explore Z-Wave for wall switches so this is a bit new to me. It seems that these GE/Jasco ZW4008 model are slow sending out Z-Wave updates very slow compared to some other devices I have... in fact a Jasco Enbrighten in-wall motion switch ZW4006 is near instantaneous and is in very same gang box and I think that rules out a routing issue. A Leviton switch I have is also near instantaneous response on ISY when turning on/off physically, which is a surprise since it also has more overhead and processes a hail/query command because no instant status. I just got two ultra pro ZW4008 less expensive models that GE brand and they have same slow response 2-3 seconds. The ZW4006 (motion wall switch) would not control an Insteon scene like ZW4008 but a program does still work and is minimal delay. Update:I tested the same Ultra Pro Jasco ZW4008 on both Polisy with S2 dongle, and my ISY994i with 500 series Z-Wave module - there is no difference and both take 2-3 seconds to receive an update from the switch. I will test a Zooz plug soon in same location, removing and re-adding, and follow-up. I don't have any other Z-Wave light switches to test but will order one... any suggestions? Conclusion: Some Z-Wave devices are slow to report their status, and it seems right now that it is most likely not ISY's fault. Until more testing, I will not buy anymore Jasco switches for now for anything major... however I was just getting them for a couple bathrooms that I never bothered to install Insteon in the past, so not really going to be used in scenes. Maybe I will look at a Zooz switch next. Actually the only thing I use scenes for in Insteon is for virtual 3-way and linking keypads to buttons. Be interesting to hear if others who have issues can also determine if it is a particular brand/model of Z-Wave switch. Couple videos showing my test with Jasco Ultra Pro ZW4008... will test my Zooz plug which is the only other z-wave device that I have which has instant status. And I said earlier that my Leviton, with a hail program, respond almost instant on ISY when I physically turn on/off switch. IMG_8364.mov IMG_8360.mov

@asbrilSince you only use ISY, and have a lot of, Z-wave devices, I am curious why you are not using another controller? For the majority of people that use ISY, it is because they have a lot invested in Insteon. I just reloaded my old ISY994i with the Z-Wave only firmware. It is on 5.3.4 so I will see if there are any differences. I just got in a couple Jasco Ultra Pro switches I will test later. I remember now that I added a switchlinc relay to a Jasco switch that was a controller in a scene, and was also slow to respond 1-2 seconds... maybe it is just the keypadlinc that seem faster. A better test is later I will setup an Insteon 2477D as a controller for a Z-Wave lamp dimmer and see if performs the same as a keypadlinc key.

I am using ISY on Polisy 5.3.0 and do not have any of those Z-Wave Scene or Z-Wave association options.. When I create a Z-Wave only scene between a couple Jasco wall switches, it takes about 1-2 seconds for the other zwave switch to respond. Lets hope they fix this in a future update with association options. But having said that, if I create a program that detects a z-wave switch on, and turns on another z-wave, it is only about half a second in comparison to the scene method, therefore I think something may be wrong with ISY Z-Wave scene handling... there is some overhead there definitely and I think it should be faster. Also when controlling Z-Wave devices in a scene from an Insteon device eg. a keypadlinc button, it is fast with about the same short half second delay as my program. I also notice cosmetically that when adding a Z-Wave as a controller, the ISY does not "remember" it is a controller and I it only shows this device is a responder for.... scene name on the right pane. But there is a difference when looking in the actual scene and shows the pulldown option so it is in fact setting up as a controller. If I remove and re-add as responder only then it does not show the pulldown.

I have been following this thread... and I keep reading "if you are on 5.3.4", so is this something not available in current Polisy 5.3.0? I don't see this Scene or Association on any of my recent Z-Wave switches either - just default, command, ignore, so I presume that the ISY handles all of the scene communication in this case.

@Mr01Thanks! How does this mount to underneath of Polisy? Do I have to take the rubber feet off and does it screw in somehow? I was actually thinking Velcro before I saw this... time to dust off my 3D printer! Also, has anyone else noticed that when rubbing fingertip across Polisy it vibrates? I think it is just the material it is but it is a weird effect.

Here is video what I have to do to get running again... after about 15 min of waiting after restarting ISY on Polisy, it is still showing nodeserver offline. In PG2, a manual restart resolves. Img 8316.m4v

Here is a followup screenshot, I just restarted ISY on Polisy and this is only thing I seen around 21:21 when I restarted it. After 10 min ISY still shows this on Alarm Panel node from Envisalink-DSC... normally would show Connected. It is the same with Ecobee. It does not show NodeServer Online etc. I

The only other nodeserver I am running is EnvisaLink-DSC and that is still on PG2. I have left it all sit for over an hour after ISY on Polisy restart and does not sync up/connect (meaning I do not see any updates on ISY) - the only way is if I manually restart the nodeserver in PG2 or PG3. I am sure updates are happening in-between this time eg. a motion sensor from my DSC alarm would send an update. The Nodeserver online status in ISY is also blank in Ecobee controller, and Alarm Panel nodes (respective of each nodeserver), until I restart from the PG2/PG3. I do not see any obvious errors in the logs but not really sure what I am looking for.

This happens with both PG2 and PG3 Nodeservers. If I reboot the ISY on Polisy, the PG2 and PG3 still show connected but the nodes on ISY do not show any information. Manually restarting the nodeserver after reboot ISY on Polisy makes it reconnect. Pic after reboot ISY on Polisy Wait approx 10 min and still blank, PG3 still shows connected A few moments after pressing Restart and ISY on Polisy is updating This also happens on PG2 Issue is when I reboot entire Polisy, it does not sync up and I have to go into PG2/PG3 and restart. Currenty using ISY on Polisy 5.3.0 I just moved my Ecobee to PG3 thinking was limited to PG2 and wouldn't care as much since PG2 is old, but PG3 is same issue. Anyone else have this problem?

I don't see a Hue or LIFX nodeserver for PG3 in nodeserver store on my Polisy.

Dumb question, but I remove my current Z-Wave dongle from Polisy (shut down Polisy first) and plug in my PC. Then I run the software and update, then put back in Polisy? WIll this affect any settings for ISY on Polisy after plugging back in eg. does it reset the Z-wave dongle, or does this even matter? BTW, after installing simplicity studio, you can isolate the Z-Wave controller portion here... even zip it up and transfer to a new PC. C:\SiliconLabs\SimplicityStudio\v5\developer\tools\zwave\pc_controller Current version I show is 5.52.301

@Michel KohanimOk Please provide instructions how to retrieve the log. Brian

ISY on Polisy restarts - seems to be when doing a manual query all and having console open, the entire Polisy itself does not. I have not seen ISY on Polisy restart since Jan 30th and the Query 3am has been running fine.

@Michel KohanimIt is a 1.5A power supply. Brian

PG2 on the Polisy. When I restart entire Polisy device, it requires me to enter the password for ISY in settings. If I restart ISY while Polisy is running, the nodeservers on ISY do not update... I have to go into PG2 and simply restart each one then connection/updates resume instantly.

@Michel Kohanim I will let you know the power supply later when home. I edit my post above indicating that the query all ran fine at 3am this morning without reboot. I am thinking that it reboots when I run manual query program manually, and possibly while I am logged in the administrative console and watching... which what I did also after it kept rebooting on startup before (which is why I disabled query on restart). BTW, is this just a cosmetic glitch in system status?

Since last week I find my Polisy reboots over and over on startup. I got around this by disabling query at restart, then a manual query seemed to work but now I am not sure... I do notice today that when I run query all program the ISY will restart. The reason I want to query all is that I cannot turn on/off lights via ISY etc. if it does not know the current state. Seems that it seems to be spending an unusual amount of time on my Zooz Zen25 double plug with the system busy dialog. I think I will try to remove the plug and see what happens. Also every time ISY restarts, loses communication with PG2 and I have to go into dashboard and restart each node server. If I reboot the entire Polisy then I have to go and enter password in PG2 - seems to forget it. I am contemplating reverting back to ISY994i for now since I don't have time for this right now.. maybe will open a ticket and next update could resolve some of my issues. Edit... I just ran query all and I got a message that ISY has restarted and had to login, and ISY is now restarted! Edit 2... noticed that the query all program ran at 3am without restarting... seems that when I am logged into ISY using the Java program while it is running the program I get the restarted message...

I just upgraded to ISY on Polisy and my ZL-PD-100 dimmers work perfect. I even have it on a scene to an insteon keypadlinc button and dim up / down in real time from the keypadlinc.

I have recently moved to ISY on Polisy. I have only two Node Servers installed... Envisalink DSC and Ecobee. I notice that the communication at ISY end seems to not update after a while. I have to go into PG2 and restart each nodeserver which resolves. If I restart the ISY it usually causes this issue and have to go in PG2 and restart the nodeservers. Also there is issue with PG2 having a red message that it auto discovered my ISY and needs the password for ISY... I go into settings and enter password which resolves. It does not seem to remember the password. This also occurs after restarting PG2.