set-protocols changes receiver frequency and blocks reception

[pludov]

Using the set-protocols utility to enable all protocols on my receptor changed its frequency from 433.92MHz to 433.42MHz, and dropped it's ability to receive signals in my case.

I have debugged the tool and found it passes 0 by default for the frequency. Manually changing it to pass 433.92 resolved the issue (but will probably break devices on other frequency...):

    // Send the command
    rfxtrx.configureRFX(433.92, 0, protocolsToEnable.map(entry => rfxcom.protocols[receiverTypeCode][entry]));

My device itself is identified by:

{
  subtype: 0,
  seqnbr: 1,
  cmnd: 2,
  receiverTypeCode: 83,
  receiverType: '433.92MHz transceiver',
  hardwareVersion: '1.2',
  firmwareVersion: 1048,
  firmwareType: 'Pro 1',
  enabledProtocols: [
    'BLYSS',        'RUBICSON',
    'FINEOFFSET',   'LIGHTING4',
    'RSL',          'BYRONSX',
    'IMAGINTRONIX', 'MERTIK',
    'LIGHTWAVERF',  'HIDEKI',
    'LACROSSE',     'X10',
    'AC',           'HOMEEASY',
    'OREGON',       'KEELOQ'
  ],
  transmitterPower: 10,
  noiseLevel: 75
}

I am willing to create a PR, but am not sure about a proper fix for this. Would having the frequency as an option be useful for other hw ?

[maxwellhadley]

Ah yes: I think this has happened because the utility didn't get updated when new hardware types were added to the main library package. I will take a look after Christmas. Many thanks for reporting the issue