Jump to content

Beaker

Members
  • Posts

    35
  • Joined

  • Last visited

Recent Profile Visitors

730 profile views

Beaker's Achievements

Member

Member (3/6)

5

Reputation

  1. Thank all for the assistance. Responses to the above questions/suggestions: Q - When you run the then clause does the device tree show it running (solid green)? After running the Then clause, the program turns on the green indicator but the actual device never turns on in the devices tree. Q - Can you turn on the device “Irrigation / Irrigration-1 - Z1 Front Lawn” from device tree in the AC and confirm it actually turns on in the yard?: Yes, Since the upgrade, I've been manually cycling through each of the zones to irrigate the lawn. suggestion: I'd be sure to right click on the device in the AC and "update" it I will do this and if that does not work, I will remove and re-add the two controllers and re-configure each zone and see if that helps. Will report back on progress. Thank for the assistance. Cheers, Ken.
  2. Thanks Techman for reviewing. Here is the test program in clipboard format. New Program-TEST - [ID 003E][Parent 0008][Not Enabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Irrigation / Irrigration-1 - Z1 Front Lawn' On Wait 2 minutes Set 'Irrigation / Irrigration-1 - Z1 Front Lawn' Off Else - No Actions - (To add one, press 'Action') Cheers, Ken.
  3. OK. Here is a fresh three line program to turn an irrigation zone on, wait 2 minutes and shut it off. I tested it and the program shows as running but no irrigation. <?xml version="1.0" ?><triggers><d2d><trigger><id>62</id><name>New Program-TEST</name><parent>8</parent><if></if><then><cmd id="DON" node="23 8D E8 1"></cmd><wait><minutes>2</minutes></wait><cmd id="DOF" node="23 8D E8 1"></cmd></then><else></else><comment></comment></trigger></d2d></triggers> Cheers, Ken.
  4. Greetings, Post my upgrade to v5.8.4, I came across an issue with programs that I use to automate my irrigation setup. I have two SmarTENiT model # 5010A, 8 zone controllers. I am able to manually turn on any of the zones via highlighting the device and turning it on, watering starts as expected. But my program will not run through the zones even though the program shows as running. I have tried writing a new programs several times, simple one-liner in the Then statement that turns on one of the zones. I rune the Then statement but same results, no irrigation. All other programs that do not reference the irrigation controllers appear to work fine. Has anyone seen similar issues with programming or is it that my controllers are no longer supported? Any suggestions/help you can provide would be great. Cheers, Ken.
  5. thanks all for the intel. I'll put in a ticket to get the details on how to best recover. Cheers, Ken.
  6. Greetings. I've gone ahead and performed the upgrade. After install I am able to log into the management console and all my devices are listed etc. I come to find that I can no longer manage any devices. Z-Wave and Zigbee report not responding and my PLM status report not connected. I have power cycled the system and restarted the IoX several times with no success. Is there something additionally I can try? Cheers, Ken.
  7. Cheers dbwarner5 for the tip on the startup program to confirm any programs that should be disabled. Ken.
  8. Greetings... Any status update on the polisy OS update to 13.2? UPDATE: Sep. 29 Just executed a package update and 13.2 was successfully installed. Cheers, Ken.
  9. Greetings. Having issues with PKG failing with an error condition. Just recently it is complaining that it's having issue with the public key for the UDI repository. Has anyone else experienced this? Any assistance in a resolution would great. pkg: -----BEGIN PUBLIC KEY----- MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAxTMqmSpfMcy2Cg0OEOfo lj7xl0shuUNGKmPWksD2fUc8cXb4dOsLtKiuz25k2liU09c8wYNlHZcy/HKIWyvk n8Rj340GM3vd/uLsOn0dBZ7Zv/7kYKCIqyWZv1RGj6E3dFM9hQVpBl/FGVVJXDoV JMvZ3ZWP4Srr98kigYUA/Y2LSiuNbB2eLsHaWkkoPktjVPNuo0tFLSLzOaZweP34 1yhjiHT/FV9tEQ6/LZqGfHYBoAu1hBg4CGXzJoLBDrneMIq5GnSgfR+XqWe7xM2l 4vuUDh76S/lQFLtT220K1kg8ucQJIX8zHZI/clg6A1cfsC0yPls1FaumYKVRx1pw pSxPj42SRqN1kwjOFF79bB24OdPFUAFj7MZzL2tT8tlYsF5yfSNWfixCocBD+9Ql q16vanYtQkbwgP2v/rRBK6zeIGPd6ECkspUn7P42DP7reOyZAfFVceFXyS4O7vMv 3c5n1JwmVSNyfj5kCoPGS1cT6dQNCd/olIlRn2KRmu+j9cwfRlljpAWYKj2vHdz/ HIZGUjvqBT4io6UgUSOqM+9OxEONoXGOEzuKzG91MIVqvOenXr/ykTvBbFvudk1q nuLOuzHerDcdiIvfcJAdK2QHJ3I+yQGxHmhB3cBlAqUbJdIb5t6b2JuNX4ANnDNv vzad3n4NnxGJS5sElx/xs8kCAwEAAQ== -----END PUBLIC KEY----- : rsa signature verification failure pkg: Invalid signature, removing repository. Unable to update repository udi Error updating repositories! Cheers, Ken
  10. Cheers, thanks for the response. do the restart and still no luck. Started reading through the thread that MrBill noted above. It was noted that pg3 and PG3X needed to be re-upgraded. Currently my Polisy only has pg3 install. Is PG3X only for eisy or do I need to reinstall PG3X? Cheers, Ken.
  11. Question. Chris noted above "Please upgrade packages again, PG3X & PG3 should be working again." Are both packages required on Polisy or is PG3X only required for eisy? I'm still having issues, Polisy reports PG3 is up to data but PG3X is not installed. Cheers, Ken.
  12. Greetings, Having issues with pkg upgrade. I initiated the package upgrade via the Poliisy console. The Console exited out as expected and all appeared good. waited several minutes and attempted to log into the Polisy console and found that the Polisy was no longer listed in the launcher. Attempted to re-add it an unable to connect error was generated. Rebooted the Polisy from the command line but still no luck. The following warning messages I noted in the messages file: /etc/rc: WARNING: $ud_pkg_stat_enable is not set properly - see rc.conf(5) From here I executed the following command, sudo pkg upgrade -Fn , and found that the following package was listed for upgrade: node19: 19.5.0 [udi] At this point given I'm not able to get into the Policy console via the ISY Launcher, I manually attempted to upgrade node19: 19.5.0 from the Polisy command line and this resulted in the following error: pkg: node19-19.5.0 conflicts with node18-18.13.0 (installs files into the same place). Problematic file: /usr/local/bin/corepack. Has anyone seen anything similar and/or can assist in further troubleshooting? Cheers, Ken
  13. Posting here as I have a similar question as it relates to the Polisy restore process. I'm finally getting around to migrating to the Polisy but have not installed the Zwave/Matter upgrade kit yet. My question is should I install it before or after restoring the config to Polisy? I assume the kit should be installed prior restoring the config but wanted to confirm. Cheers. Ken.
  14. Thank you for the quick response. worked like charm. Cheers, Ken.
  15. I recently attempted to perform a package update on Polisy. After kicking of the process via the IoP console I waited aprox. 30 minutes, SSHed into the Polisy to find that the process was still running. Seemed odd that it hadn’t completed, I kicked off the following cmd ‘sudo tail -f /var/udx /logs/log’ to find the pkg upgrade process in an endless loop. It was basically complaining that the pkg command itself had to be upgraded first but it was not taking place and continued to loop. I’ve posted a snapshot of the above noted log. The below block of text continued to fill the log file. Any assistance would be great. Cheers, Ken. Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. New version of pkg detected; it needs to be installed first. Checking integrity... done (0 conflicting) The most recent versions of packages are already installed Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. New version of pkg detected; it needs to be installed first. Checking integrity... done (0 conflicting) The most recent versions of packages are already installed
×
×
  • Create New...