xlurkr

I want to turn on the fan in another bathroom. They both exhaust into the same duct, and there's some crossover. So I want to have both fans on whenever either one is switched on. Eventually I'll add some timer logic, too. Status will probably work. I won't know until I automate the other fan. It doesn't need a double switch, so I might go with Insteon for that one. Still mulling it over. -Tom

According to the release notes, this "Basic Node" stuff was added in 5.2.0, so I don't have that option. -Tom

It seems to work with Status, but not Control. Maybe I can make that work. -Tom

I declared victory too soon. The relay switch does report its status to the ISY when manually actuated. But a program that starts with If 'ZW 033.1 On-Off Power Switch' is switched On' never triggers. Dang it. @asbril, I'm guessing you have programs triggered by the relay. Do you do anything special to make it work? -Tom

Wow, that ended up being a lot of worry for little reason. The solution started (I think) when I observed by accident that the Zen30 worked well when I had the dual outlet box rotated so that the GE outlet was facing the ISY. If rotated the other way, it was flakey. Was the Intermatic shielding the GE, or interfering with it, or intercepting the signal and relaying it incorrectly? Who knows, but I took the Intermatic out of the box and, lo and behold, the Zen30 worked as long as the GE was between it and the ISY. That gave me the confidence to proceed with the installation. I replaced my bathroom outlet with the GE, and installed the Zen30 and a KPL. Right now, it's all working...except the dimmer STILL needs to be queried if I want the status to be correct when it is manually actuated. Later I'll capture some logs and post here and/or create a support ticket. I can turn it on and off in programs, and the status shows correctly then, and that's probably all I really need. But I'm accustomed to being able to use every switch as a controller or program trigger, so that's my ultimate desire. @asbril, thanks for the support, and especially for being the original guinea pig for this switch. It is an (almost) perfect solution for me. -Tom

@asbril As far as (*), that's exactly how it is configured. I have always included it about 5 feet away from the ISY (since first trying about 10 feet away and failing). It works fine there, with rapid response and no communication errors. When I unplug it and move it any significant distance from the ISY, the errors start, and get intolerable by the time it gets to where I want to install it, which is less that 20 feet from the ISY, with a few walls between. As far as (**), I have done that, too. I have another pigtailed box with two outlets in it: a GE/Jasco and an Intermatic. Both of them are easily controlled by the ISY. As my final attempt to fix the problem, I plugged it in halfway between the ISY and the Zen30 final location, with only one wall and less than ten feet between them. First I tried it without healing, and then with a network heal. I still get the errors. All this time, all of my other Zwave devices - that double outlet box, another GE/Jasco outdoor plugin module, and my Schlage lock (thank God) - have continued to work without a hitch. So I'm thinking it's the Zen30, and either it's bad, or it isn't well enabled with 300 series/5.0.16C. Given that it does work OK within 5 feet, I'm thinking the former. But also given that the relay and the dimmer behave differently, and the dimmer doesn't report status for me like you say it does for you, maybe the latter? I'll probably never know unless I upgrade, but I'm worried about the Schlage lock and 500 series range problems. -Tom

This thing is totally kicking my butt. I've done 11 excludes and includes now, and one hardware reset of the switch (after exclusion #7 or so). I can't seem to get it to behave well any more than 5 feet from the ISY. I have tried putting another device between it and the ISY, and doing a network heal several times, but it's no use. It keeps getting "can't communicate" errors on the dimmer part, but not on the relay. Another weird thing is that several actuations of the relay button can make it connect again - sometimes - but eventually it fails again. I'll probably permanently install it tomorrow, because I really need a dual switch in that box, even if it isn't automated. But if anyone has any suggestions on how to get this thing to behave - other than upgrading my dongle and moving to 5.3 - I'm all ears. @asbril: did you ever try this switch with the 300 series dongle and/or 5.0.16? How far is it from your ISY? -Tom

Updated to 5.0.16C, and the pending updates are gone. I hope they'll still be gone in the morning. The Dimmer node still must be queried, and there are still no options for setting the variables. After I do the physical installation, I'll do a network heal and see if anything changes. If not, that's OK. I only need to be able to set the dimmer on/off. The relay MUST be sensed when manually switched. Someday I'll upgrade to the 500 series dongle and >5.0.16, but the war stories of that dongle with the Schlage locks are holding me back. -Tom

I'm halfway through installing one of these and it's not going great. First, let me state that I'm on FW 5.0.16B, and have the 300 series dongle. After several false starts, I have the set of nodes displayed in the attached image. I can control the Dimmer Switch node, but I need to query it to get it to show the correct status. It also doesn't have an Options button, and looks exactly like an Insteon dimmer, so I'm wondering if the ISY got confused when adding it. The 26.1 On-Off Power Switch can be controlled, and also automatically updates the status. Cool. The Binary Switch and Scene Buttons are blank, but that's consistent with what everyone else is reporting. I could probably live with it as it is now, except that, as the image shows, it claims that updates are pending to everything except the On-Off. It's been that way for 8 hours now. I have clicked "Write Changes" on the dimmer, right clicked and selected "Write Updates to Device", rebooted the ISY, and nothing changes. I can certainly exclude it and include it again (will be the 6th time), and might just try that after posting. I could do a network heal, too, but I'm reluctant to, because I spent 4 hours yesterday adding a Schlage lock, and I'm afraid to do anything with network-wide consequences unless absolutely necessary. Also, the Zen30 is in a temporary box close to the ISY to do the inclusion and setup, and I'd rather not heal until it is installed in its permanent location. Recommendations, anyone? -Tom

And I can verify that if you try to log in to your account on the website, the only option is a button that redirects you to the portal. -Tom

@Michel Kohanim Is there anything you can do to get the AC (and REST calls, etc.) to reflect that the STATUS of a dimmer is 100% if it has an on level of less than 100% (or is currently at <100%), and is turned on a second time to go to 100%? If not, OK, I'll use lilyoyo1's workarounds. But I thought you might want to think about eliminating one possible source of STATUS being inaccurate, if it's not too difficult or problematic to implement. -Tom

I have been making some changes lately to my ISY, and just noticed something. I have several dimmers and KPLs that will turn on to the on level (let's say 75%) when first manually switched on, then go to 100% when switched on again. Not sure if all Insteon dimmers do this, but probably. Anyway, in the AC and UD Mobile and maybe all other interfaces (tbd) the status of the node remains at the initial on level after I do the second manual on actuation. Is this by design? Even weirder, if I dim it manually (up to 85% let's say), the status reflects that. Then if I manually press on again, the light goes to 100%, but the status drops to 75%. Sorry if this is well known or a defect that has been fixed. I'm on 5.0.16B. I was trying to create some scenes with levels of less than 100%, with lights I couldn't see from my location, and the difference between the status as reported by the AC and the actual light levels was messing me up. -Tom

@simplextech: Do you know if ZLink has their own switches that are the same as the 200 series of HomeSeer? The naming and feature set of the ZLinks look more like the HomeSeer 100 series. -Tom

FWIW, it is stories like this that are keeping me from upgrading to the 500 series board and > 5.0.16. I have no need to upgrade, but I'd like to stay current if possible. I only have a few Z-Wave devices, but I don't want them to stop working. -Tom

When I was having my problem, I copied Michel's command and pasted it into a ssh terminal session on the Policy. I got the HTML response, and bash choked on it. Two days later I did exactly the same thing, and it updated correctly. I would say that the server destination has occasionally been borked. Not sure how or why, but this isn't just about browsers or incorrect paths. -Tom

This morning, the curl | bash command worked, and I successfully upgraded to 12.2. The NS installed correctly. After initial configuration, it's working fine. Thanks to all for your help, especially Rob. The most logical conclusion is that the current version of this NS requires version 12.2 of the OS. I hope 12.2 doesn't break any of the other NSs, but I suppose if it does, the authors will fix them over time. -Tom

Michel: It is working this morning. It was not yesterday. Curl was returning HTML, not a bash script, and bash was choking on it. See my first post in this thread. I don't know what changed, but it was broken, and now it's not. Thank you. -Tom

Ticketed. -Tom

Ticketed. -Tom

That's what I'm saying. Thanks for the the technical version. What I've been trying to do all day is run my first NS on my new Policy. The Policy is up-to-date, as far as it knows. The NS won't install correctly. Everyone trying to help me has already upgraded the OS to 12.2, so they told me to do so. I tried to and can't, apparently. I'm out of next moves. -Tom

Can you try this yourself? The curl command on its own, I mean. I get back some html, not an install script. -Tom

Couldn't you run the curl command and pipe it to more, like I did, just to see what you get? I wonder if that command returns something different now, compared to when you early upgraders did it. Michel said this was temporary, as he was moving to a new upgrade process, or something. I will open a ticket, once it looks like my situation is unique. -Tom

OK, I will, but isn't curl returning the wrong thing? What I got back doesn't look like a shell script to me. -Tom

Yes.

Yes, ssh in Terminal on a Mac. I am using the correct pipe character. I got the curl output I posted above by piping that to more. What do you get, right now, if you execute the curl command? -Tom