3.0.1.130 Stable now ?

[rjh]

If it assigns the same node #, that means it really did not get removed from the network. This could also be a range issue. Some devices need to be close to the controller to be removed.

OK, I have tried a couple of times, but will persevere. Interestingly it always assigns the same Node Number (31) even though I have removed it. Does that mean its caching some info? How do I drop that node number a force it to use a brand new one?

[bartbakels]

rich,

i have updated to the newest zwave beta (147) due to the fibaro dimmer 2 issues, but same errors and the current device root has no zwave id anymore assigned. it has 32 but this node number has been disappeared from the list. However i can still control the device.

any ideas?



bart

[Guest]

.130 Issues here too

Since upgrading, I'm having issues too. Half of my devices will no longer communicate. I can sometimes control them, but their responses never get updated. And it's not like all of a particular type, only some. Most of my dimmers are Leviton, but some work, some don't. I have a handful of Aeotec, same there as well, some not all, and my Kwikset deadbolt won't communicate.
I've had issues with the Kwikset before, but never had a problem with any of the others.

[John245]

Reset accumulated values does not hold (Qubino Flush 2 relay)

I'm on .130

The reset of accumulated values does not hold for a Qubino flush 2 relay. Resetting the Blue Eco 320 Pump (819.3) kWh the value will be 0 (see below).


However the next poll the value is 819.3 (see below) which is the value befor applying the reset.



---
John

[John245]

Status graphics does not hold (partly) when rescanning Qubino Flush 2 relay

I'm on .130.

When rescanning a Qubino flush 2 relay the status graphics are changed. I will not suspect this behaviour.

The image below shows the original formating (Blue Eco 320 pump is relevant)


The image below shows that formatting of the values of the Blue Eco Pump 320 changed (Node 4) - after rescan of Node 4.


---
John

[olof]

Fibaro Dimmer 2 version 3.5

Hi there,

I just included one of my 20 Dimmer2s with version 3.5 on 3.0.1.148 beta and it works.

It would be very nice if you would also add support of scene activation. I have asked this for a couple of year now.

When scene activation is enabled it will send for example

okt-07 16:43:02 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_SWITCH_MULTILEVEL_V3 Frame(7)=5
okt-07 16:43:02 Z-Wave Set_New_Level_Real called for 1st Floor Sleep Olof Switch Multilevel 1, Type=COMMAND_CLASS_SWITCH_MULTILEVEL_V3, EndPoint=0
okt-07 16:43:02 Z-Wave Set_New_Level_Real: Initial device is 1st Floor Sleep Olof Switch Multilevel 1
okt-07 16:43:02 Z-Wave Set_New_Level_Real: STARTING
okt-07 16:43:02 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_BASIC_V2 Frame(7)=1
okt-07 16:43:02 Z-Wave Error Node Change Event for Node 3 on Network FB595D71, CC=COMMAND_CLASS_SCENE_CONTROLLER_CONF but no valid devices were found. (2B-01-17-00-E2-9F-E9)
okt-07 16:43:01 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_SCENE_ACTIVATION Frame(7)=1
okt-07 16:42:59 Z-Wave Error Node Change Event for Node 3 on Network FB595D71, CC=COMMAND_CLASS_SWITCH_MULTILEVEL_V3 but no valid devices were found. (26-04-00-00-05-01-D4)
okt-07 16:42:59 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_SWITCH_MULTILEVEL_V3 Frame(7)=4
okt-07 16:42:59 Z-Wave Error Node Change Event for Node 3 on Network FB595D71, CC=COMMAND_CLASS_SCENE_CONTROLLER_CONF but no valid devices were found. (2B-01-16-00-D1-AE-EA)
okt-07 16:42:59 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_SCENE_ACTIVATION Frame(7)=1


28. Scene activation functionality
SCENE ID depends on the switch type configurations.

Momentary switches
SCENE ID: S1 input SCENE ID: S2 input
16 : 1 x click
14 : 2 x click
- : 3 x click
12 : hold
13 : release
26 : 1 x click
24 : 2 x click
25 : 3 x click
22 : hold
23 : release

See manual

[rjh]

For scene activation, is this an Aoetec dimmer? If so, they have an issue in the firmware and I have already sent them the details, awaiting for them to fix.

Hi there,

I just included one of my 20 Dimmer2s with version 3.5 on 3.0.1.148 beta and it works.

It would be very nice if you would also add support of scene activation. I have asked this for a couple of year now.

When scene activation is enabled it will send for example

okt-07 16:43:02 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_SWITCH_MULTILEVEL_V3 Frame(7)=5
okt-07 16:43:02 Z-Wave Set_New_Level_Real called for 1st Floor Sleep Olof Switch Multilevel 1, Type=COMMAND_CLASS_SWITCH_MULTILEVEL_V3, EndPoint=0
okt-07 16:43:02 Z-Wave Set_New_Level_Real: Initial device is 1st Floor Sleep Olof Switch Multilevel 1
okt-07 16:43:02 Z-Wave Set_New_Level_Real: STARTING
okt-07 16:43:02 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_BASIC_V2 Frame(7)=1
okt-07 16:43:02 Z-Wave Error Node Change Event for Node 3 on Network FB595D71, CC=COMMAND_CLASS_SCENE_CONTROLLER_CONF but no valid devices were found. (2B-01-17-00-E2-9F-E9)
okt-07 16:43:01 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_SCENE_ACTIVATION Frame(7)=1
okt-07 16:42:59 Z-Wave Error Node Change Event for Node 3 on Network FB595D71, CC=COMMAND_CLASS_SWITCH_MULTILEVEL_V3 but no valid devices were found. (26-04-00-00-05-01-D4)
okt-07 16:42:59 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_SWITCH_MULTILEVEL_V3 Frame(7)=4
okt-07 16:42:59 Z-Wave Error Node Change Event for Node 3 on Network FB595D71, CC=COMMAND_CLASS_SCENE_CONTROLLER_CONF but no valid devices were found. (2B-01-16-00-D1-AE-EA)
okt-07 16:42:59 Z-Wave ApplicationCommandHandler from node 3 HANDLING: COMMAND_CLASS_SCENE_ACTIVATION Frame(7)=1


28. Scene activation functionality
SCENE ID depends on the switch type configurations.

Momentary switches
SCENE ID: S1 input SCENE ID: S2 input
16 : 1 x click
14 : 2 x click
- : 3 x click
12 : hold
13 : release
26 : 1 x click
24 : 2 x click
25 : 3 x click
22 : hold
23 : release

See manual

[olof]

For scene activation, is this an Aoetec dimmer? If so, they have an issue in the firmware and I have already sent them the details, awaiting for them to fix.

No these are Fibaro Dimmer 2s but also Fibaro Dimmers 1st version have these features
That feature is very handy and all other controllers are supporting this feature

You can find details in the manual of Fibaro

[rjh]

I have not tested it on the Fibaro dimmer, but can. But I did have one user confused at to how this works. So just to be clear, the dimmer can only be the target of a scene, it cannot initiate a scene. So in HS, on the Z-Wave plugin scene management page you create a scene, then add the dimmer to the scene, then save and program. To trigger the scene, you can use a Z-Wave action or trigger it from a scene controller, like the Cooper scene controller.

I know this works with other scene capable devices as we tested it last week with a Cooper scene controller and some Cooper switches.

No these are Fibaro Dimmer 2s but also Fibaro Dimmers 1st version have these features
That feature is very handy and all other controllers are supporting this feature

You can find details in the manual of Fibaro

[olof]

I have not tested it on the Fibaro dimmer, but can. But I did have one user confused at to how this works. So just to be clear, the dimmer can only be the target of a scene, it cannot initiate a scene. So in HS, on the Z-Wave plugin scene management page you create a scene, then add the dimmer to the scene, then save and program. To trigger the scene, you can use a Z-Wave action or trigger it from a scene controller, like the Cooper scene controller.



I know this works with other scene capable devices as we tested it last week with a Cooper scene controller and some Cooper switches.

[Paul32]

Fibaro FGS-222 v2.1 status not always update

Hi rjh,

I use now z-wave plug-in version 1.0.1.148 but have still 1 use
My Fibaro FGS-222 v2.1 is not always updating the status, some times it works ok, and a hour later it reports nothing when local controlled.
I have added it again non-secure but no result.

My Fibaro FGS-222 v2.2 (4 pcs) working fine.
Also my Fibaro FGD-212 v3.3 (2pcs) are working OK now, when added non-secure

In version 3.0.1.87 everything worked fine.

[rjh]

Chasing down different versions of firmware will be impossible so I would like to make sure the latest works, which it appears it does. I would update your older devices to the latest.

Hi rjh,

I use now z-wave plug-in version 1.0.1.148 but have still 1 use
My Fibaro FGS-222 v2.1 is not always updating the status, some times it works ok, and a hour later it reports nothing when local controlled.
I have added it again non-secure but no result.

My Fibaro FGS-222 v2.2 (4 pcs) working fine.
Also my Fibaro FGD-212 v3.3 (2pcs) are working OK now, when added non-secure

In version 3.0.1.87 everything worked fine.

[sooty]

Chasing down different versions of firmware will be impossible so I would like to make sure the latest works, which it appears it does. I would update your older devices to the latest.

So whilst I have a bit of spare time I thought I would have a play with updating the Z-Wave plug-in from .143 to .150. What a mistake that was...

I have 34 Fibaro FGD 212 (Dimmer 2) devices in my network which are a mix of 3.2 and 3.3 firmware versions. They were all originally included (non securely) with something earlier than .143 and whilst the S2 devices didn't represent their status properly, everything else worked fine only requiring Group 1 to be associated to Homeseer for all child devices to update correctly.

A while after the update I noticed some warnings in the log about meter reports (accumulated power) coming in but not being able to find the relevant child node. I suspected that something had changed with the device updating procedure so thought I would try a rescan.

With 34 of these devices (some of which are not readily accessible) and umpteen linked events, I didn't fancy the task of excluding and re-including so opted to delete all child devices from 1 unit and do a rescan. I purposely chose a device in the same room as my controller because I know how unreliable this procedure can be with distant nodes.

The result was that the S2 and accumulated power devices then began to update properly but I noticed that it had added 2 child devices for power (instant watts) but only 1 was updating. I deleted the non updating device and then the next issue was that it was updating one of the notification devices with the S1 value as well as updating the correct device.

It also appears (in my case) to set up the associations incorrectly for the FGD-212 with a factory configuration.
According to the Fibaro documentation, Group 1 (lifeline) should have a single association to the controller, however HS3 sets an additional association on Group 1 from EP1. It also sets up Group 2 with EP2 which looks like it should be EP1.

From the Fibaro manual:


I was considering doing an exclude re-include on a single device to see if it would then behave but I'd had enough at this point and just reverted back to .143.

Is it really necessary to have to exclude and re-include a node to have it work properly? Is it not possible to have the re-scan procedure add any missing child devices and / or update any existing devices with the proper data?

Paul..

[SteveMSJ]

Chasing down different versions of firmware will be impossible so I would like to make sure the latest works, which it appears it does. I would update your older devices to the latest.

[rjh]

Unfortunately these devices use multichannel and there is information that is saved in the device when you add it to the network. Since I am not aware of any class changes (class changes require the device to be removed and re-added), you should be able to delete all the devices for the node then just do an import. I know that still messes up your events but the node ID does not change.

I have the latest dimmer 2 on a system here and from all my testing it looks ok.

I would remove association 2 and 4 if they are added as that is for older controllers that only accept BASIC commands for control. HS can handle the multilevel command class ok. The basic command could cause the wrong devices to be modified. That is another reason I normally suggest to remove and re-add the device as HS will set the proper associations for you. But in your case you may have older associations set and removing the devices will not remove existing associations.

So whilst I have a bit of spare time I thought I would have a play with updating the Z-Wave plug-in from .143 to .150. What a mistake that was...

I have 34 Fibaro FGD 212 (Dimmer 2) devices in my network which are a mix of 3.2 and 3.3 firmware versions. They were all originally included (non securely) with something earlier than .143 and whilst the S2 devices didn't represent their status properly, everything else worked fine only requiring Group 1 to be associated to Homeseer for all child devices to update correctly.

A while after the update I noticed some warnings in the log about meter reports (accumulated power) coming in but not being able to find the relevant child node. I suspected that something had changed with the device updating procedure so thought I would try a rescan.

With 34 of these devices (some of which are not readily accessible) and umpteen linked events, I didn't fancy the task of excluding and re-including so opted to delete all child devices from 1 unit and do a rescan. I purposely chose a device in the same room as my controller because I know how unreliable this procedure can be with distant nodes.

The result was that the S2 and accumulated power devices then began to update properly but I noticed that it had added 2 child devices for power (instant watts) but only 1 was updating. I deleted the non updating device and then the next issue was that it was updating one of the notification devices with the S1 value as well as updating the correct device.

It also appears (in my case) to set up the associations incorrectly for the FGD-212 with a factory configuration.
According to the Fibaro documentation, Group 1 (lifeline) should have a single association to the controller, however HS3 sets an additional association on Group 1 from EP1. It also sets up Group 2 with EP2 which looks like it should be EP1.

From the Fibaro manual:




I was considering doing an exclude re-include on a single device to see if it would then behave but I'd had enough at this point and just reverted back to .143.

Is it really necessary to have to exclude and re-include a node to have it work properly? Is it not possible to have the re-scan procedure add any missing child devices and / or update any existing devices with the proper data?

Paul..