3.0.1.130 Stable now ?

[ian351c]

Rich,

by the looks of things they may have changed something in 3.4.

see below

I'm having the same issue with a brand new Fibaro FGS-223 (Dual Binary Switch) running firmware 3.2 (looks like the only version available for this model). My logs are similar:

Aug-30 2:31:58 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to INVALID VALUE
Aug-30 2:31:58 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:31:57 PM Device Control Device: Z-Wave Node 157 Switch Binary 2 to Off (0) by/from: CAPI Control Handler
Aug-30 2:31:54 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to INVALID VALUE
Aug-30 2:31:54 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:31:54 PM Device Control Device: Z-Wave Node 157 Switch Binary 2 to On (255) by/from: CAPI Control Handler
Aug-30 2:31:50 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:31:50 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:31:50 PM Device Control Device: Z-Wave Node 157 Switch Binary 1 to Off (0) by/from: CAPI Control Handler
Aug-30 2:31:45 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:31:45 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:31:40 PM Device Control Device: Z-Wave Node 157 Switch Binary 1 to On (255) by/from: CAPI Control Handler
Aug-30 2:30:20 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:30:20 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:30:20 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:30:20 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:30:20 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to OFF
Aug-30 2:30:17 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:30:17 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:30:17 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:30:17 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:30:17 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to ON
Aug-30 2:30:15 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:30:15 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:30:15 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:30:15 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:30:15 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to OFF
Aug-30 2:30:11 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:30:11 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:30:11 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:30:11 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:30:11 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to ON
Aug-30 2:30:02 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to INVALID VALUE
Aug-30 2:30:02 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:30:02 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to OFF
Aug-30 2:30:00 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to INVALID VALUE
Aug-30 2:30:00 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:30:00 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to ON
Aug-30 2:29:56 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to INVALID VALUE
Aug-30 2:29:56 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:29:56 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to OFF
Aug-30 2:29:54 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to INVALID VALUE
Aug-30 2:29:54 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:29:54 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 2 Set to ON
Aug-30 2:29:26 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:29:26 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:29:26 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:29:26 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:29:26 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to OFF
Aug-30 2:29:23 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:29:23 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:29:23 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:29:23 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:29:23 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to ON
Aug-30 2:28:15 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:15 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:28:15 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:15 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:28:15 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to OFF
Aug-30 2:28:13 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:13 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:28:13 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:13 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:28:13 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to ON
Aug-30 2:28:07 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:07 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:28:07 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:07 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:28:07 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to OFF
Aug-30 2:28:04 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:04 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:28:04 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:04 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:28:04 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to ON
Aug-30 2:28:00 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:00 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:28:00 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:28:00 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:28:00 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to OFF
Aug-30 2:27:57 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:27:57 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 20-03
Aug-30 2:27:57 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to INVALID VALUE
Aug-30 2:27:57 PM Z-Wave Warning Probable Invalid (BINARY) Frame Received from Node 157 = 25-03
Aug-30 2:27:57 PM Z-Wave Device: Z-Wave Node 157 Switch Binary 1 Set to ON
Aug-30 2:27:30 PM Z-Wave 8 out of 8 Child devices of node 157 were created successfully.
Aug-30 2:27:29 PM Z-Wave Adding Z-Wave Node 157 Watts as an Energy tracking device.
Aug-30 2:27:29 PM Z-Wave Adding Z-Wave Node 157 kW Hours as an Energy tracking device.
Aug-30 2:27:28 PM Z-Wave Assigning return route from node 1 to Z-Wave Node 157 Fibaro Switch Binary
Aug-30 2:27:28 PM Z-Wave Enabling instant status for Z-Wave device Z-Wave Node 157 Fibaro Switch Binary (157) on Group 5
Aug-30 2:27:27 PM Z-Wave Assigning return route from node 1 to Z-Wave Node 157 Fibaro Switch Binary
Aug-30 2:27:27 PM Z-Wave Enabling instant status for Z-Wave device Z-Wave Node 157 Fibaro Switch Binary (157) on Group 3
Aug-30 2:27:26 PM Z-Wave Assigning return route from node 1 to Z-Wave Node 157 Fibaro Switch Binary
Aug-30 2:27:26 PM Z-Wave Enabling instant status for Z-Wave device Z-Wave Node 157 Fibaro Switch Binary (157) on Group 1
Aug-30 2:27:23 PM Z-Wave Getting association information for Z-Wave Node 157 Fibaro Switch Binary
Aug-30 2:27:23 PM Z-Wave Assigning return route from node 1 to Z-Wave Node 157 Fibaro Switch Binary
Aug-30 2:27:22 PM Z-Wave znet1: Adding association for Z-Wave device Z-Wave Node 157 Fibaro Switch Binary (Node 157, Group 2, Endpoint 2) to HomeSeer
Aug-30 2:27:22 PM Z-Wave Assigning return route from node 1 to Z-Wave Node 157 Fibaro Switch Binary
Aug-30 2:27:20 PM Z-Wave znet1: Adding association for Z-Wave device Z-Wave Node 157 Fibaro Switch Binary (Node 157, Group 1, Endpoint 1) to HomeSeer
Aug-30 2:27:20 PM Z-Wave Root Node Device Z-Wave Node 157 Fibaro Switch Binary was created for node 157 on network 0184EF25
Aug-30 2:27:20 PM Z-Wave All associations for node 157 have been retrieved successfully, it supports associations on these groups: 1, 2, 3, 4, 5.
Aug-30 2:27:20 PM Z-Wave Node 157 Association Group 5 can have 5 associations, and currently has 0
Aug-30 2:27:20 PM Z-Wave Node 157 Association Group 4 can have 5 associations, and currently has 0
Aug-30 2:27:20 PM Z-Wave Node 157 Association Group 3 can have 5 associations, and currently has 0
Aug-30 2:27:20 PM Z-Wave Node 157 Association Group 2 can have 5 associations, and currently has 0
Aug-30 2:27:20 PM Z-Wave Node 157 Association Group 1 can have 1 associations, and currently has 0
Aug-30 2:27:18 PM Z-Wave Getting association information for node 157
Aug-30 2:27:17 PM Z-Wave Node 157 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
Aug-30 2:27:17 PM Z-Wave Node 157 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
Aug-30 2:27:17 PM Z-Wave Processing Information for Node 157 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL, Endpoint 2
Aug-30 2:27:17 PM Z-Wave Warning Could not get the supported METER information from node 157, so devices for the METER class will not be created or rebuilt.
Aug-30 2:26:47 PM Z-Wave Processing Information for Node 157 Multi-CHANNEL Command Class of METER_V2, Endpoint 2
Aug-30 2:26:47 PM Z-Wave Processing Information for Node 157 Multi-CHANNEL Command Class of SWITCH_BINARY_V2, Endpoint 2
Aug-30 2:26:47 PM Z-Wave Processing Information for Node 157 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL, Endpoint 1
Aug-30 2:26:47 PM Z-Wave Warning Could not get the supported METER information from node 157, so devices for the METER class will not be created or rebuilt.
Aug-30 2:26:16 PM Z-Wave Processing Information for Node 157 Multi-CHANNEL Command Class of METER_V2, Endpoint 1
Aug-30 2:26:16 PM Z-Wave Processing Information for Node 157 Multi-CHANNEL Command Class of SWITCH_BINARY_V2, Endpoint 1
Aug-30 2:26:15 PM Z-Wave Node 157 is a Z-Wave Plus node. Retrieving ZWPlus Info...
Aug-30 2:26:15 PM Z-Wave Node 157 is Z-Wave version: Lib: 4.05 App: 3.2
Aug-30 2:26:15 PM Z-Wave Z-Wave manufacturer information for node 157, ID: 271=10FH (Fibaro), Type: 515=203H, ID: 8192=2000H
Aug-30 2:26:15 PM Z-Wave Received information on 9 secure command classes from node 157
Aug-30 2:26:14 PM Z-Wave Getting SECURITY class information for node 157
Aug-30 2:26:14 PM Z-Wave Z-Wave Security Scheme and Key Exchange was successful for node 157, now waiting for the device to finish storing information before proceeding...
Aug-30 2:26:14 PM Z-Wave Security device (Node 157) is verified as operating securely in this network.
Aug-30 2:26:14 PM Z-Wave Negotiating or Verifying SECURITY SCHEME for node 157
Aug-30 2:26:12 PM Z-Wave Done. Node 157 Added.

[rjh]

I think it is fixed, I found some G2 modules to test with. Try Z-Wave plugin 3.0.1.142 in the Beta section.

Here is for the Smart Dimmer:
[ATTACH]63061[/ATTACH]
And for the Smart Switch:
[ATTACH]63062[/ATTACH]

Thanks!

[Daweeze]

Hi Rich,

Recent Z-Wave PI Versions started to log these warnings for my Monoprice Branded (Vision) Smoke Detectors:

Sep-01 11:02:06 AM Event Event Trigger "Smoke & CO Alarms (Timers) Master Bedroom - Smoke - Heartbeat - Timer Reset"
Sep-01 11:02:06 AM Z-Wave Warning HomeSeer SmartStick+: Device (Node 10) woke up, but queued command failed to be sent. Command=Poll Device
Sep-01 11:02:05 AM Z-Wave Wake-Up Util Proc for (Upstairs Master Bedroom Smoke Alarm - Root) handling: Poll Device
Sep-01 11:02:05 AM Z-Wave HomeSeer SmartStick+: Wake-Up Notification Processing for Node 10 (Upstairs Master Bedroom Smoke Alarm - Root)
Sep-01 11:02:05 AM Z-Wave HomeSeer SmartStick+: Z-Wave Wake-Up Notification Received for Node 10

I deleted the nodes and then re-added them. Once I did that the messages didn't appear but then the wake-up status wasn't updating the status time so my events checking communication weren't firing. Then I noticed there wasn't any polling value so I set it to a random 20 min like it was before. Now the events fire again but the error message is back. I don't remember this being an issue a few months back.

Just to be on the current release, I just updated to 3.0.1.142 a few mins ago, was 3.0.1.140.

Node info attached.

Any ideas?

-Travis

[rjh]

Check the wake up timer and then see if you get the error every time the unit wakes up (make sure the poll time is less than the wake up time). There were some changes made recently to the wake up handling. What it looks like is that when the device woke up HS was not able to send a command to it, or did not get a response. The times are really short in your log so I assume the device was still awake. To test this theory move the device close to your Z-Wave interface and see if you still see the errors. In previous versions we did not log this type of error so it could have still been happening.

Hi Rich,

Recent Z-Wave PI Versions started to log these warnings for my Monoprice Branded (Vision) Smoke Detectors:

Sep-01 11:02:06 AM Event Event Trigger "Smoke & CO Alarms (Timers) Master Bedroom - Smoke - Heartbeat - Timer Reset"
Sep-01 11:02:06 AM Z-Wave Warning HomeSeer SmartStick+: Device (Node 10) woke up, but queued command failed to be sent. Command=Poll Device
Sep-01 11:02:05 AM Z-Wave Wake-Up Util Proc for (Upstairs Master Bedroom Smoke Alarm - Root) handling: Poll Device
Sep-01 11:02:05 AM Z-Wave HomeSeer SmartStick+: Wake-Up Notification Processing for Node 10 (Upstairs Master Bedroom Smoke Alarm - Root)
Sep-01 11:02:05 AM Z-Wave HomeSeer SmartStick+: Z-Wave Wake-Up Notification Received for Node 10

I deleted the nodes and then re-added them. Once I did that the messages didn't appear but then the wake-up status wasn't updating the status time so my events checking communication weren't firing. Then I noticed there wasn't any polling value so I set it to a random 20 min like it was before. Now the events fire again but the error message is back. I don't remember this being an issue a few months back.

Just to be on the current release, I just updated to 3.0.1.142 a few mins ago, was 3.0.1.140.

Node info attached.

Any ideas?

-Travis

[Daweeze]

Wake timer is approx every 62 minutes. Device is only 7' away. 5 of these do the same thing.

[rjh]

Do you see the error every 62 minutes? And even if you do, is the device updating ok? Could be a false error.

Wake timer is approx every 62 minutes. Device is only 7' away. 5 of these do the same thing.

[Daweeze]

Do you see the error every 62 minutes? And even if you do, is the device updating ok? Could be a false error.

Yeah, it does update just fine (once I set the polling time). Is it generated based on the information in the Node Info though? Not sure if this is normal (Highlighted in red).

-Travis

[bartbakels]

I still have an issue, also with the latest zwave plugin beta, with the Fibaro Dimmer V2, which is mupdating the status to invalid status every time it sends an update. There is also still an issue with the power usga ereporting which expectsanother byte count.

regards

bart

[ian351c]

I think it is fixed, I found some G2 modules to test with. Try Z-Wave plugin 3.0.1.142 in the Beta section.

I've updated to 3.0.1.144 and the settings for these devices are much more responsive. Thanks! However, adding a new device (I tested with a G2 Smart Illuminator) still results in the root device changing state whenever the physical switch is used.

Thanks.

[rjh]

Which device is this exactly? I have a smart dimmer 2nd generation model DSC25-ZWUS and the button does not send any Z-Wave commands.

I've updated to 3.0.1.144 and the settings for these devices are much more responsive. Thanks! However, adding a new device (I tested with a G2 Smart Illuminator) still results in the root device changing state whenever the physical switch is used.

Thanks.

[ian351c]

Which device is this exactly? I have a smart dimmer 2nd generation model DSC25-ZWUS and the button does not send any Z-Wave commands.

It's an Aeotec "Micro Smart Energy Illuminator G2" Model: DSC19103-ZWUS. I included it using the usual process via Homeseer (Plugins > ZWave > Controller Management then choose Add/Include a Node from the drop down and click Start, then press the button on the device). Then change/confirm the Notification option on the root device to Enabled. If I then use a physical switch wired to the "wall switch" terminals on the Illuminator, the Root device changes rather than the Switch Multilevel child device.

[britkat]

Echoing a previous post. I have a problem with version 3.0.1.144 and my Fibaro Dimmer 2 modules. It does not recognise the switch status. Attached are the node info and log capture:

[stefxx]

I have Qubino sending us some samples.

Did you already receive them? I also have issues with about 50% of the switches not reporting Watts anymore. Rescanning those devices gives the following error:

Could not get the METER TYPE from node 12, so devices for the METER class will not be created or rebuilt.

Any idea?

[Matt Powell]

Rich,

Any updates on the Fibaro Dimmer? Did you get the update from Fibaro?

Here is the Add log if it helps.


Add Node started...
Activate the 'Add to Network' function on the device...
A new node is being added...
Adding a new SLAVE NODE...
DONE - Add Node Operation is Complete.
Done. Node 32 Added.
Reloading (importing) node information...
Synchronizing node information with HomeSeer and creating new device(s) as necessary...
Synchronize nodes finished. Number of device nodes to be created/added = 1
Device synchronization needs to get Z-Wave class information for one node.
Negotiating or Verifying SECURITY SCHEME for node 32
Z-Wave Security Scheme and Key Exchange was successful for node 32, now waiting for the device to finish storing information before proceeding...
Getting SECURITY class information for node 32
Z-Wave manufacturer information for node 32, ID: 271=10FH (Fibaro), Type: 258=102H, ID: 4096=1000H
Node: 32 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION_V2, MANUFACTURER_SPECIFIC_V2, SWITCH_MULTILEVEL_V3, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION_V2, POWERLEVEL, SECURITY, FIRMWARE_UPDATE_MD_V2, CRC_16_ENCAP, CONFIGURATION_V4, SENSOR_MULTILEVEL_V7, METER_V3, MULTI_CHANNEL_ASSOCIATION_V3, MULTI_CHANNEL_V3, PROTECTION_V2, NOTIFICATION_V6, SWITCH_ALL, APPLICATION_STATUS
Node: 32 Supports Secure Class(es): BASIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION_V2, SWITCH_MULTILEVEL_V3, MULTI_CHANNEL_ASSOCIATION_V3, MULTI_CHANNEL_V3, CONFIGURATION_V4, PROTECTION_V2, SWITCH_ALL
Node: 32 Controls Class(es): SCENE_ACTIVATION
Node: 32 Controls Secure Class(es): SCENE_ACTIVATION
Node 32 is Z-Wave version: Lib: 4.05 App: 3.4
Node 32 is a Z-Wave Plus node. Retrieving ZWPlus Info...
Warning: Node 32, EndPoint=1 Multilevel Sensor Report was not received (B) - the child device will NOT be configured properly.
Warning: Node 32 did not respond to the Notification Supported request.
All associations for node 32 have been retrieved successfully, it supports associations on these groups: 1, 2, 3, 4, 5.
Root Node Device Node 32 Z-Wave Fibaro Switch Multilevel was created for node 32 on network D220525B
New Interface: Adding association for Z-Wave device Node 32 Z-Wave Fibaro Switch Multilevel (Node 32, Group 1, Endpoint 1) to HomeSeer
New Interface: Adding association for Z-Wave device Node 32 Z-Wave Fibaro Switch Multilevel (Node 32, Group 2, Endpoint 2) to HomeSeer
Enabling instant status for Z-Wave device Node 32 Z-Wave Fibaro Switch Multilevel (32) on Group 3
Enabling instant status for Z-Wave device Node 32 Z-Wave Fibaro Switch Multilevel (32) on Group 4
Enabling instant status for Z-Wave device Node 32 Z-Wave Fibaro Switch Multilevel (32) on Group 5
9 out of 9 Child devices of node 32 were created successfully.
Finished.

[budejake]

Been away for a few weeks on holiday and gone to version 1.44 and problem with fibaro dimmer still there (S1 S2 the same when non secure and no status update when secure).

Is it not possible to add version 126 anywhere as this works?