upstatemike

If the radio was in range it should have. PLC was probably bridging two areas that were out of radio range with each other so when the PLC got squashed the only path was broken. You could build out with more dual band devices just as you would with RF only stuff or get a filter for the deep fryer to keep it from causing problems.

@apostolakisl 1) I think they need to use the existing line, already UL approved and tooled at the factory, as a quick way to resume cash flow but I think both the look and the feature set will need to be refreshed ASAP to give new customers a reason to consider Insteon. 2) I agree on licensing but it might be hard to find anybody who wants to at this point, especially if there is much of a fee involved. (Of course without the revenue from licensing there is not much reason to do it.) 3) Maybe a compromise is a dealer network that can do firmware upgrades without trying to support the headache of letting end users do it. 4) PLC is the magic bullet that lets you add devices anywhere without "building out" a radio path to remote devices. It is already in the protocol, it just needs to be marketed better. I don't buy the theory that PLC interferance degrades RF communication. 5) Specialty items are great but it is more important for them to get profitable at this point so I don't see them tying up capital in low volume products right away. If they do invest in specialty devices it should be strategic such as a new Fanlinc module that is the size of a Micro Module so you can actually fit it in an existing electrical box. Competing protocols still don't have a viable offering to address the need to control both fan and light in a location that wasn't wired for it. 6) Insteon has always had a "cut off our nose to spite our face" attitude when it comes to UDI. I have always wondered what the real story is behind that and I don't know if things will change. It would also be interesting to know why the UDI purchase offer was rejected... did this group of "users" really have a better offer? Or was it just "No to UDI no matter what"?

My questions are also simple: Will Insteon follow through on the Nokia deal or at least inorporate those new designs into the regular line in order to put a fresh face on Insteon? Will Insteon finally acknowledge the chronic capacitor issue and insure that all new products have proper capacitors that do not lead to premature device failures? Will Insteon encourage integration with major user platforms such as Smartthings, UDI, Hubitat, and Home Assistant in order to build good will and product buzz within those communities? Will Insteon seek partnerships with non-competing brands such as Hue or Sonos to expand the appeal of an Insteon based Home? Will Insteon aggressively market the advantages of their technology over routed protocols with ads that talk about smooth scene control v.s. "popcorn effect", the ability to add devices anywhere v.s. "building out a network", and so on? Will Insteon make themselves a reliable partner that professional integrators can depend on for support and realistic wholesale pricing? Will Insteon use their strengths to challenge direct competitors such as Lutron Caseta by emphasizing products the others don't offer such as the Fanlinc? Will Insteon engage more directly with end users on forums to understand what those users are really looking for? Perhaps have a full-time product ambassadore similiar to Eric at Yolink?

That means Smarthome has successfully linked to your checking account.

I edited my post because I meant Elk, not ISY. My ISY uses a different email account but it should work the same. When you turn on 2 factor authentication in GMail it will give you an option under security settings to generate an app password. In ISY email settings replace your regular GMail password with the 16 character app password. Don't make any other changes to the email settings and everything should resume working.

I applied the 2FA fix to Elk M1, Blue Iris, and my PC that is still running Outlook 2010. Worked fine on all of them.

Both Homeseer and Home Assistant are using old hubs as interfaces (virtual PLMs) but I don't know any details. Is their method not compatible with Polisy?

If you are concerned about how Matter will impact the future of Home Automation you might want to try this exercise: Make a list of the primary problems in automation today; Popcorn effect, 2.4GHz overcrowding, lack of enforcement to standardize implementation of advanced features, etc. Then go through all the announcements related to Matter to see how many of those problems will get resolved when Matter becomes available (spoiler alert, it is a very low number). Then decide if Matter is worth worrying about or not.

So aren't we just talking about a broadcast protocol and individual devices that maintain a table of broadcasts they are supposed to repond to and how? As far as I know there are no sessions and device "awareness" is nothing more than the list of addresses and broadcast commands that a given device has stored in its table to listen for. This has a few advantages: The tables can be built without a central controller using device-to-device association (button presses) If there is a controller the various associations and actions still work when that controller is down. Many devices can respond to a single broadcast so group actions are smooth Replacing or restoring the controller gateway (PLM) is not the the dramatic, difficult, nightmare that it seems to be with other technologies. You can repair/restore the tables in devices in a couple of minutes... no waiting to "rediscover" neighbors or "re-optimize" routing info. When you program everything you are done. No waiting for the mesh to settle or heal or whatever. If you know the address of a device you can enter it remotely to add it to a system. No crawling into the attic to push the pairing button to initiate the link (though you still have the option to do it that way if you want to) A broadcast that is repeated by all devices is simpler and naturally resilient to changes in device topography. A single key device can really screw up a routed protocol if it fails or is removed and the recovery time is never as fast or smooth as the product brochure promises it will be.

I like the way Pico remotes match the styling of Caseta switches so they mix well in a multi-gang plate. If Caseta switches to the Sunnata look will there be matching Sunnata Picos as well?

I needed a lot of APs to cover the shaded areas but definitely had to cut back the power on 2.4GHz radios to avoid making things worse with interferance. I should probably shut off the 2.4GHz radios on half of the APs to further improve the RF environment. I still need 5GHz radios on all of them to get full 5GHz coverage.

I have used a red Insteon light pipe with the yellow LED Icon to mae a dark orange. It fit OK. You are not going to turn a yellow LED white though. All you can do is make the white LEDs on Insteon switches yellow to match using yellow light pipes.

You could put yellow light pipes on all of your Insteon switches and get everything to match that way.

As I recall the Icons had green or yellow LEDs with clear light pipes so no way to get to white.

Just seems like they should have made the names different for appearance sake if for no other reason. Are they trying to look as sleazy as possible for some reason? If I was a creditor I woud not trust this company was working to benefit me rather than working to benefit the debtor.

"despite their similiarity in name, Assignor and Assignee have no corporate affiliation to each other." So how does that work?

Not area but rather penetration issues. 5 stone chimneys. All plaster and lathe walls. Lots of tile with metal backing. Across 4 floors. Could get away with less for 2.4GHz but 5GHz has no penetration at all so I have to cover the shaded areas.

Now that I think about it, I have never owned a Wi-Fi router. My first Wi-Fi setup used access points connected to my already existing router and switches. Currently I have: 1 dual WAN router with a hot spare (all config changes get copied to the spare on a regular basis) 1 24-port managed switch at the core of my system with a 24-port unmanged hot spare 4 8-port POE switches with unused ports on each so I can move things around if one of them fails 5 8-port unmanaged switches in enterainment rooms and the automation rack (I have lots of spare small switches) 10 Wireless Access Points Typical load is 63 wireless clients plus 66 wired clients (including the APs) I have 187 DHCP reservations. Except for a few Lifx bulbs I generally do not use Wi-Fi based lighting products.

You should advertise the hubs on the Homeseer forum.

As always I approach any selection with a checklist of critical features and then look for what ticks all the boxes. For a router it would be: Multi-WAN with option for failover or load splitting. Enough RAM and CPU to max out the full available address space without performance issues No limit to the number of addresses that can be included in the DHCP table Can manage wireless access points in the same interface that manages the router All management pages show devices by the name I assign them; I'm not going to troubleshoot a couple of hundred clients using MAC addesses! This needs to include any view of DHCP assignments, active clients, clients connected to wireless access points, session information., etc. Basic VLAN and Port forwarding Some basic rule capability (restrict a certain client to only use a particular WAN port, etc.) This is pretty basic stuff but it immediately rules out any consumer Mesh solution and a lot of the so called prosumer wireless routers.

Here is an example of the latest thinking around Matter:

Where I have basic lighting functionality that depends on a controller I so far haven't had any problems but I am mindful that a controller coordinates many different integrations (or nodes) any one of which could go rogue and crash the controller and disable my abilikty to control those lights... even if the integration that went bad has nothing to do with lighting. The fact that Insteon kept device link info including how the device should respond to a given broadcast from another device, made it pretty much immune to this concern.

A good example is how when contacting Zooz support they always refer to how they address your particular issue on the Smartthings platform. They have very limited knowledge around UDI Isy994 or Homeseer or similiar platforms and probably see no urgency to change that.

Pull it out and make the decision on whether to reuse it later on. The effort to swap them out is annoying but worth it to have a "clean" sale with no technology questions/issues.