Neueste Beiträge

Seiten: [1] 2 3 ... 10
1
Sonstige Systeme / Antw:Xiaomi Smart Home Komponenten
« Letzter Beitrag von leif am Heute um 02:55:38 »
Guten Abend,

erst einmal Danke für dieses wunderbare Modul - eigentlich funktioniert alles wunderbar. Allerdings habe ich ein äußerst seltsames Problem.

Sobald ich dieses Modul installiere startet bei mir FHEM nicht mehr mit dem Raspberry Pi 3 mit - ich muss es immer manuell starten (sudo /etc/init.d/fhem start).   Was ich noch seltsamer finde ist dass es mit der gleichen SD Karte und im selben Netzwerk auf meinem Raspberry Pi Zero W weiterhin startet. Ist FHEM einmal gestartet läuft alles normal, die Sensoren werden erkannt und ich kann zuverlässig schalten.

Was kann das sein?


Der Log

2017.11.23 02:59:16 0: Server shutdown
2017.11.23 02:59:21 1: Including fhem.cfg
2017.11.23 02:59:21 3: telnetPort: port 7072 opened
2017.11.23 02:59:22 3: WEB: port 8083 opened
2017.11.23 02:59:22 3: WEBphone: port 8084 opened
2017.11.23 02:59:22 3: WEBtablet: port 8085 opened
2017.11.23 02:59:22 2: eventTypes: loaded 831 events from ./log/eventTypes.txt
2017.11.23 02:59:22 3: wz_computerlicht: I/O device is Hue
2017.11.23 02:59:22 3: fl_flurlicht: I/O device is Hue
2017.11.23 02:59:22 3: wz_sofalicht: I/O device is Hue
2017.11.23 02:59:23 3: wz_tischlicht: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup3: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup6: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup16: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup20: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup19: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup5: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup0: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup2: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup17: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup4: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup18: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup1: I/O device is Hue
2017.11.23 02:59:23 3: YeeLight bz_badlicht defined at 192.168.178.219:55443
2017.11.23 02:59:23 3: Opening bz_badlicht device 192.168.178.219:55443
2017.11.23 02:59:23 3: Can't connect to 192.168.178.219:55443: Network is unreac                                                        hable
2017.11.23 02:59:23 3: Opening bz_badlicht device 192.168.178.219:55443
2017.11.23 02:59:23 1: PERL WARNING: Use of uninitialized value $model in string                                                         eq at ./FHEM/32_YeeLight.pm line 172, <$fh> line 216.
2017.11.23 02:59:23 3: TelegramBot_Define telebot: called
2017.11.23 02:59:23 2: TelegramBot_DoUrlCommand telebot: FAILED http access retu                                                        rned error :https://api.telegram.org/botxxxxxxx382:AAGxxxxxxxxxxLaLF9ceHnJVl8CbGp                                                        LuRQA/getMe: Can't connect(1) to https://api.telegram.org:443: IO::Socket::INET:                                                         Bad hostname 'api.telegram.org:443':
2017.11.23 02:59:23 3: XiaomiFlowerSens (hawaipalme) - defined with BTMAC C4:7C:                                                        8D:65:A9:B5
2017.11.23 02:59:23 3: XiaomiFlowerSens (hawaipalme) - set interval to 900
2017.11.23 02:59:23 3: XiaomiFlowerSens (chili) - defined with BTMAC C4:7C:8D:65                                                        :CA:E2
2017.11.23 02:59:23 3: XiaomiFlowerSens (chili) - set interval to 900
2017.11.23 02:59:23 1: PERL WARNING: Prototype mismatch: sub main::round ($$) vs                                                         none at /usr/share/perl/5.24/Exporter.pm line 66, <$fh> line 313.
2017.11.23 02:59:23 1: PERL WARNING: Scalar value @arround[...] better written a                                                        s $arround[...] at ./FHEM/71_XiaomiSmartHome_Device.pm line 243, <$fh> line 317.
2017.11.23 02:59:23 1: PERL WARNING: Scalar value @arround[...] better written a                                                        s $arround[...] at ./FHEM/71_XiaomiSmartHome_Device.pm line 250, <$fh> line 317.
2017.11.23 02:59:23 1: Including ./log/fhem.save
2017.11.23 02:59:23 2: HUEBridge_OpenDev: error reading description: http://192.                                                        168.178.100/description.xml: Can't connect(1) to http://192.168.178.100:80: IO::                                                        Socket::INET: connect: Network is unreachable
2017.11.23 02:59:23 2: Hue: empty answer received for http://192.168.178.100/api                                                        /QSDnRzE1k7cTuA4NcgVMNxxx5RhuSykuAzqlfuj-/config
2017.11.23 02:59:23 2: HUEBridge_OpenDev: got empty config
2017.11.23 02:59:23 3: telnetForBlockingFn_1511402363: port 45701 opened
2017.11.23 02:59:23 1: usb create starting
2017.11.23 02:59:23 3: Probing CUL device /dev/ttyAMA0
2017.11.23 02:59:24 3: Probing TCM_ESP3 device /dev/ttyAMA0
2017.11.23 02:59:24 3: Probing ZWDongle device /dev/ttyAMA0
2017.11.23 02:59:24 3: Probing FRM device /dev/ttyAMA0
2017.11.23 02:59:29 1: usb create end
2017.11.23 02:59:29 0: Featurelevel: 5.8
2017.11.23 02:59:29 0: Server started with 58 defined entities (fhem.pl:15466/20                                                        17-11-20 perl:5.024001 os:linux user:fhem pid:431)
2017.11.23 02:59:29 3: Opening bz_badlicht device 192.168.178.219:55443
2017.11.23 02:59:30 3: ABFALL Muelltonnen - CALENDAR:Muelltonnen_Kalender trigge                                                        red, updating ABFALL Muelltonnen ...
Creating socket: Invalid argument
Set scan parameters failed: Input/output error

Die "Socket" Fehler erscheinen wenn ich FHEM dann nochmal manuell starte, die Karte im PI Zero habe oder dieses Modul nicht in Verwendung habe nicht.
2
TabletUI / Switch schaltet nicht zurück
« Letzter Beitrag von Gunther am Heute um 02:03:25 »
Mein Switch schaltet nicht vom Zustand "2" auf den Zustand "1".
Wenn er auf "2" steht schaltet er
set <device> 2statt
set <device> 2
Das ist mein Code:
    <div data-type="switch"
data-device="haus_Status"
data-set-on="1"
data-set-off="2"
data-states='["1","2"]'
data-icons='["fa-angellist", "fa-bed"]'
data-colors='["white", "white"]'
data-background-colors='["green", "red"]'
class="big top-space">
</div>

Habe ich einen Denkfehler?
3
ESP8266 / Sonoff S20 - wifi Steckdosen
« Letzter Beitrag von AitschPi am Heute um 01:42:35 »
(https://uploads.tapatalk-cdn.com/20171123/515f00432d4c65a5d9008c76c968eb58.jpg)
Kennt jemand diese Dosen? Die wurden als „S20“ verkauft und laufen mit der App für die anderen sonoff- nur leider finde ich keine Anschlüsse, mit denen ich die Firmware flashen kann.


Gesendet von iPhone mit Tapatalk Pro
4
Nabend,

ich stehe gerade vor einem kuriosen Problem. Bis heute lief mein FHEM im Pi3 ziemlich reibungslos und der Autostart machte keinerlei Probleme. Doch nun tauchen nach dem Neustart des Pi3 in den FHEM Logs immer derlei Einträge auf

2017.11.23 02:59:16 0: Server shutdown
2017.11.23 02:59:21 1: Including fhem.cfg
2017.11.23 02:59:21 3: telnetPort: port 7072 opened
2017.11.23 02:59:22 3: WEB: port 8083 opened
2017.11.23 02:59:22 3: WEBphone: port 8084 opened
2017.11.23 02:59:22 3: WEBtablet: port 8085 opened
2017.11.23 02:59:22 2: eventTypes: loaded 831 events from ./log/eventTypes.txt
2017.11.23 02:59:22 3: wz_computerlicht: I/O device is Hue
2017.11.23 02:59:22 3: fl_flurlicht: I/O device is Hue
2017.11.23 02:59:22 3: wz_sofalicht: I/O device is Hue
2017.11.23 02:59:23 3: wz_tischlicht: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup3: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup6: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup16: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup20: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup19: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup5: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup0: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup2: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup17: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup4: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup18: I/O device is Hue
2017.11.23 02:59:23 3: HUEGroup1: I/O device is Hue
2017.11.23 02:59:23 3: YeeLight bz_badlicht defined at 192.168.178.219:55443
2017.11.23 02:59:23 3: Opening bz_badlicht device 192.168.178.219:55443
2017.11.23 02:59:23 3: Can't connect to 192.168.178.219:55443: Network is unreac                                                        hable
2017.11.23 02:59:23 3: Opening bz_badlicht device 192.168.178.219:55443
2017.11.23 02:59:23 1: PERL WARNING: Use of uninitialized value $model in string                                                         eq at ./FHEM/32_YeeLight.pm line 172, <$fh> line 216.
2017.11.23 02:59:23 3: TelegramBot_Define telebot: called
2017.11.23 02:59:23 2: TelegramBot_DoUrlCommand telebot: FAILED http access retu                                                        rned error :https://api.telegram.org/botxxxxxxx382:AAGxxxxxxxxxxLaLF9ceHnJVl8CbGp                                                        LuRQA/getMe: Can't connect(1) to https://api.telegram.org:443: IO::Socket::INET:                                                         Bad hostname 'api.telegram.org:443':
2017.11.23 02:59:23 3: XiaomiFlowerSens (hawaipalme) - defined with BTMAC C4:7C:                                                        8D:65:A9:B5
2017.11.23 02:59:23 3: XiaomiFlowerSens (hawaipalme) - set interval to 900
2017.11.23 02:59:23 3: XiaomiFlowerSens (chili) - defined with BTMAC C4:7C:8D:65                                                        :CA:E2
2017.11.23 02:59:23 3: XiaomiFlowerSens (chili) - set interval to 900
2017.11.23 02:59:23 1: PERL WARNING: Prototype mismatch: sub main::round ($$) vs                                                         none at /usr/share/perl/5.24/Exporter.pm line 66, <$fh> line 313.
2017.11.23 02:59:23 1: PERL WARNING: Scalar value @arround[...] better written a                                                        s $arround[...] at ./FHEM/71_XiaomiSmartHome_Device.pm line 243, <$fh> line 317.
2017.11.23 02:59:23 1: PERL WARNING: Scalar value @arround[...] better written a                                                        s $arround[...] at ./FHEM/71_XiaomiSmartHome_Device.pm line 250, <$fh> line 317.
2017.11.23 02:59:23 1: Including ./log/fhem.save
2017.11.23 02:59:23 2: HUEBridge_OpenDev: error reading description: http://192.                                                        168.178.100/description.xml: Can't connect(1) to http://192.168.178.100:80: IO::                                                        Socket::INET: connect: Network is unreachable
2017.11.23 02:59:23 2: Hue: empty answer received for http://192.168.178.100/api                                                        /QSDnRzE1k7cTuA4NcgVMNxxx5RhuSykuAzqlfuj-/config
2017.11.23 02:59:23 2: HUEBridge_OpenDev: got empty config
2017.11.23 02:59:23 3: telnetForBlockingFn_1511402363: port 45701 opened
2017.11.23 02:59:23 1: usb create starting
2017.11.23 02:59:23 3: Probing CUL device /dev/ttyAMA0
2017.11.23 02:59:24 3: Probing TCM_ESP3 device /dev/ttyAMA0
2017.11.23 02:59:24 3: Probing ZWDongle device /dev/ttyAMA0
2017.11.23 02:59:24 3: Probing FRM device /dev/ttyAMA0
2017.11.23 02:59:29 1: usb create end
2017.11.23 02:59:29 0: Featurelevel: 5.8
2017.11.23 02:59:29 0: Server started with 58 defined entities (fhem.pl:15466/20                                                        17-11-20 perl:5.024001 os:linux user:fhem pid:431)
2017.11.23 02:59:29 3: Opening bz_badlicht device 192.168.178.219:55443
2017.11.23 02:59:30 3: ABFALL Muelltonnen - CALENDAR:Muelltonnen_Kalender trigge                                                        red, updating ABFALL Muelltonnen ...
Creating socket: Invalid argument
Set scan parameters failed: Input/output error

und der Service startet nicht richtig.

Also dachte ich erst ich hätte mir irgendwas in der Netzwerk Konfiguration zerschossen, doch wenn ich FHEM dann anschließend via sudo /etc/init.d/fhem/ start manuell starte läuft alles einwandfrei.

So richtig kurios wurde es dann als ich die SD Karte aus meinem PI 3 in meinen Pi Zero W steckte - dort läuft der Autostart einwandfrei.

Was kann das sein? Nachdem ich nun auch noch andere Netzteile ausprobiert habe (der Zero W ist da ja genügsamer als der Pi3) und dies auch nichts brachte bin ich nun total ratlos.
5
Bastelecke / Antw:Funksensor mit Bosch sensortec BME680 / Luftgüte
« Letzter Beitrag von hdgucken am Heute um 00:57:22 »
Na klar  ;)
Der Aufbau ist so:

OK CC  ID  T1 T2  HH  P1 P2  I1 I2  L1 L2  UB  G1 G2 G3 CRC     

100er + 10er bedeutet linkes Nibble 100er, rechtes Nibble 10er usw. !

OK CC - fest für CustomSensor Protokoll
ID - Sensor ID (0-FF)
T1 - (Temp + 40 * 10): 100er
T2 - (Temp + 40 * 10): 10er + 1er
HH - humidity 1-99
P1 - pressure = 1000er + 100er                                   
P2 - pressure = 10er + 1er
I1 - IAQ = MSB,100er
I2 - IAQ = LSB, Wert unter 100
L1 - LightLevel = 1000er + 100er
L2 - LightLevel = 10er + 1er
UB - BatteryVoltage * 10 = (0-255; 3,3V = 33)
G1 - gas resistance = 100.000er + 10.000er
G2 - gas resistance = 1.000er + 100er
G3 - gas resistance = 10er + 1er
CRC - crc byte

IAQ muss ich evtl. noch auf 100er, 10er und 1er Stelle ändern.

Gruß Thomas
6
Ach nochmal gefragt: Dem Preis nach zu urteilen handelt es sich bei dem Girateil nur um den gedruckten Rahmen, ohne Elektronik, gel?
(da würde ich dann evtl. noch einen dazunehmen).
7
Anfängerfragen / Antw:Dummy: Reihenfolge von Werten einer setlist
« Letzter Beitrag von Gunther am Heute um 00:41:36 »
kann ich 015 nehmen um damit woanders zu rechnen?
Also als 15 Minuten und in einem
wait [meindummy]*60
8
Anfängerfragen / Antw:Dummy: Reihenfolge von Werten einer setlist
« Letzter Beitrag von CoolTux am Heute um 00:34:45 »
Das geht leider nicht. FHEMWEB sortiert von sich aus.
9
Was steht denn im fhem log?

Meist steht dort der Grund, evtl. fehlt eine perl-lib/modul...

EDIT: lib etc. scheidet wohl aus. Hab eben die neue Version (grad erst entdeckt) aus github geladen bzw. versucht, klappt nicht... Hier mal ein paar Logeinträge:

Too many arguments for main::TVSender_Change_HTTPMOD_Device_userattr at ./FHEM/98_TVSender.pm line 180, near "'')"
Too many arguments for main::TVSender_Change_HTTPMOD_Device_userattr at ./FHEM/98_TVSender.pm line 181, near "'')"
Too many arguments for main::TVSender_Change_HTTPMOD_Device_userattr at ./FHEM/98_TVSender.pm line 182, near "'')"
Too many arguments for main::TVSender_Change_HTTPMOD_Device_userattr at ./FHEM/98_TVSender.pm line 183, near "'')"
syntax error at ./FHEM/98_TVSender.pm line 735, near """:"
syntax error at ./FHEM/98_TVSender.pm line 739, near "}"
Global symbol "$value" requires explicit package name (did you forget to declare "my $value"?) at ./FHEM/98_TVSender.pm line 742.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 743.
Global symbol "$name" requires explicit package name (did you forget to declare "my $name"?) at ./FHEM/98_TVSender.pm line 743.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 744.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 745.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 745.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 746.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 746.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 747.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 747.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 749.
Global symbol "$name" requires explicit package name (did you forget to declare "my $name"?) at ./FHEM/98_TVSender.pm line 749.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 750.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 751.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 751.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 752.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 752.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 753.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 753.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 755.
Global symbol "$name" requires explicit package name (did you forget to declare "my $name"?) at ./FHEM/98_TVSender.pm line 755.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 756.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 757.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 757.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 758.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 758.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 759.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 759.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 761.
Global symbol "$name" requires explicit package name (did you forget to declare "my $name"?) at ./FHEM/98_TVSender.pm line 761.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 762.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 763.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 763.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 764.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 764.
Global symbol "$hash" requires explicit package name (did you forget to declare "my $hash"?) at ./FHEM/98_TVSender.pm line 765.
Global symbol "$httpmoddevice" requires explicit package name (did you forget to declare "my $httpmoddevice"?) at ./FHEM/98_TVSender.pm line 765.
syntax error at ./FHEM/98_TVSender.pm line 766, near "}"
./FHEM/98_TVSender.pm has too many errors.

Ich spiele mal wieder die "alte" Version ein...

EDIT2: gut doch noch nicht eingespielt die "alte" Version... ;)  Ich hab es zwar jetzt hinbekommen, dass das Modul geladen werden kann (waren einige "Verschreibsler" drin und irgendwie stimmt das mit den Argumenten ;) ). Aber die Logik passt in dem was ich zusammengebastelt hab nicht. Es wird zwar was erzeugt aber so richtig sieht das dann nicht aus...

Gruß, Joachim
10
Anfängerfragen / Antw:IP Sinocam Überwachungskamera Live Bilder in FHEM
« Letzter Beitrag von stefanru am Heute um 00:20:38 »
Hi Mario,

was mir auffällt sind die 3 Zeilen mit Permission denied.
Z.B.:
2017-11-19 14:43:28,749 raspberrypi proftpd[813]: unable to bind to Unix domain socket at '/run/test.sock': Permission denied

Startest du ihn mit dem falschen user?

Gruß,
Stefan
Seiten: [1] 2 3 ... 10