Michel Kohanim

@larryllix, Just to be clear, this is only for programs and not the clock at the top of the Admin Console? With kind regards, Michel

@larryllix, Definitely related to PG2 and mongo. It's fixed in PG3. With kind regards, Michel

@MWareman, Can you please temporarily add ${alert.event} to your resource string just to see if the event that caused the program to run is what you expected? With kind regards, Michel

@MWareman, Did you restart Polyglot and Mongodb? In short, once you do that, you should do: sudo service mongod restart sudo service polyglot restart Apologies for not being more explicit. With kind regards, Michel

@MWareman, Looking into it. With kind regards, Michel

@MWareman, You can delete the mongodb (/var/db/mongodb) and then restart polyglot. With kind regards, Michel

It's a bug. Should be fixed in a day or two. With kind regards, Michel

Scott, Are you referring to the Admin Console or anything else? With kind regards, Michel

@LarryCRetired, Tha k you very very very much! With kind regards, Michel

@GJ Software Products, Z-Wave node numbers are generated by the Z-Wave dongle. We have absolutely no control over them. With kind regards, Michel

@MrBill, They can use the temp one or use Gmail. With kind regards, Michel

@LarryCRetired, Thank you very much for the details and, yes, it's quite helpful. I think the data that's not populated is due to short/long poll values for those node servers. Have you tried Query on those nodes? Do they get populated? With kind regards, Michel

@n_sievers, Did you upgrade through the portal or manually using the firmware.zip file? With kind regards, Michel

Thank you very much @LarryCRetired. With kind regards, Michel

@TLangham, 1. Do you have ISY Portal? If so, do you use Polyglot Cloud? 2. Do you have Polisy and/or Polyglot 60GB does not look right. With kind regards, Michel

@LarryCRetired, Thanks SO very much. Yes, very helpful but please do not feel obligated. PG3 is to be out soon and thus this is not urgent. With kind regards, Michel

@LarryCRetired, I am so very very sorry you had to go through all these hoops. I am certain it's a bug in Polyglot because you are not the only one with this issue. My question was specifically about whether or not your solution always works because it'll help us debug. With kind regards, Michel

@LarryCRetired, This really works? With kind regards, Michel

@n_sievers, Please upgrade to 5.3.4. With kind regards, Michel

THANK YOU @Javi. With kind regards, Michel

Hello all, I logged into Stephane's system and the issue was that pip3 was pointing to py37 instead of py38. Somewhere along the line, our script that migrates all these links had a bug and didn't run. Trying to find the root cause. If you have this issue, all you need to do is: sudo ln -s /usr/local/bin/pip-3.8 /usr/local/bin/pip3 With kind regards, Michel

@sjenkins, Please try again: sudo pkg update && sudo pkg upgrade sudo service udx restart sudo service isy restart With kind regards, MIchel

@sjenkins, Did you reboot after upgrade to 13? With kind regards, Michel

@larryllix, We had completely ignored that our customers are very technical and will inevitably change ports. Completely our fault. We shall remove that option ... Now, what you need to do, ssh to polisy and: sudo rm -f /var/isy/FILES/CONF/0.UCF sudo service isy restart With kind regards, Michel

@Techman, Yes, that's a bug. With kind regards, Michel