Teken

When I look around my home and all the things plugged into the outlets. It would be very hard to have the same devices on the wall and wouldn't look funny.

Great history lesson thanks! [emoji106] Sent from my iPhone using Tapatalk

The way your outlets are installed on the lower walls isn't very common in Canada. The closet I've seen them orientated like this is on counters but never on walls. Is this a common thing in your neck of the woods?

Can you provide an image of the area in question and some data points as to the length and project goals? You can go from ghetto to spend what ever meaning it could be what ever cable and just paint over it. From installing wire mold . . . Keep in mind the distance and the amount of current (voltage drop) dictates what wire (AWG) gauge that must be used for X. Depending upon your reply and needs there are countless wire applications available to you. Comes down to costs and meeting those visual needs and what you're willing to sacrifice.

Just to offer a little more insight regarding the folder colors. You can literally see folders flickering to what appears to be strobing none stop. Even if you don't see multiple folders strobing or changing state quickly. Be aware the ISY Series Controller is essentially a smart clock with a FIFO (First In First Out) operations. Meaning every thing happens in sequential order this is why its also important to cut down on *Run at Startup* programs. Also, something that has reduced the amount of boot time and responsiveness is to disable the polling of the Insteon network upon reboot. When you surpass hundreds of programs and hundreds of network resources all of these small things like reduced run at start up and polling the Insteon network helps the stability of the system. Lastly, if you have lots of inbound REST / out bound network resources being pushed to other cloud hosted services. These can slow down the ISY Series Controller to a point where the system appears to be in a unknown state of frozen, unresponsive, to locked up.

One thing to point out is if your system is very loaded with tight loop programs this can cause the system to hang and freeze. I personally don't believe tracking the up time minutes is a good course of action. Monitoring the hourly up time removes any possible time constraints on the system and even balances out program conflicts.

I'm still holding out hope the new guy who bought Smartlabs will bring to market some fresh eyes and how to do business. If we see nothing in ways of new / refreshed hardware besides software crap in 2018. Insteon will be relegated to X-10 history of *Had so much potential*

Don, LOL ~ You're such a pirate, Bravo!

LOL ~ Yes, but someone thought it was much better to lock down the user.

Ideally, the 2413S PLM would simply use a standard global address say 00:AB:F3: So no matter when you replaced the PLM it would always have the same Insteon ID. A secondary unique ID could be present too for other requirements for security etc.

There are portions where a person needs to be physically there to complete some of the tasks. In case you're not aware the only reason the 2413S PLM exists is that lone piece of hardware is the repository of all the hardware links in the Insteon network. Ideally what Smartlabs should have done in its Insteon concept and topology is to make the 2413S PLM like a dumb AP / RE. Where it doesn't require knowing its Insteon MAC address but they didn't. Technically what you're suggesting has been done before but the outcome has been a mixed bag and on a small Insteon network. If someone was to enroll two identical 2413S PLM and left one in the example as you stated unpowered and ready to go and had all the 1:1 links as the primary unit. The very first steps would be to be using the ISY Series Controller firmware that does not declare a fault where the 2413S PLM is missing or can't be contacted. That is a very easy fix simply by installing the appropriate firmware. Next, in your example you would need to time a few things to happen which is to power down the primary PLM. Bring the secondary PLM on line at this point lets assume everything operates as expected primary is off line, secondary is on line. Now you need to reboot the ISY Series Controller so it see's the secondary PLM. At this point its really a mixed bag whether the system will come up with out declaring a fault. Lets assume its *Good to go* you still need to complete a PLM restore so all the links are properly associated to the Insteon network. Which of course doesn't even address the fact you need to be present to initiate the update for legacy battery operated devices. That isn't something that can be done remotely and I can tell you from years of doing this a PLM restore isn't something you want to be doing hundreds of miles away with out some kind of solid remote connectivity and ability to cycle power outside of the Insteon network. I've done this very thing myself with varying results from 100% success to utter failure as a proof of concept. I know in my setup that I could accomplish 90% of the overall task where the system would be 95% solid. But for those who have a mission critical system this isn't something to take lightly as the results can be pretty bad depending upon the dependencies. Its a great idea worth testing out if its something that someone wants to prove out in a isolated manner.

The problem going this route is that the ISY Series Controller must enroll the 2413S PLM into its system. The Insteon hardware is than linked to both the controller and 2413S PLM. Your proposal is a novel one but suspect the final outcome will be a mixed bag in deployment and operations.

Do you have the same experience when using another computer system to access and view the ISY AC? Sent from my iPhone using Tapatalk

If you select any other tabs in the AC does every other page open and is populated like email, general, etc? Are you on 4.6.2 firmware? Sent from my iPhone using Tapatalk

They could certainly have more insight based on the error logs and help explain why the programs don't appear. Just to be clear are you saying once you select the programs tab on the left side no programs are listed? Or are you saying when you select a program from the list the IF, THEN, ELSE, sections appear to have blank selections / values / options?

No, do not attempt to perform a *Remote* restore as this will cause you all kinds of headaches. As noted being on site and local is not only best practices its something you need to be present for. If you remote boot the system let me know if the programs are still missing. Some considerations to keep in mind and try in no specific order of importance; - Disable any firewall & anti virus to see if this behavior is still present or fixed - Ensure the Java software is the latest release - Always ensure both UI & Firmware match under the AC Help -> About - Try opening the AC in another computer system to see if the same behavior is seen or not - Programs: There are times where *Tight Loop* programs can cause the system to hang and this may cause different tabs to be missing or slow to load - What is the Upload / Download speed of the ISP at the remote site?? If its still using dial up or DSL it may be too low. Please cross off the items listed above and report back success vs failure . . .

Not sure if full support will be provided in 4.6.2 as this has been said to be last release of the 4.XX platform. UDI indicates they are still waiting for a revised API for this sensor. ETA?

I appended an image capture for you as a picture tells a thousand words better. Let me know if you need more insight or guidance in this endeavor. You will notice there are two programs one is to address the older style motion sensors. Once that sensor see's movement it will remain on to auto update. The other is an example of ANY device which has a heart beat node. As you can see I selected a random device and choose the appropriate node for both conditions. Once seen it will remain on and update and than go back to sleep. As I stated early on you may find a *Wait* statement is required for the most consistent response and completion. I've found a wait from 0~3 seconds is the window that works. NOTE: For the benefit of others or new users the heart beat node of On vs Off is not a mistake. As some versions of firmware shockingly sent a off signal instead of a expected ON signal. Thus the reason to monitor both states which will allow you to auto update the device with pending writes. Of course you need to wait the customary 24 hour period before this will happen. Which of course relies upon you having a strong Insteon RF mesh in the home where ever the devices reside. The Hidden Door Sensor which has adjustable heart beat interval will of course update based on that defined report in.

This is normal anytime the ISY Series Controller has been rebooted. This is not unique just to updating the firmware so no worries there.

Not a big deal just something to keep in mind. Also if your battery only hardware is newer and has the heartbeat node. You can create a program to update those devices when the heart beat comes in. The update works on some pretty good while others are hit and miss. Playing with a wait time seems to help in this aspect. Since the update can you see all of the programs? Sent from my iPhone using Tapatalk

Bare in mind this should be done when you're able to do so while on site. As doing so will leave any battery operated devices with a unknown state icon or not reflect its last state until it changes.

I have been using Prowl for many years with excellent results. Others like Pushover as I believe its supports multi platform OS and offers some extra features.

That's great to hear one last tip for you in case this hasn't been done or known to you. There are two versions of ISY firmware that anyone can use on the system. One assumes you have and use Insteon and requires the 2413S PLM. Should the 2413S PLM ever fail and not be seen by the ISY Series Controller it will declare a fault and more often than not you will not be able to access the Admin Console (AC). The other firmware supports Insteon, Z-Wave, and ZigBee. If you install that firmware should the 2413S PLM fail it will still allow you to access and use the controller. Even though the Insteon network is not fully operational or at all at least this isn't one extra thing to worry about. Please do consider updating your ISY Series Controller to this firmware version. Happy New Years . . .

I would reboot the controller first and report what you can see. If you select restore ISY that will leave any battery operated device in a unknown state. Sent from my iPhone using Tapatalk

At 26 months its probably time to replace that 2413S PLM. If you accessed the ISY Series Controller from home where you are you need only select the *Reboot* in the general tab on the Admin Console. This of course assumes you set up port forwarding on the router where the remote system resides.