Electric curtains behaving weird - Forest Shuttle
Moderator: leecollings
- kevink
- Posts: 7
- Joined: Thursday 08 September 2016 16:08
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.5700
- Location: Netherlands
- Contact:
Electric curtains behaving weird - Forest Shuttle
Hi,
I have an electric curtain brand/type: Forest Shuttle with a Z-wave module attached to it. If operated manually (by pulling the curtain a little bit), it opens and closes as expected, thus the 'open' and 'closed' positions are known.
Today I started using Domoticz (Hi, new on this forum!) on my Raspberry Pi 2 type B and followed this guide to configure the RaZberry z-wave controller. http://www.vesternet.com/resources/appl ... 9F16JN96L_.
First I included a Danfoss LC13 to control the temperature in my room, which works fine, so I assume the RaZberry is properly configured.
Then I included the Forest Shuttle. Inclusion worked and it shows up in the hardware list (see screenshots), but I have no clue how to configure the switch. I tried many switch types, such as blinds, blinds percentage, dimmer, on/off, push on button, but none seem to work properly.
The curtains sometimes randomly open or close, without pushing the switch buttons. Also the reaction time seems very slow; sometimes something happens almost a minute after switching things; how can I speed this up?
First, I'd like to have a button to fully open/close the curtains and avoid the random opening/closing. Can someone help me with that? Thanks in advance.
Once that's working I'd like to proceed maybe 'inbetween' scenes, where the curtains are not fully closed, but just a little.
I have an electric curtain brand/type: Forest Shuttle with a Z-wave module attached to it. If operated manually (by pulling the curtain a little bit), it opens and closes as expected, thus the 'open' and 'closed' positions are known.
Today I started using Domoticz (Hi, new on this forum!) on my Raspberry Pi 2 type B and followed this guide to configure the RaZberry z-wave controller. http://www.vesternet.com/resources/appl ... 9F16JN96L_.
First I included a Danfoss LC13 to control the temperature in my room, which works fine, so I assume the RaZberry is properly configured.
Then I included the Forest Shuttle. Inclusion worked and it shows up in the hardware list (see screenshots), but I have no clue how to configure the switch. I tried many switch types, such as blinds, blinds percentage, dimmer, on/off, push on button, but none seem to work properly.
The curtains sometimes randomly open or close, without pushing the switch buttons. Also the reaction time seems very slow; sometimes something happens almost a minute after switching things; how can I speed this up?
First, I'd like to have a button to fully open/close the curtains and avoid the random opening/closing. Can someone help me with that? Thanks in advance.
Once that's working I'd like to proceed maybe 'inbetween' scenes, where the curtains are not fully closed, but just a little.
- Attachments
-
- The highlighted one
- 2.-Node-is-included.jpg (300.78 KiB) Viewed 2123 times
-
- The motor and z-wave module
- Screen Shot 2016-09-08 at 16.24.42.png (226.06 KiB) Viewed 2123 times
-
- inclusion successful
- 1. Include node.png (42.88 KiB) Viewed 2123 times
- LouiS22
- Posts: 433
- Joined: Friday 27 February 2015 13:21
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Budapest, Hungary
- Contact:
Re: Electric curtains behaving weird - Forest Shuttle
According to your last screenshot, de device itself is unknown, so there's no config xml - hence you can't configure your device. Are you on the beta channel or the stable one? The beta ozw contains one xml for this manufacturer, but it could be a new one which is not in the ozw github at all.
- kevink
- Posts: 7
- Joined: Thursday 08 September 2016 16:08
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.5700
- Location: Netherlands
- Contact:
Re: Electric curtains behaving weird - Forest Shuttle
Thanks Louis. I'm sorry for not answering earlier, didn't have time to try again until now.
I was on the stable channel, but updated now to beta Version: 3.5700. I excluded the node and included it again. I get the same message; unknown. I suppose it's a different one than the xml that is already on the beta ozw and thus not supported yet?
Is it possible to make such an xml myself? How do I make this work...
I also contacted the manufacturer. I've been told that they didn't make the Z-wave receiver themselves and thus don't have tech. specs, but that it's based on the receiver in the attached document. I hope this helps?
I was on the stable channel, but updated now to beta Version: 3.5700. I excluded the node and included it again. I get the same message; unknown. I suppose it's a different one than the xml that is already on the beta ozw and thus not supported yet?
Is it possible to make such an xml myself? How do I make this work...
I also contacted the manufacturer. I've been told that they didn't make the Z-wave receiver themselves and thus don't have tech. specs, but that it's based on the receiver in the attached document. I hope this helps?
- Domosapiens
- Posts: 232
- Joined: Wednesday 20 August 2014 12:08
- Target OS: Windows
- Domoticz version: V3.5981
- Location: NL
- Contact:
Re: Electric curtains behaving weird - Forest Shuttle
Kevink,
Use this link as guidance for a How-to
http://www.domoticz.com/forum/viewtopic ... anufact%2A
In domoticz/Config/electronicsolutions/
there is a file: dbmz.xml
You could try to use that one, it seems to be generic.
How-to:
In domoticz/Config/
there is a file: manufacturer_specific.xml
Search for electronicsolutions and Add:
Stop Z-Wave
Remove the node 033 related section from your zwcfg_0xaaaaaaa.xml
Restart Z-Wave
Check you log file and see if a Configuration screen comes for the node.
Hope this helps
Domosapiens
Use this link as guidance for a How-to
http://www.domoticz.com/forum/viewtopic ... anufact%2A
In domoticz/Config/electronicsolutions/
there is a file: dbmz.xml
You could try to use that one, it seems to be generic.
How-to:
In domoticz/Config/
there is a file: manufacturer_specific.xml
Search for electronicsolutions and Add:
Code: Select all
<Product type="4647" id="0002" name="DBMZ Motor Control" config="electronicsolutions/dbmz.xml"/>
Remove the node 033 related section from your zwcfg_0xaaaaaaa.xml
Restart Z-Wave
Check you log file and see if a Configuration screen comes for the node.
Hope this helps
Domosapiens
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555
Re: Electric curtains behaving weird - Forest Shuttle
I'm using the forest curtain with the build in zwave module. This one also has no xml configuration file but is working correctly. So the file is not always necessary.
- Domosapiens
- Posts: 232
- Joined: Wednesday 20 August 2014 12:08
- Target OS: Windows
- Domoticz version: V3.5981
- Location: NL
- Contact:
Re: Electric curtains behaving weird - Forest Shuttle
Just curious..has no xml configuration file but is working correctly
And are you able to configure:
- Unit calibration state
- Unit motor direction state
- Unit tilt feature state
In the Nodes configuration tab?
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555
- kevink
- Posts: 7
- Joined: Thursday 08 September 2016 16:08
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.5700
- Location: Netherlands
- Contact:
Re: Electric curtains behaving weird - Forest Shuttle
@Domosapiens
thank you for the detailed explanation. I'm new to Domoticz, so not really sure about the things I'm doing.
I didn't really understand the link you sent, but I managed to find the dbmz.xml file. I also added that product line to manufacturer_specific.xml.
I don't know how to stop and restart z-wave. I think I succesfully removed the 033 related section. Enclosed the file in case you want to check. Then I rebooted the raspberry pi. I hope this has the same effect as restarting z-wave.
Then I tried to include the node, and this time it showed:
"Included node:3
DBMZ Motor Control"
which, I think, is the desired result
Now under hardware, I think it's idx 3? I pressed the green button to "add light/switch device"
In the Switches tab, my new switch appeared. I expected my curtains to close after pressing it, but that didn't happen. I included what appeared in my log.
What does this timeout notification mean?
and @ceedebee
I think your newer version of the Forest Shuttle uses a different Z-wave device. My Z-wave unit is a seperate little box, connected with a utp-cable.
LOG:
zwcfg_0xf02a1f6a.xml (before including the node):
thank you for the detailed explanation. I'm new to Domoticz, so not really sure about the things I'm doing.
I didn't really understand the link you sent, but I managed to find the dbmz.xml file. I also added that product line to manufacturer_specific.xml.
I don't know how to stop and restart z-wave. I think I succesfully removed the 033 related section. Enclosed the file in case you want to check. Then I rebooted the raspberry pi. I hope this has the same effect as restarting z-wave.
Then I tried to include the node, and this time it showed:
"Included node:3
DBMZ Motor Control"
which, I think, is the desired result

Now under hardware, I think it's idx 3? I pressed the green button to "add light/switch device"
In the Switches tab, my new switch appeared. I expected my curtains to close after pressing it, but that didn't happen. I included what appeared in my log.
What does this timeout notification mean?
and @ceedebee
I think your newer version of the Forest Shuttle uses a different Z-wave device. My Z-wave unit is a seperate little box, connected with a utp-cable.
LOG:
Code: Select all
2016-09-29 18:53:51.339 New sensors allowed for 5 minutes...
2016-09-29 18:53:51.341 OpenZWave: Node Include command initiated...
2016-09-29 18:54:06.066 OpenZWave: New Node added. HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:54:06.086 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SWITCH MULTILEVEL, Label: Level, Instance: 1
2016-09-29 18:54:06.087 (RaZberry) Light/Switch (Level)
2016-09-29 18:54:06.102 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SWITCH MULTILEVEL, Label: Bright, Instance: 1
2016-09-29 18:54:06.103 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SWITCH MULTILEVEL, Label: Dim, Instance: 1
2016-09-29 18:54:14.266 (RaZberry) Thermostat (Heating 1)
2016-09-29 18:54:16.340 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:54:16.376 (RaZberry) Thermostat (Heating 1)
2016-09-29 18:54:16.589 OpenZWave: NodeID: 2 (0x02), Thermostat Clock: Monday 23:00
2016-09-29 18:54:16.589 (RaZberry) General/Thermostat Clock (Thermostat Clock)
2016-09-29 18:54:16.598 OpenZWave: All Nodes queried
2016-09-29 18:58:02.399 User: Admin initiated a switch command
2016-09-29 18:58:02.400 OpenZWave: Domoticz has send a Switch command!, Level: 255, NodeID: 3 (0x03)
2016-09-29 18:58:02.402 (RaZberry) Light/Switch (Gordijn)
2016-09-29 18:58:12.429 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:58:22.453 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:58:32.458 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:58:42.462 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:58:52.466 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:59:02.470 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:59:07.224 (RaZberry) Thermostat (Heating 1)
2016-09-29 18:59:12.473 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:59:22.500 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:59:32.504 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:59:42.508 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 18:59:52.512 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 19:00:02.516 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
Code: Select all
<?xml version="1.0" encoding="utf-8" ?>
<Driver xmlns="http://code.google.com/p/open-zwave/" version="3" home_id="0xf02a1f6a" node_id="1" api_capabilities="0" controller_capabilities="40" poll_interval="60000" poll_interval_between="false">
<Node id="1" name="" location="" basic="2" generic="2" specific="1" type="Static PC Controller" listening="true" frequentListening="false" beaming="true" routing="false" max_baud_rate="40000" version="4" query_stage="Complete">
<Manufacturer id="147" name="Z-Wave.Me">
<Product type="400" id="1" name="RaZberry Controller ZWave+" />
</Manufacturer>
<CommandClasses>
<CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" after_mark="true">
<Instance index="1" />
<Value type="byte" genre="basic" instance="1" index="0" label="Basic" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
</CommandClass>
</CommandClasses>
</Node>
<Node id="2" name="" location="" basic="4" generic="8" specific="4" type="Setpoint Thermostat" listening="false" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Complete">
<Manufacturer id="2" name="Danfoss">
<Product type="5" id="4" name="Z Thermostat 014G0013" />
</Manufacturer>
<CommandClasses>
<CommandClass id="67" name="COMMAND_CLASS_THERMOSTAT_SETPOINT" version="1" request_flags="4" override_precision="2" innif="true" base="0">
<Instance index="1" />
<Value type="decimal" genre="user" instance="1" index="1" label="Heating 1" units="C" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="4.00" />
</CommandClass>
<CommandClass id="70" name="COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE" version="1" request_flags="4" innif="true" change_counter="0">
<Instance index="1" />
<Value type="schedule" genre="user" instance="1" index="1" label="Monday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="schedule" genre="user" instance="1" index="2" label="Tuesday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="schedule" genre="user" instance="1" index="3" label="Wednesday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="schedule" genre="user" instance="1" index="4" label="Thursday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="schedule" genre="user" instance="1" index="5" label="Friday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="schedule" genre="user" instance="1" index="6" label="Saturday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="schedule" genre="user" instance="1" index="7" label="Sunday" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="list" genre="user" instance="1" index="8" label="Override State" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="None" value="0" />
<Item label="Temporary" value="1" />
<Item label="Permanent" value="2" />
</Value>
<Value type="byte" genre="user" instance="1" index="9" label="Override Setback" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="127" />
</CommandClass>
<CommandClass id="114" name="COMMAND_CLASS_MANUFACTURER_SPECIFIC" version="1" request_flags="4" innif="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="117" name="COMMAND_CLASS_PROTECTION" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="list" genre="system" instance="1" index="0" label="Protection" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="Unprotected" value="0" />
<Item label="Protection by Sequence" value="1" />
<Item label="No Operation Possible" value="2" />
</Value>
</CommandClass>
<CommandClass id="128" name="COMMAND_CLASS_BATTERY" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="byte" genre="user" instance="1" index="0" label="Battery Level" units="%" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="70" />
</CommandClass>
<CommandClass id="129" name="COMMAND_CLASS_CLOCK" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="list" genre="user" instance="1" index="0" label="Day" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="Monday" value="1" />
<Item label="Tuesday" value="2" />
<Item label="Wednesday" value="3" />
<Item label="Thursday" value="4" />
<Item label="Friday" value="5" />
<Item label="Saturday" value="6" />
<Item label="Sunday" value="7" />
</Value>
<Value type="byte" genre="user" instance="1" index="1" label="Hour" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="byte" genre="user" instance="1" index="2" label="Minute" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="57" />
</CommandClass>
<CommandClass id="132" name="COMMAND_CLASS_WAKE_UP" version="2" innif="true">
<Instance index="1" />
<Value type="int" genre="system" instance="1" index="0" label="Wake-up Interval" units="Seconds" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="300" />
<Value type="int" genre="system" instance="1" index="1" label="Minimum Wake-up Interval" units="Seconds" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="60" />
<Value type="int" genre="system" instance="1" index="2" label="Maximum Wake-up Interval" units="Seconds" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="1800" />
<Value type="int" genre="system" instance="1" index="3" label="Default Wake-up Interval" units="Seconds" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="300" />
<Value type="int" genre="system" instance="1" index="4" label="Wake-up Interval Step" units="Seconds" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="60" />
</CommandClass>
<CommandClass id="134" name="COMMAND_CLASS_VERSION" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="string" genre="system" instance="1" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="6" />
<Value type="string" genre="system" instance="1" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3.67" />
<Value type="string" genre="system" instance="1" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="1.01" />
</CommandClass>
<CommandClass id="143" name="COMMAND_CLASS_MULTI_CMD" version="1" request_flags="4" innif="true">
<Instance index="1" />
</CommandClass>
</CommandClasses>
</Node>
</Driver>
- kevink
- Posts: 7
- Joined: Thursday 08 September 2016 16:08
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.5700
- Location: Netherlands
- Contact:
Re: Electric curtains behaving weird - Forest Shuttle
Update: It actually started moving after switching a few more times! But the response is slow, my log is still filled with:
OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
And the behaviour is kind of unpredictable; currently the curtains just randomly open or close or open, then close again a few minutes after switching.
FYI: the raspberry pi with RaZberry module and curtains are in the same room - about 5m distance. Right next to the curtains is a Danfoss Z-wave thermostat, so I don't think the range is an issue.
Any ideas on how to improve?
OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
And the behaviour is kind of unpredictable; currently the curtains just randomly open or close or open, then close again a few minutes after switching.
FYI: the raspberry pi with RaZberry module and curtains are in the same room - about 5m distance. Right next to the curtains is a Danfoss Z-wave thermostat, so I don't think the range is an issue.
Any ideas on how to improve?
- Domosapiens
- Posts: 232
- Joined: Wednesday 20 August 2014 12:08
- Target OS: Windows
- Domoticz version: V3.5981
- Location: NL
- Contact:
Re: Electric curtains behaving weird - Forest Shuttle
The unit could be in the calibration state ....
Go to the Nodes configuration tab
Go to the Nodes configuration tab
Make a snapshotJust curious..
And are you able to configure:
- Unit calibration state
- Unit motor direction state
- Unit tilt feature state
In the Nodes configuration tab?
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555
- kevink
- Posts: 7
- Joined: Thursday 08 September 2016 16:08
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.5700
- Location: Netherlands
- Contact:
Re: Electric curtains behaving weird - Forest Shuttle
When I tried the switch today, I got the following error:
Error sending switch command, check device/hardware !
Also in the nodes configuration tab the status was"!" (see screenshot). Available options in the dropdown menu's:
1. Calibration: Normal, Calibration or Factory default
2. Motor Direction: Normal or Reversed
3. Tilt feature: No or Yes
In log, under the Status tab:
So uhm. It died...
After restarting domoticz, it's alive again (status: green checkmark) and I can press the switch. But it's still not really responsive; it takes over a minute before the curtains finally start moving...
Error sending switch command, check device/hardware !
Also in the nodes configuration tab the status was"!" (see screenshot). Available options in the dropdown menu's:
1. Calibration: Normal, Calibration or Factory default
2. Motor Direction: Normal or Reversed
3. Tilt feature: No or Yes
In log, under the Status tab:
Code: Select all
2016-09-29 20:01:24.677 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 20:01:34.681 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 20:01:44.685 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 20:01:44.866 OpenZWave: Received Node Dead notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-29 20:01:54.689 OpenZWave: Received timeout notification from HomeID: 4029292394, NodeID: 3 (0x03)
2016-09-30 00:00:02.239 EventSystem: reset all events...
2016-09-30 17:32:06.144 User: Admin initiated a switch command
2016-09-30 17:32:33.222 User: Admin initiated a switch command
2016-09-30 18:07:39.865 User: Admin initiated a switch command
After restarting domoticz, it's alive again (status: green checkmark) and I can press the switch. But it's still not really responsive; it takes over a minute before the curtains finally start moving...
- Domosapiens
- Posts: 232
- Joined: Wednesday 20 August 2014 12:08
- Target OS: Windows
- Domoticz version: V3.5981
- Location: NL
- Contact:
Re: Electric curtains behaving weird - Forest Shuttle
Ok. The configuration options look normal.
Did you execute the calibration cycle?
Then you post ...
More useful is a post where node 003 is shown
Did you execute the calibration cycle?
Then you post ...
Not so usefullzwcfg_0xf02a1f6a.xml (before including the node):

More useful is a post where node 003 is shown
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555
Who is online
Users browsing this forum: No registered users and 1 guest