Teken

Just so we are on the same page I have appended *Start Linking* button which is the two colored whirling arrows. In the Admin Console press that button and go to the switch and press it for 3-5 seconds. You may see the load flash and hear a beep from the switch. Go back to the Admin Console and select Finish.

Step one is to start the linking process. Step two is to press the clear set button. Step three select Finish in the Admin Console.

The Matrix is telling you something! [emoji2357][emoji1787][emoji2957]

I’d create a dedicated gmail account for the ISY Series Controller. This would be a interim break fix so emails could be sent out. Until you figure out the technical issues with O365. [emoji106]

I’d start with the basic which should have been done. - Can you send & receive email now from this account. Use another email and validate new mail arrives without issue. - Are there default filter rules in place to reduce spam / junk. If so disable them and check. - Firewall: If there are any firewall rules in place disable them all to see cause & effect. - Antivirus: Disable all to see cause & effect. - Gmail: Create a Gmail account and see if mail arrives successfully. - WiKi: The UDI WiKi will call out all of the network errors to narrow down possible root cause. - Support: If trying all of the above create a support ticket with UDI. Reference this thread and relay all error logs with your submission.

Try the following to see if there is any change in behavior: SMTP Server: smtp-mail.outlook.com Time Out: 1000 From: ISY Series Controller: whateverisyouremail@hotmail.com

Hi Tim, You need to be in the Admin Console so follow the WiKi to install the *Launcher* https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop

Received the same email this morning and just had to say *Ah Sh^t* . . . ?‍♂️ ?

True, as my hand was forced to do so. [emoji2357] Anyone who has ever sat across a monitor to see the finder / launcher blank knows this pain! [emoji35] If you can’t even see the controller to login there’s no way to complete any of the other steps! [emoji1785]

I would appreciate it if you could just clone the old media to the new one. From there insert the same into the test unit and let us know the outcome of pass / fail. I have to order another 32 Micro SD cards for a small project. But won’t be able to receive them for another few weeks.

@hart2hart To be clear the process outlined by the UDI WiKi should be followed in the ideal situation. For me I had to go another route as the system would not locate / find my ISY Series Controller. Having spent more than twenty minutes on no less than five different computer systems to gain access I went down the path as listed below. - Old Card: Remove old Micro SD card and copy all files assuming you can. As in the past if the card is completely damaged and unreadable there's nothing for you to do. The steps below resolves the issue where a Micro SD card is completely damaged and unreadable. - New Card: Insert new card into the ISY Series Controller the system will create several base folders which will be empty. Power down the ISY Series Controller and remove the new Micro SD card. - Back Up: Insert your new Micro SD card into your media reader. Locate and unzip a known good ISY backup and copy over the entire contents to the new Micro SD card. Eject the card gracefully in Windows than physically remove the same from the card reader. - Restore: Insert the new Micro SD card into the ISY Series Controller and power it up. Once up the Finder / ISY Launcher will list out the controller for Admin Console access. Than select File -> Restore ISY -> Select known good backup file -> Grab a cold spirt of choice and wait. NOTE: As stated up above the first attempt at restoring the data from a backup failed with a mismatch error. I don't pretend to know why that is as no errors were present during its creation. I proceeded to use another backup and the restore process completed without errors or issues. Hence its imperative to test all backups at some defined threshold in a real world use case. Take Away: Any network appliance that writes consistently to memory should use High Endurance media regardless of what the maker calls it. Any media that indicates a Lifetime Warranty for High Endurance / Industrial grade more than likely use the highest grade of technology to offer the same. No matter what the bad sector value is listed as - Don't count on it. No matter what the memory error indicates on the face of the controller - Don't count on it. Every Micro SD card that has failed has never presented any of the above status indicators. This is why its imperative to budget and schedule based on the use case of the writes from that network appliance to replace said media on a defined interval. Going this route costs more money but any down time you have is controlled and managed by you! This is normal process for all of us in Enterprise as cycling through media is how systems and services can sustain 99.99999 uptime. Following the same industry standards (Best Practices) insures a Happy Wife = Happy Life! ?

@hart2hart I never had the problems seen and experienced by @MrBill Once the new card was installed to allow the ISY Series Controller to do what ever it does to a new card. I simply removed it and copied over all of the old files from the backup. This was done primarily because the *Finder* didn't allow me to add or find the controller! ? Once the old data was in place I simply completed the ISY Restore from a known good backup copy. Everything was there from time zone, email server, minus the NTP server because the backup on hand was done prior to that change. Regardless, this was a good conversation for others to consider or follow should it arise! ?

@Michel Kohanim So let me reiterate what you stated up above (at some point) in time all modules will exist in a Node Server form - correct? When you say Insteon could be native does the team have a 2413S PLM connected to the Polisy for serial communications?? As stated in the past, and now, no one is going to hold you or UDI responsible for the lack luster support offered by Smarthome / Smartlabs. I don't always agree with the direction the company is heading but know your sincerity to find a common ground for all. ? The one point you didn't answer was my question about Steve Lee. If this needs to be taken off line that's fine by me but thought this important resource would have assisted the team / company in bridging information to support Insteon.

I'm not sure I follow what your question / problem is?!? One thing I haven't tested as I ran out of memory cards is trying to clone the new card to see if it was fine once inserted. This is what I believe you had asked initially so if you have a spare card give it a try and let us know. One would gather you have a 50 / 50 chance of success vs failure in this endeavor. I would favor you would be successful in cloning the second card once the new one was confirmed fully operational.

I don't believe anything stated up above by me is exaggerated. ☝️ I'm unsure the distinction you're trying to make with respect to support vs migration. I could quote everything you stated up above to prove my point. But, that's not why I offered my feedback as to the current state of affairs. I wanted to add my voice to the chorus of others wanting to see Insteon, and all of the ISY Series Controller modules be present. When the Polisy is ready for migration . . . If Insteon isn't even supported within the Polisy there's zero possibility for the same to be migrated! This isn't semantics or a different point of view this is the reality of where the (Polisy) platform is.

+1 Given all of the modules I have purchased there was a reason having specifically purchased the Network Module. As stated by others there are just some products / services that aren't supported. Which leads to the whole issue at hand which is there was never any talk about NOT supporting Insteon in Polisy. That is one of the major reasons I purchased and supported the Polisy hardware at launch! Having waited more than ten years for a real computer to replace the ISY Series Controller was the biggest ask from the community. ☝️ Now that its here, it seems that everything just keeps getting parsed down or removed . . . ? The reality is if the Polisy hardware didn't have a direct path to mirror a 1:1 capability of the ISY Series Controller. The whole discussion of it being the direct replacement should have never come up. It should have been left as *Add On* to enhance the ISY Series Controller even if not ideal it would have probably resulted in less development and public grief. ?‍♂️

Just to clarify my remarks with respect to scheduling memory replacement. My SOP (Standard Operating Procedure) is to use the manufactures listed warranty as a reference to guide me to a replacement interval. All of this hinges upon knowing if the environment is high stress use vs little read / writes. So if the standard *High Endurance* memory offers only two year warranty I have no problem letting that card ride inside of the ISY Series Controller for four years. Given the previous card was a far cry of being considered High Endurance. ? Now, if the we go to the polar extreme where I have mission critical systems that manage my security system. I use the industrial memory with a lifetime warranty and change it out at the 8-10 year mark. Given memory continues to drop in price while also increasing in reliability and performance at 4~10 years the cost in ownership is extremely small. Obviously if I just let the industrial card ride until it explodes whelps that $16 ~ 85.XX investment surely has paid itself in full! But, going down that route has obviously led me back to where I am today! ?‍♂️ Everyone will need to decide what path makes the most financial / time effort sense for them. As I understand money doesn't grow on tree's for anyone. Even if it did having to endure a very time consuming process of restore or data transfer isn't something people just wake up and say *Wow do I love swapping memory* ?

The log size can be increased as Michel helped me do the same. I believe you need to balance doing so vs adding more writes to the card regardless of the quality. The memory cards that indicate so called High Endurance use MLC / TLC technology which some incorporate wear leveling, ECC, and Health Status. Regardless of what the company calls the memory if you see a company offering a lifetime guarantee which is reflected in its purchase price. This memory card is using one of the highest grades and technology present to do so . . . Having used every major brand of memory I can say don't even think about using Samsung! ? They are hands down the worst company to deal with warranty coverage and out and out lie to the consumer about *No Warranty* on products that clearly indicate 10 years! One only needs to read the endless threads on the Interwebs where these scum bags have told (Me) and millions of others there is no warranty! Even if you just bought it 1 second ago from Best Buy . . . All I can say is dealing with great companies like Best Buy is the only saving grace if you so happen to have purchased Samsh^t memory!

@MrBill I didn't use the format process via Telnet and the system created most if not all of the native folders. Obviously they were blank as there was no past data from the old card present. Regardless, the system had no problem seeing the SanDisk 32 GB High Endurance card within the system as seen here. One thing to note which probably comes from years of personal experience is not relying on any monitor indicating system health. I have yet to see the System Status ever declare a bad sector / status - ever . . . I'll also add that the memory display on the front of the unit has never declared a memory fault!! ? Yet, we all know this exists because we're replacing the blasted card due to it being bad! Now to be fair older cards didn't incorporate health check, write lock, wear leveling, etc. Regardless, having used the cheapest to the most expansive memory known to man I have yet to see a bad sector called out! ? As a matter of *Best Practice* as dreadful and labor some it is I budget and schedule to replace the memory cards at a defined interval. ⏱️ Doing so will insure long term reliability, uptime, and performance which you know and manage . . . For those who may stumble upon this thread these are some of the behaviors I saw indicating a failing memory card in no specific order or relevance: - Programs: Do not activate on time or at all. Programs which were inside of folders just automagically became ungrouped and were present in the parent tree. Programs show the green saving icon when nothing was changed. Trying to save the same would take forever or declare an error in doing so. Opening the program tab would take years or would just declare an error in doing so which required the user to close the Admin Console and reboot the ISY Series Controller just to access the same. The famous *Teal Colored* folders which no one has ever seen besides me . . . - Hardware: Anything that was linked to other devices seemed to lose their ability to display their true on / off state. - Backup / Restore: Obviously trying to complete a backup / restore would display endless failed errors in completing the same. - Time: As odd as this sounds there were recent emails sent from the system with dates that called out future years like 2088 or 1980's. This obviously impacted one of the critical programs which I use to track the uptime of the ISY Series Controller. As the email sent would either not increment or when the system was physically hard rebooted the uptime interval never reset back to zero. I would see heart beat messages that something failed to report in on time or every device that had a heart beat would just return to a zero state. Hearing Julie U.S. declare a fault at 3:00 AM isn't something I enjoy dealing with never mind being blinded by a gazillion lumens lighting up the entire home and property. ? - Self Reboot: The system would automagically self reboot.

Michel, Back in the day I recalled Steve Lee was a team member with UDI. He doesn’t post much so don’t know his current status. Given his many years at Smartlabs along with his direct knowledge of Insteon and connections with the same. Is Steve Lee no longer a resource and conduit to Smartlabs?!? Regardless, please do add my name to the list for Alpha / Beta trials with respect to Insteon / Energy Management within the Polyisy! [emoji106]

If you're brand loyal I gather purchasing whoever meets your needs. I've been using the SanDisk branded memory in various capacity and flavors. Each of them offer better long term performance, warranty, and longevity. This version offers only two year warranty but have been using them since launch and never had a failure. They come in various capacities and the price is extremely competitive. https://www.amazon.ca/SanDisk-Endurance-microSDXC-Adapter-Monitoring/dp/B07NY23WBG/ref=sr_1_5?crid=286RQFK5EKMVH&dchild=1&keywords=high+endurance+micro+sd+card&qid=1615245333&sprefix=high+endur%2Caps%2C183&sr=8-5 This one is more expansive but offers ten year warranty: https://www.amazon.ca/SanDisk-Endurance-microSDXC-Adapter-Security/dp/B084CJ9T2R/ref=sr_1_5?crid=337XIGUQL0QBK&dchild=1&keywords=max+endurance+micro+sd+card&qid=1615245553&sprefix=max+en%2Caps%2C190&sr=8-5 These come in restricted capacity but offer a lifetime warranty. I use these in mission critical applications or where the device is extremely hard to access. https://www.amazon.ca/SanDisk-Industrial-MicroSD-UHS-I-SDSDQAF-016G/dp/B07CV344WJ/ref=sr_1_11?crid=30EFBIZZUU1GD&dchild=1&keywords=industrial+micro+sd+card&qid=1615245611&sprefix=industrial+micro%2Caps%2C180&sr=8-11 I use all three in different network appliances and the true test is on vehicle cams / IP camera's that are written to 24.7.365

I'll add my name to the list of people who experienced a Micro SD card failure. ? Truth be told I had purchased 62 SanDisk High Endurance memory cards in various capacities for several projects on the go. One of the 32 GB cards was assigned to the ISY Series Controller but later was deployed into another network appliance. ? I already knew this was playing with fire as last year Michel was kind enough to assist in recovering my system from another corrupt media. Fast forward to March 08, 2021 I had two separate memory card failures on different network appliances!?!? ? One thing which I'll call out having gone through this process about 5-6 times over the course of twelve years. If you can't find the ISY Series Controller via the launch (Start) link. Take any recent backup and unzip it and copy the entire contents and dump it to the new card. For me that was a break fix to simply access the Admin Console. Once logged in I proceeded to restore the ISY from a known good back up that was as recent as possible. Even upon the first ISY Restore it had failed calling out there was some kind of mismatch . . . The ISY Gods must have been watching as they allowed me to restore from another backup! ? Bottom line, use High Endurance media proven to work, keep a copy of your backup's on different media and locations, test your backup to insure they work!

Can’t be [emoji2955] Surprised it’s all [emoji50] Then again crazy just works [emoji1787] What have I done [emoji2357] Oh wells [emoji106][emoji481]

I'll have to begrudgingly agree with @lilyoyo1 to a certain extent ? I'll add my $0.00000000000000000000002 to this discussion with points which many can relate to. The fact anyone is here on this specific forum places you in the 1% of the humans who have taken the notion of automating their homes. This percentage gets to the 0.1% by the shear fact you're using one of the most powerful home automation controllers in the world. Assuming a person is interested in Home Automation one of the first controllers people will read about is Smartthings. Regardless, this puts the very people into the same category of *Die Hard, Fanatics, Over the Top* etc. I personally don't see a problem asking for the controller to offer the ability to complete a auto back up. It's only 2021 for God's sakes, it can be done, it really comes down to the team having the time to do so . . . Given, the demand is quite low that's not going to happen along with Michel affirming this isn't something on the road map for the ISY-994. I would hope the Polisy at some later date would be capable of doing so seeing its a real computer that has plenty of horse power to do the same! Ultimately, if there are no changes to the system a one time backup that is stored on different mediums & locations is just fine. If people want to complete a monthly backup where nothing ever changes I don't see the value in doing so! With respect to *Act of God* events @lilyoyo1 is correct in stating one can always try their very best to plan, implement, and hopefully mitigate losses. The reality is we all live on this blue planet and if anyone truly believes Mother Nature can't wipe you out in a single breath. These same people haven't taken the time to learn history. ? Some would probably say I am the epitome crazy, over the top, and nuts. Given, all the things I have done when my home was built along with the never ending projects under way to offer more resilience in the face of so called *Act of God* events. Speaking for myself only, I do these things because I can, because these *Industry Best Practices* have allowed my family to be secure & safe. It has also reduced the incidence of failures because the internal systems are so robust which have backup, redundancy, and fail over designed as the prime objective. With all this investment in time, material, and resources none of this supersedes the fact all I am doing is buying time. Sometimes buying time is what matters whereas in other cases buying time simply delays the inevitable outcome. In closing, people need to roll a hard 8 and do what they believe matters to them . . . ?

I’m on the road and not by a computer so can’t check. But the UDI WIKI will outline the steps to reset the network or worst case default the controller. The pushing and hold timing is a little tricky so might have to do it a few times. No matter what make sure the 2413S PLM is connected even if you reset the ISY. Unless you’re using the firmware that doesn’t look for the 2413S PLM. It will cause you endless pain if not powered up in sequence and together. If in doubt unplug both units. Wait ten seconds and power PLM. Wait ten seconds and then power up the ISY. At this point don’t know if you hard reset the ISY. If so do it again per the WIKI until you see the LED pattern outlined. Than go through the set up process. Than restore ISY. If you have a Pro version select the delay battery write as this will cause you nothing but hours / days of grief waiting and message failures. Once all of the hardwired gear is properly enrolled and physically / software working. You can do a single battery device until done. Just right mouse click on each item and write any pending 0110 writes. Obviously, place that (single) battery device into linking mode! Good luck . . . [emoji106][emoji481]