Michel Kohanim

@pmoles, Are you certain your ISY is on the same network as your computer? And have you not changed ISY web server ports? If so, the next thing would be firewall. With kind regards, Michel

@pmoles, What's the pattern of lights on the front as you reboot? With kind regards, Michel

@TriLife, 12V min 1A. With kind regards, Michel

@Nishal, What exactly is it that you want to do? What you have is correct . With kind regards, Michel

@Geddy, Thanks so much for the kind words. Just to emphasize, UD Mobile does not need an ISY Portal subscription. With kind regards, Michel

@hchain, If you can telnet to ISY, please type the following on the command prompt: RF /CONF/UDFLPL.XML If not, please take the SD Card out, put it in an SD Card reader, navigate to that file and remove it. With kind regards, Michel

Thank you. We have uncovered a bug. So please don't upgrade till further notice. With kind regards, Michel

Thank you all. Please be patient while we upgrade the OS to 13. With kind regards, Michel

Hello all, Thank you for noticing. I take credit for composing it! In short, we had many systems that were stuck on FreeBSD 12.1 ... so, we automated that and also streamlined package management in addition to: 1. Additional security enhancement using TPM service 2. Support for mDNS (so you can find the unit via polisy.local or polisy) The musical tones were added for your amusement and, for us: a) the OS has the correct level, b) udx version 2+ is running, and c) TPM and mDNS are running With kind regards, Michel

@oper8, Please submit a ticket. With kind regards, Michel

@swamp2, Most of these devices have user defined parameters for polling and other aspects of the operation. You need to look at the user manual. With kind regards, Michel

@residualimages, Yes. With kind regards, Michel

@larryllix and @asbril, thank you very much for your vote of confidence. Alas, I must pass. In this day and age where being hacked is no longer a matter of _if_ but a matter of _when_, I am hoping that their new line includes security enhancements. With kind regards, Michel

@residualimages, As you have noticed, we are migrating nodes/properties, to node servers which would make the "formatted" tag obsolete. With kind regards, Michel

@n4bos, What does this mean "I had to go into the router and set the DHCP range OUTSIDE the assigned IP address for the ISY so that the router assigned a NEW address within the new DHCP range"? Or, better yet, this is what MUST be done regardless. Actually, the static IP address should be OUTSIDE of DHCP range. Or, maybe I am not understanding what you are saying. Also, if you want static IP addresses, it's best to use DHCP reservation rather than assigning static IP to ISY. And, finally, make sure you are not port forwarding UDP packets. With kind regards, Michel

@carealtor, You are right. I should have been clear. As I mentioned to someone else, we have PTSD when it comes to INSTEON. With kind regards, Michel

@jblackst5000, Yes, for sure. With kind regards, Michel

@TriLife, The image you sent me is from Polyglot Cloud dashboard and not Polisy. With kind regards, Michel

@Blackbird, 1. Existing INSTEON devices shall be supported either natively or through node servers. Cannot guarantee that migration is going to be as easy as migrating ISY to another ISY but we'll do our best 2. We have not been privy to any new INSTEON protocol changes/products. And, many sources (except one) tell me that they do not want to integrate with or support third parties. So, I hope you do NOT think we are going to sacrifice ourselves (again) just to support them. We won't. Never again. Unless they provide us with meaningful documentation/specs and commitment for support. e.g. we spent months reverse engineering MSII, gave them a list of bugs, and at the end got blamed for not supporting it properly by our customers. I want to set the expectations again: We shall NOT support New INSTEON devices without proper documentation/specs and their commitment for Support. With kind regards, Michel

Hi All, Apologies. The email also had a link back to the news on our website. So, if you hover over the link, you can see our website. In short, yes, we were hacked and the hacker wanted $1500 in bitcoin! With kind regards, Michel

@hart2hart, If new, you don't need to format. With kind regards, Michel

@MrBill, The NLS files are put in place by the upgrade and not the format. With kind regards, Michel

@MrBill, The LIB Error 403 is because the NLS files have not been installed. It has nothing to do with the format. With regard to the logs, ISY does not log continuously. It stores as much as possible into the memory before flushing it. The size of the log matters (as @Teken suggested, you can change this value through the shell). Furthermore, ISY rotates the logs based on the size you choose. So, you will have error.A, B, and C files before they are rewritten. If you have too much traffic/logging, it's best to use larger log sizes. With kind regards, Michel

@Teken, 1. As mentioned, existing INSTEON is either native or node server with preference for the latter. Migration might not be included 2. Network resources should work with the exception of binary payload (at least initially). Preference is to get rid of these modules and make everything a node server. Perhaps a generic node server for sending packets 3. ELK is already a node server 4. Climate is already there as node server with many more options 5. Z-Wave will be a dongle Again, please do not hold us responsible for new INSTEON devices. At the moment, and without further information from SmartHome/INSTEON, we have no plans of supporting them natively. If we go the node server route, perhaps the developer him/herself might. But, then again, the rumors and indications point to the world where third party integration is not something being offered by SmartHome/INSTEON. Am I missing anything? With kind regards, Michel

@Teken Exaggerate a little? 1. Support is different than migration 2. Please read everything above again (twice more) With kind regards, Michel