Michel Kohanim

@SteveKlos, What's the pattern of lights on the front as ISY reboots? With kind regards, Michel

@toddhutch, Not sure what you are trying to do. Open close sensors are battery operated so a) you cannot modify their setting unless they are in programming mode b) they have no state after ISY reboot and c) if you tried programming them while asleep, ISY will keep trying and not only you will see green or grey 1011 icons on them but also system busy. The only way to recover is to put them in programming mode and right mouse click/ Write update to device. With kind regards, Michel

@ElectricCPR, Would love to include it in our Wiki: https://wiki.universal-devices.com/index.php?title=ISY-99i_Generic_Jewish_Calendar Thanks SO very much. With kind regards, Michel

@PurdueGuy, Thanks so very much! Got them all. I see the issue ... I think PGC is now bombarding ISY/ISY Portal. That's why Alexa worked for a few minutes. Looking into it as we speak. With kind regards, Michel

Hello all, Sincere apologies for the interruption in service. Once of the proxy servers had to be replaced and is now online. Things should go back to normal shortly. With kind regards, Michel

@JSylvia007, I am so very sorry to hear. I think this is due to DNS propagation delays. Can you please reboot one more time and then send your error log to support@universal-devices.com? With kind regards, Michel

Hi @PurdueGuy, What errors are you getting in PGC? With kind regards, Michel

Hello all, Sincere apologies for the interruption in service. One of the proxy servers had to be migrated and thus the reason for this issue affecting only a certain number of folks (those that were connected to this proxy server). Things should go back to normal shortly on their own. If you have not done so, please reboot your ISY; this will cause ISY to connect to the working proxy. With kind regards, Michel

@cwitter, We'll look into it. With kind regards, Michel

@Clif, Please reset your credentials: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Resetting_Your_Userid/Password With kind regards, Michel

@kkempster99, This is really really odd. The only thing I can recommend is this: curl -s https://pkg.isy.io/script/update121.sh | sudo bash Before you do so, though, make sure you backup your Polyglot. With kind regards, Michel

@widnerm, Please send your error log to support@universal-devices.com. With kind regards, Michel

@TexMike et Al, The sincere apologies. PGC was upgraded last night and I do very much apologize for not letting everyone know. With kind regards, Michel

And, uname -a? With kind regards, Michel

@kkempster99, Just to be clear, syctl dev.cpu.0.temperature Returns nothing? If so, what's the output of uname -a? With kind regards, Michel

@lilyoyo1, THANK YOU! With kind regards, Michel

@kkempster99, Do you see the module being loaded in dmesg? With kind regards, Michel

@simplextech, It's only one of the few of the same brand/model with this issue. And, they do not have a parameter for configuration. I suspect it's firmware on that specific sensor. With kind regards, Michel

@brandwidth, It all depends on: 1. Whether or not the time includes processing by your computer (i.e. making a connection) 2. What's ISY doing at that time There are 3 HTTP tasks in ISY, so, if ISY is doing something with all three, then your request will wait. The best test case would be to do this on a factory reset ISY that has NOTHING else connecting to it (no port forwarding, no portal, no programs, ...). With kind regards, Michel

@pilotgeek, It should work. It might take longer the first time since it has to download all the relevant files. With kind regards, Michel

@gviliunas, Error 6 means that the socket has not closed on the other side. I wouldn't worry about it unless you run out of buffers. With kind regards, Michel

@EVictory, Before you do that, check to see if you have an INSTEON device with that address. If you do, remove it from ISY and then link it back in. If you don't, it's ok to delete. With kind regards, Michel

@drs4life, Please submit a ticket to support@Universal-devices.com. We may be able to support it if we use your system for development and testing. With kind regards, Michel

Hello everyone, Sincere apologies. This is not a scam. This came from our staging server where we are developing the store for node servers. Your production accounts are all OK and alive. This is sent to accounts that have not logged in for over 6 months. And, obviously, most of you have not logged into the staging server! Again, sincere apologies. With kind regards, Michel

@btreinders, You need to telnet to ISY: RF /CONF/NODES/UN0205.BIN <return> With kind regards, Michel