Originally posted by: <email address deleted>
Hi,
I'm using rfxcom receiver, and see the support for oregon is just
started.
I want also to add rfxmeter to it. I'm not well in programming but I
can do tests with it.
the xpl-perl form beanz has support for it, but I have no idea how it
can be ported.
I know Wili did rfxcom with oregon, maybe he can port it so I can test
it???
regards Richard
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.
Originally posted by: <email address deleted>
> I know Wili did rfxcom with oregon, maybe he can port it so I can test
> it???
Hi Richard,
I have just looked into beanz code that supports rfxmeter (xpl-perl/
lib/xPL/RF/RFXMeter.pm).
What xpl-perl parses and returns seem to be the cumulated kwh of the
device:
return [xPL::Message->new(
message_type => 'xpl-trig',
class => 'sensor.basic',
head => { source => $parent->source, },
body => {
device => 'rfxmeter.'.$device,
type => 'energy',
current => $kwh,
}
)];
Is it this sufficient for you? Do you just need the kwh values?
To add this to my code and add an rfxmeter module should be no big
task.
Before I code rfxmeter support I would like to ask you to install FHEM
5.0, attach RFXCOM to this host and configure RFXCOM as descibed in
commandref.
After this please issue to increase verbosity in FHEM
attr global verbose 4
You should see messages in the FHEM logfile (probably /var/log/fhem/
fhem-2010-12.log) like the following
2010.12.02 20:56:37 4: OREGON: ERROR: Unknown sensor_id=b2a3 bits=56
message='38b2a30100000000'.
After some minutes you may decrease verbose again .
Please mail these messages to me. The hexcodes in message= will show
me your rfxmeter codes.
Please note that I probably will not have time to code the new
rfxmeter module within the next three weeks due to other ongoing
tasks. Hopefully I will have some time for coding between Xmas and new
year.
Regards Willi
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.
Originally posted by: <email address deleted>
On Dec 2, 9:14 pm, Willi wrote:
> > I know Wili did rfxcom with oregon, maybe he can port it so I can test
> > it???
>
> Hi Richard,
>
> I have just looked into beanz code that supports rfxmeter (xpl-perl/
> lib/xPL/RF/RFXMeter.pm).
> What xpl-perl parses and returns seem to be the cumulated kwh of the
> device:
>
> return [xPL::Message->new(
> message_type => 'xpl-trig',
> class => 'sensor.basic',
> head => { source => $parent->source, },
> body => {
> device => 'rfxmeter.'.$device,
> type => 'energy',
> current => $kwh,
> }
> )];
>
> Is it this sufficient for you? Do you just need the kwh values?
It should recieve 3 values, power gas and water
In heyu logfile i get these values
03-12 18:46:06 rcva func rfxWater : hu L1 Meter 202897 ltr
(Water)
03-12 18:46:06 rcva func rfxPower : hu L2 Meter 7433.532 kWh
(Power)
03-12 18:46:07 rcva func rfxGas : hu L3 Meter 1769.82 cu_m
(GAS)
>
> To add this to my code and add an rfxmeter module should be no big
> task.
>
> Before I code rfxmeter support I would like to ask you to install FHEM
> 5.0, attach RFXCOM to this host and configure RFXCOM as descibed in
> commandref.
>
> After this please issue to increase verbosity in FHEM
>
> attr global verbose 4
>
> You should see messages in the FHEM logfile (probably /var/log/fhem/
> fhem-2010-12.log) like the following
>
> 2010.12.02 20:56:37 4: OREGON: ERROR: Unknown sensor_id=b2a3 bits=56
> message='38b2a30100000000'.
>
> After some minutes you may decrease verbose again .
>
> Please mail these messages to me. The hexcodes in message= will show
> me your rfxmeter codes.
>
I will send you them
> Please note that I probably will not have time to code the new
> rfxmeter module within the next three weeks due to other ongoing
> tasks. Hopefully I will have some time for coding between Xmas and new
> year.
>
No problem
> Regards Willi
regards Richard
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.
Originally posted by: <email address deleted>
Hi Willi,
Sorry for the late raction, but when I put the rfxcom on my usb and
start it I get get very much errors in fhem.log
When I go back to heyu, it works fine. Any idea what went wrong?
2010.12.30 13:16:23 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
2010.12.30 13:16:24 0: Strange call for nonexistent RFXCOMUSB: ReadFn
On Dec 3, 6:46 pm, kroon040 wrote:
> On Dec 2, 9:14 pm, Willi wrote:
>
>
>
>
>
>
>
>
>
> > > I know Wili did rfxcom with oregon, maybe he can port it so I can test
> > > it???
>
> > Hi Richard,
>
> > I have just looked into beanz code that supportsrfxmeter(xpl-perl/
> > lib/xPL/RF/RFXMeter.pm).
> > What xpl-perl parses and returns seem to be the cumulated kwh of the
> > device:
>
> > return [xPL::Message->new(
> > message_type => 'xpl-trig',
> > class => 'sensor.basic',
> > head => { source => $parent->source, },
> > body => {
> > device => 'rfxmeter.'.$device,
> > type => 'energy',
> > current => $kwh,
> > }
> > )];
>
> > Is it this sufficient for you? Do you just need the kwh values?
>
> It should recieve 3 values, power gas and water
>
> In heyu logfile i get these values
>
> 03-12 18:46:06 rcva func rfxWater : hu L1 Meter 202897 ltr
> (Water)
> 03-12 18:46:06 rcva func rfxPower : hu L2 Meter 7433.532 kWh
> (Power)
> 03-12 18:46:07 rcva func rfxGas : hu L3 Meter 1769.82 cu_m
> (GAS)
>
>
>
>
>
>
>
>
>
>
>
> > To add this to my code and add anrfxmetermodule should be no big
> > task.
>
> > Before I coderfxmetersupport I would like to ask you to install FHEM
> > 5.0, attach RFXCOM to this host and configure RFXCOM as descibed in
> > commandref.
>
> > After this please issue to increase verbosity in FHEM
>
> > attr global verbose 4
>
> > You should see messages in the FHEM logfile (probably /var/log/fhem/
> > fhem-2010-12.log) like the following
>
> > 2010.12.02 20:56:37 4: OREGON: ERROR: Unknown sensor_id=b2a3 bits=56
> > message='38b2a30100000000'.
>
> > After some minutes you may decrease verbose again .
>
> > Please mail these messages to me. The hexcodes in message= will show
> > me yourrfxmetercodes.
>
> I will send you them
>
> > Please note that I probably will not have time to code the new
> >rfxmetermodule within the next three weeks due to other ongoing
> > tasks. Hopefully I will have some time for coding between Xmas and new
> > year.
>
> No problem
>
> > Regards Willi
>
> regards Richard
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.
Originally posted by: <email address deleted>
On 30 Dez., 13:20, kroon040 wrote:
> 2010.12.30 13:16:23 0: Strange call for nonexistent RFXCOMUSB: ReadFn
Are there any initialization messages in the log like the following?
2010.12.09 19:06:33 3: RFXCOM opening RFXCOM device /dev/rfxcom
2010.12.09 19:06:33 1: RFXCOM: RFXCOM_OpenDev /dev/rfxcom done
2010.12.09 19:06:33 3: RFXCOM: device opened
2010.12.09 19:06:34 1: RFXCOM: Init OK
If not are you sure that you have defined the correct Device in
fhem.cfg?
define RFXCOM RFXCOM /dev/USB_DEVICENAME_OF_YOUR_RFXCOM
How does your define look like? Normally it should be /dev/ttyUSBX
where X is a number.
Use dmesg to find out what the device name is.
You could also try to unplug the USB device and attach it again.
FHEM should detect this:
2010.12.30 18:08:31 1: RFXCOM: /dev/rfxcom disconnected, waiting to
reappear
2010.12.30 18:08:41 1: RFXCOM: RFXCOM_OpenDev /dev/rfxcom done
2010.12.30 18:08:41 1: RFXCOM: /dev/rfxcom reappeared (RFXCOM)
2010.12.30 18:08:42 1: RFXCOM: Init OK
Regards Willi
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.
Originally posted by: <email address deleted>
Willi,
I had define rfxcomusb rfxcom in fhem.cfg , after replacing rfxcomusb
with rfxcom it worked.
Here some unknown sensor id, i hope these are from the rfxmeter
OREGON: ERROR: Unknown sensor_id=ea4c bits=76
message='4cea4c4083241590a30e20'.
OREGON: ERROR: Unknown sensor_id=ea4c bits=72
message='48ea4c4083241590a30e'
OREGON: ERROR: Unknown sensor_id=ea4c bits=76
message='4cea4c4083241590a30e10'.
If you need more let me know
regards Richard
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.
Originally posted by: <email address deleted>
On 31 Dez., 08:44, kroon040 wrote:
> OREGON: ERROR: Unknown sensor_id=ea4c bits=76
> message='4cea4c4083241590a30e20'.
> OREGON: ERROR: Unknown sensor_id=ea4c bits=72
> message='48ea4c4083241590a30e'
> OREGON: ERROR: Unknown sensor_id=ea4c bits=76
> message='4cea4c4083241590a30e10'.
>
> If you need more let me know
>
> regards Richard
Unfortunately these messages are from a temperature device (probably a
THN132N) and not of RFXmeter.
I have looked into xPL-perl. RFXmeter messages will have a length of
48 bits (bits=48").
As 40_RFXCOM.pm currently only parses messages for devices with bits
>=68 (Oregon devices), you need to change line 281 from
RFXCOM_Parse($hash, $hash, $name, $rmsg) if($rmsg && $bits >= 68);
to
RFXCOM_Parse($hash, $hash, $name, $rmsg);
Please change this, attach RFXCOM to your FHEM server and start it
again.
I need messages like the following:
OREGON: ERROR: Unknown sensor_id=.... bits=48 message='....'
Also please tell me what heyu logs on the RFXmeter values at nearly
the same time.
Regards Willi
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.
Originally posted by: <email address deleted>
For the RFXCOM CVS users of FHEM:
I wrote a new RFXCOM module named 42_RFXMETER.pm that handles RFXMeter
devices. It is used by 40_RFXCOM.pm.
Thanks to Richard for his help and his sample data.
After appropriate tests I have added this to the FHEM CVS.
41_OREGON.pm (the module to parse Oregon sensors) was enhanced to
support Oregon UV devices (UVN138, UVN800).
40_RFXCOM.pm has been enhanced with a new option "noinit" which skips
initialization of the RFXCOM device. This is useful if you share a
RFXCOM device via TCP by multiple instances. It is also userful if you
want to simulate an RFXCOM device for tests (using netcat). This way I
can test the modules without having the appropriate devices myself.
Feedback is welcome.
@Rudolf: Is it ok to change commandref.html to reflect these changes?
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.
> @Rudolf: Is it ok to change commandref.html to reflect these changes?
Of course, it is even mandatory :)
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.
Originally posted by: <email address deleted>
Here somescreenshots , and how it looks like
http://www.domoticaforum.eu/viewtopic.php?f=66&t=5882
regards Richard
--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.