Michel Kohanim Posted December 3, 2021 Posted December 3, 2021 Fixes: - Time zone reverts to LA - Support for SNI in Network Resources - SMTP sends truncated messages or creates attachments - Node servers show numbers instead of a formatted string Enhancements: - Support for Z-Wave (Test build) - You can now define custom latitude/longitude just like you did on ISY - Support for IPv6 web server in double stack mode (both IPv4 and IPv6)Bugs: - In some cases, Polisy will only allow IPv6. If you cannot get to Polisy using the Admin Console, please wait 60 seconds and then reboot - USB connected dongles (such as the PLM or Z-Wave Zooz Stick), cannot be unplugged and then plugged back in while ISY service is running. If, for any reason, you need to unplug, please use the Admin Console | Configuration tab | Reboot button to restart the service How To Install: - First, backup please! - If on 5.1.1, Admin Console | Help | Automatically Upgrade. Once the Admin Console closes, wait 30 seconds before trying again. If Polisy does not show up in the ISY Launcher, please wait 60 seconds and reboot - Otherwise, ssh and do: sudo pkg update && sudo pkg upgrade How to use Z-Wave: - Plugin your Zooz Stick in one of the USB ports on ISY - Go to Admin Console | Configuration, check Z-Wave Support checkbox. Save and then click on the Reboot button - From that point, Z-Wave works as it does on the ISY-994 with the following exceptions --- Backup/Restore of the Z-Wave dongle is not yet available --- Z-Wave | Z-Wave Version is likely to be blank - Note: for now, S2 is not yet supported With kind regards, Michel 7
larryllix Posted December 3, 2021 Posted December 3, 2021 (edited) Away for another two weeks glued to pool and tropical drinks. Can't test run for another two weeks. Sent from my SM-G781W using Tapatalk Edited December 3, 2021 by larryllix 1 2 1
MrBill Posted December 3, 2021 Posted December 3, 2021 (edited) 6 hours ago, Michel Kohanim said: - If on 5.1.1, Admin Console | Help | Automatically Upgrade. Once the Admin Console closes, wait 30 seconds before trying again. If Polisy does not show up in the ISY Launcher, please wait 60 seconds and reboot Was on 5.1.1, choose automatically upgrade. waited much longer than 30 seconds (got sidetracked), finder didn't find it. Rebooted polisy... waited much longer than a few minutes (sidetracted again), finder still doesn't find it. Tried to manually add http://192.168.1.89:8080/desc , Not found. -------------- Edit: sudo pkg update && sudo pkg upgrade and sudo service isy restart solved... Edited December 3, 2021 by MrBill
tazman Posted December 3, 2021 Posted December 3, 2021 I did the update but mine was stuck in a system busy loop that would not go away. Then through the command line I removed ISY and Installed it, I wanted to start over from there but I can never get ISY to have a portal tab in a fresh install state so I restored my backup and everything is back to where it was. I added 1 Z-Wave device and it is working fine so far. I want to just switch everything over but my the weird error log I'm getting has me concerned and I also have issues with node servers at times. NaN/NaN/NaN NaN:NaN:NaN System -5 Start NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/TMP NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/LOG NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/WEB NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CODE NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF/D2D NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF/MAIL NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/USER NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/USER/WEB NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF/NET NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF/SEP NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF/OADR NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF/BILLING NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF/DEF NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/GLOBAL NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/GLOBAL/i1 NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/GLOBAL/i1/nls NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/GLOBAL/i1/editor NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/GLOBAL/i1/nodedef NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/f1 NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/f1/i1 NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/f1/i1/nls NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/f1/i1/editor NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/f1/i1/nodedef NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/DEF/f1/i1/emap NaN/NaN/NaN NaN:NaN:NaN System -110026 ./FILES/CONF/DEF/f10 NaN/NaN/NaN NaN:NaN:NaN System -110022 ./FILES/CONF/UZW0001.BIN NaN/NaN/NaN NaN:NaN:NaN System -110012 ./FILES/CONF/UZW0001.BIN NaN/NaN/NaN NaN:NaN:NaN System -110022 ./FILES/CONF/UZW0001.BIN NaN/NaN/NaN NaN:NaN:NaN System -110012 ./FILES/CONF/UZW0001.BIN NaN/NaN/NaN NaN:NaN:NaN System -110022 ./FILES/CONF/UZW0001.BIN NaN/NaN/NaN NaN:NaN:NaN System -110012 ./FILES/CONF/UZW0001.BIN NaN/NaN/NaN NaN:NaN:NaN System -170001 UDQ: Queue(s) Full, message ignored NaN/NaN/NaN NaN:NaN:NaN System -110022 ./FILES/CONF/INSTENG.OPT NaN/NaN/NaN NaN:NaN:NaN System -110012 ./FILES/CONF/INSTENG.OPT NaN/NaN/NaN NaN:NaN:NaN System -140005 ISY NaN/NaN/NaN NaN:NaN:NaN System -50001 -1 NaN/NaN/NaN NaN:NaN:NaN System -7030 n/a NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetISYConfig xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetISYConfig></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:Authenticate xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><name>tazrules</name><id>Big22fat.</id></u:Authenticate></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetStartupTime xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetStartupTime></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><name>/CONF/INTEGER.VAR</name></u:GetSysConf></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><name>/CONF/STATE.VAR</name></u:GetSysConf></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><type>1</type></u:GetVariables></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><type>2</type></u:GetVariables></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetNodesConfig xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetNodesConfig></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemTime xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemTime></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:SetDebugLevel xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><option>1</option></u:SetDebugLevel></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemOptions xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemOptions></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:Subscribe xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><reportURL>REUSE_SOCKET</reportURL><duration>infinite</duration><send>F</send></u:Subscribe></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:IsSubscribed xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><SID>uuid:26</SID></u:IsSubscribed></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -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> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:RefreshDeviceStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><sid>uuid:26</sid></u:RefreshDeviceStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetDisclaimerStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetDisclaimerStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>QUERY</control><action></action><flag>65531</flag><node>n005_50029132c0dd</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>QUERY</control><action></action><flag>65531</flag><node>n005_10521ccc6c6e</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>QUERY</control><action></action><flag>65531</flag><node>n005_10521ccc6c6e</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>DISCOVER</control><action></action><flag>65531</flag><node>n005_controller</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>QUERY</control><action></action><flag>65531</flag><node>n005_10521ccc6c6e</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>QUERY</control><action></action><flag>65531</flag><node>n005_50029132c0dd</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>DON</control><action></action><flag>65531</flag><node>n005_50029132c0dd</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -140005 ISY NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetLastError xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetLastError></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:ClearLastError xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:ClearLastError></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>DOF</control><action></action><flag>65531</flag><node>n005_50029132c0dd</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>DON</control><action></action><flag>65531</flag><node>n005_10521ccc6c6e</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>DOF</control><action></action><flag>65531</flag><node>n005_10521ccc6c6e</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>QUERY</control><action></action><flag>65531</flag><node>n005_10521ccc6c6e</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:UDIService xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><control>QUERY</control><action></action><flag>65531</flag><node>n005_50029132c0dd</node></u:UDIService></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> NaN/NaN/NaN NaN:NaN:NaN System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>
bgrubb1 Posted December 4, 2021 Posted December 4, 2021 I upgraded via SSH and had issues (1) after reboot finder complained that admin console was 5.1.1 and needed to be 5.2 delete, update java, clear cache, reinstall fixed that (2) finder see's the Polisy, but with a UUID of 00:00:00:00:00:01 admin console loads but is in a continuous loop of refreshing views (3) reboot and UUID correct, but wont launch admin console from finder (4) sudo service isy restart, now appears up and working now off to Zwave ...Barry
MWareman Posted December 4, 2021 Posted December 4, 2021 (edited) I backed up (of course!) I was on 5.1.1. "Admin Console | Help | Automatically Upgrade" I was offered '5.2.1' - and I selected to upgrade. After about a minute - I restarted the ISY finder - and if found Polisy version 5.2.0 Connecting - I have this dialog. It's making progress - but *very* slow. I'm going to let that complete. Meanwhile - some programs are reporting 'Out of memory': I have another reboot to go (to test zwave) but I'm going to wait for the 'System Busy' to complete before continuing... Edit: almost 15 mins of the above dialog - it got to 100% - then this dialog appeared: Edit2: 15 minutes the above is at 99% and iminent. Meanwhile, my location is 'unknown' after the upgrade: Tried changing it to the correct location - and I got this: Meanwhile - the 'System Busy' dialog dissappeared for a couple of seconds - and was replaced... with a new one: Edited December 4, 2021 by MWareman 1
larryllix Posted December 4, 2021 Posted December 4, 2021 It sounds like........A Long and Winding Load!Sent from my SM-G781W using Tapatalk 1
tazman Posted December 4, 2021 Posted December 4, 2021 @Michel KohanimI added another Z-Wave device but it is not functioning properly https://www.amazon.com/gp/product/B01LWMTUI8/ref=ox_sc_saved_title_5?smid=A1O77D5UJY7IVU&psc=1 Nodes on ISY <node flag="128" nodeDefId="UZW0003"> <address>ZW011_1</address> <name>ZW 011 Notify Sensor</name> <family>4</family> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW011_1</pnode> <rpnode>ZW011_1</rpnode> <sgid>1</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>185</cat> </devtype> <ELK_ID>A02</ELK_ID> </node> <node flag="0" nodeDefId="UZW0004"> <address>ZW011_104</address> <name>ZW 011 Binary Sensor 1</name> <family>4</family> <parent type="1">ZW011_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW011_1</pnode> <rpnode>ZW011_1</rpnode> <sgid>104</sgid> <custom flags="40" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>104</cat> </devtype> <ELK_ID>A03</ELK_ID> <property id="ST" value="100" formatted="On" uom="78"/> </node> <node flag="0" nodeDefId="UZW0005"> <address>ZW011_306</address> <name>ZW 011 Access Control Alarm</name> <family>4</family> <parent type="1">ZW011_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW011_1</pnode> <rpnode>ZW011_1</rpnode> <sgid>306</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>306</cat> </devtype> <ELK_ID>A04</ELK_ID> </node> <node flag="0" nodeDefId="UZW0006"> <address>ZW011_184</address> <name>ZW 011 Barrier 1</name> <family>4</family> <parent type="1">ZW011_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW011_1</pnode> <rpnode>ZW011_1</rpnode> <sgid>184</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>184</cat> </devtype> <ELK_ID>A05</ELK_ID> <property id="ST" value="100" formatted="Open" uom="97"/> </node> <node flag="0" nodeDefId="thingnodetype"> <address>n004_fdlockeded</address> <name>FD Locked</name> <family instance="4">10</family> <parent type="1">n004_controller</parent> <type>0.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n004_controller</pnode> <ELK_ID>A06</ELK_ID> </node> <node flag="0" nodeDefId="UZW0008"> <address>ZW011_308</address> <name>ZW 011 Home Security Alarm</name> <family>4</family> <parent type="1">ZW011_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW011_1</pnode> <rpnode>ZW011_1</rpnode> <sgid>308</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>308</cat> </devtype> <ELK_ID>A07</ELK_ID> </node> <node flag="0" nodeDefId="UZW0009"> <address>ZW011_173</address> <name>ZW 011 Tamper Code Alarm 1</name> <family>4</family> <parent type="1">ZW011_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW011_1</pnode> <rpnode>ZW011_1</rpnode> <sgid>173</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>173</cat> </devtype> <ELK_ID>A08</ELK_ID> <property id="ST" value="" formatted=" " uom="0"/> </node> Node on Polisy <node flag="128" nodeDefId="UZW0077"> <address>ZW004_1</address> <name>ZW 004 Notify Sensor</name> <family>4</family> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW004_1</pnode> <rpnode>ZW004_1</rpnode> <sgid>1</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>185</cat> </devtype> </node> <node flag="0" nodeDefId="UZW0078"> <address>ZW004_104</address> <name>ZW 004 Binary Sensor 1</name> <family>4</family> <parent type="1">ZW004_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW004_1</pnode> <rpnode>ZW004_1</rpnode> <sgid>104</sgid> <custom flags="40" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>104</cat> </devtype> <property id="ST" value="100" formatted="On" uom="78"/> </node> <node flag="0" nodeDefId="UZW0079"> <address>ZW004_306</address> <name>ZW 004 Access Control Alarm</name> <family>4</family> <parent type="1">ZW004_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW004_1</pnode> <rpnode>ZW004_1</rpnode> <sgid>306</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>306</cat> </devtype> </node> <node flag="0" nodeDefId="UZW007A"> <address>ZW004_184</address> <name>ZW 004 Barrier 1</name> <family>4</family> <parent type="1">ZW004_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW004_1</pnode> <rpnode>ZW004_1</rpnode> <sgid>184</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>184</cat> </devtype> <property id="ST" value="" formatted=" " uom="0"/> </node> <node flag="0" nodeDefId="UZW007B"> <address>ZW004_308</address> <name>ZW 004 Home Security Alarm</name> <family>4</family> <parent type="1">ZW004_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW004_1</pnode> <rpnode>ZW004_1</rpnode> <sgid>308</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>308</cat> </devtype> </node> <node flag="0" nodeDefId="UZW007C"> <address>ZW004_173</address> <name>ZW 004 Tamper Code Alarm 1</name> <family>4</family> <parent type="1">ZW004_1</parent> <type>4.7.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW004_1</pnode> <rpnode>ZW004_1</rpnode> <sgid>173</sgid> <custom flags="8" val1="0"/> <devtype> <gen>4.7.1</gen> <mfg>410.3.3</mfg> <cat>173</cat> </devtype> <property id="ST" value="" formatted=" " uom="0"/> </node> The Barrier and alarm nodes shows open and closed on ISY but does not register anything on Polisy. I used the same strip on both devices so I know the strip works.
randyth Posted December 4, 2021 Posted December 4, 2021 4 hours ago, MWareman said: I backed up (of course!) I was on 5.1.1. "Admin Console | Help | Automatically Upgrade" I was offered '5.2.1' - and I selected to upgrade. After about a minute - I restarted the ISY finder - and if found Polisy version 5.2.0 Connecting - I have this dialog. It's making progress - but *very* slow. I'm going to let that complete. Meanwhile - some programs are reporting 'Out of memory': I have another reboot to go (to test zwave) but I'm going to wait for the 'System Busy' to complete before continuing... Edit: almost 15 mins of the above dialog - it got to 100% - then this dialog appeared: Edit2: 15 minutes the above is at 99% and iminent. Meanwhile, my location is 'unknown' after the upgrade: Tried changing it to the correct location - and I got this: Meanwhile - the 'System Busy' dialog dissappeared for a couple of seconds - and was replaced... with a new one: SSH into your Polisy and try this: sudo service isy restart That solved the problem for me.
MWareman Posted December 4, 2021 Posted December 4, 2021 2 hours ago, randyth said: SSH into your Polisy and try this: sudo service isy restart That solved the problem for me. Wow - I stepped away for a few hours - and came back to the same busy dialog. Seems to have been repeating and repeating. The 'sudo service isy restart' solved the issue where a full Polisy reboot did not appear to. Thank you!
MWareman Posted December 4, 2021 Posted December 4, 2021 (edited) 2 minutes ago, MWareman said: Wow - I stepped away for a few hours - and came back to the same busy dialog. Seems to have been repeating and repeating. The 'sudo service isy restart' solved the issue where a full Polisy reboot did not appear to. Thank you! Maybe I was too fast. My admin console went to 'Ready' - but knowing Java I figured it disconnected. So - exited the admin console and re-opened it. And - back to this: Edit: I guess I was impatient. This one only lasted a few mins. Edited December 4, 2021 by MWareman
MWareman Posted December 4, 2021 Posted December 4, 2021 @Michel Kohanim The variable substitution issue does not appear resolved. Here are the properties of the timedata NR on a physical ISY (5.3.3): <properties> <property id="GV0" value="20" formatted="20" uom="0"/> <property id="GV1" value="32" formatted="32" uom="0"/> <property id="GV10" value="2" formatted="Autumn" uom="25"/> <property id="GV11" value="0" formatted="False" uom="2"/> <property id="GV12" value="0" formatted="0" uom="0"/> <property id="GV13" value="0" formatted="False" uom="2"/> <property id="GV14" value="8108" formatted="8108" uom="0"/> <property id="GV15" value="18965" formatted="18965" uom="0"/> <property id="GV16" value="10" formatted="Debug" uom="25"/> <property id="GV2" value="4" formatted="4" uom="0"/> <property id="GV3" value="12" formatted="December" uom="25"/> <property id="GV4" value="2021" formatted="2021" uom="0"/> <property id="GV5" value="5" formatted="Saturday" uom="25"/> <property id="GV6" value="49" formatted="49" uom="0"/> <property id="GV7" value="338" formatted="338" uom="0"/> <property id="GV8" value="0" formatted="EVEN" uom="25"/> <property id="GV9" value="486512" formatted="486512" uom="0"/> <property id="ST" value="1" formatted="True" uom="2"/> </properties> Here are the properties for the exact same nodeserver when paired with Polisy/ISY running : <properties> <property id="GV0" value="14" formatted="14" uom="0"/> <property id="GV1" value="35" formatted="35" uom="0"/> <property id="GV10" value="2" formatted="2" uom="25"/> <property id="GV11" value="0" formatted="False" uom="2"/> <property id="GV12" value="-6" formatted="-6" uom="0"/> <property id="GV13" value="0" formatted="False" uom="2"/> <property id="GV14" value="8102" formatted="8102" uom="0"/> <property id="GV15" value="18965" formatted="18965" uom="0"/> <property id="GV16" value="10" formatted="10" uom="25"/> <property id="GV2" value="4" formatted="4" uom="0"/> <property id="GV3" value="12" formatted="12" uom="25"/> <property id="GV4" value="2021" formatted="2021" uom="0"/> <property id="GV5" value="5" formatted="5" uom="25"/> <property id="GV6" value="49" formatted="49" uom="0"/> <property id="GV7" value="338" formatted="338" uom="0"/> <property id="GV8" value="0" formatted="0" uom="25"/> <property id="GV9" value="486155" formatted="486155" uom="0"/> <property id="ST" value="1" formatted="True" uom="2"/> </properties> The 'formatted' value for the attribute 'GV3' (for instance) lists '12' instead of December'. The same is occurring on the ELK nodeserver. I have not tested others yet. Michael.
MWareman Posted December 4, 2021 Posted December 4, 2021 @Michel KohanimThe NR I have configured for debugging variable substitution in NRs not recognizing the # is also still not working. It wasn't called out as fixed for this release though. ${alert.event} I get: 'null null received' Michael.
gviliunas Posted December 4, 2021 Posted December 4, 2021 (edited) I tried including an Aeontech Multisensor 6. The device included without any trouble but it doesn't work. - It does not respond to motion - The only parameter reported is battery level (100% - But my sensor is USB powered. Note: I did a factory reset on the MS6 before including. Edited December 4, 2021 by gviliunas Include Event Viewer data on MS6
kzboray Posted December 4, 2021 Posted December 4, 2021 Upgraded yesterday and was unable to access the Polisy ISY from launcher. Tried reverting to 5.1.1 and still couldn't get it to work. Reinstalled 5.2 from SSH, rebooted, and restarted ISY and still no joy. Found an update around 11pm last night and tried that, no luck. Still couldn't access ISY. Went to bed then up today for another update and it's working great. Now on to playing with z-wave!!! Thank you @Michel Kohanim and team!
randyth Posted December 4, 2021 Posted December 4, 2021 I'm attempting to keep my ISY994i running in parallel with ISY/Polisy while I slowly migrate tasks from one to the other. Both are connected to the Portal with active licenses. However, the ISY Optimized for Smart Home v3 skill for Alexa refuses to find the devices/scenes entered for my Polisy via Select Tool->Connectivity->Amazon Echo. I have made several attempts at new device/scene discovery through voice ("Alexa, discover my devices"), the app, and the https://alexa.amazon.com/spa/index.html#smart-home site with no luck. Is this a known issue (perhaps the skill can't deal with multiple ISYs)? @larryllix, how did you handle this?
MrBill Posted December 4, 2021 Posted December 4, 2021 13 minutes ago, randyth said: I'm attempting to keep my ISY994i running in parallel with ISY/Polisy while I slowly migrate tasks from one to the other. Both are connected to the Portal with active licenses. However, the ISY Optimized for Smart Home v3 skill for Alexa refuses to find the devices/scenes entered for my Polisy via Select Tool->Connectivity->Amazon Echo. I have made several attempts at new device/scene discovery through voice ("Alexa, discover my devices"), the app, and the https://alexa.amazon.com/spa/index.html#smart-home site with no luck. Is this a known issue (perhaps the skill can't deal with multiple ISYs)? @larryllix, how did you handle this? Log into the portal and look for MyProfile in the Upper right corner. Change the dropdown to "Use All ALexa's on Account." 1
larryllix Posted December 4, 2021 Posted December 4, 2021 17 minutes ago, randyth said: I'm attempting to keep my ISY994i running in parallel with ISY/Polisy while I slowly migrate tasks from one to the other. Both are connected to the Portal with active licenses. However, the ISY Optimized for Smart Home v3 skill for Alexa refuses to find the devices/scenes entered for my Polisy via Select Tool->Connectivity->Amazon Echo. I have made several attempts at new device/scene discovery through voice ("Alexa, discover my devices"), the app, and the https://alexa.amazon.com/spa/index.html#smart-home site with no luck. Is this a known issue (perhaps the skill can't deal with multiple ISYs)? @larryllix, how did you handle this? I saw the dual and/to arbitration setting for dual ISY polisy situation but never attempted to use both. I felt I was past the commit point when I did it, just switched my ISY off and later deleted it from ISY Portal. Most of my Alexa vocals are for lighting levels and colour anyway and they were easy to switch over and test. I still have a few vocal varieties that have not been implemented yet. Every few days I find some other alternate lighting vocal missing from my selections. 1
randyth Posted December 4, 2021 Posted December 4, 2021 4 minutes ago, MrBill said: Log into the portal and look for MyProfile in the Upper right corner. Change the dropdown to "Use All ALexa's on Account." That's it! Thanks so much @MrBill 1
bgrubb1 Posted December 4, 2021 Posted December 4, 2021 I have the same issue as @gviliunas I installed a Ecolink motion sensor that I removed from the ISY It installed, but motion never turns off
bpwwer Posted December 5, 2021 Posted December 5, 2021 3 hours ago, gviliunas said: I tried including an Aeontech Multisensor 6. The device included without any trouble but it doesn't work. - It does not respond to motion - The only parameter reported is battery level (100% - But my sensor is USB powered. Note: I did a factory reset on the MS6 before including. I did the same thing, with similar results. Motion doesn't appear to work but I am getting temp, humidity, battery and luminance. I'm also powering mine via USB.
gviliunas Posted December 5, 2021 Posted December 5, 2021 (edited) @bpwwerI spent some time trying to duplicate your results with the MS6 and made some discoveries: - If I include the MS6 in "Secure Mode" (Press the MS6 button 2x when including), I get the Temperature, Humidity, Luminance, UV and Battery Level values displayed immediately after inclusion. Also, the values seem to update according to the interval time set in parameter 111. (I did not need to change the wakeup interval time for this to work) - If I include the MS6 in "Regular Mode" (Press the MS6 button 1x when including), I only see the Battery Level value displayed. Waiting here doesn't matter. The default MS6 reporting should be every 5 minutes. I waited ~15 minutes and still the other values failed to be displayed.....but can be coaxed-out.... - To see the other sensor values when the MS6 was included in "Regular Mode," I needed to click the "Wakeup" button on the Multi-level sensor node and then click to write updates to device. Once I did this, the sensor values were displayed. Notes: 1. Clicking the "Query" button at the bottom of the Multi-level sensor node page appeared to do nothing. 2. I did not set any particular wakeup interval - just left the default 0-seconds when I clicked wakeup. - Okay - Now I have initial values for the sensors when included in Regular Mode BUT, the values do not update. I changed the update interval parameter (111) to 10 sec and varied the light striking the sensor. The only way to see the displayed value change was to click the "Wakeup" button on the Multi-level sensor node and then click to write updates to device. BUT it only updates this one time. I need to change to a different wakeup interval time (greater than parameter 111 value) and click Wakeup to see an updated sensor value. So, it appears that when the MS6 is included in Secure Mode, sensors and sensor reporting appears to work normally while if included in "Regular Mode," the wakeup interval needs to be set and constantly changed to see or have updated sensor values. - In all attempts I could not get motion-sensing to work. Edited December 5, 2021 by gviliunas 1
Michel Kohanim Posted December 5, 2021 Author Posted December 5, 2021 @MWareman, Thank you very much for reporting. How many node servers do you have or, better yet, how many nodes that are node server based do you have? All, We'll review the Z-Wave status not reporting issues. With kind regards, Michel
MWareman Posted December 6, 2021 Posted December 6, 2021 13 hours ago, Michel Kohanim said: @MWareman, Thank you very much for reporting. How many node servers do you have or, better yet, how many nodes that are node server based do you have? 12 nodeservers currently configured to ISY/Polisy: Ring (PGC) has 18 nodes MyQ (PGC) has 3 nodes Push (PGC) has 13 nodes LiFX (Local) has 12 nodes WeatherflowPoly (Local) has 9 nodes Ping (Local) has 17 nodes UnifiPresence (Local) has 9 nodes ELK (Local) has 36 nodes NOAA (Local) has 1 nodes Timedata (Local) has 2 nodes Virtual (Local) has 2 nodes WirelessTag (Local) has 17 nodes Total appears to be 139 nodes via nodeservers. Thank you! Michael.
gviliunas Posted December 6, 2021 Posted December 6, 2021 SUCCESS with Aeontech Multisensor 6 Motion Detection with S0 mode inclusion @Michel KohanimI was going to dive back into my Aeontech M6 this morning to see if any settings changes could make motion detection work. The sensor was included under S0 secure mode yesterday. I discovered that MOTION DETECTION IS in fact WORKING along with the environment reporting. To test this, all parameters are default except I set the PIR timeout (parameter 3) to 10 seconds. I apologize for the incorrect report that motion sensing was not working. I think I did not wait long enough for the PIR to stabilize.
Recommended Posts