Jump to content

mbking

Members
  • Posts

    263
  • Joined

  • Last visited

Everything posted by mbking

  1. The update tonight fixed Polisy not returning a reply to a request for updates.
  2. I updated Polisy last night (100+ packages for FreeBSD to 13.0 p6 and a UDX upgrade) and Polisy no longer responds to a request for available updates. I get the usually message that it has submitted the request, but no response. Anyone else seeing this after a recent upgrade? This has happened before and was then fixed. This is a minor issue, but I do use it as a quick way of determining that updates are available and then ssh in to do the updates manually so I have a record of the changes. And when there are 100+ updates, it's nice to see the progress on the screen.
  3. @bpwwer, This could be a big deal in the future. I'm planning to replace my aging network equipment soon and had been planning to organize my IP's a little differently than what I have now. That was going to mean changing the IP for Polisy. I've used DHCP reservations to reserve IP's on my current network without setting a static IP on my devices and will do the same on the new network. It sounds like I need to set a static address on Polisy, but I've avoided that because of issues I remember people having early on getting that to work. Is that the best approach to avoid the problem you're describing here? Also, I use an ethernet connection and I don't see a way to set that to static. The WiFi settings seem to be there. Maybe I'm just looking at the configuration screen wrong.
  4. I've manually moved all devices from my ISY-994i to ISY on Polisy that do not integrate with my node servers. Those are working OK. Now I'm ready to move the remaining devices, delete the node servers from the ISY-994i, point PG2 to ISY on Polisy, and re-add the node servers. Are there any critical issues in the integration of PG2 and ISY on Polisy? If there are, I'll wait. Otherwise, I'm ready to make the move. Any input would be appreciated.
  5. Just wanted to recognize the quick response of the UD Mobile team regarding this issue. I haven't personally seen it, but the push notification was a quick and unexpected heads up and I appreciate that. I did a quick backup to insure I had the latest so I'm now prepared if it does impact my UD Mobile configuration. Nice support.
  6. Got it working; thanks!
  7. @Javi, I've had my ISY on Polisy and an ISY-994i connected to UD Mobile for testing. The ISY-994i could only be controlled locally because it used Mobilinc Connect for remote connections. I deactivated Mobilinc Connect and added the ISY-994i to the ISY Portal. Everything tests out OK and the license shows up in the ISY-994i. I've gone into Settings and turned on "Use ISY Portal for remote connections" and my Portal Account name shows up in the Portal Account window, same as for ISY on Polisy. When I click the Search symbol to get the Remote URL, I get a Portal login window, fill out login info and then get the following error. Not sure whether I'm doing something wrong or this is a bug. Any help would be appreciated. Mark
  8. @Javi, I've been continuing to test the iOS version of UD Mobile and I'm impressed with what can be done to customize the Favorites interface, especially being able to set color and formatted text based on conditions. It's working great. I especially like being able to set the HEX value for colors. I know there has been some discussion of adding a color picker in UD Mobile which i'm not opposed to, but I hope the user can retain the ability to enter a specific HEX value. This makes for a very customizable interface which is really nice. Just my two cents. Mark
  9. @Michel Kohanim, Will there be a backup/restore for just the node servers? I'm doing a manual transfer of my z-wave and insteon devices from ISY-994i to ISY on Polisy so I can reinstall after a factory reset of the devices. Some are quite old and I'm cleaning up some of my "old" programming in the process. But a backup/restore of the node servers to ISY on Polisy would be handy. If not, I'll just reinstall them. That brings up another question, Polyglot 3. I installed it on Polisy so I could follow the addition of new node servers. Two out of the five I need are available in PG3, but it's Alpha I believe. What will be the migration path if any from PG2 to PG3? I'm eager to pay some of these developers for their work. Mark
  10. @MWareman, I'm having the same issue. The timestamp is correct on a reboot or when I manually change the value in the Variables screen of the Admin Console. They are 6 hours behind when the variables are changed by a program. I'm on Central time. Mark
  11. @Javi, I've been testing the latest iOS version of UD Mobile and the enhancements are really nice. The ability the manage color and define formatted status values makes this interface very user friendly. Really nice work. Can you give an estimate as to when you might be able to implement push notifications? I know some of the structure is there. I'll be able to move more devices to ISY on Polisy when that functionality is activated. Mark
  12. With the Zooz S2 Stick 700 installed and activated, I added a Aeotec Range Extender 7 and a Honeywell (Jasco) Smart Dimmer successfully. Both devices are working as expected.
  13. After upgrading ISY on Polisy from 5.2.0_56 to 5.2.0_58 this morning, I Iost all communications with my Insteon devices through the Admin Console. While doing the upgrade, I executed sudo service isy restart. I did not reboot Polisy this time. I regained communications by powering off Polisy, then the USB PLM, then re-powering the PLM and then Polisy. This corrected the problem and all seems back to normal. I haven't seen this happen on other updates, but then I usually reboot Polisy after an update. @Michel Kohanim, I'm not sure if I did something wrong, but I wanted to pass on the experience and solution in case someone else runs into the same problem. Note: I do have the Zooz S2 Stick 700 plugged into the other USB port on Polisy and have activated it, but have not linked it to any devices yet.
  14. That fixed the problem! Thanks Michel!
  15. @ase, Thanks for the command lines to restore. I'm an amatuer at those and I appreciate the help. I'm going to hold off going back until I get a response on the ticket I logged. I may need to provide other error information to help locate the issue. But if need be, I'll put those commands to work. Fortunately, ISY on Polisy 5.2 is running the programs I have installed on it, so I have a little time to wait for a fix. Thanks again, Mark
  16. I have the same issue except I can’t reach ISY on Polisy with UD Mobile either. I created a ticket and included the debug.log file. There are numerous errors, but the ISY is still executing programs. Sent from my iPhone using Tapatalk
  17. iOS 0.5.5 @Javi, Thanks for adding back the Grouped Nodes. Works great with my Venstar and ELK node servers favorites. I like the hide/unhide solution. Mark
  18. @bpwwer, Thanks for the explanation; it seemed strange that versioning went backwards. With that, I can reinstall.
  19. @Michel Kohanim, I regularly check for updates on Polisy and the upgrade I found on 12Nov2021 removed PG3. Was this normal? The portion of the update listing looked like this: [admin@polisy ~]$ sudo pkg upgrade 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. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: node16: 16.13.0 [udi] Installed packages to be UPGRADED: npm: 6.14.8 -> 6.14.8_1 [udi] Number of packages to be Number of packages to be The process will require 11 MiB to be downloaded. installed: 1 upgraded: 1 37 MiB more space. Proceed with this action? [y/N]: y [1/2] Fetching npm-6.14.8_1.pkg: 100% 4 MiB 619.0kB/s 00:06 00:08 [2/2] Fetching node16-16.13.0.pkg: 100% Checking integrity... done (1 conflicting) 7 MiB 970.2kB/s - node16-16.13.0 [udi] conflicts with node-17.0.1 [installed] on /usr/local/bin/node Checking integrity... done (0 conflicting) Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them. The following 4 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: node: 17.0.1 pg3: 3.0.29_2 New packages to be INSTALLED: node16: 16.13.0 [udi] Installed packages to be UPGRADED: npm: 6.14.8 -> 6.14.8_1 [udi] Number of packages to be removed: 2 Number of packages to be installed: 1 Number of packages to be upgraded: 1 The operation will free 61 MiB. Proceed with this action? [y/N]: y [1/4] Deinstalling pg3-3.0.29_2... [1/4] Deleting files for pg3-3.0.29_2: 100% ==> You should manually remove the "polyglot" user. ==> You should manually remove the "polyglot" group [2/4] Deinstalling node-17.0.1... [2/4] Deleting files for node-17.0.1: 100% [3/4] Installing node16-16.13.0... [3/4] Extracting node16-16.13.0: 100% [4/4] Upgrading npm from 6.14.8 to 6.14.8_1... [4/4] Extracting npm-6.14.8_1: 100% By the way, I have all of my time based loops on ISY on Polisy 5.1.1 and they have been working as expected. I'm waiting for Push Notifications in UD Mobile and PG3 to begin moving additional loops. Mark
  20. @DaveStLou, I have the same issue. I updated Polisy yesterday and it uninstalled PG3. I can't say why, but I suspect it will be back soon.
  21. @Techman, I bought a right angle adapter on Amazon and it fits with a USB cable plugged into the lower port going to the USB PLM. The two do not touch each other. I got this one: https://www.amazon.com/dp/B07C1Z552Z?psc=1&ref=ppx_yo2_dt_b_product_details I'm going to try that first when Polisy is ready to accept Z-Wave, but I might do as others have suggested and use a cable to remote mount it. Probably will try both ways to see if there are any advantages to one or the other.
  22. When I'm ready to move my node servers from the ISY-994 to ISY on Polisy, do I simply change the ISY IP address and port in PG2? Will this automatically add the nodes to the new ISY? I can see doing this in the near term and then moving to the PG3 versions as they become available.
  23. This pricing seems reasonable to me. I will be happy to pay those prices to get the functionality.
  24. I currently have ISY on Polisy version 5.1.1 running and have begun moving some of my production loops to the new ISY. These are independent loops, mostly time based, so if there are any issues, it's not a big deal. So far so good. 5.1.1 seems pretty solid. Note: For a variety of reasons, I'm choosing to manually move my Insteon and Z-Wave devices over to the new ISY. The next step will be to move my node servers to the new ISY. Are there any recommendations on how to do this given a new version of Polyglot is in the works? Can I simply change the address and port in Polyglot 2 to the new ISY to get those nodes to show up there and then upgrade to Polyglot 3 when it's available. Or should I wait for Polyglot 3 and just reinstall everything? Some of my schedule for all of this depends on Push Notifications being added to UD Mobile, but I'd like to be building some idea of how all of this will happen. Thoughts from the experts? Mark
  25. I updated to ISY on Polisy 5.1.1 and all is good. Will keep testing. Mark
×
×
  • Create New...