OpenZWave and Jasco 14299 dimmer

Configuration Z-Wave
1

Hello all!

I migrated over to the new OpenZWave beta and all is working pretty well expect for a light I have.

I have a script that turns on the light when I go to bed at 80 brightness and then over the next 30 minutes it turns the light off.

The script looks like the following:

sequence:                                                           
  - data:                                                             
      brightness: 80                                                  
    entity_id: light.hallway                                          
    service: light.turn_on                                            
  - delay:                                                            
      hours: 0                
      minutes: 1            
      seconds: 0            
      milliseconds: 0                    
  - data:                   
      transition: 1800      
    entity_id: light.hallway
    service: light.turn_off

The problem is the light never turns off :slight_smile: I have seen this issue in other threads in regards to the COMMAND_CLASS_SWITCH_MULTILEVEL and modifying the zwave config files.

I wonder if anybody else is having this issue and can suggest a workaround or a potential fix?

Thanks!

2

If you want that device to work properly you have to poll it. Also, I recommend you use Zwave_JS as OpenZwave (beta) at the current time doesn’t seem like it will be getting updates as the main developer has decided to take a break.

FWIW, I removed all my 14299 dimmers from my setup because they were so problematic on every network I put them on (OpenZwave, Smartthings).

3

Adding the command class gets it to properly update in the UI after it turns on (with polling). I believe that’s already added to the current configurations.

4

Well that is good to know. Unfortunately the dimmer was chosen specifically because it’s a 3 way light switch in on old house without a neutral wire.

Anyhow - in the old setup before OpenZwave (beta) it worked quite well.

Is there an easy way to enable polling with OpenZwave? This is something I have not done before.

5

There’s no easy way to do it. You have to go through MQTT commands to enable polling.

I suggest you move back to Zwave 1.4 and wait until polling is available in zwave_js.

6

Actually, you don’t need polling. I must have been dyslexic when I read your post originally. For some reason I read your model number as 12xxx not 14xxx. You need to add the command class, although it should already exist in the current rev. Either way, If you switch to Zwave_JS, that device will work fine. I have 5 of them running on my network.

Sorry for the confusion!

7

I dug a little deeper into this, the config for this device doesn’t exist. So a whole new config file would need to be made and it would need to be added to the manufactures.xml file. This is no small task. It’s possible that it uses another configuration file. What does the openzwave admin say that it found?

8

I moved over to ZwaveJS and I will do some testing and see how that goes. It was not that hard to move over as I only have about 7 devices so most of the work was renaming after they were all found in Home Assistant.

9

FYI, zwave-js does not support transitions at all right now.

10

Ok - thanks for the update @freshcoast. Do you know if there is a plan to support transitions in the future?

Now that I am moved over I would kinda like to stick with it haha

11

@petro - openzwaveadmin was correctly identifying the device. I would have to roll back now to get you a screenshot.

1 Like
12

So - first of all - ZwaveJS is just fantastic. I have never had ZWave devices respond so quickly before and so far stability seems good (although it’s only been 24 hours).

I did some digging into duration and it seems like there is a ticket in place for the upstream project.

I’d actually love to help but I have no experience building / testing that code. I work primarily as a Java developer so if I can find some spare time I will go and check out the code and poke around. It’s so awesome that we have an active team working on ZwaveJS.

In the meantime I hacked it to say that after 10 minutes the light goes to a lower light level, and after 10 minutes an even lower level, and then off. It’s not perfect but it works for now :slight_smile: