Not sure what changed recently, but my zwn-sc7 that had not worked in about a month just stayed working? I never loaded any new code or anything?
Two days later, back to nothing working, not even button 1, try the Configure Tile, no help… Turn unit in or wait for ST to fix some backend settings they keep messing up?
It’s sounding more and more like a defective device, particularly since other people have been able to add new ones that seem to work fine. Those are always a pain to debug. You have my sympathies.
So. Does anyone have any ideas as to what the heck is going on with regards to the primary outstanding issue with this device?
Pressing a button after the devise has not been used in a while does not activate the desired action — one must press the button a second or third time.
Where is this bug?
a) device itself — does this behavior show up on other zwave controllers? I’ll investigate the behavior seen on other forums such as vera, zipato, etc
b) device type — is there code that is causing it to ignore the first press?
c) associated button apps — do app’s go into an idle state and thus need to be woken up? Perhaps the device type doesn’t check to ensure that the app has received the message? I’ll look into whether actions specified in the app (turn lights on/off/toggle) behave differently than actions specified as ‘hello home’.
Does anyone else have other theories as to what is going on? How can we actively solve this?
I’d like to be able to deploy a bunch of these in a vacation rental house, but telling short term renters that they may have to poke at buttons a random number of times isn’t going so well for the one that I’ve put in there as a test. =/
2 Likes
@codytruscott… yeah, this is driving me bonkers too. Seemed to be working properly for a week or two, then broke again last week. My girlfriend hates me.
Depressing news from ST Support, no plans to add the ZWN-SC7. I’m confused, a system without a wall-mounted controller?
“While device certification team is constantly adding new products, the Enerwave ZWN-SC7 is not on the supported list, and may not ever get added. I checked in with my device certification team, and it is not on a list to get certified.”
“Wall mounted controllers are so 2000’s.” (sarcasm!) 
What happened to the Community written handler, though?
If I understand correctly, while Community SmartApps get priority for submitted code certification, “working” Device Handlers have a decent chance of getting in the Device queue with perhaps a little promoting.
If we can’t get it working, though, then that implies SmartThings engineers would also find it to be a resource consuming challenge.
and that’s why we need them, so any granny visiting the home knows how to use everything, if a baby and a grandma dont know how to use it, it isnt user friendly enough.
4 Likes
Not at all. They are useful and, as @Eduardo_Veras mentions, they work even for little kids, something wall mount tablets often don’t. Iris and Staples Connect both have them, and neither was around before 2011.
Heck, Philips added the Tap after Hues first came out because there was so much demand.
Plus, read @Tyler is working on getting more handheld and Wall mount controllers certified as SmartThings compatible.
This one, it appears, is not on that list, but it’s not the form that’s the likely issue.
1 Like
Gave it one final try with the ZWN-SC7, it was totally unresponsive to to programing via app, all LED’s flashing. Configuration tile no help, tried to exclude, but no response to ST, forced it then factory reset ZWN-SC7. Reincluded to ST and then button 1 functioned properly, but all others just made all LED’s flash. tried reprogramming and configure tile, no joy. Finally killed power to ZWN-SC7 for a min, powered back up and all good…
Now I seem to have the issue everyone else has, most of the time I need to press a button twice…
Honestly, @jimmay3 , yours sounds like a failed device. How old is it?
The typical double press issue, as I understand it, is people saying that when the device hasn’t been used for awhile ST doesn’t seem to have its prior state and so needs an initial extra press on each button to prime the pump. But after that it’s ok again. Is that what you’re seeing?
That’s correct, it’s not on our current list of supported devices or on our list of devices that are coming up. This is because we don’t have platform or hub level support for scene/secondary controllers in a way that would allow this device to function as intended. Additionally, our current implementation for remotes/buttons is limited.
I do want to clarify though that we’re looking at how (and when) we can add support for devices like this. Once the infrastructure is in place we’ll take another look.
Thanks!
2 Likes
Yeah, the penny finally dropped for me last week: if smartthings relied on Zwave scene commands, those controllers would only work with zwave devices. And since the ST ecosystem includes zigbee relays and lights and, of course, Hello Home Actions, that wouldn’t make sense. In order to have a button device that can control a zigbee bulb plus a zwave appliance module plus a Hello Home Action, it has to use something other than zwave scene commands.
Maybe I’m missing something, but it seems to work fine for me to just use this device as 7 individual buttons, not as a scene controller. The device type supplied in this thread sets it up this way already. The only thing that makes it feel like a scene controller is that the light remains lit for the last pressed button, but I don’t think that matters much. Especially if you set up the buttons to run actions that feel somewhat like scenes, then it may be nice to have that button lit.
1 Like
A few months. Working about 95% capturing presses now.
I must be reading the above wrong, the ZWN-SC7 is a zwave scene controler that via ST it can control zigbee devices and zwave devices the same. You can program a button to operate multiple mixed protocol items, so not sure why we wouldn’t want to support the device. ST is what makes this device a gem, its able to control any and multiple devices on your ST network, including mode changes and hello home actions.
1 Like
No, the double press does not appear to be a wakeup action for the device or a state issue, just randomly missing, more like a network timing or delay or priority issue with ST. I’ve used a button to toggle a device on and off, I could press it 3 times in 5-10 secs and it will flip the state perfect, then the 4th press it might miss and pickup on the 5th only seconds later. Just randomly misses, so it’s a little annoying. Seems like the devicetype is changing on the app button status ok, but the SmartApp just fails to reply to the device request.
Seems to be similar issues with the community myq SmartApp status problems. Seems like non official supported SmartApps have a lower processing priority on the servers causing processing delays.
You’re reading it right, except that I said if it relied on zwave scene commands. Which the community-supplied device handler does not.
There are two separate issues here.
-
Which devices should be fully supported by SmartThings as their manufacturers intended them to be used
-
Which devices can be used by SmartThings with a custom device handler that, say, treats each button as a contact sensor or through some other variation.
The Enerwave 7 has been working for many community members using the community-developed device handler that @obycode mentioned, but in the second category.
Tyler was discussing the device in terms of the first category, which is what I was responding to, as I have been one of the people asking for several months why SmartThings, as a zwave controller, had not implemented the Zwave scene command set.
Sorry for any confusion.
I don’t think SmartThings could announce “official support” for a device that didn’t work as the manufacturer intended without a lot of footnote caveats. And announcing official support for a device that utilizes zwave scene commands without having any way of supporting those scene commands would be really tricky to make clear to a typical consumer.
But of course I agree that many devices can be made to work unofficially in the ST ecosystem by pretty much ignoring the command set the manufacturer got the device certified for and rather just dealing with Basic Set commands.
Which is why I suspect @jimmay3 may just have a defective device right now. Other people have the same model working without difficulty except for the “prime the pump” issue.
@jimmay3 , this device has a two year manufacturer’s warranty. If you have proof of purchase, I would ask them to exchange it and see if that fixes the issues you’re having.
http://www.enerlites.com/storage/zwn-sc7-7-button-scene-controller.html
2 Likes
Not true, many have had setup issues, it comes and goes and seems more relayed to timung of ST backend changes, mobie app updates and ST outages/delays. Should I turn a device it that functions great for a few months then quits for 3 days then mysteriously starts working on its own after a ST email comes out saying they fixed some system problem. Hard to say, might buy another and see if they fail at the sametime for no apparent reason.
1 Like
Oh… I guess y’all didn’t realize that I was being sarcastic, facetious…, sorry.
I’ve been asking and hoping for wall controllers since Day 1, but had the impression that SmartThings didn’t feel they were appropriate for the product – i.e., SmartThings seems to feel that wall controllers, or landscape mounted tablets, or constant labels on Thing Tiles, frankly, are unnecessary features. It is hard to get any different impression after 3 years of no movement on this.
Meanwhile, I am “satisfied” with Aeon Minimotes velcroed to my walls… And I thought we had managed to get this Enerwave 7-Button working in the nearly the same way.
@mattjfrank managed to replicate the Minimote handling almost entirely.
Why did it stop working?