fwMd

Begonnen von Paul Guijt, 08 Oktober 2025, 14:15:56

Vorheriges Thema - Nächstes Thema

Paul Guijt

What's the idea with fwMd?

Currently, it reports "fwMdManId: 0371, fwMdFwId_0: 0018, fwMdChkSum_0: 0000".

The definition of fwUpdate is
fwUpdate <decimal Target> <filename>

What is the decimal Target here?
RasPi 2B, CUL 433, Jens' FW, Berker, HomeMatic, KlikaanKlikuit, RFXtrx443, Squeezebox, Z-Wave, TradFri in die Niederlände

rudolfkoenig

ZitatWhat is the decimal Target here?
The NodeId of the device, in decimal

Paul Guijt

#2
Eh, perhaps it's an idea to change that in commandRef?
I suppose, the NodeId is available in the Module so it shouldn't have to be a parameter here.

Also, the fwUpdate definition says: The supported targets can be requested with the get fwMetaData command. And the resulting fwMd reading does not include 19, the NodeID, or 13, the nodeIdHex.
RasPi 2B, CUL 433, Jens' FW, Berker, HomeMatic, KlikaanKlikuit, RFXtrx443, Squeezebox, Z-Wave, TradFri in die Niederlände

rudolfkoenig

Sorry, my previous answer is wrong.

As far as I understand the code, the number must be one of the <X> from of the fwMdFwId_<X> Strings in the fwMetaData reading.
A single ZWave device can in theory have more than one firmware, with this number you select the one to be updated.
If you enter the wrong number, you get the message: "Device $hash->{NAME} does not support target $target"

The OTA code is by SamsonBox: https://forum.fhem.de/index.php?topic=101961 and I have never tested it.
If you can confirm the above theory, then I will clarify the parameter in the documentation.