FHEM Forum

FHEM => fhem-users => Thema gestartet von: Guest am 20 Mai 2012, 22:31:23

Titel: 95_FLOORPLAN reload nach jedem startfhem
Beitrag von: Guest am 20 Mai 2012, 22:31:23
Originally posted by: <email address deleted>

Hallo zusammen,

seit langer Zeit, eigentlich seitdem ich FLOORPLAN nutze, mus ich nach
jedem startfhem ein manuelles RELOAD 95_FLOORPLAN und ein REREADCFG
ausführen. Ansonsten wird das Modul nicht geladen und im Log stehen immer
Fehlermeldungen. Woran kann das liegen? Muss man eine bestimmte Reihenfolge
in der cfg-Datei einhalten?

So wird der FLOORPLAN bei mir definiert:

setdefaultattr room Server
setdefaultattr fp_stylesheetPrefix dark
setdefaultattr fp_arrange 1

define EG FLOORPLAN
define SB FLOORPLAN
define OG FLOORPLAN

attr EG fp_default 1

setdefaultattr

Das ist die Ausgabe in der Console zum Starten von FHEM:

# sh startfhem
# String found where operator expected at ./FHEM/95_FLOORPLAN.pm line 240,
near "FW_pO "\n""
Subroutine FLOORPLAN_Initialize redefined at ./FHEM/95_FLOORPLAN.pm line
122, <$fh> line 46.
Subroutine FP_define redefined at ./FHEM/95_FLOORPLAN.pm line 150, <$fh>
line 46.
String found where operator expected at ./FHEM/95_FLOORPLAN.pm line 240,
near "FW_pO "\n""
Subroutine FLOORPLAN_Initialize redefined at ./FHEM/95_FLOORPLAN.pm line
122, <$fh> line 47.
Subroutine FP_define redefined at ./FHEM/95_FLOORPLAN.pm line 150, <$fh>
line 47.
String found where operator expected at ./FHEM/95_FLOORPLAN.pm line 240,
near "FW_pO "\n""
localtime(nan) too large at ./FHEM/59_Twilight.pm line 194, <$fh> line 78.
localtime(nan) too large at ./FHEM/59_Twilight.pm line 195, <$fh> line 78.

und das kommt im Log-File:

2012.05.20 22:28:21.386 2: Telnet port 7072 opened
2012.05.20 22:28:21.585 3: Opening cul01 device /dev/ttyACM0
2012.05.20 22:28:21.948 3: Setting cul01 baudrate to 38400
2012.05.20 22:28:21.959 3: cul01 device opened
2012.05.20 22:28:22.115 1: reload: Error:Modul 95_FLOORPLAN deactivated:
Global symbol "$FW_RET" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 165, <$fh> line 36.
Global symbol "$FW_wname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 168, <$fh> line 36.
Global symbol "$FW_wname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 169, <$fh> line 36.
Global symbol "$FW_ss" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 169, <$fh> line 36.
Global symbol "$FW_tp" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 170, <$fh> line 36.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 171, <$fh> line 36.
Global symbol "$FW_RET" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 194, <$fh> line 36.
Global symbol "$FW_RET" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 195, <$fh> line 36.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 197, <$fh> line 36.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 199, <$fh> line 36.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 207, <$fh> line 36.
Global symbol "$FW_cname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 218, <$fh> line 36.
Global symbol "$FW_wname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 219, <$fh> line 36.
Global symbol "$FW_ME" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 220, <$fh> line 36.
./FHEM/95_FLOORPLAN.pm has too many errors.

2012.05.20 22:28:22.115 0: Global symbol "$FW_RET" requires explicit
package name at ./FHEM/95_FLOORPLAN.pm line 165, <$fh> line 36.
Global symbol "$FW_wname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 168, <$fh> line 36.
Global symbol "$FW_wname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 169, <$fh> line 36.
Global symbol "$FW_ss" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 169, <$fh> line 36.
Global symbol "$FW_tp" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 170, <$fh> line 36.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 171, <$fh> line 36.
Global symbol "$FW_RET" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 194, <$fh> line 36.
Global symbol "$FW_RET" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 195, <$fh> line 36.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 197, <$fh> line 36.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 199, <$fh> line 36.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 207, <$fh> line 36.
Global symbol "$FW_cname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 218, <$fh> line 36.
Global symbol "$FW_wname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 219, <$fh> line 36.
Global symbol "$FW_ME" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 220, <$fh> line 36.
./FHEM/95_FLOORPLAN.pm has too many errors.

2012.05.20 22:28:22.119 3: Please define EG first
2012.05.20 22:28:22.123 3: Please define EG first
2012.05.20 22:28:22.127 3: Please define EG first
2012.05.20 22:28:22.127 3: Please define EG first
2012.05.20 22:28:22.159 1: reload: Error:Modul 95_FLOORPLAN deactivated:
Global symbol "$FW_RET" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 165, <$fh> line 46.
Global symbol "$FW_wname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 168, <$fh> line 46.
Global symbol "$FW_wname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 169, <$fh> line 46.
Global symbol "$FW_ss" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 169, <$fh> line 46.
Global symbol "$FW_tp" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 170, <$fh> line 46.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 171, <$fh> line 46.
Global symbol "$FW_RET" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 194, <$fh> line 46.
Global symbol "$FW_RET" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 195, <$fh> line 46.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 197, <$fh> line 46.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 199, <$fh> line 46.
Global symbol "$FW_subdir" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 207, <$fh> line 46.
Global symbol "$FW_cname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 218, <$fh> line 46.
Global symbol "$FW_wname" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 219, <$fh> line 46.
Global symbol "$FW_ME" requires explicit package name at
./FHEM/95_FLOORPLAN.pm line 220, <$fh> line 46.
./FHEM/95_FLOORPLAN.pm has too many errors.

und noch einige Zeilen mehr.

Leider sagen mir diese Zeilen alle nicht wirklich etwas.

Kann da jemand Auskunft geben?

Das ganze läuft auf einer 7390 mit eigentlich aktuellstem Stand.

Gruß

Bernd

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Titel: Re: 95_FLOORPLAN reload nach jedem startfhem
Beitrag von: Guest am 20 Mai 2012, 22:40:14
Originally posted by: <email address deleted>

Am Sonntag, 20. Mai 2012 22:31:23 UTC+2 schrieb Bernd:
>
> Muss man eine bestimmte Reihenfolge in der cfg-Datei einhalten?


Hi,
ja, genau. Die Definition eines FHEMWEB-device muss in fhem.cfg *VOR* der
ersten floorplan-Definition stehen.
Beispiel:
#fhem.cfg
#Erstmal Pfadangaben, Global etc, dann zB
define WEB FHEMWEB 8083 global
# usw; erst *DANACH*
define EG FLOORPLAN # etc

Siehe floorplan.pdf Seite 19 :)

Gruß, Uli

 

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Titel: Re: 95_FLOORPLAN reload nach jedem startfhem
Beitrag von: Guest am 21 Mai 2012, 21:23:03
Originally posted by: <email address deleted>

Hallo Uli,

super, endlich entfällt dieses RELOAD :-)

Danke und Gruß

Bernd

Am Sonntag, 20. Mai 2012 22:40:14 UTC+2 schrieb UliM:
>
>
>
> Am Sonntag, 20. Mai 2012 22:31:23 UTC+2 schrieb Bernd:
>>
>> Muss man eine bestimmte Reihenfolge in der cfg-Datei einhalten?
>
>
> Hi,
> ja, genau. Die Definition eines FHEMWEB-device muss in fhem.cfg *VOR* der
> ersten floorplan-Definition stehen.
> Beispiel:
> #fhem.cfg
> #Erstmal Pfadangaben, Global etc, dann zB
> define WEB FHEMWEB 8083 global
> # usw; erst *DANACH*
> define EG FLOORPLAN # etc
>
> Siehe floorplan.pdf Seite 19 :)
>
> Gruß, Uli
>
>  
>

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