Teken

In your case did going this route cause the smart display to cut out and get reset? That board looks different to others I’ve seen?!? [emoji848] Sent from my iPhone using Tapatalk

Based on the link table count and 2413S PLM produced on 2014, 38 week. It’s time to replace the PLM. Once you receive the new 2413S PLM. You may consider repairing it based on the forum thread at UDI Forums. That will provide you a back up and you’ll learn a new skill for future endeavours. [emoji106] I’ll try to find the reference link as to how to determine Insteon links once I get back to a real computer. [emoji1787] Sent from my iPhone using Tapatalk

Perform a PLM link count 4 times and let us know what you see in terms of results. How many Insteon devices do you have in the network? In the UDI WiKi you can get a general idea if the links you have are too low for the amount of hardware in place. With respect to the date please reference the information on the two white stickers on the back of the 2413S PLM. Sent from my iPhone using Tapatalk

Tornado? [emoji848] Sent from my iPhone using Tapatalk

Sounds more like a failing 2413S PLM. [emoji52] Sent from my iPhone using Tapatalk

Hi Steve, - What firmware are you running on the controller? Have you confirmed in the past both UI & Firmware match? - Micro SD Card: Where is it and why isn’t it inside the controller as it needs to be in place to operate. - Launcher: Have you tried to access the controller using the new launcher application? - Java: Are you using the latest Java release and have you confirmed the controller is listed as an approved device for certificates? If you haven’t cleared the Java cache and history give it a try keeping in mind doing so will delete the Admin Console link on your desktop. You can download another copy from the forum. Firewall: If there are any firewall appliances on the network white list / remove this applicable. Antivirus: UDI has a great WiKi about checking and making changes to antivirus please check yours if in place and in use. Network: Assuming you aren’t using the firmware that ignores a missing 2413S PLM. What does the controller do when you unplug the Ethernet cable? Also have you changed out said cable? PLM: As noted up above unplug the PLM. What do you see at the controller assuming you’re not using the firmware that ignores a missing PLM? Access: Are you using a Windows or Mac computer system? If a Mac can you let us know what OS and also try accessing using a Windows PC? Sent from my iPhone using Tapatalk

The fail over portion was one action item on my list. I haven't validated the Polisy will operate as I hope when I remove the tethered Ethernet connection. So if you get to that let us all know as that would be great to know there's one less thing to worry about. Which also provides a measure of fail over and redundancy for our little toys! Oh these first world problems . . .

This is similar to what happen to one of the sites I helped manage: Tens of thousands of volts was injected into the facility over the course of an hour. The problem(s) which very few people ever address or understand is unlike a voltage surge, voltage sag, a slow increase in line voltage can't be blocked by a standard SPD. Nor can they address a voltage sag condition when present. The vast majority of SPD 1, 2, 3, 4 are designed to shunt and dissipate a voltage surge event to ground or sacrifice itself through what ever inline device whether it be HRC, MOV, Zener, GDT, RCL. This is why mission critical facilities must use and deploy some kind of voltage regulation or AVR. Even the best online UPS must still be protected at the service entrance by a SPD 1, and the service panel via a SPD 2. All down stream devices *Point of Use* must have a SPD 3 to insure a comprehensive surge protection system. As each type of SPD is rated to operate in a well defined voltage range / speed. As noted up above all the SPD 1-4 in place at this facility had no benefit as it didn't address slow voltage rise / voltage sags. As all this did was smoke the SPD's and everything else connected to the electrical system. When the transformer like what you see in this video finally let loose tens of thousands of volts (the facility) had no protection and everything that was still connected lit on fire / blew up. The insurance claim exceeded eight million dollars for the building and the industrial equipment and took that facility off line for more than nine months. More than 35 thousand people lost their jobs which were associated to this facility in some direct / indirect manner. When dealing with out of band voltage conditions one must try to deal with all possible scenarios the best they can within their financial capability. Injected (radiated) voltage rise is extremely hard to address even when using coils to RCL networks. Installing giant inductors isn't something most people can or willing to do but one only needs to view some of the best in class sites to see they exist and work. Spark gaping is also a fine science and only addresses very specific conditions and doesn't even address lightning / induced EMF.

Hi Mike, Sorry, I should have clarified the DC barrel jack appears to be the same size and fits from both the ISY Series Controller & Polyisy.

Seems to fit perfectly fine here?!? [emoji848] Sent from my iPhone using Tapatalk

As of this writing the weather module is EOL. So nothing for you to do besides start learning about Polyglot / Node Servers as a weather module replacement. [emoji106] Sent from my iPhone using Tapatalk

The Polyisy is 12 VDC @1 ampere. Considering it’s a mini computer system let us know how it runs on that DC UPS. Sent from my iPhone using Tapatalk

Ping the controller and report back the response. Check the router and confirm it’s listed as a device on the network. Ensure the controller is set to DHCP along with all other network devices to avoid a IP conflict. Sent from my iPhone using Tapatalk

[emoji106] Sent from my iPhone using Tapatalk

From personal experience I have relied on lots of the available tools from various systems and hardware. Along with long term observations and documenting what is being seen. In no specific order I follow these best practices as much as possible. New Hardware Validation: - Level 3 logs: I clear and run this level of logging prior to see what the current activity is. - Scene Test: While viewing the level 3 logs I run the various scenes and see how many hops are left prior to any hardware addition. This offers me a base line of the controller to reference too. - Physical Test: Newer hardware offer blink (red) on errors as such manually test all hardware to see that I see (green) on every system. This offers me a base line of physical operations. - Add New Hardware: Now using the two above I rinse and repeat to see if there are increases in hop count, error LED, or failed scenes operating. - RF / EMI Testing: I have two old school methods of detecting spurious noise / EMI. One is simple AM - FM portable radio which I tune to a open channel. If there is a huge burst or constant noise received by the radio I document this. I do the same thing with a wired radio in case something is being injected on the power line. I follow up with a very small florescent tube light fixture I used to use for automotive diagnostics. Anytime the is carbon tracking on the distributor housing. RFI / EMI would surely follow and show up on the pulsing tube light. I also have a industrial RFI / EMI meter which measures the same but rarely break it out because it simply offers the strength, frequency, etc. Which is good to quantify factually what the emissions are vs just WAG. ? - Stop Look Listen: It goes without saying anybody who has ever been a field tech in almost any industry knows and lives: Stop, Look, Listen. I've probably written about watching various model / brands of bulbs for years. If I hold a power supply and feel it buzzing or making a odd noise - its gone. If I see LED bulbs making the same, or pulse, strobe, flicker - its gone. - Insteon Diagnostic Tool: For a very brief period of time Smartlabs offered a KPL box which offered limited diagnostic tests. I have one of these tools which for what it was - was OK. it's currently with another forum member for the last five years! ?? Regardless, depending upon hardware type and model the user has the ability to turn on-off power line vs RF on those pieces of hardware. Doing so will identify if there are RF vs Power Line issues if present. - 4 Tap Beacon Test: Following the 4 tap beacon test has also brought to light noise makers / signal suckers when present when confirming proper coupling / bridging of the split single phase electrical system. Keeping in mind ideally a person should see bi-directional confirmation of coupling when initiated. I've found this is not always the case so using all of the above best practices offers another piece of insight. Hope some of this helps the forums members . . .

I think the only way to tell is to have the unit plugged in and wait and see. I can only speak for myself but all of my gear is on a limited amount of filters in the home. I've been fortunate enough to have just two Filter Linc's in my entire home. Primarily because I took the time to test, validate, and monitor long term if any of the electronics were going to impact the Insteon network. Well, besides a lot of the hardware are on dedicated circuits! ?

For some this is to avoid the whole AC-DC vs DC-DC. I see value for both but like others larger is better for many of us. But, this device is also very small while offering a long run time and also uses lithium cells. Unless one goes the route for the much (Read Crazy Expansive) lithium UPS systems this is a good compromise for low power consuming units while also being portable.

Hello, I've been tracking several threads with respect to maintenance for various services for the company. I believe the take away from some users is there needs to be multiple paths of communications to the end clients. As the pain point for some is not always coming to the UDI forum to find out about the same. May I humbly suggest a three prong approach such as these in hopes of reduced service requests and low customer satisfaction: Forum Message: This is already being done but a longer lead time for some would be great to see. Email Broadcast: The vast majority of clients have already signed up to receive news releases and updates. I know when receiving an email from UDI 100% of the time its related to large milestone for the company with respect to features / services. The other is related to support service tickets which are extremely rare for many of us. Regardless, a group broadcast for a pending maintenance or service outage would be great. ISY Series Controller: It's apparent to me the company has the ability to push notifications or status of the various systems / services. Perhaps the team could implement a service down / pending maintenance window message in the portal tab. As this would at least inform the user why Alexa / Home isn't operating as expected.

Hi Mike, At first blush all of the previous last states would be seen by the ISY Series Controller. I can't say if that is good or bad as this comes down to user preference and expectation. I prefer to see the last known state of the device in my controller instead of a blank state which is common after a reboot / power outage. As noted early on if one has the appropriate programs in place some of the unknowns can be eased on the user. Heart Beat: If you haven't began tracking the heart beat on various battery operated devices. This would probably be a good time to do so as this will at least give you a indicator as to RF range, battery status, and operations which obviously gives you a status obviously not on-off / open-close but its something. PLM UPS: Some have gone the route of placing the 2413S PLM on a UPS. Doing so more often than not will remove the power line communications due to internal filtering from the UPS. So at that point the 2413S PLM will be receiving its Insteon signals solely by RF. In this forum there have been a few people doing this for a couple years with great success. I did this for one large install and as of this writing its been working fine for that client. The one thing that we did plan out was the UPS was a higher quality double conversion pure sine wave model vs the more common PWM (Pulse Width Modulated) square wave UPS. As noted filtering or the lack there of will either allow you to see dual band or not. In our case it was really dumb luck there was very little filtering on the unit to impact the power line signal. It goes without saying testing and validation is paramount if one is expecting a specific outcome. Keep in mind in this install the client had very specific needs and wants which was to first protect the 2413S PLM from dirty power. Next, was being able to receive RF signals from the battery operated devices regardless of the line power. Lastly, having the 2413S PLM allowed the whole house generator enough time to come on line to than control the remaining power line only devices in the home. You may consider a small pure sine wave UPS for the 2413S PLM to address the first two items I called out. ISY Uptime: As noted up top if you haven't created a up time counter program this might be a good time to do so. As this will enable you to associate other Insteon / environmental's in the home to the up time of the controller. Obviously this assumes you were going to let the ISY lose power - but your not! LOL Insteon Power Monitor: This is why I called out using the I/O Linc to monitor the line voltage. Once power is lost and this assumes the ISY, PLM are on a UPS this would allow you to know power somewhere was interrupted. Keeping in mind this doesn't address quick and short outages seen by many people throughout North America. But, its another tool in the Insteon arsenal that allows you to track in a general way what is happening in your home while you're away. Fail Over: Lastly, as you probably realize this hobby gets pretty expensive solely to *Just Know* ? This is why I have so many other systems tracking, validating, and sending the current state of the homes electrical system. If there was just one perfect system that anyone could buy with a shoe string budget it surely would have been done by the masses years ago! I've always walked the path from simple & easy to expansive & hard (IF) and when required. For power monitoring that is 100% bullet proof and reliable it really comes down to investment in time and often than not money. ? Regardless of all the systems in place it's paramount to test, validate, and be consistent in both as time goes on. For me all of this is standard fair as testing & validation is a large part of my job and how I have been trained in various industries and fields. Let us know how the new UPS works in your home and if you also see the low 12 volt output as seen by others. As I might consider picking one up as a testing platform for a unrelated project I have going on now.

Well, I can only share with you how some of this was addressed by me in my personal environment. First, I tracked the incoming line voltage from the POCO through no less than five independent systems as this insured a measure of fail over and validation. Once I knew line voltage was interrupted I tracked for how long it was off as this dictates what systems will react and start a sequence of load shedding within the homes super structure. Based on how long the line voltage was interrupted various systems in the home will remain powered or removed from power to extend the runtime of various UPS systems. Many sub systems are left in a state of *Fail Safe vs Fail Secure* as I didn't want a loop in voltage where its common to see power flicker on - off. Anyone who has experienced such electrical events knows that's a perfect example & time of letting out the magic smoke in electronics. So for me for some very specific appliances / devices once power / voltage is interrupted those devices must be manually brought back on line by activating SSR relays, outlets, switches, modules. Things which you want a *Fail Safe* mode to continue to operate once power / voltage is restored like sump, furnace, fridge, freezer, etc. Other expensive but none critical appliances like washer, dryer, dishwasher, microwave, A/V, etc all use *Fail Secure* mode and must be manually brought back on line. The next step was creating various programs in different systems to send information to the ISY Series Controller to act upon a line voltage issue. Related, but not, is the very common program to track the up time of the ISY Series Controller. Based on this it can execute the Query All program to identify power line devices but as noted by others it does not allow you to know the status of battery operated devices. One very easy and novel power monitoring device is using an Insteon I/O and once relay closes it signals the ISY Series Controller. This method to monitor power loss obviously has limits but it was designed and conceived for a very specific instance like a GFCI tripping on a dedicated circuit. I'll add more later its dinner time . . .

Is this from the perspective of being remote and wanting to know? [emoji848] Sent from my iPhone using Tapatalk

[emoji106] Sent from my iPhone using Tapatalk

What action steps did you complete? 1. Did you add the new email and assign it with Admin access rights? Did you confirm the email account you created prior is active and does receive inbound mail? Sent from my iPhone using Tapatalk

Login to the Portal -> Users Tab -> Select the red (X) Delete email account. Select Add User and insure its set as the Admin. It goes without saying make sure your new email address is active and receiving mail before you even attempt to delete the older email account.

You're probably right about having too many in this short depth server rack. Getting pretty close in max weight capacity but the second short depth server rack is even heavier and almost as tall! ? If shipping wasn't so crazy expansive from Canada to the USA you might have found at least one coming your way last year!! ?