Support to Scene modes using Remotec ZRC-90

Tags: #<Tag:0x00007f7398e9d9d8> #<Tag:0x00007f7398e9d848>

@Kartono Hi mate tried having a go but have a few questions. Sorry if I’m a PITA.

Cannot see “turn_on.yaml” on techellomello’s github. Am I missing something?

With “Add script: !include script/turn_on.yaml to configuration.yaml” This inst familiar to me. Can you please elaborate what this would look like in configuration.yaml please? Script commands I’ve seen in this type of format:

script:
notify_pushover:
sequence:
etc

Doing Tail works fine, thanks for that. In your example however you cut off 4 parts at the end when you said remove 3. Is 3 a typo?
If I can please get an example of your zwave-events.py that is prefilled (take out password info) that will help me heaps.
Will also make it clearer when I get to the part "also remove line 28,30 and 31 fix the format on line 29 " Not getting at at the moment :stuck_out_tongue:

I think I’ll be fine from there. Thanks again mate

Hi @ackfool

you can find my files here: https://github.com/kartono24/myHomeAssistant

“Cannot see “turn_on.yaml” on techellomello’s github. Am I missing something?” sorry you had to cut the script that was pasted on this page and make the file up

“Doing Tail works fine, thanks for that. In your example however you cut off 4 parts at the end when you said remove 3. Is 3 a typo?”

yes typo sorry - the second to last one is the button id
Detail, Node004, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x04, 0x05, 0x5b, 0x03, 0xef, 0x00, 0x01, 0x47
Detail, Node004, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x04, 0x05, 0x5b, 0x03,’

“With “Add script: !include script/turn_on.yaml to configuration.yaml” This inst familiar to me. Can you please elaborate what this would look like in configuration.yaml please? Script commands I’ve seen in this type of format:”

I use groups, when you make a folder you need your config to know where the script file is

just copy my layout in github

hope this helps

Hello!

I’ve modified @tchellomello’s original zwave-events.py to include support for single click, double click, and long press. You can find the modified zwave-events.py that I use at: https://gist.github.com/clintoncrick/f7aeb59bd314f6cb6b3fd0d103e23ddc

Please note that you will most likely need to modify these lines: #36, #62, #63, #66. Also note: the event that gets called is no longer compatible with the previous turn_on.yaml- there’s been a change to the base name and added support for the click types. The new events look like: script.zrc90_button_<button #>_<ClickNumbers value> or script.zrc90_button_1_2

1 Like

FYI, you will all want to keep an eye on anything related to the HomeSeer line of switches since they also use Central Scene. I started a fresh PR on the OZW repos that I hope to get back to in the next few days. It’s almost done.

3 Likes

Hi @clinton

Thanks for the work on this

:slight_smile:

@clinton Awesome!!! Good job!! Thanks for working on this!

Any news on your pull request to OZW?

I’m using a slightly-modified version of the scripts posted by @mfdutra to monitor for double/triple clicks and to trigger events in response. The result is very fast (sub-second response time) and has been reliable thus far. I’ve documented the complete procedure for deploying this script along with a service definition that should be ready to copy/paste into your terminal.

I’m not hard-coding any node IDs into the monitor script here, the script will detect any Central Scene command and then pass it through as an event. Adding/changing nodes to detect is a simple matter of modifying the automations.yaml to respond to the specific device.

2 Likes

Hi, i tried your script and it dint work for me. I think it has something to do with the matching.

This is what I get in my OZW.log file:

2017-11-09 09:31:54.605 Detail, Node013,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x0d, 0x05, 0x5b, 0x03, 0x61, 0x00, 0x01, 0xc0
2017-11-09 09:31:54.605 Detail, 
2017-11-09 09:31:54.605 Info, Node013, ApplicationCommandHandler - Unhandled Command Class 0x5b
2017-11-09 09:31:56.094 Detail, Node013,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0d, 0x03, 0x80, 0x03, 0x5d, 0x22
2017-11-09 09:31:56.094 Detail, 
2017-11-09 09:31:56.095 Info, Node013, ApplicationCommandHandler - Unhandled Command Class 0x80

Do i need to update open zwave or what do you think could be wrong with it?

My script was setup to work with the Homeseer HS-WD100+ and HD-WS100+ switches. Your log looks different from mine, are you using the same switches? Specifically, I don’t see any Central Scene command being sent by your device.

Im using the Remotec ZRC-90. What version of open-zwave do you have?

python-openzwave (0.4.0.35) on Python 3.6.3, but it’s worth repeating - my scripts are explicity setup to support the HomeSeer devices, I have no knowledge of how the ZRC-90 works or the messages it sends and the script hasn’t been tested against that device. Chances are it won’t work.

1 Like

Thank you anyway!

Hi, Im trying to use your code but it randomly craches for me…

This is the error i get:

Traceback (most recent call last):
  File "zwave-events.py", line 81, in <module>
    line = line.strip().decode('utf-8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 113: invalid start byte

Here is a link to the exact code i’m using: https://hastebin.com/icidufeyij.py

Does anyone know whats wrong?

any updates regarding this device? I would lite to get it working, running hass.io 0.57.2 :slight_smile:

Maybe this can be applied to HA too?

https://www.domoticz.com/forum/viewtopic.php?f=31&t=12539&start=20

In all honesty didn’t read all latest links/topics - just want to provide my two fortunate cents :slight_smile:

Working great over here (only changed zwcfg file on stopped HASS, basic python3-virtualenv linux install, 0.59.1)

  • stopping (note … stopping!) hass,
  • adjusting the zwcfg_…xml file (make a backup!)
  • starting hass (and wait for it as per usual)

The actual XML varies (having a wallmote, keyfob and today the remotec over here), but they do work perfectly

For the Remotec and Keyfob commandclass 91 and the wallmote same with 43 works just fine.

                        <CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="5" innif="true" scenecount="0">
                                <Instance index="1" />
                                <Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
                                <Value type="int" genre="system" instance="1" index="1" label="Scene 1" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
                                <Value type="int" genre="system" instance="1" index="2" label="Scene 2" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
...snip... repeat up to 8 on remotec, 8 on keyfob, 4 on wallmote ...snip...
                        </CommandClass>

Automation snip for button number 3

  - id: something
    alias: Doit
    trigger:
      - platform: event
        event_type: zwave.scene_activated
        event_data:
          entity_id: zwave.scenecontroller_1
          scene_id: 3
          scene_data: 0

Where the scenedata 0 is single-press, 2 is continued press, 1 is released from press and 3 is double-pressed (within a second).

For people having trouble, check OZW_log output what is returned … the 91 comes from where the >>> <<< are below, hex-to-dec for your number.

2017-12-06 18:20:28.383 Detail, Node032,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x20, 0x05, >>>0x5b<<<, 0x03, 0x23, 0x00, 0x01, 0xaf

Also check the message below this which resembles the OP’s post

2016-09-28 17:52:52.805 Warning, Node004, No ValueID created for Scene 8

So you should change the XML file to have ‘whatever string is behind the word for’, in this case “Scene 8”. For the wallmote I’d have to look it up (not on-premise here at home)

1 Like

worked like a charm for my ZRC-90
Thanks
Rolf

Thanks for this post, CoMPaTech! I got my wallmote working based on it

How dose your full xml look for the ZRC-90?

Do you change the evert time you repeat it?

//Tim