lilyoyo1

You're welcome. Anytime. Theres an internal and external board for Matter

I'm not sure if the Zooz stick works with eisy so that would be the first/main thing. If it doesn't then it's worthless with eisy. Since other boards besides zooz, do work with polisy there's a chance that it will. Besides the differences that you've stated, you would be limited to what you currently have with zwave. That means no ota updates via the Isy. You could still update your devices; you'd just have to put your zooz stick into your computer and use other software. You will not receive s2 (if that matters). The main benefit of the new board for you would be the ability to use direct associations to create your zwave scenes. Also, Michel has stated, all new features will come to the new board so if you stick with Zooz, you'll be limited to what you do now Eisy is a whole new system that shares the same external adapter as Polisy. Think of it simply as Polisy 2.0

That is correct. I believe he mentioned the external USB drive for polisy will will work with eisy. That way, you can swap it to you eisy should you put purchase it later

You are right. The whole point of automation is to make things simpler. No one ever said it would be easy getting there. Everything that runs well takes putting in work to get there. We all wish things were easier but the nature of automation makes it complicated. It's like building a model car. They have the simple setups for beginners and those who do not want to put much work into it. They can snap a few pieces together and be done. This is basic control systems like hue, Amazon, Google and others like them. They're easy because they're limited. Then you have advanced setups. These require thought, skill, patience, practice, and more. You're responsible for every detail. If you don't plan out what you're doing, you'll have issues. This is automation. The very nature of automation is complex. This isn't limited to the isy. Every single full automation controller has it's complexities. This is why C4, Creston, homeworks, and others require expensive classes and dealers to install them. They know it's beyond most people to program and don't want them in the hands of the avg person to screw them up. If a person doesn't want to do the work involved to learn and set things up- this is the path for them. UDI could provide detailed information about everything that you ask but then you'd have information overload. Look at the isy cookbook. It's close to 700 pages and is still missing a lot of detail. That's not including the wiki which would add even more. Those who take the time to learn about their chosen system generally struggle less with automation systems. Those who jump in without a plan and/or don't take time to learn about what they're using struggle much more. UDI can add all that you ask but at what cost? The more they add, the more they'll need to charge for the Isy (controllers themselves). Programming isn't free. They're balancing costs with features and what people are willing to pay. People complain now about polisy choosing 350 bucks. Can you imagine how many people would use UDI if they charged 600? All for something that provides limited return If a person doesn't take the time (or doesn't want to) to educate themselves, all of that will be for naught. I agree with you in that the hue Node server could provide more (and better) documentation about setting it up and possibly making changes. As i said before it's free. If it were 50-100 bucks, my expectations would've been much greater. In the end, you get what you pay for.

Michel stated on another post that no deal was made. Unless things change with imsteon, no plms will be available from udi

I think the developer assumes someone who is using HUE already knows how hue works and has already set it up prior to trying to use the ISY to control it. Personally, I use Network resources to control my lights as its quicker and easier than what you have to go through with the Node server (for me). I prefer this method because once the work is done, I dont have to go into the ISY to make changes. I can simply update the scene in the app with whatever changes I want to make. The only thing I miss is being able to dim devices from my switches (which I dont do anyway). The flexibility the ISY gives to controlling disparate devices also makes building a strong foundation paramount (and time consuming). The Node server currently does not support dynamic scenes as its based on the older API. Until the new api is completed by hue (which allows for more dynamic scenes), I do not see a developer spending the time updating to it only for hue to make changes that break things. If you actually choose your created hue app scenes, you will avoid the popcorn effect. The ISY is not a zigbee controller so it cannot create scenes within the hue app which is why you get the popcorn effect. For dimming purposes, the ISY uses standard dimming levels (1-255 I believe. Could be wrong about the exact numbers) for dimming. There can be variances with different devices due to how each protocol/mfg. handles their own dimming. Unfortunately, some concessions had to be made for uniformity purposes so there could be some things off. The fact that the ISY has to talk to the hue bridge, then the bridge has to talk to the devices will create a delay with the dimming commands. As stated earlier, if you want to avoid the popcorn effect, you'll need to control your created hue scene. The good and bad thing is that the Node server is free. You get what you pay for which means there will be some concessions (though they'd exist even if you did have to pay). Hopefully, the next Node server will answer some of your shortcomings when hue completes the api

Any that are available would be in the full owners manual for the device. You can generally find this on the mfg. website. If they don't have one, then there probably isn't any extra parameters

Never even heard of it. From my experience, secondary controllers are flakey. I would ensure both controllers are within range of one another since it won't work if they aren't. After that, you'll have to follow their instructions on

The best thing to do is buy a bulb you want to use and test it with a dimmer. I've found that bulb compatibility can change even within the same mfg. lineup. I've purchased bulbs that worked perfectly and had buzzing with later purchases. Ditto for those that didn't work in the past. If you find one that you like and it works, i recommend buying a few extra. This way, if you need to replace one down the road, you'll know it'll still be compatible and the light it puts out will be the same as your existing (yes, this changes too). This isn't unique to insteon but all dimmers/bulbs out there.

Did you recently upgrade to 5.0.16? I'd say make sure you've cleared your Java cache and that the UI matches your firmware. You can also make sure the board is seated properly. Outside of that, the board could be going bad.

I've never had a need to try it so i can't answer that. I know I've updated my stick without ilosimg devices. The key is stored in the stick do i doubt it

I'd take their advice and try it. Yes, it's a lot of work but that'll be the only way to get to the bottom of things and solve your issues.

Yes to both. Follow the instructions on the firmware upgrade page found on under the current release section

I know ge has an open API. Does Frigidaire?

I understand what you're saying. With you having multiples, I would use one or 2 to practice on. Going off Brian H. post, I have my suspicions since he understands the insides of the devices. But if there's a way to work and the original poster isn't around anymore, it's hard to see anyone taking the time in that manner for something with minimal gains for themselves. Especially when there are other alternatives that most are turning to so they aren't caught in a bind again. Unfortunately, from the way it sounds, most likely it's not something that's going to be easily recreated for others to follow suit like recapping (or using a service) can do. For your sake and others in your position, I do hope you or someone does figure out how to make it work and easily replicated by others. It's not a bad idea.

I apologize for thinking you were talking about Nokia hubs. You mentioned being able to use them so i assumed you were referring to those as well. Yes, there would be value in using the standard hub. What would be easier is simply fixing your old PLM. A drop in replacement however does require code not modifying something. Maybe you could try to pm the poster of the hub mod and see if they could provide clearer instructions and give it a go yourself. Hubs are cheap enough on eBay to get a few to practice modding with.

It's faster direct but limited to 5 devices within range (has to be direct device to device communication). Unlike insteon, you wouldn't be able to use direct association if a repeater is required to be in communication with another device. These groupings are good for on/off control of like devices.

I'd assume associations work properly with eisy but with the limitations of it, you'd probably be better off with the ISy doing the routing unless speed is of the essence such as using a sensor to turn in a light.

Where does it say that? Insteon scenes reside in each device regardless of device type...ie: any insteon device can control any other insteon device regardless of what it is. Just had to be in range of the signal With zwave you have 3 ways to control other devices. 1) controller is the middleman for scenes (most common) 2) direct association: device to device communication. Limited to 5 other devices. Must be in direct range of the controlling device and all devices must support that association and the controlling device must be scene capable. (2nd most common) 3)assigned association. Same thing applies except you are able to talk to devices not in direct communication with the controlling device. With that said, the controlling device must support this capability as it sets its own path separate from the controller. (Least common). In addition, instruction devices can all have different ramp rates and levels. Not so much with zwave. Where is it that insteon is similar to this?

Zwave doesn't handle scenes the way insteon does so if you're used to insteon you'll be sorely disappointed. Theirs is a convoluted mess which the Isy doesn't handle well but from what I'm hearing has been redone to work better with the new board (still a mess though). Depending on your issues, the new way still may not fix it due to how different zwave devices work.

You might want to re-read those discussions about nokia hubs. It was UDI discussing adding support if they could get their hands on them which unfortunately fell through. Even if what you say were possible- who has one? Are they supposed to support something that only a handful of people has, has not been released, and that's next to impossible to get? Reality is; insteon is dead. You have a new guard acting like the old guard which looks like 3rd party support/cooperation isn't a priority. It's not worth it to anyone to spend time and effort trying to reproduce a hack that 1 person popped up on here saying they did and then disappeared when there is a tried and true method of restoring bad poms along with a resident expert that's more than willing to help (along with a repair person on ebay).

Reverse engineering. It's not that it can't be done. It's that no one wants to hack it together to make it work. HA is open source so anyone can work on things while UDI is a company that has to answer to themselves and investors. It's not cost effective for them to take the time for a dead system that even the owners aren't currently concerned about themselves.

Were they wireless devices or controlled by wireless devices

I'm not referring to this as an installer. I'm referring to UDI having to take the time to reverse engineer how it works to get the isy to support it. It's not as simple as hooking up a standard PLM and getting it operable. This is an issue insteon needs to solve not UDI ***See Goose66 post above.

For the consumer it's useful. For business purposes not so much when you're spending time trying to make something work without support from the mfg... Especially for a dead/dying brand. That's time and resources being taken away from other things that can earn more money for them.