Teken

For the benefit of others this is the reference link asking this feature be included in the next generation Insteon product line: http://forum.insteon.com/forum/main-category/new-insteon-device-wish-list/16482-native-beep-flash Please select the *Like* and add your voice. As this is the ONLY method to show demand and bring this feature to market.

I would humbly suggest that you create a new personal account for the ISY in gmail. This will get you sorted out faster than waiting for UDI to figure out what is going on with their servers. I know for me since they moved the forum over to another hosting site along with changing exchange mail servers. There have been periods where notifications have been spotty and random.

Why are you not using your own ISP account or others such as a personal gmail account?

You have to keep in mind the maker included the beeper / LED solely as a hardware confirmation and error detection. It was not provided to the end user as a means of self automating and controlling its native behaviour. Hence why I suggested that Smartlabs reconsider these hardware aspects to allow an end user to control and manipulate both LED's and beep functions. The latter does not rely on continuous COM's to be sent over the line as its done now. With the new feature the device could be programmed to beep / LED pulse set by the user as it would be native and not requested externally as it is done now. Encrypted By: Phoenix Security Solutions

There is a post in the new Insteon forum under the wish list sub group. Requesting that all future devices have a native beep / LED feature. This would in essence allow the end user to initiate the beep, LED blink, set the duration & frequency. What the OP is doing is simply sending a broadcast message that fills the power line with endless messages. Which everyone knows is very bad for COM's and is not consistent in its end result. Please consider lending your voice to that thread and perhaps this feature will be added in later iterations. Encrypted By: Phoenix Security Solutions

Some basics to keep in mind and to follow once all of the gear arrives. 1. Hard reset (factory reset) all devices before adding to the ISY, programming, and linking. 2. Confirm you have properly coupled / bridged both sides of the electrical feed in your home. The full users manual outlines how each Insteon device reacts to the beacon test. 3. Once all devices are properly (physically) installed in their final resting place. Ensure they control the local load correctly if so continue to step four. 4. You can then add them into ISY Series Controller making any links, associations, programs, etc. 5. Ideally, you should unplug all electronic devices that you can in the home. Add each electronic device one at a time while testing your Insteon networks communications. If things work as expected keep plugging things in one at a time and keep confirming COM's are good. If something you literally just plugged in causes a delay, none responsive On / Off either locally, or via the Admin UI console. Its probably wise to install a filter to that device / circuit. 6. No matter what you do ensure the physical install is sound and correct. Only move forward with linking and programs once the foundation of the network is confirmed. This will ensure the best experience and will allow you to trouble shoot with a more factual position of reference. 7. Things that have been known to cause endless headaches are (but not limited to) are UPS, Computers, Cell chargers, Motors, LED, CFL, Ballasts, Neon, Baby Monitors, etc. To reduce the over all costs its easier to plug multiple devices into a power bar and filter the entire system. Should you have any further questions or run into problems you have the support of UDI directly, or the power of the ISY Community.

First love the Avatar and screen name! I do agree as a successful company you need to identify products / services that are bleeding you out. My point is that I have watched from a far both extremely large companies (Microsoft / Google) enter a space put around for a few years then jump ship. One could say perhaps the market and the demand was too low and they were way too early in entering the space. That is one thing I have to concede and perhaps this new effort to enter the HA space will bring back the energy monitoring aspect that both were champions for. At the end of the day time is the victor as it has always been. Lets see how it all unfolds and perhaps we all will be on the winning end of things!

I believe you're giving Google too much credit with respect to them taking over the market in the HA space. I could list out all of their business failures and ventures in 10 minutes but I digress. The problem with Google is no long term plan or the having the ability to stick it out. Case in point their energy monitoring play thing web site. Microsoft was in this same space more than 10 years ago with energy monitoring where did that go? In the toilet like they have for Windows ME, Vista, Windows 8. Never mind their complete failure of the Surface tablet which cost them 100 million dollars in write offs which they literally gave away to schools for the sole purpose to penetrate the education space in hopes of taking it away from Apple. The only real plan Google has is to monetize your information and track your behavior in hopes of turning a profit. It's apparent there are more sheep in the world then people willing to do things on their own. I am more curious to see how this partnership with Microsoft / Smartlabs will pan out. Its safe to say Microsofts Nokia purchase was a flop and another boat anchor to their bottom line.

The Icon line was dropped to increase profits plain and simple. It was also to reduce dual offerings which competed with the major Insteon line up. Its safe to say it was profit before people, but that is just plain business. With the ever expanding presence of Insteon in retail, on line, and brick & mortar establishments. Smartlabs is still on a good track to make in roads and remain strong & profitable.

I believe what was really telling is in one forum posts a member indicated from an internal staff the amount of Insteon products they move per week, month, year. Its safe to say Insteon provides great profits for Smartlabs / Smarthome. To be fair ( as I have been known to cast the first rock ) Insteon has quite a few devices that are much lower in price then competitive vendors. Another key thing worth affirming is that Insteon bar non has the best looking and feeling devices. Having played with quite a few UPB, Leviton, GE, devices which look like crap and feel even worse. The nod has to go to Insteon for that upscale look and feel. I am not a personal fan of their HUB but who ever is in charge of the Phone App, and the interface for the HUB has some great design flare and taste. Not too sure if this is just a Apple *look & feel* that people copy but I will take that over the interface of the ISY any day. If it wasn't for the fact the UI just works its a simple fact I would have used another UI interface straight away. As the UI is like working on something from the 80's.

As Brian H clearly stated and by the manual these considerations must be taken into account. Failure to plan ahead or even consider this area will result in poor reliability, erratic behaviour, and low customer satisfaction. Given you plan on spending several hundred dollars to enter this arena. Wouldn't you want the best Insteon experience? [emoji55] Encrypted By: Phoenix Security Solutions

I have been around since DOS. Used every windows OS that Microsoft has released. But it's safe to say the PC market has been on a steady decline for many years. This has been single handily been caused by the introduction of the mobile tablet. Since the release of the ARM processor and the customs designs from Apple. Every chip maker has either suffered massive sales loss or market share. Whether it be TI, Qualcomm, Intel, etc. The windows OS share has steadily fallen YOY. They still hold a firm grip in enterprise because of their Exchange Server OS along with office suites. Z-Wave: It's safe to say the development of this protocol with UDI is still on going. I am pretty sure in the next year or so this platform will be public ready. In the interim, it's fair to say COM's for the ISY Series Controller need more work and diagnostic, reporting, and device support need more development. I am uncertain why there are so many issues with locks, bad COM's, or the endless healing / routing issues. But it's fair to say there is obviously more than one way to develop a controller for Z-Wave. But would think what ever development kit is offered would indicate the basics that are required for hardware support. I for one will sit this Beta trial out until the road map and diagnostics are more fully developed. Encrypted By: Phoenix Security Solutions

Pretty sure comparing Apple to Smartlabs is equivalent to comparing the Earth to the Sun. [emoji4] Apple does not make anything directly. But is involved in many electronic & software spaces. Whether that be phones, tablets, PC's, music, productivity suite software. They are heavily invested into technology companies from solar to A/V. Apple has a ten year plan in almost all things they do and aspire to compete in. Smartlabs does not compete on any level in any space when the two are compared. Keep in mind before the whole Samsung vs Apple came to light. All of their eggs were indeed in one basket. Currently four companies build, manufacture, and design their equipment which prevents one single point of failure or interruption in LOB. I believe it's safe to say another company should have been selected as a reference point. [emoji5]️ [emoji6] NOTE: People like to refer to the Texas plant as making. The Texas plant only assembles items for a finished product such as the newly released Mac Pro. Encrypted By: Phoenix Security Solutions

Hello Don, Answers in line . . .

If you're speaking about the software modules then the answers are in line.

Agreed on many points: The key thing with such an idea is that the (future) devices are built and designed to do so. This is something that is designed from the ground up and keeps in mind (long term development goals) to ensure hardware changes do not impact the ability to update firmware. Specifically, Smartlabs as over time replaced and upgraded caps, resistors, power supplies, in many devices. All of which are not related or impacted by firmware upgrades. Obviously, the IC that controls the device must be ready to accept such changes but there aren't very many physical items that would stop a person from flashing the hardware unless it was very old. This is why companies that future proof their designs are able to keep updating their hardware and reduce obsolescence for the masses. I know with some of the gear I own (more than 10 years old) the company planned ahead and still is able to upgrade my systems with a very small firmware upgrade. These are the hall marks of a company planning, thinking, and developing for tomorrow and not just for today. The biggest issue is how does one deploy such a scheme that ensure a successful firmware upgrade and reduces the chance of a bricked situation? Based on my personal experience it would encompass a separate process that puts all other devices asleep. This forces COM's to be focused on one device and all others in a state where they are literally off and can not hinder a firmware load. This is one of the steps my device maker has in place. Next, the most proven and reliable method is a direct tethered approach to transfer the firmware. Again, using induction ports similar to the Apple Thunderport, Magsafe, or worse case scenario Lightning *style* port would allow a clean look and I/O. Since the iteration of Low Power Blue Toot 4.0 this is another method and this negates a physical interface and also ensure close proximity is required to upload the firmware. Given the very cheap IC's for Blue Tooth these days its not something that would increase the cost to a device very much. Even if Smartlabs was to provide these devices as a separate *Premium* offering this would at least test the market for acceptance and reliability in the wild. I agree the faint of heart may not be ready or even willing to go down such a path. But, its safe to say tens of thousands of us fall in a small minority of HA (which continues to grow) each year. Which by default separates us from the *Doers* from the I don't care.

Before you throw any money at this please engage Smarthome about this issue. If the unit is within the 2 year warranty period they will send out a new one to you. I also suspect (good guess) that even if its out of the two year warranty period they will assist you either way. Please give them an opportunity to help you resolve this issue and report the final outcome.

When you select the *Tools* Diagnostics -> PLM Info Status in the Admin Console what does it say the firmware is for the PLM that connects to the ISY. This is the only one that matters at this point in time.

This has been reported as a PLM firmware issue. You can engage Smarthome about obtaining a replacement PLM which has been upgraded to address early cap failure and the *ALL ON* firmware glitch. Please state what the information on the back of the PLM and the firmware from the ISY under the Tools -> Diagnostics -> PLM Info / Status.

I can assure you most of us have gone through the same thing. The fact you stuck it out and reviewed all the steps affirms your willingness to learn and share with others. [emoji4] Now, carry on and enjoy your home even more. Share the information with others so they too can find a solution. [emoji5]️ Encrypted By: Phoenix Security Solutions

Given the very small firmware size (maybe less than 500 KB) I don't see this being an issue where this task was completed over power line. Obviously some kind of error correction would need to be in place and a write verify process at the ready. This is done on several of my security devices in my home and at work. So that portion can be done as it is by others. If a physical transfer must be done no need for a USB (ugly) interface. A simple induction port similar to the Apple mag safe could be utilized. 3-8 small little dots at the base under the plate cover is easily hidden.

Oh I know and agree with your view about wanting the consumer to replace / upgrade. All I am saying is the device(s) are absolutely upgrade-able but requires a physical connection to the header. The reality is, making some adjustment in the flash EEPROM and some hardware changes would allow the end user to update and address issues and add features. This whole throw away society is not sustainable in the long run.

In the 30 plus years in the industry its safe to say serial communications isn't going anywhere. Serial communications is still alive, kicking, and huge in the industrial world. I am not sure if that's a good thing but the reality is that serial communications has always been the defacto method. There are more and more Ethernet based devices for sure and that is a welcomed sight to see. At this point even before people get into talking about Smartlabs offering Ethernet. Lets focus on building upon their strengths and resolving their weaknesses in areas like communication, feature parity, and making the blasted device field up-gradable! It's only 2014, and 2015 is fast approaching and they won't incorporate a user method to update firmware?? WTF??

Didn't know Google was getting into the smart watch arena. But, hey more the merrier I say because it will drive down the cost and make similar technology common place. Whether it succeeds is up to their executing and delivery and mass adoption of the people. The echo video was pretty gay but the information was provided. I am looking forward to seeing how this plays out and what API interface will be made available to the masses in the HA realm.

Having more choices is great but lets see how long this product lasts. I say this because no matter how big you're such as Microsoft, Google, Amazon, they all had epic fails and abandoned products mid stream. I am going to sit and wait and see how this plays out.