Z-Wave Window opener Fakro ZWS230

[Domosapiens]

I bought the 230V Fakro Z-wave controlled window opener ZWS230 for €229
( https://www.betaalbare-domotica.nl/motoren.html )

FAK_ZWS230_small.png (41.07 KiB) Viewed 12731 times

My objective is to open a triangle shaped window (later 2 windows) to flush fresh air trough the living for one hour or so, during the night.

The Fakro ZWS230 is not in the manufacturer_specific.xml nor there is a node description.
That means that it's not supported yet, by OpenZwave nor by Domoticz

This post will cover the following parts:
- window situation
- description of the ZWS230
- adaptation of the manufacturer_specific.xml
- installation problem in Domoticz
- adaptation of the zwcfg_0xxxxxx.xml
- the switch type selection in Domoticz
- a Blockly script for timed Open and Close
- mounting on the window (todo)
- final findings

Hope you will enjoy,
Domosapiens

[Domosapiens]

To ventilate the living during the night for a limited period of time i like to use an automated script.
The ceiling in my house is 2.5 meter but partly 3.5 meter. In that area there is a South and a North window.
The triangle shaped windows are around 90x90x90 cm and the handle is located on 2.5meter.
Using a stick was the only option for open and close.

Window_small.png (152.87 KiB) Viewed 12726 times

The South window is making a right turning circle arc.
The handle at 65cm from the point of rotation, is pushing maximal 20cm straight for a window opening of around 16 degrees.
That gives already friction on the current handle solution.
The window follows the cicle arc: 2*Pi*65cm*16/360 while the handle follows Pythagoras: SQRT (65cmPower2+20cmPower2).
So the point of action (NL:aanhechtingspunt) has a rotation of 16 degrees and a translation of 3 cm.
An electrical opener has to deal with both.
The practical value for ventilation will be around 10 cm.
But the maximum opening of the ZWS230 is 36cm, so the worst case values are around 30 degrees and 5.2 cm translation.

[Domosapiens]

The Fakro ZWS230 is an unique chain controlled window opener in compactness and combination with Z-wave for €229.
Alternative could be the Kaiser Nienhaus window opener (Conrad €179) in combination with a separate Z-Wave switch plus housing (around €60)
The advantage of this alternative is the possibility to limit the Kaiser Nienhaus in it's swing length and Domoticz support for a few Z-wave roller-blind switch.
The disadvantage is mounting against the window frame instead of in the window frame witch makes an insect screen very difficult.
Chinese window openers are more or less the same price but bulkier and most of them 24V.

The Fakro ZWS230 feels solid and well build and comes in a synthetic housing (plastic sounds so cheap) with a 1.2 meter cable, operating at 230V, 15W,
with a chain length of 360mm and chain speed of 10mm/sec. Operation noise is limited and acceptable.
There are 2 limit switches according to the documentation: maximum swing by a reed relay and an overload switch when closing force is >20kg (must be 196 Newton) with a red led flashing.
After closing, the chain is released for some 2 or 3mm, I have to see if the window will be wind tight closed due to that release.
The ZWS230 has two buttons, the red one for Z-wave network Inclusion and after that Association.
A black one for manual operation: Push button chain goes out. Push button chain stops. Push button chain goes in.
This picture shows a workbench operation with right the mounting on the window that can be easily released from the chain for window cleaning

Chain bending to the left.png (259.33 KiB) Viewed 12721 times

The chain is free in the left direction but has a constraint into the right direction due to the chain connectors.
That is a pity! The South window just needs the opposite! Could upside down mounting be an option ?
The mounting support can be seen at the left side. The unit is connected with only a screw on the left and right side.
On left and right there are 4 holes to choose from, 2 by 2 they are 15mm and 5mm apart.
In the window closed position a few millimeter chain has to stay outside the ZWS230 to keep the closing force on the window.

Because the cable length of 1.2 meter is too short, I had to open the unit to replace the cable. Rather strange that opening is needed for such common action!

Electrical cable replacement.png (268.29 KiB) Viewed 12721 times

Top right the folded chain supported by a nylon plate with in the center a nock that is guided in a nylon shape (left) towards the end position with the reed relay underneath.

Looking for the cable replacement, we see 3(!) connectors:

3 wires 2 in use.png (217.9 KiB) Viewed 12721 times

At the other side of the cable the grey lead is cut off. That suggests that normal operation with a 2 direction switch could be possible (as Z-Wave by-pass).
Reader be aware: I did not tried this! For manual operation the color coding is strange, one would expect Blue as zero (instead of Brown??) and Black and Grey as the 2 directions?

[Domosapiens]

While we are at this stage, it's good to look at the mechanical construction.
There is 1 mounting screw on the left and the right side:

1 side mounting screw.png (201.36 KiB) Viewed 12719 times

For each screw there are 4 choices. 2 choices encapsulated on the upper and 2 on the lower part of this picture (the screw comes from the right):

4 positions per side 1 screw means 100Nf.png (127.79 KiB) Viewed 12719 times

For almost 100N side force, this looks somewhat fragile. But we will see.

To end this inspection the last picture is without the nylon plate of the nock guidance.
We can see the Z-wave antenna (the black wire coming from the left) and the reed relay (right, under):

Z-wave module detail.png (186.98 KiB) Viewed 12719 times

The final question is:
Is the ZWS230 suitable for upside down operation, because then the chain could bend towards the right and would solve the needed translation for window opening,
even under worst case conditions (the full 360mm swing when the Open operation is not stopped in time by some failure).
My observation:
- the mounting support can not handle upside down operation, due to it's height and cable outlet
- it is not made for upside down operation, the nylon support on both sides are not identical, the bottom one is a real support, the top one is nock guidance.
- but the primary guidance of the chain: at the left side it is centered by the roller, at the outlet by the gear.
- bearings seem to be secured on both sides
- the upside down chain drags in the worst case over the top nylon plate.
- no strange noise when operated upside down

Conclusion:
Upside down operation is not forbidden in the manual, it is possible with an adapted mounting, it will lead to some reduced number of operation hours,
but seams acceptable without heavy duty use.
Upside down mounting solves the right handed window opening.

[Domosapiens]

The Fakro ZWS230 does not work straight out of the box with Domoticz.
Some fiddling has to be done.
Reader be aware: I hardly know what i'm talking about but .. it works ..
The adaptation of the manufacturer_specific.xml is most of all cosmetic at this moment, as long as the OpenZwave community does not support the ZWS230.

To Include the ZWS230 in the network: disable the Z-wave stick in Domoticz. Take it out and go to your ZWS230.
Push the Z-wave stick button once, it starts blinking. Push the red ZWS230 button for one second. The Z-wave stick will acknowledge by fast blinking. The ZWS230 accepts the network and the red led will be off (see note1)
When you included the ZWS230 in the network, you will see: Unknown: id:0085 Unknown: type=0003, id=0001.
Looking in the manufacturer_specific.xml you will find Fakro and it's id, but you have to add the line in between

Code: Select all

<Manufacturer id="0085" name="Fakro">
		<Product type="0003" id="0001" name="ZWS230"/>
</Manufacturer>

Add this: <Product type="0003" id="0001" name="ZWS230"/>
Preferable it would be this:
<Product type="0003" id="0001" name="ZWS230" config="fakro/ZWS230.xml"/>
There is no directory/map fakro yet and I could not find on the web a ZWS230.xml
Reader be aware: This modification has to be done after every Domoticz release until ZWS230 is supported by OpenZwave.

Note1. I did the Inclusion 2 times. First it was #17, later #18. The second time I Excluded first, Included again and then pushed the red button again to Associate (?? is that possible with the stick??) don't know if that did the job, but after the second time, I used a trick that will be explained in the next chapters installation problem in Domoticz and adaptation of the zwcfg_0xxxxxx.xml.

[Domosapiens]

After Inclusion, bring back the Z-stick to Domoticz and enable the Z-stick.
The Z-stick goes in Setup mode and stays in that mode.

Z-stick stays in setup.JPG (15.35 KiB) Viewed 12693 times

Not all nodes queried.JPG (53 KiB) Viewed 12693 times

There is a recogition and a registration in the zwcfg_xxxxx.xml file

ZWS230 registratie in zwcfg_xxxx.xml.JPG (49.3 KiB) Viewed 12693 times

But the node starts sleeping ...
Note1. I did the Inclusion 2 times. First it was #17, later #18.

[Domosapiens]

...
At least the ZWS230 is recognized in the Z-wave network:

Node 18 in the network but no group_crop.png (370.04 KiB) Viewed 12683 times

(note: the ZWS230 is with 5 interconnections a weak contributor to the network, my other nodes do 8 - 13)

The OpenZwavePanel (Node management,Control Panel) shows the current state: SecurityReport

OpenZwaveControlPanel.JPG (40.76 KiB) Viewed 12683 times

When I looked in the zwcfg_xxxx.xml, I found under Node 18:

Code: Select all

	<Node id="18" name="Unknown" location="" basic="4" generic="17" specific="6" type="Motor Control Class B" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="SecurityReport">

There it is about the last part:
query_stage="SecurityReport", while all other nodes are in query_stage="Complete"

The registration of a node is a multi-step query proces, we have a hick-up at QueryStage_SecurityReport:

QueryStage_SecurityReport.JPG (119.61 KiB) Viewed 12683 times

(Table found here: http://www.openzwave.com/dev/classOpenZ ... a644e1f220 )

The Fakro ZWS230 can do secured transmission, but I don't know if Domoticz is ready for that.

Here comes the trick:
Disable the Z-stick.
Edit the zwcfg_xxxx.xml.
Replace query_stage="SecurityReport" by query_stage="ManufacturerSpecific2"
Enable the Z-stick.

The QueryStage_SecurityReport is skipped and ...
Tada ... the Fakro ZWS230 is available under Devices where you can name it and add it to the Switch tab

[Domosapiens]

....
Now a switch can be found at the Switch tab.
The next step is to select a suitable switch, possible options are:

Switch options.JPG (24.86 KiB) Viewed 12677 times

The percentage slider seems to have no influence. (Blinds Percentage and Dimmer)

The Venetian Blinds do have a Stop button:

Venetian Blinds EU.JPG (21.09 KiB) Viewed 12677 times

But that gives: command not recognized. So no benefit.

The command sequence seems to be: Action=Start Open, Action=Stop, Action=Close.
The best and most logical choice: Blinds inverted

Blinds Inverted.JPG (21.14 KiB) Viewed 12677 times

Blind open is Window open. Blind close will stop opening. The next Blind close will close the window.
The behavior of the status in the Blinds switch: Open or Closed, is not clear to me.
Sometimes it's correct, sometimes not. Sometimes F5 helps, sometimes not.
I have seen similar problems with temperatures that are not updated in the browser since release V2.2365.

Where the Blind switch shows Closed, under Blockly with the Show current states it gives as status: Open.
This needs further tests with Blockly.

[Domosapiens]

The Blockly for test purposes:

Blockly Window timed OPEN-CLOSE.JPG (51.05 KiB) Viewed 12669 times

This timed Blockly works.
- Window_Opener_S is connected to the ZWS230.
- Take care for On/Off and not Open/Closed.
- D_Switch2 is a dummy switch that act as indication on the Dashboard for Open and Close.
- The WWWWW in the log, makes searching more easy.
- Opening and Closing Time will be changed to nightly hours in the real situation.
- The 5 seconds Off delay leads to 5cm chain release (correct according to the 10mm/sec)
Not sure if this is also correct if/when the node is sleeping (during test there is no time for sleep!).
Because the Domoticz counter will already count down while the node is awakening (that could take some seconds and needs some tuning).

This Blockly needs 2 further refinements:
- a Manual mode, plus a check on Manual mode, to open the window during a party or gourmet.
- before opening, a check on the current status of the window: if the window is already open (for some reason), opening could lead to a doubled opening distance.

The adapted Blockly will be posted here, later on.


Here ends my first batch of postings of the Fakro ZWS230.
The left overs:
- mounting on the window (todo, the real work) and making an insect screen solution
- final findings
will be posted later.

Your comments are welcome and appreciated,
Domosapiens

[Domosapiens]

Fakro ZWS230 mounted on the window and up & running!

Fakro_ZWS230_mounted_small.png (173.9 KiB) Viewed 12593 times

Mounting in the window frame was not possible (NL: in de dag) due to the size of the unit, plus the support on the window, plus some mm chain has to stay out for closing force.
So it has to be mounted on the window frame (NL: op de dag).
I used a wooden lath (24x38mm) as mounting for the ZWS230 with a cut for the chain passage and with insect protection on that passage.
The insect screen is mounted on the window frame(NL: op de dag) and the new lath.
Fitting the insect screen in the "almost" 60 degrees corners was most of the job.
The power line is replaced by a longer one.

Two Blockly's are operational:
Manual based operation (for special events):

Blockly Window Manual Control V1_small.png (160.24 KiB) Viewed 12573 times

D_Window_Automatic=the dummy switch between automatic operation or manual operation
D_Window_manual = the dummy switch for manual operation
D_Window_open = the register for the current window status, protection against double opening distance and for logging
Window_Opener_S = the ZWS230 status feedback and actual switch
7 seconds = empirically determined burglar-proof opening
8 seconds delay for D_Window_open, to make sure that no "in between" operation possible is. (open during close)
WWWWWW makes searching in the log easier

Time based operation (nighttime ventilation):

Blockly Window Time Control V1_small.png (158.73 KiB) Viewed 12573 times

An exact time is added. The more robust Time > then had a strange repetition effect even with the D_Window_open as AND condition.


One more Blockly will be added:
Temperature based operation (if not in manual mode):
IF the room temperature exceeds X Celsius the window will open
IF the room temperature falls below X Celsius the window will close.
This will bring an additional condition in the other Blockly's and will overrule Time based operation.

First operational impression:
- at closing the window, it stops on closing force but then releases the chain for 1 or 2 mm, this has to be adapted by the weatherstripping (NL:tochtstrip)
- so my weatherstripping needs a Botox treatment : i will put a peace of air hose from the pond pump under it to make it more adaptive
- if the window opens further, it is not burglar-proof, there is no way to create a burglar-proof connection between chain and the support on the window
- so I asked by mail to Fakro to comment on that
- high WAF factor
- the North window needs one too !

The final findings will follow later.
Domosapiens

[2-5-2015 edit: D_Window_Automatic switch added for Auto/Manual operation, Blockly pictures replaced]

[Domosapiens]

Time for an update on this project.
The South window is in flawless automatic operation for more than 2 weeks.
In the mean time I bought a second Fakro ZWS230 for operation on the North window.

This one didn't need to operate upside down because the window rotation direction was according to the flexible direction of the Fakro chain.
The Fakro mounting frame (see Description of the ZWS230) was not applicable, so I used again 2 simple L shaped support of 40 by 40x10mm (pointing to each other).
The 2 bolts in the Fakro stay a little lose to adapt for friction (as per original mounting frame).

Network inclusion is simple: Push the Z-wave stick button once, it starts blinking. Push the red ZWS230 button for one second. The Z-wave stick will acknowledge by fast blinking. The ZWS230 accepts the network and the red led will be off.
By replacing query_stage="SecurityReport" to query_stage="ManufacturerSpecific2" the Fakro ZWS230 becomes available under Devices.

Maturity development:
- the state Automatic, does not exclude manual operation
- the 2 windows can operate in conjunction or apart
- a try to simplify

GUI items:

Slide1a_crop_corr.PNG (220.82 KiB) Viewed 12356 times

Window_Opener_S and Window_Opener_N are the direct control of the Fakro without the chain length limitation and therefore password protected.
D_Window_Automatic is the dummy switch between Automatic and Manual operation
D_Window_S_manual and D_Window_N_manual are the manual operation buttons (with chain length limitation)
D_Window_S_open and D_Window_N_open are semaphores to prevent double opening (they should and will be password protected) and their log is used to check correct operation.
The group Windows_open is for timed and manual conjunct-ed operation. The group makes a call to the 2 Blockly's as used for manual operation.

Blockly's:

Slide1b_crop.png (253.1 KiB) Viewed 12369 times

The Windows_open group is executed on time, if in Automatic mode.
The group makes a call for ON to D_Window_S_manual and D_Window_N_manual. (and is translated by Domoticz to Open status ??? )
If the window is not Open yet as declared by the window__open semaphore and status of the Fakro, then the semaphore blocks other operations and the open cycle starts for 7 seconds.
The OFF call from the group is an unconditional Close operation where the Fakro will stop automatic and the semaphore is released after 8 seconds (1 sec. extra because the Domoticz schedule resolution is 1 seconds)

Automatic or Manual:

Slide2_crop.PNG (263.99 KiB) Viewed 12369 times

The state change from Automatic to Manual or v.v. has to be executed once. Therefore the variable V_Window_Automatic makes it an impulse and has an initial value of 1.
To determine this state change, the window_open semaphore blocks other operation and a close cycle is executed even if it is superfluous.
Both semaphores are released after 9 seconds (2 sec. extra for schedule resolution of the 2 operations)

Possible pitfall:
Can D_Window_Automatic and V_Window_Automatic be out of sync?
- At Domoticz start-up the shut-down status of D_Window_Automatic is remembered.
- V_Window_Automatic has an initial value of 1, but I'm not sure what Domoticz does with variables at start-up: renew the initial value or remember the last value,
testing shows no problems. It seems that the variables are also remembered (no statement in User Variables Wiki)

Remarks:
1) ... testing can only show the existence of bugs, it does not prove the correctness of a program.

2) Correctness proofs are not supported in programming languages (still not after my study 35 years ago FYI search on E.W.Dijkstra)

3) Even Blockly needs documentation and GUI too

Hope to inspire others,
Domosapiens

Edit 25-5-15: corrected picture Slide1a_crop_corr.PNG + typo's

[ErikJ]

Hello Domosapiens,

Recently I bought a Fakro window with electric opener and the outdoor shutter which is also electric. If I read you post correctly you explain that you can determine the opening position as follow. Event open (window open), closing action (window stops) again closing action (window closes). In my case, I can only open the window completely and if I use the close action the windows stops for a second and then it will close completely.

Do you have anything changed so you got the action of stopping?

I use Domoticz on a Synology NAS combined with Aeon USB stick. At my window there is AB enclosed which was already linked with the window and shutter. As a result I could not connect the USB stick directly to the Fakro and have to do some things to include the Aeon in the same network (I got it done with an external tool on the PC).

[Domosapiens]

ErikJ.
Sorry for the typo's but this is made on an iPad

Yes, for me it works like:

Code: Select all

Event open (window open), closing action (window stops) again closing action (window closes).

And i was warned by the supplier that it would work like that.
So no special tricks or changes.

Yes, i have Aeon stick too.
Could it be that your Aeon stick is seen as secondary controller, because the Fakro was already included in the RC network?

Suggestion?
1)
You could try an other blind switch in Domoticz? The one with stop in between open and close? Or a blockly with a stop command?
2)
Exclude the fakro from both networks. Include fakro on the aeon network first, then include rc to the aeon network.
Most of the time one rc can handle multiple clients so an exclude/include function will be available.

Hope this helps
Domosapiens

[ErikJ]

Hello Domosapiens,

Thanks for your quick reply

I already tried the option with the venetian blinds, but when I use the stop command there will be an error popup “Error sending switch command, check device/hardware” and no stop action.
So I tried your other suggestion and exclude the stick and the fakro. After that I include the fakro directly to the aeon stick. Bit still the same action. Open is open all the way en close is close all the way. There is no combination witch I can use to stop de Fakro during the open or close action.

Maybe I have a newer model and the stop action is an extra command. If I use a different Zwave software there is definition: Switch multilevel. But if I send the command with that software is the same result.

In Domoticz I have two extra zwave devices, but when I tried to activated the command I receive the notification: Error sending switch command, check device/hardware.

At the hardware tab is see the information as enclosed, so if I am right the sticks sees some more devices. But no extra details.

At this moment I only have the Fakro window opener and Fakro outdoor shutter. So is it possible that the stick receives extra information/commands but domotics cannot handle/translate them?

A other thing is that a cannot find the file zwcfg_xxxx.xml, only zwcgf.xsd and in that file and all the others there is no such details as you describe earlier in this topic.

Hope you have some more suggestions, otherwise I am at a dead end.

[Domosapiens]

ErikJ.
You are running on NAS but I assume it's the same.

Without the zwcfg_xxxx.xml file I think no Z-wave device will work in Domotics
You Z-stick has a zwcfg_xxxx.xml file (with xxxx as your specific stick number).
There you can find the lines of your Fakro, and check if it's in the query_stage="Complete"

Find att. from my zwcfg the part of 1 of the Fakro ZWS230.

Then I have 1 device, that can be configured in the switch tab.

Fakro as device.PNG (22.74 KiB) Viewed 12101 times

Hope this helps
Domosapiens

[ErikJ]

Still no success..

Command open is open, and command close is close.

Strange thing is that in the Zwave Control Panel menu I have some different options as you show above.

Capture 1.JPG (102.38 KiB) Viewed 11524 times

When I press "submit:open" the window will open and stops when I release that option and the window stays in that position. When I press "submit:close" the window will close as long I activate that option. I use Domoticz version 2.2715 on a synology NAS, can you check for me if you have those options in the Zwave Control Panel menu?

I also enclosed the details showed at the information page.

Capture.JPG (168.87 KiB) Viewed 11524 times

You might think if it is possible to have a certain level with the "submit:open" and "submit:close" in the Control Panel, there must be a way to control it in Domoticz as a blind.

[Domosapiens]

ErikJ,
so sorry for you.

Find below my OpenZwave Control Panel pics
(Configuration is empty, so i did not included it).
The naming difference comes from the manufacturer_specific.xml.

This is the situation where the windows are closed ! Is that caused by Blinds Inverted ?? See later in my post.
While you have Off & 0, mine is On & 254

OZCP_Fakro_ZWS230_1.JPG (78.43 KiB) Viewed 11496 times

OZCP_Fakro_ZWS230_3.JPG (100.42 KiB) Viewed 11496 times

I use a dummy Switch, that is connected to a Blockly, that controls the Fakro switch.
See a few post above, how I control the Fakro with Blockly with On and Off after a few seconds.
That works.

When I try to use the Fakro switch directly in Domoticz, it starts with Open Blinds, a next click does nothing, it stops with Close Blinds, a next click does a close.
I use the Lighting 2, Zwave, Blinds Inverted

Then I have a Zwave remote control RC2.
A short push is fully open. A push again does nothing.
The other button gives fully closed. A push again does nothing.
That one seems to act as in your situation.

Hope this helps
Domosapiens

[mfranken]

I have just bought and installed the Fakro FTU-V U3 Z-Wave (66x118) which contains the Fakro ZWS21 motor.

fakro dakraam

fakro_1.png (62.78 KiB) Viewed 11258 times

I'll share my findings here

With the help of this topic (and this info and more specific in XML) I edited my manufacturer_specific.xml:

Code: Select all

<Manufacturer id="0085" name="Fakro">
      <Product type="0003" id="0001" name="ZWS12"/>
</Manufacturer>

After that I unscrewed the casing for the motor and fiddled around with including the zwave control into my domoticz. It finally worked after deleting the remote control ZWP10 from the motor and including the motor to my Aeon Z-stick.

Directly I saw the Fakro in my zwave config:

Zwave config

Screen Shot 2015-09-07 at 19.55.31.png (105.85 KiB) Viewed 11262 times

The log shows:

Code: Select all

2015-09-07 19:39:37.961  OpenZWave: Value_Added: Node: 14 (0x0e), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2015-09-07 19:39:38.039  OpenZWave: Value_Added: Node: 14 (0x0e), CommandClass: SWITCH MULTILEVEL, Label: Step Size, Instance: 1
2015-09-07 19:39:38.039  OpenZWave: Value_Added: Node: 14 (0x0e), CommandClass: SWITCH MULTILEVEL, Label: Inc, Instance: 1
2015-09-07 19:39:38.039  OpenZWave: Value_Added: Node: 14 (0x0e), CommandClass: SWITCH MULTILEVEL, Label: Dec, Instance: 1
2015-09-07 19:39:38.040  OpenZWave: Value_Added: Node: 14 (0x0e), CommandClass: SWITCH MULTILEVEL, Label: Level, Instance: 1
2015-09-07 19:39:38.042  OpenZWave: Value_Added: Node: 14 (0x0e), CommandClass: SWITCH MULTILEVEL, Label: Open, Instance: 1
2015-09-07 19:39:38.042  OpenZWave: Value_Added: Node: 14 (0x0e), CommandClass: SWITCH MULTILEVEL, Label: Close, Instance: 1

And 3 new devices are available:

Domoticz Fakro devices

Screen Shot 2015-09-07 at 20.00.39.png (60.26 KiB) Viewed 11262 times

[houk]

I have ZWS12 and couple of ARZ Wave. In Micasa Vera I have stop button and its working fine for this devices.
But in Domoticz i can't use that.

I hear some rumors that new version is in testing right now of zwave modules for fakro devices that may have zwave 5 version.

[sincze]

...
At least the ZWS230 is recognized in the Z-wave network:

Node 18 in the network but no group_crop.png
(note: the ZWS230 is with 5 interconnections a weak contributor to the network, my other nodes do 8 - 13)

The OpenZwavePanel (Node management,Control Panel) shows the current state: SecurityReport

OpenZwaveControlPanel.JPG

When I looked in the zwcfg_xxxx.xml, I found under Node 18:

Code: Select all

	<Node id="18" name="Unknown" location="" basic="4" generic="17" specific="6" type="Motor Control Class B" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="SecurityReport">

There it is about the last part:
query_stage="SecurityReport", while all other nodes are in query_stage="Complete"

The registration of a node is a multi-step query proces, we have a hick-up at QueryStage_SecurityReport:
QueryStage_SecurityReport.JPG
(Table found here: http://www.openzwave.com/dev/classOpenZ ... a644e1f220 )

The Fakro ZWS230 can do secured transmission, but I don't know if Domoticz is ready for that.

Here comes the trick:
Disable the Z-stick.
Edit the zwcfg_xxxx.xml.
Replace query_stage="SecurityReport" by query_stage="ManufacturerSpecific2"
Enable the Z-stick.

The QueryStage_SecurityReport is skipped and ...
Tada ... the Fakro ZWS230 is available under Devices where you can name it and add it to the Switch tab

Tnx for the information regarding the multi stage pairing process. I'm not going to hijack the post. But I hope it will help me figure out why I've some missing sensor information.