Based on my zero knowledge on zwave class and groovy, I tried to figure out the unhandled event. Command Class 50 is meter and 37 is binary switch. I suspect the power meter is not handled properly resulted the child device cannot be added to the dashboard. I also found that the power / energy reading is missing from the child device page. Not sure if this makes sense at all.
Looking at the driver code, not sure if this is a problem:
Merry Christmas to all. I have some good news to share, I managed to fix the driver code with some trials and errors. The fix is rather simple, the version defined for the multichannel command is still pointing to v3 in the Github code. Update the following:
private getCommandClassVersions() {
[
0x20: 1, // Basic
0x25: 1, // Switch Binary
0x70: 2, // Configuration
0x98: 1, // Security
0x60: 4, // Multi Channel
0x8E: 2, // Multi Channel Association
0x26: 1, // Switch Multilevel
0x87: 1, // Indicator
0x72: 2, // Manufacturer Specific
0x5B: 1, // Central Scene
0x32: 3, // Meter
0x85: 2, // Association
0x86: 1, // Version
0x9B: 1, // Association Command Configuration
0x90: 1, // Energy Production
0x73: 1, // Powerlevel
0x30: 1, // Sensor Binary
0x28: 1, // Switch Toggle Binary
0x2B: 1, // Scene Activation
0x75: 2 // Protection
]
}
Good spot @gabriel_kpk - I have submitted this pull request to Eric's github link, so this is fixed for everybody else who copies from the link on this thread.
Cheers
I expect when you changed the device handler it did not re-attempt the initialise command (it ran initialise while using the wrong device handler, so didnt think it needed re-running). Possibly....
Would be fairly easy to fix, but would probably suggest it needs somebody else to report this error before fixing, as I dont think this behaviour is what I would expect.
As suggested, I continue the Is there any chance that my Fibaro 223 will work properly? thread here.
Devices started working properly after changing hub location and routing. The hub is now in the same room as a few Fibaro 223 devices. I've noticed that when there are no additional nodes on the way, everything works fast and properly. However, as soon as an additional node appears, delays and sometimes even unresponsiveness occur. The worst thing is that one of the devices, that is located a few meters from the hub, changes the routing by passing through other rooms and causes the above problems. What can I do with this?
is anybody else having problems with floods of energy reports?is driving me crazy !!!!
if i set to 0 parameter 53 and 57 it spams even more and even if i try to make them as slow as possibile is still plenty of spam.
From what i've been reading about there is a problem with some firmware version . I have 5 fgs 223 i'm close of accepting my lose and throw them out of the window
I'm having trouble adding the Fibaro FGS223 to Hubitat. It just doesnt detect it. Exclusion from ST was successful, but hubitat doesn't detect it when I try to discover it. I have C7.
Tried a lot but nothing working with fibaro devices. Aeotec works seamlessly, but Fibaro double switches are not bring detected by hubitat, neither when I try to exclude or include them
I had to pair a Fibaro FGS-223 (ZW5 v3.2) close to the hub and then relocate it to it's final position at the other end of the house. Once it was all wired in to that final location I left it over night but then had to run a Z-wave repair as it wasn't connecting back to the hub. Once that completed it's been perfect for the last 2 years.
thanks for your replies but frankly I tried bringing the hub right next to the Fibaro FGS223 but still nothing. And I tried with 2 of the FGS223 and still same. I managed to tranafer 50+ devices successfully but frankly all Fibaro devices gave lots of hard time and the FGS223 in particular never worked. Aeotec were way more smoother to migrate
If you exclude Fibaro, you need to wait a while as the device resets(?). Wait until the green LED comes on for 3 or so seconds, and then you can start inclusion.
I am fighting my Z-wave mesh.
I have a bout 30 Z-wave devices and most of them are FGS-223.
It seems that every time I am running a scene involving many devices (good night for example) turnning all lights off, My Z-wave gets too busy and performance is below accepted.
I was thinking maybe I should look for a way to reduce trafic by not reporting power meter from the devices as I do not realy care about this functionality.
Is there an easy way to make the devices stop reporting power consumption?
They are already in “no security” mode.
Looking at the log files I see power reports and I wish I could easily remove them and make it easier for the Z-wave net