Autor Thema: Only 2 Oregon sensors from 10 being detected  (Gelesen 2592 mal)

homer

  • Gast
Only 2 Oregon sensors from 10 being detected
« am: 26 März 2013, 14:52:37 »
Hello.

I have RFXTRX433 connected to my WHS2011 running FHEM5.3. I can't seem to get any more than 2 temperature sensors being auto detected. In my config file I have:

define RFXTRXUSB TRX COM4@38400 noinit

In my log, I get:

2013.03.26 13:45:46 1: Including fhem.cfg
2013.03.26 13:45:46 3: telnetPort: port 7072 opened
2013.03.26 13:45:46 3: WEB: port 8083 opened
2013.03.26 13:45:46 3: WEBphone: port 8084 opened
2013.03.26 13:45:46 3: WEBtablet: port 8085 opened
2013.03.26 13:45:46 1: TRX: RFXTRXUSB no init is done
2013.03.26 13:45:46 3: Opening RFXTRXUSB device COM4
2013.03.26 13:45:46 3: Setting RFXTRXUSB baudrate to 38400
2013.03.26 13:45:46 3: RFXTRXUSB device opened
2013.03.26 13:45:46 1: TRX: defined with noinit. Do not send init string to device.
2013.03.26 13:45:47 1: Including ./log/fhem.save
2013.03.26 13:45:47 3: initialUsbCheck return value: This command is not yet supported on windows
2013.03.26 13:45:47 2: .
2013.03.26 13:45:47 0: Server started with 31 defined entities (version Fhem 5.3 (DEVELOPMENT), $Id$, pid 9372)
2013.03.26 13:45:48 3: Opening ml device 192.168.0.44:62910
2013.03.26 13:45:48 3: ml device opened
2013.03.26 13:45:48 2: MAXLAN_Parse: Cube thinks it is 26.3.2013 14:46
2013.03.26 13:45:48 2: MAXLAN_Parse: Time difference is 61 minutes

I get 2 sensors created in TRX_WEATHER:

TRX_WEATHER
THGR132N_1 T: 14.2 BAT: ok
THGR228N_1 T: 2.4 H: 56 BAT: ok

... but I have 8 more THGR132N sensors that aren't being detected. If I use RFXmngr, I can see all of the messages being received from the other sensors.

Can anyone help?
Thanks
Homer




[/ALIGN]

Offline Willi

  • Sr. Member
  • ****
  • Beiträge: 594
Aw: Only 2 Oregon sensors from 10 being detected
« Antwort #1 am: 26 März 2013, 23:45:33 »
Zitat von: homer schrieb am Di, 26 März 2013 14:52

TRX_WEATHER
THGR132N_1 T: 14.2 BAT: ok
THGR228N_1 T: 2.4 H: 56 BAT: ok

... but I have 8 more THGR132N sensors that aren't being detected. If I use RFXmngr, I can see all of the messages being received from the other sensors.


[/ALIGN]


For FHEM commandref is always a good point to look at ;-)

On default the TRX module displays the different channels supported for a sensor. See for example http://oregonscientific.premiumstore.com/pdf/oregon/sensorchart.pdf of the number of channels supported by a sensor by Oregon Scientific.

THGR132N only support three different channels. Thus you can see at most three diffent sensors if you set the channels right. On your case you seem to have all sensors set to channel 1 (dip switches).

The module also allows to support more IDs using the attribute longids. See commandref of TRX for this.

In your case just issue:
attr RFXTRXUSB longids THGR132N

After this the TRX modules will use the long IDs of the sensors.

The drawback is described in commandref:
"The drawback is that the deviceid changes after changing batteries. All devices listed as longids will get an additional one byte hex string appended to the device name."

Because of this this is not the default setting. Normally I do not advise to buy more sensors that different channels supported by Oregon Scientific.

Thus you have to live with the fact that your IDs will change after changing the battery.

If you think that my description in commandref is not described well, just give me something new to put in there.

Regards

Willi

FHEM@Q600(debian) mit DS9490R (1Wire) | FHEM@Sheevaplug(debian) mit RFXCOM-Receiver(80002), CULv3 & USB-WDE1 | FHEM@odroid mit CULv2 & RFXtrx433

homer

  • Gast
Aw: Only 2 Oregon sensors from 10 being detected
« Antwort #2 am: 28 März 2013, 08:55:44 »
HI Willi,

Thank you for your very detailed reply. I was using the commandref but I think part of my problem is that FHEM is new to me so I'm still learning the "tricks" to get things done. My only suggestion would be to perhaps offer some more examples in the commandref - that would have helped with my problem. However, I'm very impressed with FHEM and the flexibility it can offer.

Thanks again.

Homer