Originally posted by: <email address deleted>
Hi,
After a couple minutes, my fhem crashes. I dit an updatefhem today and
after that it is not stable.
I recieve this error
Can't use string ("fake") as a HASH ref while "strict refs" in use at /
usr/bin/fhem.pl line 2210.
and fhem is stopped
logging doesn't say anything
2012.04.20 15:25:41 3: FHEM2FHEM opening Schuurtemp at
192.168.2.150:7072
2012.04.20 15:25:41 3: FHEM2FHEM device opened (Schuurtemp)
2012.04.20 15:25:41 3: RFXCOM opening RFXCOM device /dev/rfxcom
2012.04.20 15:25:41 1: RFXCOM: RFXCOM_OpenDev /dev/rfxcom done
2012.04.20 15:25:41 3: RFXCOM: device opened
2012.04.20 15:25:42 1: RFXCOM: Init OK
2012.04.20 15:25:42 2: FHEMWEB port 8083 opened
2012.04.20 15:25:42 2: FHEMWEB port 8084 opened
2012.04.20 15:25:42 2: FHEMWEB port 8085 opened
2012.04.20 15:25:43 0: Server started (version 5.2+SVN from 2012-04-18
($Id: fhem.pl 1462 2012-04-17 11:10:32Z rudolfkoenig $), pid 9798)
regards Richard
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
> I recieve this error
As you know, the info supplied is not enough to reproduce the problem, so all
we can do now is to feel sorry for you...
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Same Problem here,
coming back after a week of vacation - fhem was running perfect....
i have not done any changes -
just updated fhem this afternoon with updatefhem...
SAME MESSAGE:
Use of implicit split to @_ is deprecated at /opt/lib/FHEM/95_FLOORPLAN.pm
line 411, <$fh> line 463.
*Can't use string ("fake") as a HASH ref while "strict refs" in use at
/opt/bin/fhem.pl line 2210.*
... and fhem terminates after the second message..., approx 15 seconds
after starting. - even when not doing any access thru WEB or Telnet.
i suspect something wrong with floorplan, but i did not get thru....
Log verbose 5 dos not show anything unusual, i post here just the last few
lines....
2012.04.20 17:55:10 5: Executing INSERT INTO current(TIMESTAMP, DEVICE,
TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2012-04-20 17:55:10',
'Wohnzimmer_Thermostat', 'FHT', 'actuator: 0%', 'actuator', '0', '%')
2012.04.20 17:55:10 5: Wohnzimmer_Thermostat trigger: Checking
FileLog_AussenTempHum for notify
.
.
.
2012.04.20 17:55:15 5: FHEM2FHEM/RAW: /dummy WLANstatus ErwinatHome 0
2012.04.20 17:55:15 4: FB_FHEM: dummy WLANstatus ErwinatHome 0
the last line obviously causes fhem to crash.
thanks for yr. support.
Am Freitag, 20. April 2012 16:08:36 UTC+2 schrieb Rudolf Koenig:
>
> > I recieve this error
>
> As you know, the info supplied is not enough to reproduce the problem, so
> all
> we can do now is to feel sorry for you...
>
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
Am Freitag, 20. April 2012 18:18:31 UTC+2 schrieb Erwin:
>
> i suspect something wrong with floorplan, but i did not get thru....
>
> Don't think so. Line 411 is a regular split, nothing special about it:
my $cols = ($cmdlist ? (split(":", $cmdlist)) : 0);
Especially, this line hasn't changed.
Maybe there is the same root cause for this effect?
https://groups.google.com/d/msg/fhem-users/UY3DgEl4D6I/E5EryqAFNnAJ
Cheers, Uli
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Sorry Uli,
stimmt es liegt nicht an Floorplan,
hab jetzt mittlerweile "verdächtige Module" aus meiner Konfig entfernt,
... eins nach dem anderen, also nach der Ausschluß-Methode.....
schaut für mich so aus, als ob FHEM2FHEM der Bösewicht ist....
.... damit kann ich eine Zeitlang leben, das ist nicht soo dringend,
Hauptsache FHEM läuft wieder....
Am Freitag, 20. April 2012 18:26:59 UTC+2 schrieb UliM:
>
>
>
> Am Freitag, 20. April 2012 18:18:31 UTC+2 schrieb Erwin:
>>
>> i suspect something wrong with floorplan, but i did not get thru....
>>
>> Don't think so. Line 411 is a regular split, nothing special about it:
> my $cols = ($cmdlist ? (split(":", $cmdlist)) : 0);
> Especially, this line hasn't changed.
>
> Maybe there is the same root cause for this effect?
> https://groups.google.com/d/msg/fhem-users/UY3DgEl4D6I/E5EryqAFNnAJ
>
> Cheers, Uli
>
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
> schaut für mich so aus, als ob FHEM2FHEM der Bösewicht ist....
Welche Version haben die jeweiligen Installationen?
Kannst Du mir die beiden fhem.cfg Dateien perl PM zuschicken?
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
...email ist unterwegs...
danke
erwin
Am Freitag, 20. April 2012 19:38:26 UTC+2 schrieb Rudolf Koenig:
>
> > schaut f�r mich so aus, als ob FHEM2FHEM der B�sewicht ist....
>
> Welche Version haben die jeweiligen Installationen?
> Kannst Du mir die beiden fhem.cfg Dateien perl PM zuschicken?
>
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
Rudolf,
It looks like when I try to use fhem2fhem, the errors happens
when I do
define Buitentemp FHEM2FHEM 192.168.2.5:7072 LOG:.*
I get this error
Can't use string ("fake") as a HASH ref while "strict refs" in use at /
usr/bin/fhem.pl line 2210.
when I do
define Buitentemp FHEM2FHEM 192.168.2.5:7072 RAW:CUL
I get
telUse of uninitialized value $rname in string ne at /usr/share/fhem/
FHEM/93_FHEM2FHEM.pm line 153.
Use of uninitialized value $rname in string ne at /usr/share/fhem/FHEM/
93_FHEM2FHEM.pm line 153.
neUse of uninitialized value $rname in string ne at /usr/share/fhem/
FHEM/93_FHEM2FHEM.pm line 153.
Use of uninitialized value $rname in string ne at /usr/share/fhem/FHEM/
93_FHEM2FHEM.pm line 153.
Use of uninitialized
regards RIchard
On 20 apr, 16:08, Rudolf Koenig wrote:
> > I recieve this error
>
> As you know, the info supplied is not enough to reproduce the problem, so all
> we can do now is to feel sorry for you...
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
> *Can't use string ("fake") as a HASH ref while "strict refs" in use at
> /opt/bin/fhem.pl line 2210.*
Occured if a LOG type FHEM2FHEM device received a message, and it was caused by
the recent STATE -> state change. It was buggy before the change too, but due
to the wrong spelling nobody noticed it :)
I fixed it, tested it, and put it into to the SVN. Available via updatefhem
tomomorrow, as usual.
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
> define Buitentemp FHEM2FHEM 192.168.2.5:7072 LOG:.*
This should be fixed.
> define Buitentemp FHEM2FHEM 192.168.2.5:7072 RAW:CUL
You have to define the CUL on both instances (possibly with device none on the
receiver), although the define should check for this problem.
I've get no errors right now with my FHEM2FHEM RAW setup here, so I wonder what
went wrong there.
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
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
On 20 apr, 21:21, Rudolf Koenig wrote:
> > define Buitentemp FHEM2FHEM 192.168.2.5:7072 LOG:.*
>
> This should be fixed.
>
> > define Buitentemp FHEM2FHEM 192.168.2.5:7072 RAW:CUL
>
> You have to define the CUL on both instances (possibly with device none on the
> receiver), although the define should check for this problem.
>
> I've get no errors right now with my FHEM2FHEM RAW setup here, so I wonder what
> went wrong there.
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
Sorry, found a little bit but still errors. I defined this
define RFXCOM RFXCOM none
define Buitentemp FHEM2FHEM 192.168.2.5:7072 RAW:RFXCOM
define Buitentemp OREGON THGR228N_bb
I get many new devices in the log
2012.04.20 22:34:52 3: RFXCOM: Unknown OREGON device detected, define
one to get detailed information.
2012.04.20 22:34:55 3: RFXCOM: Unknown OREGON device detected, define
one to get detailed information.
2012.04.20 22:34:56 3: RFXCOM: Unknown OREGON device detected, define
one to get detailed information.
2012.04.20 22:34:56 3: RFXCOM: Unknown OREGON device detected, define
one to get detailed information.
2012.04.20 22:34:56 3: RFXCOM: Unknown OREGON device detected, define
one to get detailed information.
2012.04.20 22:34:56 3: RFXCOM: Unknown OREGON device detected, define
one to get detailed information.
2012.04.20 22:34:56 3: RFXCOM: Unknown OREGON device detected, define
one to get detailed information.
2012.04.20 22:34:57 3: RFXCOM: Unknown OREGON device detected, define
one to get detailed information.
2012.04.20 22:34:58 3: RFXCOM: Unknown OREGON device detected, define
one to get detailed information.
I don't get temperatur ehumidity readings, as on the local fhem?
fhem> l Buitentemp
Internals:
Clients :RFXMETER:OREGON:RFXX10REC:RFXELSE:
DEF 192.168.2.5:7072 RAW:RFXCOM
FD 9
Host 192.168.2.5:7072
NAME Buitentemp
NR 8
PARTIAL
STATE connected
TYPE FHEM2FHEM
informType RAW
rawDevice RFXCOM
Attributes:
Local fhem with real rfxcom
fhem> l Buitentemp
Internals:
CODE THGR228N_bb
DEF THGR228N_bb
IODev RFXCOM
NAME Buitentemp
NR 51
STATE T: 7.7 H: 65
TIME 2012-04-20 22:37:39
TYPE OREGON
CHANGETIME:
Readings:
2012-04-20 22:37:39 battery 10
2012-04-20 22:37:39 humidity 65
2012-04-20 22:37:39 temperature 7.7
On 20 apr, 22:07, kroonen wrote:
> 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
>
> On 20 apr, 21:21, Rudolf Koenig wrote:
>
>
>
>
>
>
>
> > > define Buitentemp FHEM2FHEM 192.168.2.5:7072 LOG:.*
>
> > This should be fixed.
>
> > > define Buitentemp FHEM2FHEM 192.168.2.5:7072 RAW:CUL
>
> > You have to define the CUL on both instances (possibly with device none on the
> > receiver), although the define should check for this problem.
>
> > I've get no errors right now with my FHEM2FHEM RAW setup here, so I wonder what
> > went wrong there.
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
> Is it possible to recieve messages on an remote fhem, with fhem
> without having an rfxcom reciever on the other side??
I'm afraid you have to ask the RFXCOM author about this.
In general it is like documented in commandref.html:
- you can use FHEM2FHEM in LOG mode with each device
- using it in RAW mode is supported right now with the 2-tier modules only, as
some logic is handled by the Dispatch function.
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Hi Rudi,
i can confirm that FHEM2FHEM is working after applying the fix.
Thx. again for yr. support.
erwin
Am Freitag, 20. April 2012 21:21:14 UTC+2 schrieb Rudolf Koenig:
>
> > define Buitentemp FHEM2FHEM 192.168.2.5:7072 LOG:.*
>
> This should be fixed.
>
> > define Buitentemp FHEM2FHEM 192.168.2.5:7072 RAW:CUL
>
> You have to define the CUL on both instances (possibly with device none on
> the
> receiver), although the define should check for this problem.
>
> I've get no errors right now with my FHEM2FHEM RAW setup here, so I wonder
> what
> went wrong there.
>
>
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
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
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
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
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