Was curious if you had implemented Zigbee Switch support for the Enbrighten 43078? It’s not loading a default edge driver
For more info on this model: In-Wall Smart Switch with Energy Monitoring (Decora Style) - CSA-IOT
n/m looks like you just work on zwave drivers
@Mariano_Colmenarejo does a lot of work in the Zigbee world. Check out his drivers.
Hi Phil,
I posted about my Jasco 14285 over here: https://community.smartthings.com/t/jasco-14285-40-amp-outdoor-switch-and-power-metering/243239/24 and was wondering if there is a way to increase the frequency of the reporting value for power. The minimum is 5 min.
The 5min reporting still doesn’t seem to be enough. The well pump runs for about a min or two max. I do get a trigger now and then if the timing is just right, but most times not.
What would my next steps be to try to get the driver to poll the device? Once I setup the SmartThings CLI, where do we go from there?
know of edge driver for GE smart Motion Sensor ZW3602
thanks!
How can one figure out the firmware of their Jasco switches without IDE any longer? The API tool that someone created also doesn’t show it. On a different post, someone mentioned your Z-Wave Explorer. I installed the channel and then that driver but can’t figure out how to get it working within the ST app (perhaps that’s not where I need to go?). Any help would be appreciated.
Swap the Z-Wave Explorer driver for your existing Edge driver on any Z-Wave device you want to review, then back out of the device presentation. When you reopen the device presentation, the device information will appear.
Don’t forget to swap the driver back out when you’re done.
1 Like
Does swapping to this driver cause Routines to be deactivated or deleted because of missing capabilities?
For instance, if you’ve got a Routine for a motion sensor and swap to the explorer driver, no motion sensing capability causes the Routine to be invalid… ?
1 Like
Just learned the hard way ---- YES!
SmartThings needs a way to keep everything in place and put in a placeholder!
1 Like
Not ideal as routines got deleted in this process. Does CLI allow you to view firmware? Maybe I need to go that route
What are you planning to do with that knowledge? If you’re wanting to update firmware on a device then you’ll need a separate z-wave controller like one of the USB sticks. If you already have one of those, you can join it into your ST z-wave network and use it to query firmware version of each device.
1 Like
Agreed, not ideal. It’s a good practice to add a virtual device to any routine that might be potentially be affected before swapping drivers with varying capabilities around. The virtual device acts as a kind of placeholder, ensuring that only that device—and not the whole routine—will be affected.
It’s another reason I prefer Rules to routines.
1 Like
Where can one find more about rules and how to integrate them?
I don’t want to move this thread any further off-topic, but you can start here:
3 Likes
I have a weird problem with my UltraPro dimmer, I have a routine that turns it on at sunset with dimmer set to 100%, and it dims to 1% at midnight, but everytime it only turns back on at 1% and not 100%, what could be causing this?
It would be helpful if you post screenshots of your routines. Does your sunset routine just set the dimmer, or does it also include “Turn on” as an action? If it’s the latter then that could be the problem as the routine would be sending two different z-wave commands to the switch.
1 Like
And in the current ST implementation, setting the dim level turns on the switch anyway.
1 Like
In the current implementation of ST, you don’t. I tested it this morning. Unclick “Turn on” in the Actions of your Routine and just set a dim level. Your light will come on.
In the old architecture using a DTH, there was an option for whether the light would come on or not when setting the dim level. I know it’s not available in @philh30’s driver and even if it was, I’m not sure that it would help given the ST current implementation.
1 Like
Oh…you can uncheck turn on LOL, that was so not obvious, this will surely address the strange behavior I was getting, I would look at my other automations also
Thanks guys!