fhem stops after couple minutes

[Guest]

Originally posted by: <email address deleted>

Willi,

That works I think only get one error, I think RFXMeter something? I
get no values of my water


 Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/
fhem/FHEM/41_OREGON.pm line 99.
Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/fhem/
FHEM/41_OREGON.pm line 102.
Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/fhem/
FHEM/41_OREGON.pm line 99.
Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/fhem/
FHEM/41_OREGON.pm line 102.
Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/fhem/
FHEM/41_OREGON.pm line 99.
Use of uninitialized value $rname in string ne at /usr/share/fhem/FHEM/
93_FHEM2FHEM.pm line 152.

Internals:
   CODE       00
   DEF        00 0.5 ltr
   NAME       RFXWater
   NR         11
   STATE      
   TYPE       RFXMETER
   scalefactor 0.5
   unitname   ltr
Attributes:
   room       Meterkast

 define RFXWater RFXMETER 00 0.5 ltr




On 21 apr, 11:28, Willi wrote:
> Hello Richard,
>
> the new TRX module for RFXtrx433 transmitter (new protocol) works with
> FHEM2FHEM raw. I use it daily and without any stability problems.
>
> The old RFXCOM receiver module currently does not work with
> FHEM2FHEM:raw. Reason is that the receiver transmits binary data that can
> not be handled by FHEM2FHEM:raw. FHEM2FHEM only allows to transfer
> Ascii-Data.
>
> Fixing this is easy. I just have to convert to Ascii HEX for this as I
> already use for the TRX module.
> I will hopefully change this, test is and put this to FHEM SVN next week.
>
> After I have done the changes, do an updatefhem and you may use is as
> follows.
>
> In order to get it run, use dummy. Also you can not use the name Buitentemp
> as FHEM2FHEM definition and OREGON device. Use different names
>
> "
> define RFXCOM RFXCOM none noninit
> attr RFXCOM dummy 1
> define ds3 FHEM2FHEM 192.168.169.196:7072 RAW:RFXCOM
>
> >"
>
> If you enable autocreate you will see all devices as expected.
>
> Regards
>
> Willi
>
> Am Freitag, 20. April 2012 22:07:44 UTC+2 schrieb kroonen:
>
>
>
>
>
>
>
>
>
> > Rudolf ,
>
> > I want messages from an rfxcom device
>
> > Is it possible to recieve messages on an remote fhem, with fhem
> > without having an rfxcom reciever on the other side??
> > Should I define a rfxcom as kind of dummy? Or an the network rfxcom
> > with noinit?
>
> > I have this
>
> > define RFXCOM RFXCOM 127.0.0.1:10001 noinit
>
> > define Buitentemp FHEM2FHEM 192.168.2.5:7072 RAW:RFXCOM
>
> > define Buitentemp OREGON THGR228N_bb
>
> > still this error
>
> > Use of uninitialized value $rname in string ne at /usr/share/fhem/FHEM/
> > 93_FHEM2FHEM.pm line 153.
>
> > regards Richard

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

Hello Richard,

FHEM2FHEM:raw does not pass all binary data.

As I stated I have to change my modules for the old RFXCOM driver to pass a
hexstring instead of binary.

I did the changes some minutes ago and I am currently doing the tests.
I will send you the modules as a PM if you want to test.

Regards Willi

Am Samstag, 21. April 2012 22:19:49 UTC+2 schrieb kroonen:
>
> Willi,
>
> That works I think only get one error, I think RFXMeter something? I
> get no values of my water
>
>
>  Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/
> fhem/FHEM/41_OREGON.pm line 99.
> Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/fhem/
> FHEM/41_OREGON.pm line 102.
> Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/fhem/
> FHEM/41_OREGON.pm line 99.
> Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/fhem/
> FHEM/41_OREGON.pm line 102.
> Use of uninitialized value $_[0] in bitwise and (&) at /usr/share/fhem/
> FHEM/41_OREGON.pm line 99.
> Use of uninitialized value $rname in string ne at /usr/share/fhem/FHEM/
> 93_FHEM2FHEM.pm line 152.
>
> Internals:
>    CODE       00
>    DEF        00 0.5 ltr
>    NAME       RFXWater
>    NR         11
>    STATE      
>    TYPE       RFXMETER
>    scalefactor 0.5
>    unitname   ltr
> Attributes:
>    room       Meterkast
>
>  define RFXWater RFXMETER 00 0.5 ltr
>
>
>
>
> On 21 apr, 11:28, Willi wrote:
> > Hello Richard,
> >
> > the new TRX module for RFXtrx433 transmitter (new protocol) works with
> > FHEM2FHEM raw. I use it daily and without any stability problems.
> >
> > The old RFXCOM receiver module currently does not work with
> > FHEM2FHEM:raw. Reason is that the receiver transmits binary data that
> can
> > not be handled by FHEM2FHEM:raw. FHEM2FHEM only allows to transfer
> > Ascii-Data.
> >
> > Fixing this is easy. I just have to convert to Ascii HEX for this as I
> > already use for the TRX module.
> > I will hopefully change this, test is and put this to FHEM SVN next
> week.
> >
> > After I have done the changes, do an updatefhem and you may use is as
> > follows.
> >
> > In order to get it run, use dummy. Also you can not use the name
> Buitentemp
> > as FHEM2FHEM definition and OREGON device. Use different names
> >
> > "
> > define RFXCOM RFXCOM none noninit
> > attr RFXCOM dummy 1
> > define ds3 FHEM2FHEM 192.168.169.196:7072 RAW:RFXCOM
> >
> > >"
> >
> > If you enable autocreate you will see all devices as expected.
> >
> > Regards
> >
> > Willi
> >
> > Am Freitag, 20. April 2012 22:07:44 UTC+2 schrieb kroonen:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > > Rudolf ,
> >
> > > I want messages from an rfxcom device
> >
> > > Is it possible to recieve messages on an remote fhem, with fhem
> > > without having an rfxcom reciever on the other side??
> > > Should I define a rfxcom as kind of dummy? Or an the network rfxcom
> > > with noinit?
> >
> > > I have this
> >
> > > define RFXCOM RFXCOM 127.0.0.1:10001 noinit
> >
> > > define Buitentemp FHEM2FHEM 192.168.2.5:7072 RAW:RFXCOM
> >
> > > define Buitentemp OREGON THGR228N_bb
> >
> > > still this error
> >
> > > Use of uninitialized value $rname in string ne at
> /usr/share/fhem/FHEM/
> > > 93_FHEM2FHEM.pm line 153.
> >
> > > regards Richard

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

Changes for the RFXCOM modules to work with FHEM2FHEM has been done and
tested. RFXCOM has been also changed to use DevIO.pm.

I have checked it into FHEMs SVN some minutes ago.
You may use it tomorrow via updatefhem.

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com