Repeated frequent RCVD requestReply1 Events being logged

I am getting a steady stream of very similar entries in the Events Log examples below:

RCVD requestReply1: 01 15 00 04 10 42 0F 56 01 32 02 21 74 00 00 00 00 00 00 00 FC 79 04 (hex)

RCVD requestReply1: 01 15 00 04 00 42 0F 56 01 32 02 21 74 00 00 00 00 00 00 00 FC 79 14 (hex)

RCVD requestReply1: 01 25 00 04 10 42 1F 56 01 22 02 21 74 00 08 00 02 00 00 00 FC 79 C0 00 F7 FE 6F A5 CF 8B BD 7C 6E 59 E2 B3 FD 2E 0D (hex)

Is there anyway to decode this to give a pointer on where to look for what these mean and what might be sending them?

System is working fine but I have not had this volume of these entires when viewing the log previously.

Thanks

[matt (support)]

Those commands are encapsulated around a CRC 16 checksum class. Indigo currently just ignores those commands, although I should decode and process them. In this case they are coming from your device with Node ID / Address 66. What type of module is that?

Ah that makes sense presumably that is the 42 (hex).

Device 66 is a newly installed energy meter. I've included it to my Z-Stick locally but when I tried to sync to create new device it fails for lack of return path. I had assumed this was due to it being out of range of my existing network. When plugged into the controller the Z-Stick and Energy meter are roughly 20 metres apart with multiple block walls between them.

I will be installing some light controllers in intermediate positions which I had assumed would help solve the problem of range and hence creating the new device?

[matt (support)]

Yes, installing some non-battery modules between the meter and the Z-Stick should help to relay the commands and hopefully that return route can be reliably created. You might end up needing to exclude/re-include the meter after you've added (included + sync'd) the lighting modules.

As luck would have it after a further try to sync the next day it worked and the meter is up and running. Just a note that for this 1 phase Aeotec Energy meter in the UK it needed a firmware upgrade to 1.35 and the CRC-16 reporting turning off before what it is reporting made any sense.

[matt (support)]

Indigo 7.4.1 is now available and includes support for the CRC 16 checksum commands.