Mis configured fgwp 121 device

[GSV3MiaC]

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?

NO, my problem is NOT within Z-Wave JS UI

Checklist

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there.

Describe the bug

Parameter 10 is missing, parameters 12 and 13 are wrong. See Document at
https://manuals.fibaro.com/document/fgwp-advanced-parameters/

Result is device does not send periodic reports.

This is for fw version 4,2

Device information

Manufacturer:
Model name:
Node ID in your network:
Fibaro fgwp 121, uk version
Node 38

How are you using node-zwave-js?

• zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
• zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
• zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
• ioBroker.zwave2 adapter (please specify version)
• HomeAssistant zwave_js integration (please specify version)
• pkg
• node-red-contrib-zwave-js (please specify version, double click node to find out)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

version:
node-zwave-js branch:
zwave-js-ui branch:

Did you change anything?

yes (please describe)

If yes, what did you change?

No response

Did this work before?

Don't know, this is a new device

If yes, where did it work?

No response

Attach Driver Logfile

Log file not relevant, just check the manufacturer docs.

[zwave-js-assistant]

Because of the large amount of Z-Wave devices, we cannot write all configuration files ourselves.
Help from the community is required, so we can focus our time on improving Z-Wave JS itself. 🙏🏻

This issue has been labeled "Help wanted", meaning we kindly ask anyone who wants to help out for support. Here are a few resources to get you started - don't hesitate to ask if you are having problems:

• Contributing configuration files
• Importing from other sources
• Configuration file format
• Style guide

We may get around to doing it ourselves at some point, but community support will speed up this process immensely.

Thanks!

[apella12]

Don't know if this is still an issue. There are several of Fibaro "FGWP xxx" devices in the config DB all with different parameters. If still an issue, what is the type/ID (something like (0x0602:0x4003) of your device. Also do you have a manual for your specific device?

[GSV3MiaC]

The type Id reported bty zwave2mqtt is  271-4096-5377 (0x010f-0x1501-0x1000), but no I don't have a manual on paper, I believe it is online. Maybe at https://manuals.fibaro.com/content/manuals/en/FGWPG-121/FGWPG-121-EN-T-v1.0.pdf ⁣Rgds, Dave Storey​

…

On 28 Sep 2023, 20:21, at 20:21, Robert Eckhoff ***@***.***> wrote: Don't know if this is still an issue. There are several of Fibaro "FGWP xxx" devices in the config DB all with different parameters. If still an issue, what is the type/ID (something like (0x0602:0x4003) of your device. Also do you have a manual for your specific device? -- Reply to this email directly or view it on GitHub: #5358 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[AlCalzone]

One thing to consider, a lot of fibaro devices have different revisions that only differ by firmware version but have completely different parameters.
Their support website is pretty good though and contains all this information.

[apella12]

The zwave-js-ui parameters for devices with (0x010f-0x1501-0x1000) match the manual above. The parameters referenced in the first post are for different devices. Those parameters apply to device IDs (all 0x010f-0x0602); 0x1001, 0x1003, 0x1004, 0x4001 & 0x4003. IMHO there is not a problem here, but that's not my call.

[AlCalzone]

I haven't double-checked the IDs, so you may be right.
The information is a bit messy though. The link above lists the differences between FW <= 2.5 and FW >= 3.2, which are quite severe. And this config is indeed missing parameters 10 and 50, which are not found in the PDF, but on that page. 🤪

[GSV3MiaC]

Which is why I stated the fw version, and referenced the advanced manual in the original post.. https://manuals.fibaro.com/document/fgwp-advanced-parameters/ Which definitely does not match what zwave2mqtt was showing me, and using. Maybe the zwave config files have changed since then, so those parameters work, but i have not reloaded the system since then. The attached screenshot is what I see, which does not match the advanced paramaters listed in that document. ⁣Rgds, Dave Storey​

…

On 28 Sep 2023, 22:07, at 22:07, AlCalzone ***@***.***> wrote: One thing to consider, a lot of fibaro devices have different revisions that only differ by firmware version but have completely different parameters. Their support website is pretty good though and contains all this information. -- Reply to this email directly or view it on GitHub: #5358 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[apella12]

I'm a newcomer to zwave-js-ui, but from past experience Fibaro is a PITA because they use the same ID numbers for different versions. This can be handled, but complicates things. The other problem is that the manuals do not identify the IDs of the devices the manual applies to. There are two JSON files in the config folder related to this discussion. The first is for the link in the opening post. It provides different parameters for the different versions, but does not have the ID of your device.
fgwp102.json.txt
The other is for the manual a few posts above here.
fgwpg-121.json.txt That does have the ID of your device. It could be you have a later version with different parameters. However, changing the existing JSON will disrupt everyone that does have the device and version that manual applies to. I think there is some zwave-js-ui way to manually add a parameter and then you could see if anything changes regarding reporting.

EDIT: Thought of another idea after dinner, but need @AlCalzone to confirm it will work. Modify the first txt file (fgwp102) with your IDs, (just copy over any of the others) and save as a json in the config folder in your store. Reinterview the device and I believe you will have the parameters and can test to see if they perform as expected. If it does not work, you can delete that file and reinterview the node to get back to where you are now.

[AlCalzone]

IMO we should just ship 2 different files with all the IDs that are linked to FGWPG-121 (not 102!), separated by firmware versions.
Offering users on the 1.0 firmware two potentially non-existent parameters is okay IMO and if someone does report them not working, we can still add a condition to hide them.

[apella12]

Coming from Openhab I thought I could help out on some of the config-help wanted in the Zwave-js issue list by using the OpenSmartHouse DB to resolve some open issues like this one. I don't want to be difficult, but I believe there is no version separation for the FGWP-121, only the FGWP-102. This screen shows my dilemma here.
.

I have compared the parameters of each device in the OpenSmartHouse DB with the parameters in the ZJS config folders and they match.
One comment in the first post was about reporting. Periodic reports are param13 for 121 version 4.6 and param 14 for 102 version 3.2+. Maybe I just need to let this rest for a bit.

[GSV3MiaC]

My device is actually fgwpg, not b, but i guess that is just physical pin out. The config seems to have separate reporting intervals for power, and energy, on params 13 and 14 .. But neither are generating a report. Metering is definitely there, if I poll the device, so i am not sure why the description does not say metered, like the 102. ⁣Rgds, Dave Storey​

…

On 29 Sep 2023, 22:23, at 22:23, Robert Eckhoff ***@***.***> wrote: Coming from Openhab I thought I could help out on some of the config-help wanted in the Zwave-js issue list by using the OpenSmartHouse DB to resolve some open issues like this one. I don't want to be difficult, but I believe there is no version separation for the FGWP-121, only the FGWP-102. This screen shows my dilemma here. . I have compared the parameters of each device in the OpenSmartHouse DB with the parameters in the ZJS config folders and they match. One comment in the first post was about reporting. Periodic reports are param13 for 121 version 4.6 and param 14 for 102 version 3.2+. Maybe I just need to let this rest for a bit. -- Reply to this email directly or view it on GitHub: #5358 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[apella12]

My device is actually fgwpg, not b There is a slight difference in how Openhab and ZJS handle versions. The parameters numbers are the same between "g" and "b", but the default values (params 3, 21, 22 & 40) are different (30000 vs 18000 reflecting either 240 (13A max) or 120v (15A max). ZJS has separate config files for "g" and "b". FYI the rest of the model is FG= Fibaro Group; WP= Wall Plug. Also for Fibaro, Power = watts. Energy = KWH

If you're game, let's see if we can find the reporting issue. I apologize in advance, but my questions are going to start from the beginning as I don't know your complete setup or what you have done previously. Plug a running light or fan into the plug. Just using ZUI, drill down into configuration CC and verify 11, 12, 13 and 14 are at the defaults 15, 10, 3600 and 3600. The critical parameter is 14 because in all versions of FGWP devices this means reports. Use the arrow to update if not. Jump to the Meter CC are there any values? Hit the refresh, any change? If no values, can you get a screen shot of the expanded meter CC. I don't understand what you mean by metering? Is it the same as reporting?