We have moved at community.getvera.com

Author Topic: RFXCOM interface  (Read 116181 times)

Offline b_weijenberg

  • Full Member
  • ***
  • Posts: 129
  • Karma: +3/-1
Re: RFXCOM interface
« Reply #210 on: July 27, 2012, 05:45:51 am »
The message starting with 48DA78 is an UV sensor:
UV2[48384] UVN800 addr:BD UV factor:1 Level: low   Battery OK bits=72

The THWR288 does not have a humidity sensor:
TEMP2[36353] THN132N,THWR288,AW131 CH 1 addr:8E temp:30,9°C | 87,62°F  Battery OK bits=80

the other packets are received due to RF noise and can be ignored.

Offline antoine1964

  • Newbie
  • *
  • Posts: 12
  • Karma: +0/-0
Re: RFXCOM interface
« Reply #211 on: July 27, 2012, 08:15:02 am »
Thanks Bert, Do you have the structure of the UV messages to allow me to adapt/create a device for it ? I will try to wake up my old  development  skils lol
Gotcha :
ID Code(s) Message Length (nibbles)
EC70, D874(?) 14
Nibbles Contents Ultra-violet
9..8 UV Index Unit-less Integer
11..10 unkwnow (I suppose the low medium ...)

and second point have you already upgrade your rfxcom for ASTRAL lumiplus remote messages ?
http://www.vitapiscine.com/client/cache/produit/500_____45627_1345.jpg

I m not sure that the protocol is one you already manage ...
Thanks for all
Regards
« Last Edit: July 27, 2012, 08:35:56 am by antoine1964 »

Offline ninux

  • Jr. Member
  • **
  • Posts: 57
  • Karma: +0/-0
Re: RFXCOM interface
« Reply #212 on: July 27, 2012, 09:39:15 am »
Hello antoine1964

Could you test theses files who support the UV sensor UVN800 and remove humidity for THWR288A ?
VeraLite, RFXCOM Lan, IPX800

Offline antoine1964

  • Newbie
  • *
  • Posts: 12
  • Karma: +0/-0
Re: RFXCOM interface
« Reply #213 on: July 30, 2012, 10:43:34 am »

Hum; seems not to work and Evanes did remove your file from the source .... is it a Sign ?

On the other hand , and this is for Bert , what about the RFX sensor messages ? I currently have 4 heat sensors 1-wire connected to one I used to get inside homeseer ... what should i do to add them in the UI5 ?
regards
 

Offline j.hoekstra

  • Jr. Member
  • **
  • Posts: 70
  • Karma: +5/-0
Re: RFXCOM interface
« Reply #214 on: August 01, 2012, 09:48:14 am »
Hello, I'm contemplating getting a VERA unit to replace/accompany my current domotica-solution. I'm using several wireless sensors via RFXCom LAN-receiver/transmitter piped through a meteohub setup.
From this stems my first question, is it possible to use 2 different IP's and ports to connect to the LAN-receiver? In my case like IP1:5500 and IP2:10002 respectively?
Second question, for powermetering I use an RFXPower and for water/gas pulse meters, as far as I can tell there's no support for these included (yet)?
Would some  output from RFreceiver included with the receiver help?
Third and last question, I'm not certain that the RFXSensor is yet working/ work in progress, is it?

Thanks in advance

Offline evanes

  • Full Member
  • ***
  • Posts: 109
  • Karma: +1/-0
Re: RFXCOM interface
« Reply #215 on: August 28, 2012, 05:29:35 pm »
I have not tried using 2 rfxcom devices but I cannot imagine it not working. And you can setup ip and port for each.

Understand that this plugin is a work in progress, any help you can provide is welcomed.
My time for enhancing the plugin is very limited. Also not having hardware like the rfxpower devices makes it even more complex to develop updates.

I have no rfxsensor devices. Someone else?

Offline chris66

  • Sr. Member
  • ****
  • Posts: 318
  • Karma: +9/-8
Re: RFXCOM interface
« Reply #216 on: August 30, 2012, 02:24:42 pm »
Improvement Suggestion with sensors. I use a X10 MS13 sensor. It works fine, but recognized as a light and I would like it to be classified as a sensor, in order to be able to use it as a trigger to record pictures with my cam. Is it a way to do this? Thanks. chris

Offline j.hoekstra

  • Jr. Member
  • **
  • Posts: 70
  • Karma: +5/-0
Re: RFXCOM interface
« Reply #217 on: September 04, 2012, 06:01:31 am »
I have not tried using 2 rfxcom devices but I cannot imagine it not working. And you can setup ip and port for each.
So 1 device dedicated to receiving and another to sending? Will try that.
Quote
Understand that this plugin is a work in progress, any help you can provide is welcomed.
My time for enhancing the plugin is very limited. Also not having hardware like the rfxpower devices makes it even more complex to develop updates.

I have no rfxsensor devices. Someone else?
I do, RFXMeter with RFXPower and RFXPulse modules and also an RFXSensor type 3.
General structure would be to have D/S_RFXMeter.xml and .json?
Will take a look at it this weekend if I have time.

Offline lolodomo

  • Beta Testers
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: RFXCOM interface
« Reply #218 on: September 18, 2012, 04:18:05 pm »
Hi evanes.

I see more and more confusion from users installing the bad RFXCOM plugin !

Could we clarify the plugin names in code.mios.com and apps.mios.com, explaining clearly which RFXCOM products are supported by each plugin ?

I would propose to rename your plugin into "RFXLAN Gateway" (in code.mios.com and apps.mios.com).
There would be a "RFXLAN Gateway" and a "RFXtrx Gateway". What's your feeling ?

Offline j.hoekstra

  • Jr. Member
  • **
  • Posts: 70
  • Karma: +5/-0
Re: RFXCOM interface
« Reply #219 on: September 19, 2012, 09:46:52 am »
The names are clear enough, but description could be changed to explain the differences as well as code-revision corresponding to the one on trac.
I can't figure out which revision is in the appstore and how it corresponds to trac.

Offline lolodomo

  • Beta Testers
  • Master Member
  • *****
  • Posts: 3484
  • Karma: +74/-10
Re: RFXCOM interface
« Reply #220 on: September 19, 2012, 10:33:58 am »
I think "RFXCOM Gateway" is too much generic as RFXCOM is the mark for several products.

Offline hhg

  • Sr. Newbie
  • *
  • Posts: 21
  • Karma: +1/-0
Re: RFXCOM interface
« Reply #221 on: October 07, 2012, 01:07:26 pm »
Improved support for MS13E Motion Sensors

The attached version creates MS13E devices as Motion Sensors and not Binary Light.

It works by having a variable on the RFXCOM device "X10MotionDevices" where you add the MS13E devices. Note it should be the full altid address, i.e "X10A01,X10A05", not "A01,A05" for two MS13E on address A01 and A05.

Then delete the existing Binary Light devices, and set Autocreate mode to On. On next movement the devices will be create as Motion Sensors.

The Attached version is based on revision 44 from http://code.mios.com/svn_public/mios_rfxcom/

Any suggestion for a better mapping of the dusk/dawn sensor is welcome. Binary Light is a bit strange as On/Off has no effect....

Offline piperpilot

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: RFXCOM interface
« Reply #222 on: January 18, 2013, 03:29:33 pm »
Hi everybody,

I'm rather new to micasaverde, was a home seer user, since i took the plunge into z-wave. My problem is that i do have an old rfxcom receiver which is set at present to 32bit mode and connected via LAN.

looking at the log its seems that is is recognized but no new devices are created though auto create is set to 1

It has been functioning with homeseer.

this part of the log.

I installed the files of what i believe is the last version (trac 44?).

Any help would be appreciated.

50   01/17/13 22:27:33.032   luup_log:29: Starting RFXCOM device: 29 <0x2bae5680>
50   01/17/13 22:27:33.033   luup_log:29: Tree with number child devices: <0x2bae5680>
50   01/17/13 22:27:33.033   luup_log:29:        door sensors: 0 <0x2bae5680>
50   01/17/13 22:27:33.034   luup_log:29:      motion sensors: 0 <0x2bae5680>
50   01/17/13 22:27:33.034   luup_log:29:      keyfob sensors: 0 <0x2bae5680>
50   01/17/13 22:27:33.034   luup_log:29:      light switches: 0 <0x2bae5680>
50   01/17/13 22:27:33.034   luup_log:29:     window covering: 0 <0x2bae5680>
50   01/17/13 22:27:33.035   luup_log:29: temperature sensors: 0 <0x2bae5680>
50   01/17/13 22:27:33.035   luup_log:29:    humidity sensors: 0 <0x2bae5680>
50   01/17/13 22:27:33.035   luup_log:29:    pressure sensors: 0 <0x2bae5680>
50   01/17/13 22:27:33.036   luup_log:29:        rain sensors: 0 <0x2bae5680>
50   01/17/13 22:27:33.036   luup_log:29:       anemo sensors: 0 <0x2bae5680>
50   01/17/13 22:27:33.036   luup_log:29:      energy sensors: 0 <0x2bae5680>
50   01/17/13 22:27:33.036   luup_log:29: Open socket for read 192.168.1.7 port 10001 <0x2bae5680>
50   01/17/13 22:27:33.137   luup_log:29: Startup RFXCOM ready <0x2bae5680>

?.

50   01/17/13 22:27:45.367   luup_log:29: decodeMessage bits:0 data:00  <0x2c4e5680>
50   01/17/13 22:27:45.367   luup_log:29: Unknown Msg : 00  <0x2c4e5680>
50   01/17/13 22:27:45.394   luup_log:29: decodeMessage bits:24 data:18 60 FE 00  <0x2c4e5680>
50   01/17/13 22:27:45.394   luup_log:29: decodeArc24 <0x2c4e5680>
50   01/17/13 22:27:45.394   luup_log:29: decodeWaveman24 <0x2c4e5680>
50   01/17/13 22:27:45.395   luup_log:29: Unknown Msg : 18 60 FE 00  <0x2c4e5680>
50   01/17/13 22:27:45.396   luup_log:29: decodeMessage bits:120 data:78 FF FA 2C 6A 04 FF F0 1E E6 FF FA 2C 6A 04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.396   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.397   luup_log:29: Unknown Msg : 78 FF FA 2C 6A 04 FF F0 1E E6 FF FA 2C 6A 04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.397   luup_log:29: decodeMessage bits:112 data:F0 18 FF FA 2C 6A 04 FF F0 00 FF FA 2C 6A 04  <0x2c4e5680>
50   01/17/13 22:27:45.418   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.419   luup_log:29: Unknown Msg : F0 18 FF FA 2C 6A 04 FF F0 00 FF FA 2C 6A 04  <0x2c4e5680>
50   01/17/13 22:27:45.420   luup_log:29: decodeMessage bits:127 data:FF F0 18 FF FA 2C 6A 04 FF F0 60 FF FA 2C 6A 04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.420   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.421   luup_log:29: Unknown Msg : FF F0 18 FF FA 2C 6A 04 FF F0 60 FF FA 2C 6A 04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.422   luup_log:29: decodeMessage bits:112 data:F0 FE 00 FF FA 2C 6A 04 FF F0 78 FF FA 2C 6A  <0x2c4e5680>
50   01/17/13 22:27:45.422   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.423   luup_log:29: Unknown Msg : F0 FE 00 FF FA 2C 6A 04 FF F0 78 FF FA 2C 6A  <0x2c4e5680>
50   01/17/13 22:27:45.423   luup_log:29: decodeMessage bits:4 data:04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.423   luup_log:29: Unknown Msg : 04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.424   luup_log:29: decodeMessage bits:112 data:F0 1E FF FA 2C 6A 04 FF F0 E6 18 FF FA 2C 6A  <0x2c4e5680>
50   01/17/13 22:27:45.425   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.425   luup_log:29: Unknown Msg : F0 1E FF FA 2C 6A 04 FF F0 E6 18 FF FA 2C 6A  <0x2c4e5680>
50   01/17/13 22:27:45.426   luup_log:29: decodeMessage bits:4 data:04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.426   luup_log:29: Unknown Msg : 04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.427   luup_log:29: decodeMessage bits:112 data:F0 00 FF FA 2C 6A 04 FF F0 18 FF FA 2C 6A 04  <0x2c4e5680>
50   01/17/13 22:27:45.427   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.448   luup_log:29: Unknown Msg : F0 00 FF FA 2C 6A 04 FF F0 18 FF FA 2C 6A 04  <0x2c4e5680>
50   01/17/13 22:27:45.450   luup_log:29: decodeMessage bits:127 data:FF F0 60 FF FA 2C 6A 04 FF F0 FE 00 FF FA 2C 6A 04  <0x2c4e5680>
50   01/17/13 22:27:45.450   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.451   luup_log:29: Unknown Msg : FF F0 60 FF FA 2C 6A 04 FF F0 FE 00 FF FA 2C 6A 04  <0x2c4e5680>
50   01/17/13 22:27:45.451   luup_log:29: decodeMessage bits:127 data:FF F0 78 FF FA 2C 6A 04 FF F0 1E FF FA 2C 6A 04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.452   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.452   luup_log:29: Unknown Msg : FF F0 78 FF FA 2C 6A 04 FF F0 1E FF FA 2C 6A 04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.453   luup_log:29: decodeMessage bits:112 data:F0 E6 18 FF FA 2C 6A 04 FF F0 00 FF FA 2C 6A  <0x2c4e5680>
50   01/17/13 22:27:45.454   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.454   luup_log:29: Unknown Msg : F0 E6 18 FF FA 2C 6A 04 FF F0 00 FF FA 2C 6A  <0x2c4e5680>
50   01/17/13 22:27:45.455   luup_log:29: decodeMessage bits:4 data:04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.455   luup_log:29: Unknown Msg : 04 FF  <0x2c4e5680>
50   01/17/13 22:27:45.456   luup_log:29: decodeMessage bits:112 data:F0 18 60 FE FF FA 2C 6A 04 FF F0 00 FF FA 2C  <0x2c4e5680>
50   01/17/13 22:27:45.456   luup_log:29: decodeoregon <0x2c4e5680>
50   01/17/13 22:27:45.457   luup_log:29: Unknown Msg : F0 18 60 FE FF FA 2C 6A 04 FF F0 00 FF FA 2C  <0x2c4e5680>

Thanks in advance

Thijs

(vera 3 ui5, couple of aeonlab and fibaro switches)

Offline b_weijenberg

  • Full Member
  • ***
  • Posts: 129
  • Karma: +3/-1
Re: RFXCOM interface
« Reply #223 on: January 19, 2013, 04:07:03 am »
Thijs,

You should use Variable Lenth Mode and not 32 bits mode.
And check the baudrate.

First check with RFreceiver if you receive valid data.

Offline piperpilot

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: RFXCOM interface
« Reply #224 on: January 19, 2013, 10:45:33 am »
Hi Bart, thanks for your reply, I'll change it to variable but i'm not sure what you mean by the baudrate since it's a lan version.
With the program from rfxcom itself i seem to receive some data and it has been working well with a homeseer setup (power meter etc and oregon temp).
What it doesn't seem to do is creating new devices on its own though this is set to 1 in autocreate

Thanks

Thijs
« Last Edit: January 20, 2013, 03:05:43 am by piperpilot »