upstatemike

I guess my problem is that I don't care for the look of "new" homes. Anything less than 100 years old is just an eyesore to me, but to each their own. I do agree that Sunnata switches are a big improvement over the Maestro style though. (No opinion on Nokia until they actually become available... later this year?)

I am puzzled by the notion of a light switch's appearance getting "long in the tooth". I have switches from the 1940s that still look fine to me. I can't imagine changing them just because I suddenly feel they have gone out of style.

Some thoughts on Z-Wave vs Insteon: Z-Wave has a pretty good variety of devices from bulbs to keypads to switches to plug-in modules to wire-in modules. Insteon used to have all of these but as you noted the selection is rapidly drying up. Insteon is pretty logical in handling associations/groups/scenes using the same basic mechanism to accomplish the requirements of each. Z-Wave has some limited "line-of'site" association ability for very small groups of devices. Z-Wave scenes are kind of hit and miss and a lot of folks skip them and just replicate that function with "then" statements in a program. Insteon is a broadcast protocol that is pretty resilient in the face of topology changes. Z-Wave is a routed protocol that can struggle with topology changes. Also if the routing info gets scrambled it can be time consuming to get things sorted out. Insteon generally lets you work with program objects that represent each button or load. Z-Wave has you monitoring the changes to a Central Scene and pushing coded parameter values to accomplish things. You can replicate most (not all) insteon functionality with Z-Wave but there is definitely a learning curve and you will encounter the term "work around" a lot.

That is a good point. Before ISY was ported to Polisy the only place it could run is on a 994i so it was natural to just refer to the combintion 994i and ISY software as just an ISY... especially because the 994i is dedicated to ISY and can't do anything else. Polyglot running on a Ras-Pi or PC would always look for ISY on a 994i because that is the only place it could be. Now it can be co-located with Polyglot running on the Polisy hardware box so thinking of ISY and 994i as synonymous is no longer valid and I imagine referring to it/them that way can easily confuse newcomers. Once understood it is easy to picture yet somehow tricky to express clearly.

The second one.

I think it just verifies that they are on opposite sides of the split 220V service (180 degrees out of phase with each other).

Cool bracket! I bet that orientation puts the antennas in a more favorable position as well.

They can sell pre-orders at a Black Friday discount... unless they aren't sure if they are ever going to get the stock to fulfill pre-orders?

No Black Friday deals. I guess Nokia isn't planning to target consumers directly. Must be an "Integrator Only" product.

I have to agree that simply building out a Z-Wave network to include a remote or otherwise difficult loaction is not always practical. If Z-Wave was a broadcast protocol then having devices act as repeaters could be a solution because you can reach a point where the cumulative effect of many broadcast repeaters solves your problem in a way that is resilient even if some of those repeaters are moved or unplugged since no particular one of them is likely to be a single point of failure for getting the signal through. Since Z-Wave is routed then any change to the signal path requires the system to find a new route which may not happen instantaneously. I would be uncomfortable having to depend on that solution for any coverage beyond 1 or 2 hops. I know Homeseer solves this problem by offering network attached controllers (Z-Nets) that can be placed in strategic locations to provide coverage without having to fill the gap between those areas with extra Z-Wave devices. Hubitat also has a solution by allowing multiple hubs to be linked over the network which basically accomplishes the same thing. I wonder if using multiple Hubitats as your Z-Wave interfaces connected to ISY/Polisy via a Hubitat Node Server would create the solution you are looking for?

Less than a week until Black Friday! Excited to see what the sale prices will be on the Nokia switches and keypad.

Clearly.

OK I thought we were talking about solutions to boot things remotely without the Internet and whether anybody would still make devices that utilize land lines. My mistake.

OK Like the failover on a dual band router. You are right when it talked about setting the time delay I didn't understand what it was doing. I'll slow down and read all of the words next time.

I'm not sure if I would dismiss land lines as 70s/80s technology as if they are no longer needed at all. Large businesses still use wired phone systems with multiple lines and extension to extension calling/transfer. I don't see the technology disappearing entirely nor the products thst support it. They might just be more expensive commercial devices rther than consumer oriented items. Small to Medium sized businesses can get a small PBX and 3 or 4 land lines cheaper than dealing with a VOIP system where you need to worry about a network designed for traffic prioritization and QOS.

The point is that there is no available Internet when the reboot is required so these will not work. It must be a technology that connects to the home without depending on the Internet at all.

Still says "Email me when available". I wonder if they will launch in time for Black Friday? You would think Nokia would want to leverage the holiday season in introducing this new line.

Oops. The Nokia store no longer says "late October"; it now just says "Email me when available".

Last business day in October and the site still says "shipping late October" so preorders should be shipping now. Hope to hear back soon as folks start to get their items and test them out!

Not going to pretend I know the answer for your situation but I did have a similiar problem with a GFCI in my garage that was tripping from an Insteon switch. The switch along with an outside outlet were downstream from the GFCI. The outlet controls some outside lights but not the outlet. I swappped the GFCI and had the same problem. I swapped the Insteon switch and the problem stopped for awhile but then returned. I replaced the Insteon switch with a standard toggle to further isolate the cause and the problem stopped so it wasn't something else on the circuit. I changed the wiring so the Inseon switch was ahead of the GFCI while the outside outlet remains downstream from it (protected) and I have not had any further problems. This all happend last winter when the air was very dry. I don't know if there are some situations where Insteon devices intermittently leak current to ground but that is what it looked like. I should have lifted the ground connection from the insteon switch before changing the wiring to see what that would do but I didn't think of it in time. I don't know what the actual cause of the problem was or if it relates to what you are seeing but just mentioning because it was another case of Insteon and a GFCI not getting along.

Also watch eBay. Somebody might suddenly have a bunch to sell for $200 each.

Says sold out for me. They must have found 2 that were returned or something.

FYI- Hi Michael, We would recommend using the central scene commands here to control the switches remotely. You would set a single click on the ZEN32 button to toggle the state of the controlled switch so that it changes state anytime the button is pressed. That would take care of the double-press issue you've experienced with direct association. To keep the LED indicator in sync, you would set it to always on in the settings and then create a rule to control the indicator separately based on the status of the main switch. I'm not sure whether HomeSeer supports that last feature since this is something that was going to be added at a later date when we last followed up about the integration so we will work with their team to make sure it's implemented shortly and I'll circle back with you once we have some news here. In the meantime, would you be able to try the central scene solution instead of direct association to see if it works better for on/off control? I look forward to hearing back from you. Agnes Zooz Support Team

I have been through several Zooz support folks at this point and was just told they are escalating to a supervisor. No guarantee but at least they are taking the issue seriously. I think it might help if they hear from more people on this issue.

I just installed one of these in a Homeseer system and have the same issue. No way to associate or reference the buttons to stay in synce when the load of the other device is changed locally. Going to try changing the LED "Always On/Always Off" settings to see if this solves the problem. Also might try installing it into Hubitat to see what my options are there. I don't currently have a Z-Wave radio attached to ISY/Polisy so can't replicate what you are doing. If I come up with a clever solution (doubtful) I ill let you know. Best answer would be for Zooz to do a firmware upgrade to provide better access to control the state of the 4 scene buttons. It would also be helpful if you put in a ticket to Zooz to raise awareness of the issues around this use case. I have one open and the more demand the more likely they will address it.