Jump to content

Jimbo.Automates

Members
  • Posts

    4650
  • Joined

  • Last visited

Everything posted by Jimbo.Automates

  1. I was suggesting deleting the NS and adding it back. But yes I would prefer to see if the upcoming fix resolves the issue. Sent from my Pixel 6 Pro using Tapatalk
  2. I don't have any Hue devices. Sent from my Pixel 6 Pro using Tapatalk
  3. If you restore from PG2 to PG3 without first deleting the NS in PG2 you will have this issue. That should be part of the instructions. The only error is that you can't manually delete it from the ISY, for that we need Michel's help Sent from my Pixel 6 Pro using Tapatalk
  4. There was another error in the main polyglot log I gave to@bpwwer hopefully we can get it figured out. But if you are in a rush, have you tried deleting it and add it back? Sent from my Pixel 6 Pro using Tapatalk
  5. Restarting the NS updates to the latest version. Notifications will happen in the future.
  6. No, good question. AFAIk it only replaces the slots that were occupied on PG2, but will need to confirm that with @bpwwer
  7. For everyone interested in display on keypad, I've added more info to the issue: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/13#issuecomment-1041100647
  8. FlumeWater Nodeserver 3.0.7 released, see the Release Notes
  9. Restoring is all or nothing, so restore later will overwrite any changes made after the first restore Sent from my Pixel 6 Pro using Tapatalk
  10. each NS has a sub forum /forum/326-st-inventory Sent from my Pixel 6 Pro using Tapatalk
  11. Yes, just make sure you have purchased all of them on PG3 before you restore. And remember, this is all still considered Alpha release.
  12. 1. No 2. Many mentions have been made about backup and restore, it should work unless PG3 NS author made changes causing it to not work. 3. That would require fixing all programs that reference it. 4. Unless the NS author made the node names different then all programs will still work.
  13. Ok, then must be a PG3 Javascript error, if you are in chrome select the 3 dot menu -> More tools -> Developer tools Then try to install again and post the error, and then may need help from @bpwwer
  14. A query on a FlumeWater Sensor calls the flume update and updates the values it returns. A query on FlumeWater Hub currently doesn't really do anything. Currently a query on the FlumeWater NodeServer Controller querys all nodes, but that will be disabled in the future, so you should query the sensor node.
  15. Yes. Check main PG3 log for error and post that
  16. View the main PG3 log to find the actual error, but sounds like PG3 doesn't have the right IP address for the IoP.
  17. Sorry, a little confused on which IP address you were changing and where. Post the exact error message and will see if it makes sense. Sent from my Pixel 6 Pro using Tapatalk
  18. Yep, it's on the list: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/13
  19. Thanks, yes, I get notifications with any updates on github issues.
  20. There is a PG3 python interface error that is causing issues, I've pinged @bpwwer to see what may have caused this: 2022-02-13 16:38:26,953 MainThread udi_interface.interface ERROR interface:db_getNodeDrivers: controller not found in database.
  21. Please do a download log pack and PM it to me and I'll check it out for errors
  22. Yes, that may be an issue if you have ELKRP to open it may have issues building the initial profile, I've not tried that, but I know you can have multiple NS's running connected to the ELK.
  23. Once your ELK parameters are configured in the PG3 UI and the sync with the ELK is complete, then close and re-open the AC and that should fix it. But, I just released 3.1.2 which will build the correct default profile on initial startup when no ELK parameters are set.
  24. Did you close and open the admin console?
  25. Thanks, will take a look: https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/issues/43
×
×
  • Create New...