Jump to content

Support thread for: ISY on Polisy (IoP) v5.4.2 (March 29, 2022)


Recommended Posts

Posted (edited)

Install on my dev Polisy, started ISY Launcher, select Admin Console -> LAN and it loads up 5.4.1 and I get error message that it's not compatible with 5.4.2?

Edit: Works fine loading from Cloud.

Edited by JimboAutomates
Posted (edited)

Updated to 5.4.2 went smooth. First Isy-on-P update that I did not have to re-enter username and password in Polyglot settings, Polisy GUI.

 

Excellent! 

Edited by MBell
spelling
Posted

Upgraded to 5.4.2 with no problems.

Curious about this enhancement: "Z-Wave: Added support for showing all Z-Wave native links available (in Node Level popup menu and Top level Z-Wave menu)".  What are the benefits of this new feature?

Posted
14 hours ago, peterathans said:

Upgraded to 5.4.2 with no problems.

Curious about this enhancement: "Z-Wave: Added support for showing all Z-Wave native links available (in Node Level popup menu and Top level Z-Wave menu)".  What are the benefits of this new feature?

It allows you to quickly see all the native links available for one or all of your Z-Wave controllers.  Normally you have to create a scene and then look at the link options between a Z-Wave controller and a Z-Wave responder to see if a native link is available.

Posted
14 minutes ago, Chris Jahn said:

It allows you to quickly see all the native links available for one or all of your Z-Wave controllers.  Normally you have to create a scene and then look at the link options between a Z-Wave controller and a Z-Wave responder to see if a native link is available.

Thanks @Chris Jahn I currently have some 12 Zwave devices on IoP, of which at least one a 700 series and the others mostly 500 series. I assume(d) that I would see the 'native links'  in the Event Viewer, but so far nothing shows when clicking on 'native links'  in any of the 12 devices.

Posted
17 hours ago, JimboAutomates said:

Install on my dev Polisy, started ISY Launcher, select Admin Console -> LAN and it loads up 5.4.1 and I get error message that it's not compatible with 5.4.2?

Edit: Works fine loading from Cloud.

This has probably been answered but this is normal now.  Clear JAVA cache (And apps) and it should work.  The start java app will download the proper version after doing this.

Posted
This has probably been answered but this is normal now.  Clear JAVA cache (And apps) and it should work.  The start java app will download the proper version after doing this.
It's downloading the AC from the ISY in LAN mode, so why is it necessary to clear the java cache for LAN and not Cloud?

Sent from my Pixel 6 Pro using Tapatalk

Posted

I dont know but I was testing a lot of versions for Michel like 5.4.0_1, 5.4.0_2, 5.4.0_3.

Those worked fine.

but every time it was a upgrade like 5.4.0, 5.4.1, 5.4.2, I had to do this and it fixed it every time.

Did it work for you?

Posted
10 hours ago, asbril said:

Thanks @Chris Jahn I currently have some 12 Zwave devices on IoP, of which at least one a 700 series and the others mostly 500 series. I assume(d) that I would see the 'native links'  in the Event Viewer, but so far nothing shows when clicking on 'native links'  in any of the 12 devices.

Same here. The Native Links does not seem to do anything.

Posted (edited)

Installed great with a single click of the reset button.

Wrote a test program to set a variable to [minutes from start of day] based on a trigger from another variable.
Bugs still exist in variable "last change time"  and [minutes from start of day] value

[minutes from start of day] returns the value since midnight plus the UTC offset = 23 hours x 60 minutes =  1380 @ 7:00 PM EDT. This has changed since last IoP version but still not calculated correctly.

"last change time" displays the time changed at UTC or four hours too early from EDT. Double the UTC Offset still. No change from previous IoP version.

Quote

TestVars - [ID 0002][Parent 0001]

If
        $State_1 > 0
Then
        $State_2  = [Minutes since start of day]
Else
   - No Actions - (To add one, press 'Action')

2139978716_Variabletimeerrors.thumb.jpg.8dfe9e65b4afe6607563649d0b8a7d50.jpg

 

Edited by larryllix
Posted
On 3/30/2022 at 5:15 AM, asbril said:

Thanks @Chris Jahn I currently have some 12 Zwave devices on IoP, of which at least one a 700 series and the others mostly 500 series. I assume(d) that I would see the 'native links'  in the Event Viewer, but so far nothing shows when clicking on 'native links'  in any of the 12 devices.

I think by accident one of the source file changes we made for this didn't get put back in time for this build.  When you click 'Show Native Links', you should see a popup window containing all the possible links (not the event viewer).  Apologies, it will be available in the next build.

  • Like 1
  • Thanks 1
Posted (edited)

One thing I noticed when I upgraded to 5.4.2 is my programs are not loading in the UI.

When I call the GetProgram Web Service I see all the programs are still there.

Just another note.  I also cleared the Java Cache and reinstalled the client.  The programs always show up in the mobile app.

If I restart ISY on the Polisy I can see the programs for a little while but then it just goes blank again.

From the Error Log

Fri 2022/04/01 10:49:27 AM    0    -170001    <s:Envelope><s:Body><u:GetNodeDef xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><id>0</id></u:GetNodeDef></s:Body></s:Envelope>
Fri 2022/04/01 10:49:27 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Fri 2022/04/01 10:49:28 AM    0    -170001    <s:Envelope><s:Body><u:RefreshDeviceStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><sid>uuid:29</sid></u:RefreshDeviceStatus></s:Body></s:Envelope>
Fri 2022/04/01 10:49:28 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Fri 2022/04/01 10:49:31 AM    0    -170001    <s:Envelope><s:Body><u:GetDisclaimerStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetDisclaimerStatus></s:Body></s:Envelope>
Fri 2022/04/01 10:49:38 AM    0    -170001    <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><name>/CONF/NET/WOL.CFG</name></u:GetSysConf></s:Body></s:Envelope>
Fri 2022/04/01 10:49:38 AM    0    -170001    <s:Envelope><s:Body><u:GetAllD2D xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetAllD2D></s:Body></s:Envelope>
Fri 2022/04/01 10:49:39 AM    0    -170001    <s:Envelope><s:Body><u:GetAllD2DStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><key></key></u:GetAllD2DStatus></s:Body></s:Envelope>
Fri 2022/04/01 10:52:40 AM    0    -170001    <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
Fri 2022/04/01 10:54:58 AM    0    -170001    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="http://www.universal-devices.com/wsdk/isy/3.0">   <soap:Header/>   <soap:Body>      <ns:GetProgram/>   </soap:Body></soap:Envelope>
Fri 2022/04/01 10:54:58 AM    0    -10011    n/a
Fri 2022/04/01 10:54:58 AM    0    -170001    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="http://www.universal-devices.com/wsdk/isy/3.0">   <soap:Header/>   <soap:Body>      <ns:GetProgram/>   </soap:Body></soap:Envelope>
Fri 2022/04/01 10:55:01 AM    0    -170001    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="http://www.universal-devices.com/wsdk/isy/3.0">   <soap:Header/>   <soap:Body>      <ns:GetProgram/>   </soap:Body></soap:Envelope>
Fri 2022/04/01 10:55:01 AM    0    -10011    n/a
Fri 2022/04/01 10:55:01 AM    0    -170001    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="http://www.universal-devices.com/wsdk/isy/3.0">   <soap:Header/>   <soap:Body>      <ns:GetProgram/>   </soap:Body></soap:Envelope>
Fri 2022/04/01 10:56:05 AM    0    -170001    <s:Envelope><s:Body><u:GetErrorLog xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetErrorLog></s:Body></s:Envelope>
 

Screen Shot 2022-04-01 at 10.58.10 AM.png

Edited by JPaul
Posted
On 3/30/2022 at 6:54 PM, larryllix said:

...

[minutes from start of day] returns the value since midnight plus the UTC offset = 23 hours x 60 minutes =  1380 @ 7:00 PM EDT. This has changed since last IoP version but still not calculated correctly.

"last change time" displays the time changed at UTC or four hours too early from EDT. Double the UTC Offset still. No change from previous IoP version. ...

 

Thanks, we reproduced the bugs and fixed them for the next build.

  • Like 2
Posted

I updated to 5.4.2 without any problems.  I'm trying to change a Z-Wave parameter using the popup box but it doesn't seem to work.  If I query a parameter, I don't see the current value and I don't see anything in the event viewer using level three.  If I try set, the parameter doesn't seem to change and there is no activity in the event viewer. Anybody try changing Z-Wave parameters with the new version?

Posted
18 minutes ago, mjrush said:

I updated to 5.4.2 without any problems.  I'm trying to change a Z-Wave parameter using the popup box but it doesn't seem to work.  If I query a parameter, I don't see the current value and I don't see anything in the event viewer using level three.  If I try set, the parameter doesn't seem to change and there is no activity in the event viewer. Anybody try changing Z-Wave parameters with the new version?

Just reproduced the bug .. apologies, it was introduced in this build.  Will be fixed for the next one.

As a workaround, you can use a programs to change them until the fix is available.

Posted (edited)

Not sure when this happened, but today I checked updates in PG3 and there were 8 updates. I am now on PG3 3.0.55

Rebooting entire Polisy after updating I notice IoP is not working correctly with Z-Wave.

I troubleshoot a while and determine that something in my custom query program on startup is causing the issue. I narrow it down to when I query my Yale Z-Wave lock it fails (maybe bad communication) and then all future Z-Wave query or control on any other device fails after this. I have to restart the entire Polisy for Z-Wave to work again. This is repeatable and I have restarted Polisy about half a dozen times while troubleshooting this.

Not sure if this has anything to do with updates I did today, or not, but the regular Query All program has been running at 3am and my Z-Wave continued to work. I will see tomorrow if Query All breaks Z-Wave when I let it run overnight at 3am.

Querying a Z-Wave device and having it fail should not cause Z-Wave to fail requiring Polisy reboot.

EDIT: Z-Wave worked this morning and the Query All did run. I also did manually query the lock again and I did not experience the same issue.

I was working on this remotely and maybe the lock got into a weird state... the lock continued to report lock/unlocks yesterday. I still don't think Z-Wave entirely should have been affected unless maybe the lock was spamming the network after its query.

 

Edited by brians
Posted
1 hour ago, brians said:

Not sure when this happened, but today I checked updates in PG3 and there were 8 updates. I am now on PG3 3.0.55

@brians I updated to have a look, there were 12 updates for me.

The update went fine and querying the Z-Wave devices seems ok and no unusual behavior.

I have a Z-Wave switch and a plugin dimmer module mixed with an Insteon switch and plugin dimmer. I use the Zooz and Insteon usb controller sticks.

Posted
9 hours ago, brians said:

Not sure when this happened, but today I checked updates in PG3 and there were 8 updates. I am now on PG3 3.0.55

Rebooting entire Polisy after updating I notice IoP is not working correctly with Z-Wave.

I troubleshoot a while and determine that something in my custom query program on startup is causing the issue. I narrow it down to when I query my Yale Z-Wave lock it fails (maybe bad communication) and then all future Z-Wave query or control on any other device fails after this. I have to restart the entire Polisy for Z-Wave to work again. This is repeatable and I have restarted Polisy about half a dozen times while troubleshooting this.

Not sure if this has anything to do with updates I did today, or not, but the regular Query All program has been running at 3am and my Z-Wave continued to work. I will see tomorrow if Query All breaks Z-Wave when I let it run overnight at 3am.

Querying a Z-Wave device and having it fail should not cause Z-Wave to fail requiring Polisy reboot.

 

I had this issue too yesterday.  Yale Z-Wave locks also.   I did update neighbors to all powered devices in order from the Polisy to the furthest device.  It you go to event viewer you should get success on each one.

Then do update neighbors on yourr locks last.  At that point all locks worked but one.   On that one i took out the batteries for 30 seconds (not the z-wave module) and then put back in and then waited a minute for lock to reboot.  Then I updated neighbors on that lock and it worked.  Now they are all working.

Posted
11 hours ago, Chris Jahn said:

Thanks, we reproduced the bugs and fixed them for the next build.

I also noted (later) that the displayed time on the admin console, top left, displays the year 1952.

Posted

I disabled an insteon motion sensor.

 
It kept working.
 
So I had to disable the programs that it uses.
 
I did confirm it has the red circle over the device.
 
Confirmed with another insteon device also.
 
Guest
This topic is now closed to further replies.

×
×
  • Create New...