Hello,
Can you add integration for walli devices please ?
I can add walli-dimmer to HA configuration but I can’t setting some parameters like led color or button actions.
You can find the parameters list at this link.
Regards
Cyril
Hello @Tinkerer,
I finded the following commit for OpenZwave: link
How can I use it in my HA configuration ?
Following your link I tried to edit my HA zwcfg_*.xml config in HA config folder but when I restart HA container the config file revert from the previous version and no change is taken.
Thanks for your help 
Upgrading the config in Docker/Hass.io is tricky, and not something I can help with I’m afraid.
That commit you found is for OpenZWave 1.6, which is not compatible with HA. If you want to use it you’ll have to create your own version compatible with OZW 1.4. How to: https://github.com/OpenZWave/open-zwave/wiki/Adding-Devices-(1.4---Old-Version)
Thanks, it’s working great, but it’s not durable, cause of docker container, hope the configuration will added soon, It’s exactly the same as OpenZWave 1.6 version.
Or maybe OpenZWave 1.6 usage for HA is in roadmap ?
If someone need some information or help I can give my configuration files.
Hey,
this sounds awesome. I have just ordered the walli dimmer and roller shutter and I am really interested in your configs if you are willing to share it.
How do you mean the config isn’t durable? I use HASSIO and had to make some changes in zwcfg_*.xml for Fibaro Button (FGPB 101) but now it works well and survives reboot. I was told that it is not going to work on HASSIO because the .cfg can be overwritten by the z-wave system. However I shut down HA before editing the file and the changes look persistent. Fibaro Button works. Can I expect the same with walli integrations?
Hey,
I said the configuration is not durable because I’m using docker. I updated the open-zwave lib database to add the new device. My HA installation is based on Docker docker container, so to update open-zwave lib I edited files in container so if I delete it (update for exemple) I will lose this modifications.
Following this link I do:
- Update the manufacturer_specific.xml to add the new devices in the correct manufacturer.
I used home-assistant in docker, for me file is located at:
vi /usr/local/lib/python3.7/site-packages/python_openzwave/ozw_config
<Manufacturer>
...
<Product type="1C01" id="1000" name="FGWD111 Walli Dimmer" config="fibaro/fgwd111.xml"/>
</Manufacturer>
- Create the new config file for your new devices:
<Product Revision="1"
xmlns="https://github.com/OpenZWave/open-zwave">
<!-- Please refer to https://github.com/OpenZWave/open-zwave/wiki/Adding-Devices for instructions -->
<MetaData>
<MetaDataItem name="Name">FGWDEU-111 Walli Dimmer</MetaDataItem>
<MetaDataItem name="Description">FIBARO Walli Dimmer is a smart wall dimmer designed to control light source via Z-Wave network. It measures active power and energy consumed by the controlled load.</MetaDataItem>
<MetaDataItem name="OzwInfoPage">http://www.openzwave.com/device-database/010f:1000:1C01</MetaDataItem>
<MetaDataItem name="ProductPage">https://www.fibaro.com/en/products/smart-switches-and-outlets-walli-dimmer/</MetaDataItem>
<MetaDataItem name="ProductSupport">https://manuals.fibaro.com/walli-dimmer/</MetaDataItem>
<MetaDataItem name="ProductPic">images/fibaro/fgwd111.png</MetaDataItem>
<MetaDataItem name="ProductManual">https://manuals.fibaro.com</MetaDataItem>
<MetaDataItem name="WakeupDescription">FIBARO Walli Dimmer is powered using DC power supply unit so it is always awake.</MetaDataItem>
<MetaDataItem name="InclusionDescription">To add the device to the Z-Wave network manually:
1. Power the device.
2. Set the main controller in add mode(see the controller’s manual).
3. Quickly, three times click one of the buttons.
4. LED will start blinking yellow, wait for the adding process to end.
5. Adding result will be confirmed by the Z-Wave controller’s message and the LED frame:
• Green – successful (non-secure, S0, S2 non-authenticated),
• Magenta – successful (Security S2 Authenticated),
• Red – not successful.</MetaDataItem>
<MetaDataItem name="ExclusionDescription">To remove the device from the Z-Wave network:
1. Power the device.
2. Set the main controller into remove mode (see the controller’s manual).
3. Quickly, three times click one of the buttons.
4. LED will start blinking yellow, wait for the removing process to end.
5. Successful removing will be confirmed by the Z-Wave controller’s message and red LED colour.</MetaDataItem>
<MetaDataItem name="ResetDescription">Reset procedure allows to restore the device back to its factory settings, which means all information about the Z-Wave controller and user configuration will be deleted. Resetting to factory defaults does not reset energy consumption memory.
1. Quickly, three times click, then press and hold one of the buttons to enter the menu.
2. Release button when the device glows yellow.
3. Quickly click the button to confirm.
4. After few seconds the device will be restarted, which is signalled with red LED colour.</MetaDataItem>
<MetaDataItem id="1000" name="ZWProductPage" type="1C01">https://products.z-wavealliance.org/products/3392</MetaDataItem>
<MetaDataItem id="1000" name="Identifier" type="1C01">FGWDEU-111</MetaDataItem>
<MetaDataItem id="1000" name="FrequencyName" type="1C01">CEPT (Europe)</MetaDataItem>
<ChangeLog>
<Entry author="Makooy - [email protected]" date="10 July 2019" revision="1">Initial Creation of config file - https://products.z-wavealliance.org/Products/3392/XML</Entry>
</ChangeLog>
</MetaData>
<!-- Configuration Command Class - All Configuration Parameters should be entered into the section below -->
<CommandClass id="112">
<Value genre="config" index="1" label="Remember device state" max="1" min="0" size="1" type="byte" value="1">
<Help>This parameter determines how the device will react in the event of power supply failure (e.g. power outage). The parameter is not relevant for outputs set to pulse mode (parameter 150/151 set to 2).
0 - remains switched off after restoring power
1 - restores remembered state after restoring power
</Help>
</Value>
<Value genre="config" index="2" label="Overload safety switch" max="5000" min="0" size="4" type="int" value="3500">
<Help>This function allows to turn off the controlled device in case of exceeding the defined power. Controlled device can be turned back on via the button or sending a control frame.
0 - function disabled
10-5000 - (1.0-500.0W, step 0.1W) – power threshold
</Help>
</Value>
<Value genre="config" index="10" label="LED frame – power limit" max="5000" min="100" size="4" type="int" value="3500">
<Help>This parameter determines maximum active power. Exceeding it results in the LED frame flashing violet. Function is active only when parameter 11 is set to 8 or 9.
100-5000 - (10.0-500.0W, step 0.1W) – power threshold
</Help>
</Value>
<Value genre="config" index="11" label="LED frame – colour when ON" max="9" min="0" size="1" type="list" value="1">
<Help>This parameter defines the LED colour when thedevice is ON. When set to 8 or 9, LED frame colour will change depending on he measured power and parameter 10. Other colours are set permanently and do not depend on power consumption.
</Help>
<Item label="LED disabled" value="0"/>
<Item label="White" value="1"/>
<Item label="Red" value="2"/>
<Item label="Green" value="3"/>
<Item label="Blue" value="4"/>
<Item label="Yellow" value="5"/>
<Item label="Cyan" value="6"/>
<Item label="Magenta" value="7"/>
<Item label="Colour changes smoothly depending on measured power" value="8"/>
<Item label="Colour changes in steps depending on measured power" value="9"/>
</Value>
<Value genre="config" index="12" label="LED frame – colour when OFF" max="7" min="0" size="1" type="list" value="1">
<Help>This parameter defines the LED colour when the device is OFF.
</Help>
<Item label="LED disabled" value="0"/>
<Item label="White" value="1"/>
<Item label="Red" value="2"/>
<Item label="Green" value="3"/>
<Item label="Blue" value="4"/>
<Item label="Yellow" value="5"/>
<Item label="Cyan" value="6"/>
<Item label="Magenta" value="7"/>
</Value>
<Value genre="config" index="13" label="LED frame – brightness" max="102" min="0" size="1" type="byte" value="100">
<Help>This parameter allows to adjust the LED frame brightness.
0 - LED disabled
1-100 - (1-100% brightness)
101 - brightness directly proportional to measured power
102 - brightness inversely proportional asured powerto me
</Help>
</Value>
<Value genre="config" index="24" label="Buttons orientation" max="1" min="0" size="1" type="list" value="0">
<Help>This parameter allows reversing the operation of the buttons.
</Help>
<Item label="Default (1st button brightens, 2nd button dims)" value="0"/>
<Item label="Reversed (1st button dims, 2nd button brightens)" value="1"/>
</Value>
<Value genre="config" index="30" label="Alarm configuration - 1st slot" max="4" min="1" size="4" type="list" value="0">
<Help>This parameter determines to which alarm frames and how the device should react. The parameters consist of 4 bytes, three most significant bytes are set according to the official Z-Wave protocol specification.</Help>
<Item label="[MSB] – Notification Type" value="1"/>
<Item label="Notification Value" value="2"/>
<Item label="Event/State Parameters" value="3"/>
<Item label="[LSB] – Action" value="4"/>
</Value>
<Value genre="config" index="31" label="Alarm configuration - 2nd slot" max="4" min="1" size="4" type="list" value="0">
<Help>This parameter determines to which alarm frames and how the device should react. The parameters consist of 4 bytes, three most significant bytes are set according to the official Z-Wave protocol specification.</Help>
<Item label="[MSB] – Notification Type" value="1"/>
<Item label="Notification Value" value="2"/>
<Item label="Event/State Parameters" value="3"/>
<Item label="[LSB] – Action" value="4"/>
</Value>
<Value genre="config" index="32" label="Alarm configuration - 3rd slot" max="4" min="1" size="4" type="list" value="0">
<Help>This parameter determines to which alarm frames and how the device should react. The parameters consist of 4 bytes, three most significant bytes are set according to the official Z-Wave protocol specification.</Help>
<Item label="[MSB] – Notification Type" value="1"/>
<Item label="Notification Value" value="2"/>
<Item label="Event/State Parameters" value="3"/>
<Item label="[LSB] – Action" value="4"/>
</Value>
<Value genre="config" index="33" label="Alarm configuration - 4th slot" max="4" min="1" size="4" type="list" value="0">
<Help>This parameter determines to which alarm frames and how the device should react. The parameters consist of 4 bytes, three most significant bytes are set according to the official Z-Wave protocol specification.</Help>
<Item label="[MSB] – Notification Type" value="1"/>
<Item label="Notification Value" value="2"/>
<Item label="Event/State Parameters" value="3"/>
<Item label="[LSB] – Action" value="4"/>
</Value>
<Value genre="config" index="34" label="Alarm configuration - 5th slot" max="4" min="1" size="4" type="list" value="0">
<Help>This parameter determines to which alarm frames and how the device should react. The parameters consist of 4 bytes, three most significant bytes are set according to the official Z-Wave protocol specification.</Help>
<Item label="[MSB] – Notification Type" value="1"/>
<Item label="Notification Value" value="2"/>
<Item label="Event/State Parameters" value="3"/>
<Item label="[LSB] – Action" value="4"/>
</Value>
<Value genre="config" index="35" label="Alarm configuration – duration" max="32400" min="0" size="2" type="short" value="600">
<Help>This parameter defines duration of alarm sequence. When time set in this parameter elapses, alarm is cancelled, LED frame and relay restore normal operation, but do not recover state from before the alarm.
0 - Infinite
1-32400 - (1s-9h, 1s step) – Duration
</Help>
</Value>
<Value genre="config" index="40" label="First button – scenes sen" max="8" min="0" size="1" type="byte" value="0">
<Help>This parameter determines which actions result in sending scene IDs assigned to them. Values can be combined (e.g. 1+2=3 means that scenes for single and double click are sent). Enabling scenes for triple click disables entering the device in learn mode by triple clicking.
1 - Key pressed 1 time
2 - Key pressed 2 time
4 - Key pressed 3 time
8 - Key hold down and key released
</Help>
</Value>
<Value genre="config" index="41" label="Second button – scenes sent" max="8" min="0" size="1" type="byte" value="0">
<Help>This parameter determines which actions result in sending scene IDs assigned to them. Values can be combined (e.g. 1+2=3 means that scenes for single and double click are sent). Enabling scenes for triple click disables entering the device in learn mode by triple clicking.
1 - Key pressed 1 time
2 - Key pressed 2 time
4 - Key pressed 3 time
8 - Key hold down and key released
</Help>
</Value>
<Value genre="config" index="60" label="Power reports – include self-consumption" max="1" min="0" size="1" type="list" value="0">
<Help>This parameter determines whether the power measurements should include power consumed by the device itself.
</Help>
<Item label="Self-consumption not included" value="0"/>
<Item label="Self-consumption included" value="1"/>
</Value>
<Value genre="config" index="61" label="Power reports – on change" max="500" min="0" size="2" type="short" value="15">
<Help>This parameter defines minimal change (from the last reported) in measured power that results in sending new report. For loads under 50W the parameter is irrelevant, report are sent every 5W change.
0 - Reporting on change disabled
1-500 - (1-500%, 1% step) – Minimal change
</Help>
</Value>
<Value genre="config" index="62" label="Power reports – periodic" max="32400" min="0" size="2" type="short" value="3600">
<Help>This parameter defines reporting interval for measured power. Periodic reports are independent from changes in value (parameter 61).
0 - periodic reports disabled
30-32400 - (30s-9h, 1s step) – time interval
</Help>
</Value>
<Value genre="config" index="65" label="Energy reports – on change" max="500" min="0" size="2" type="short" value="10">
<Help>This parameter defines minimal change (from the last reported) in measured energy that results in sending new report.
0 - reporting on change disabled
1-500 - (0.01-5kWh, 0.01kWh step) – minimal change
</Help>
</Value>
<Value genre="config" index="66" label="Energy reports – periodic" max="32400" min="0" size="2" type="short" value="3600">
<Help>This parameter defines reporting interval for measured energy. Periodic reports are independent from changes in value (parameter 65).
0 - periodic reports disabled
30-32400 - (30s-9h, 1s step) – time interval
</Help>
</Value>
<Value genre="config" index="150" label="Minimum brightness level" max="98" min="1" size="1" type="byte" value="1">
<Help>This parameter is set automatically during the calibration process, but can be changed manually after the calibration.
1-98 - (1-98%, 1% step) – level of brightness
</Help>
</Value>
<Value genre="config" index="151" label="Maximum brightness level" max="99" min="2" size="1" type="byte" value="99">
<Help>This parameter is set automatically during the calibration process, but can be changed manually after the calibration.
2-99 - (2-99%, 1% step) – level of brightness
</Help>
</Value>
<Value genre="config" index="152" label="Incandescence level of dimmable compact fluorescent lamps" max="99" min="1" size="1" type="byte" value="1">
<Help>The virtual value set as a percentage level between parameters MIN (1%) and MAX. (99%). The device will set to this value after the first switch on. It is required for warming up and switching dimmable compact fluorescent lamps and certain types of light sources.
1-99 - (1-98%, 1% step) – level of brightness
</Help>
</Value>
<Value genre="config" index="153" label="Incandescence time of dimmable compact fluorescent lamps" max="255" min="0" size="2" type="short" value="0">
<Help>This parameter determines the time required for switching compact fluorescent lamps and certain types of light sources. Setting this parameter to 0 will disable the incandescence functionality.
0-255 - (0-25.5s, 0.1s step) – incandescence time
</Help>
</Value>
<Value genre="config" index="154" label="Automatic control – dimming step size" max="99" min="1" size="1" type="byte" value="1">
<Help>This parameter defines the percentage value of dimming step during the automatic control.
0-99 - (1-99%, 1% step) – dimming step
</Help>
</Value>
<Value genre="config" index="155" label="Automatic control – time of dimming step" max="255" min="0" size="2" type="short" value="1">
<Help>This parameter defines the time of performing a single dimming step set in parameter 154 during the automatic control.
0-255 - This parameter defines the time of performing a single dimming step set in parameter 154 during the automatic control.
</Help>
</Value>
<Value genre="config" index="156" label="Manual control – dimming step size" max="99" min="1" size="1" type="byte" value="1">
<Help>This parameter defines the percentage value of the dimming step during the manual control.
1-99 - (1-99%, 1% step) – dimming step
</Help>
</Value>
<Value genre="config" index="157" label="Manual control – time of dimming step" max="255" min="0" size="2" type="short" value="5">
<Help>This parameter defines the time of performing a single dimming step set in parameter 156 during the manual control.
0-255 - (0-2.55s, 10ms step)
</Help>
</Value>
<Value genre="config" index="158" label="Auto-off functionality" max="32767" min="0" size="2" type="short" value="0">
<Help>This parameter allows to automatically switch off the device after a specified time from switching the light source on. It may be useful when the device is installed in the stairway.
0 - auto-off disabled
1-32767 - (1s-9.1h, 1s step) – auto-off time
</Help>
</Value>
<Value genre="config" index="159" label="Force auto-calibration" max="2" min="0" size="1" type="list" value="0">
<Help>Changing value of this parameter will force the calibration process. During the calibration parameter is set to 1 or 2 and switched to 0 upon completion.
</Help>
<Item label="Readout" value="0"/>
<Item label="Force auto-calibration without FIBARO Bypass 2" value="1"/>
<Item label="Force auto-calibration with FIBARO Bypass 2" value="2"/>
</Value>
<Value genre="config" index="160" label="Auto-calibration status (read-only parameter)" max="1" min="0" size="1" type="list" value="0">
<Help>This parameter determines operating mode of the device (automatic/manual settings).
</Help>
<Item label="Calibration procedure not performed or the device operates on manual settings" value="0"/>
<Item label="The device operates on auto-calibration settings" value="1"/>
</Value>
<Value genre="config" index="161" label="Burnt out bulb detection" max="99" min="0" size="2" type="short" value="0">
<Help>This parameter defines percentage power variation (compared to power consumption measured during the calibration) to be interpreted as load error/burnt out bulb.
0 - function disabled
1-99 - (1-99%, 1% step) – power variation
</Help>
</Value>
<Value genre="config" index="162" label="Time delay of a burnt out bulb and overload detection" max="255" min="0" size="2" type="short" value="5">
<Help>This parameter defines detection delay for the burnt out bulb (parameter 161) and overload (parameter 2).
0 - detection of a burnt out bulb disabled
1-255 - (1-255s, 1s step) – time delay
</Help>
</Value>
<Value genre="config" index="163" label="First button – Switch ON value sent to 2nd and 3rd association groups" max="255" min="0" size="2" type="short" value="255">
<Help>This parameter defines value sent with Switch OFF command to devices associated in 2nd and 3rd association group.
0-99 - value sent
254 - send value equal to the current level
255 - value sent
</Help>
</Value>
<Value genre="config" index="164" label="Second button – Switch OFF value sent to 2nd and 3rd association groups" max="255" min="0" size="2" type="short" value="0">
<Help>This parameter defines value sent with Switch ON command to devices associated in 2nd and 3rd association group.
0-99 - value sent
254 - send value equal to the current level
255 - value sent
</Help>
</Value>
<Value genre="config" index="165" label="Double click – set level" max="99" min="0" size="1" type="byte" value="99">
<Help>This parameter defines brightness level set after double-clicking any of the buttons. The same value is also sent to devices associated with 2nd and 3rd association group.
0-99 - (0-99%, 1% step) – set level
</Help>
</Value>
<Value genre="config" index="170" label="Load control mode" max="2" min="0" size="1" type="list" value="2">
<Help>This parameter allows to set the desired load control mode. Auto-calibration sets value of this parameter to 2 (control mode recognized during auto-calibration), but the installer may force control mode using this parameter. After changing parameter value, turn the load OFF and ON to change control mode.
</Help>
<Item label="Forced leading edge" value="0"/>
<Item label="Forced trailing edge" value="1"/>
<Item label="Control mode selected automatically (based on auto-calibration)" value="2"/>
</Value>
<Value genre="config" index="171" label="Load control mode recognized during auto-calibration (read only)" max="1" min="0" size="1" type="list" value="0">
<Help>This parameter allows to read load control mode that was set during auto-calibration.
</Help>
<Item label="Leading edge" value="0"/>
<Item label="Trailing edge" value="1"/>
</Value>
<Value genre="config" index="172" label="ON/OFF mode" max="2" min="0" size="1" type="list" value="2">
<Help>This mode is necessary while connecting non-dimmable light sources. Setting this parameter to 1 automatically ignores brightening/dimming time settings. Forced auto-calibration will set this parameter’s value to 2.
</Help>
<Item label="ON/OFF mode disabled (dimming is possible)" value="0"/>
<Item label="ON/OFF mode enabled (dimming is not possible)" value="1"/>
<Item label="Mode selected automatically" value="2"/>
</Value>
<Value genre="config" index="173" label="Dimmability of the load (read only)" max="1" min="0" size="1" type="list" value="0">
<Help>This parameter allows to read if the load detected during calibration procedure is dimmable.
</Help>
<Item label="Load recognized as dimmable" value="0"/>
<Item label="Load recognized as non-dimmable" value="1"/>
</Value>
<Value genre="config" index="174" label="Soft-start functionality" max="2" min="0" size="1" type="list" value="1">
<Help>This parameter allows to set time required to warm up the filament of halogen bulb.
</Help>
<Item label="No soft-start" value="0"/>
<Item label="Short soft-start (0.1s)" value="1"/>
<Item label="Long soft-start (0.5s)" value="2"/>
</Value>
<Value genre="config" index="175" label="Auto-calibration after power on" max="4" min="0" size="1" type="list" value="1">
<Help>This parameter determines the trigger of auto-calibration procedure, e.g. power on, load error, etc.
</Help>
<Item label="No auto-calibration after power on" value="0"/>
<Item label="Auto-calibration after each power on" value="2"/>
<Item label="Auto-calibration after each LOAD ERROR (no load, load failure, burnt out bulb), if parameter 176 is set to 1 also after SURGE (output overvoltage) and OVERCURRENT (output overcurrent)" value="3"/>
<Item label="Auto-calibration after each power on or after each LOAD ERROR (no load, load failure, burnt out bulb), if parameter 176 is set to 1 also after SURGE (output overvoltage) and OVERCURRENT (output overcurrent)" value="4"/>
</Value>
<Value genre="config" index="176" label="Behaviour after OVERCURRENT or SURGE" max="1" min="0" size="1" type="list" value="1">
<Help>Error occurrences related to surge or overcurrent results in turning off the output to prevent possible malfunction. By default the device performs three attempts to turn on the load (useful in case of temporary, short failures of the power supply).
</Help>
<Item label="Device permanently disabled until re-enabling by command or external switch" value="0"/>
<Item label="Three attempts to turn on the load" value="1"/>
</Value>
<Value genre="config" index="177" label="Brightness level correction for flickering loads" max="255" min="0" size="2" type="short" value="255">
<Help>Correction reduces spontaneous flickering of some capacitive loads (e.g. dimmable LEDs) at certain brightness levels in 2-wire installation.
In countries using ripple-control, correction may cause changes in brightness. In this case it is necessary to disable correction or adjust the time of correction for flickering loads.
0 - automatic correction disabled
1-254 - (1-254s, 1s step) – duration of correction
255 - automatic correction always enabled
</Help>
</Value>
<Value genre="config" index="178" label="Method of calculating the active power" max="2" min="0" size="1" type="list" value="0">
<Help>This parameter defines how to calculate active power. It is useful in a case of 2-wire connection with light sources other than resistive.
</Help>
<Item label="Measurement based on the standard algorithm" value="0"/>
<Item label="Approximation based on the calibration data" value="1"/>
<Item label="Approximation based on the control angle" value="2"/>
</Value>
<Value genre="config" index="179" label="Approximated power at the maximum brightness level" max="500" min="0" size="2" type="short" value="0">
<Help>This parameter determines the approximate value of the power that will be reported by the device at its maximum brightness level.
0-500 - (0-500W, 1W step) – power consumed by the load at the maximum brightness level.
</Help>
</Value>
</CommandClass>
<!-- The Association Group Information -->
<CommandClass id="133">
<Associations num_groups="3">
<Group index="1" label="LifeLine" max_associations="1"/>
<Group index="2" label="On/Off" max_associations="5"/>
<Group index="3" label="Dimmer" max_associations="5"/>
</Associations>
</CommandClass>
</Product>
- Finally remove your existing zwcfg_*.xml in HA config folder, a new one with new configuration will be generated
mv zwcfg_*.xml zwcfg_*.xml.bk
2 Likes
I need help with this exact same thing. when i change the in formation in the file and restart my
system it gets deleted and reverts to the default. What am i doing wrong?
You have check your OZW logs ?
To take effect, I had to exclude the node of network and associate it again after change.
Check your file name in fibaro folder corresponding to your fibaro device and in the xml file ozw_config.
My zwave stick use to work fine now i keep getting this error message.
2020-01-31 00:50:06.383 Always, OpenZwave Version 1.4.3452 Starting Up
2020-01-31 00:50:50.482 Info, Setting Up Provided Network Key for Secure Communications
2020-01-31 00:50:50.482 Warning, Failed - Network Key Not Set
2020-01-31 00:50:50.483 Info, mgr, Added driver for controller /dev/ttyACM0
2020-01-31 00:50:50.483 Info, Opening controller /dev/ttyACM0
2020-01-31 00:50:50.484 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
2020-01-31 00:50:50.491 Info, Serial port /dev/ttyACM0 opened (attempt 1)
2020-01-31 00:50:50.492 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-01-31 00:50:50.495 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-01-31 00:50:50.496 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-01-31 00:50:50.496 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-01-31 00:50:50.496 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-01-31 00:50:50.496 Detail,
2020-01-31 00:50:50.496 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-01-31 00:50:51.497 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-01-31 00:50:51.497 Detail, contrlr, Removing current message
2020-01-31 00:50:51.497 Detail, contrlr, Notification: Notification - TimeOut
2020-01-31 00:50:51.501 Detail,
2020-01-31 00:50:51.501 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-01-31 00:50:52.501 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-01-31 00:50:52.501 Detail, contrlr, Removing current message
2020-01-31 00:50:52.502 Detail, contrlr, Notification: Notification - TimeOut
2020-01-31 00:50:52.508 Detail,
2020-01-31 00:50:52.508 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-01-31 00:50:53.508 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-01-31 00:50:53.509 Detail, contrlr, Removing current message
2020-01-31 00:50:53.509 Detail, contrlr, Notification: Notification - TimeOut
2020-01-31 00:50:53.514 Detail,
2020-01-31 00:50:53.514 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-01-31 00:50:54.514 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-01-31 00:50:54.514 Detail, contrlr, Removing current message
2020-01-31 00:50:54.514 Detail, contrlr, Notification: Notification - TimeOut
2020-01-31 00:50:54.518 Detail,
2020-01-31 00:50:54.518 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-01-31 00:50:55.519 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-01-31 00:50:55.519 Detail, contrlr, Removing current message
2020-01-31 00:50:55.519 Detail, contrlr, Notification: Notification - TimeOut
2020-01-31 00:51:03.883 Warning, WARNING: Out of frame flow! (0xfe). Sending NAK.
2020-01-31 00:51:11.333 Warning, WARNING: Out of frame flow! (0xfe). Sending NAK.
Ok, but your walli works ?
Personally, now, I doesn’t use zwave integrated to HA cause of open-zwave 1.4 is do not supported anymore.
I switched to zwave2mqtt with mosquitto and auto discovery feature enabled for HA. That permit to have the latest open-zwave version with better and more stable zawave Network. Now all my devices are natively integrated. An other benefit is the global RTT of my zwave network is lower so better response time globally .
If you are interested about this integration, let me know.
2 Likes
Yes my walli works. I was able to control it via ha. But now nuthing.I use zwave to mqtt that was what I was using.
Which version of zwave2mqtt do you use ? What is exactly your issue ?
This sounds great,
Could you please share your solution on how to integrate over zwave2mqtt, at least the main steps and if there are particularities to take care during integration.
Thank you very much
It is pretty much, plug in the dongle in the raspberry pi. put in the particulars in the config file
and download the addon zwave2mqtt. You should have mosquito up and running as well. That is another addon.
the latest version of zwave2mqtt.
I’m having issues with the Fibaro Walli as well. It works often, but sometimes Home Assistant shows incorrect device state and then I just have to reboot Home Assistant to get it working again. Also, it seems to interfere with the rest of my Z-Wave network which is now very unreliable and slow after adding the Fibaro Walli device.
Use zwave2mqtt go here https://gogs.connan.pro/Domotics/home-cc it’s my personal repo with my stack configuration. https://gogs.connan.pro/Domotics/home-assistant
Hello,
1/ has anyone managed to make walli shutter work on HA ?
2/ And is the dimmer working for your walli dimmers ? For me there is a little problem with them.
If i set the dimmer to 50% light fro example, then i switch off then on again it goes to 50% whicj is a bit annoying.
Any way the 1/ is more improtant for me to solve !