Shelly2 IP Schaltaktor

Begonnen von Prof. Dr. Peter Henning, 08 September 2018, 16:31:30

Vorheriges Thema - Nächstes Thema

Prof. Dr. Peter Henning

Bitte etwas mehr Informationen, sonst gibt es keinen Support.

Log-Auszug ?
Welches Gerät ?
Welche Attribute gesetzt ?

pah

kabanett

Log nach Installation der .pm und restart. Gerät angelegt und Verbose 5 gesetzt. Gerät wie vorab erwähnt Shelly 1!


2018.09.12 18:42:15 1: [Shelly_status] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/status
2018.09.12 18:42:15 1: [Shelly_status] has obtained data {"wifi_sta":{"connected":true,"ssid":"Netzwerkname","ip":"192.168.***.***"},"cloud":{"enabled":false,"connected":false},"time":"18:42","serial":1,"has_update":false,"mac":"************","relays" :[{"ison":true, "has_timer":true}],"update":{"status":"idle","has_update":false,"new_version":"20180910-102637/v1.2.0@7b4c6583","old_version":"20180910-102637/v1.2.0@7b4c6583"},"ram_total":51464,"ram_free":42064,"fs_size":233681,"fs_free":174947,"uptime":87889}
2018.09.12 18:42:15 1: PERL WARNING: Use of uninitialized value $ison in substitution (s///) at ./FHEM/36_Shelly.pm line 729.
2018.09.12 18:42:15 1: PERL WARNING: Use of uninitialized value $ison in substitution (s///) at ./FHEM/36_Shelly.pm line 730.
2018.09.12 18:42:47 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=on
2018.09.12 18:42:47 1: [Shelly_onoff] returns without success, cmd=?turn=on but ison=on
2018.09.12 18:42:47 1: PERL WARNING: Use of uninitialized value $overpower in string eq at ./FHEM/36_Shelly.pm line 652.
2018.09.12 18:43:12 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:43:12 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:43:25 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:43:25 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:43:43 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=on
2018.09.12 18:43:46 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:43:55 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=on
2018.09.12 18:43:55 1: [Shelly_onoff] returns without success, cmd=?turn=on but ison=on
2018.09.12 18:44:02 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=on
2018.09.12 18:44:02 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:44:05 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=on
2018.09.12 18:44:05 1: [Shelly_onoff] returns without success, cmd=?turn=on but ison=on
2018.09.12 18:44:08 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:44:08 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:44:10 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:44:10 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:44:15 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=off
2018.09.12 18:44:15 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:44:19 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:44:19 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:44:40 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=off
2018.09.12 18:44:40 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:44:43 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:44:43 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:44:52 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=on
2018.09.12 18:44:52 1: [Shelly_onoff] returns without success, cmd=?turn=on but ison=on
2018.09.12 18:44:58 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:44:58 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:45:04 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:45:04 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:45:12 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=on
2018.09.12 18:45:12 1: [Shelly_onoff] returns without success, cmd=?turn=on but ison=on
2018.09.12 18:45:18 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=on
2018.09.12 18:45:18 1: [Shelly_onoff] returns without success, cmd=?turn=on but ison=on
2018.09.12 18:45:25 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:45:25 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:48:08 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=on
2018.09.12 18:48:08 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:48:18 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=off
2018.09.12 18:48:18 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:48:21 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:48:21 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:48:23 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=on
2018.09.12 18:48:23 1: [Shelly_onoff] returns without success, cmd=?turn=on but ison=on
2018.09.12 18:48:55 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=on
2018.09.12 18:48:55 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:49:01 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=on
2018.09.12 18:49:01 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=off
2018.09.12 18:49:01 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:49:01 1: [Shelly_onoff] returns without success, cmd=?turn=on but ison=on
2018.09.12 18:49:07 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:49:07 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:49:10 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=off
2018.09.12 18:49:10 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:49:13 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:49:13 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
2018.09.12 18:49:18 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=on
2018.09.12 18:49:18 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:49:21 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=on
2018.09.12 18:49:21 1: [Shelly_onoff] returns without success, cmd=?turn=on but ison=on
2018.09.12 18:49:26 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/1?turn=off
2018.09.12 18:49:26 1: [Shelly_onoff] has invalid JSON data
2018.09.12 18:49:32 1: [Shelly_onoff] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/relay/0?turn=off
2018.09.12 18:49:32 1: [Shelly_onoff] returns without success, cmd=?turn=off but ison=off
Hardware: Fhem auf Raspi3 / selbtsbau CUL 433 und 868 MHz / MAX Thermostate / IT-Dosen nur noch Weihnachten / diverse ESP Aktoren/Sensoren / X10 Fernbedienung / Shelly 1, 1L, 2, 2.5, Dimmer, RGB2 / LaCrosseGateway / Zigbee2531 / diverse Zigbee Aktoren/Sensoren

Prof. Dr. Peter Henning

#47
Ah, ok,

ich habe aus Versehen nicht die richtige Version in den ersten Post geladen. Wird umgehend behoben.

FHEMWEB muss ich noch etwas überlisten, die WebCmds funktionieren wegen der zwei Kanäle beim Shelly2 noch nicht richtig. Vorerst also immer "set <device> on|off channel" benutzen

LG

pah

kabanett

Ich hab die neue Version installiert. Jetzt bekomme ich ein "Error:wrong channel"!


2018.09.12 20:14:55 1: [Shelly_status] called with only hash  => Issue a non-blocking call to http://192.168.***.***:80/status
2018.09.12 20:14:55 1: [Shelly_status] has obtained data {"wifi_sta":{"connected":true,"ssid":"WLan_Name!!!","ip":"192.168.***.***"},"cloud":{"enabled":false,"connected":false},"time":"20:14","serial":1,"has_update":false,"mac":"************","relays" :[{"ison":false, "has_timer":false}],"update":{"status":"idle","has_update":false,"new_version":"20180910-102637/v1.2.0@7b4c6583","old_version":"20180910-102637/v1.2.0@7b4c6583"},"ram_total":51464,"ram_free":42104,"fs_size":233681,"fs_free":174947,"uptime":93449}
2018.09.12 20:14:55 1: PERL WARNING: Use of uninitialized value $ison in substitution (s///) at ./FHEM/36_Shelly.pm line 735.
2018.09.12 20:14:55 1: PERL WARNING: Use of uninitialized value $ison in substitution (s///) at ./FHEM/36_Shelly.pm line 736.
2018.09.12 20:15:07 1: PERL WARNING: Use of uninitialized value $channel in pattern match (m//) at ./FHEM/36_Shelly.pm line 345.
2018.09.12 20:15:07 1: PERL WARNING: Use of uninitialized value $channel in concatenation (.) or string at ./FHEM/36_Shelly.pm line 346.
2018.09.12 20:15:07 1: [Shelly_Set]
2018.09.12 20:15:50 1: [Shelly_Set]
Hardware: Fhem auf Raspi3 / selbtsbau CUL 433 und 868 MHz / MAX Thermostate / IT-Dosen nur noch Weihnachten / diverse ESP Aktoren/Sensoren / X10 Fernbedienung / Shelly 1, 1L, 2, 2.5, Dimmer, RGB2 / LaCrosseGateway / Zigbee2531 / diverse Zigbee Aktoren/Sensoren

CoolTux

So lange Du nicht mehr Infos lieferst, wie ein list vom Device behaupte ich das Deine Shelly 3 kaputt ist.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

kabanett

Immer noch Shelly 1 ;)
Sorry, ich bin da nicht so fit und weiß nicht was man alles benötigt! Das ist keine Absicht!!! Ich versuche dazu zu lernen.... hoffentlich klapp es :)


Internals:
   BLOCKED    0
   CFGFN     
   DEF        192.168.***.***
   DURATION   0
   NAME       Garage_Licht
   NR         127
   STATE      OK
   TCPIP      192.168.***.***:80
   TYPE       Shelly
   DATA:
   READINGS:
     2018-09-12 20:14:55   cloud           disabled
     2018-09-12 20:14:55   firmware        v1.2.0
     2018-09-12 20:14:55   relay_0         off
     2018-09-12 20:14:55   state           OK
Attributes:

Hardware: Fhem auf Raspi3 / selbtsbau CUL 433 und 868 MHz / MAX Thermostate / IT-Dosen nur noch Weihnachten / diverse ESP Aktoren/Sensoren / X10 Fernbedienung / Shelly 1, 1L, 2, 2.5, Dimmer, RGB2 / LaCrosseGateway / Zigbee2531 / diverse Zigbee Aktoren/Sensoren

marvin78

Zitat von: kabanett am 12 September 2018, 20:42:40

Sorry, ich bin da nicht so fit

Angepinnte Beiträge im Anfängerbereich lesen, dann bist du fit.

Bartimaus

Mal nebenbei gefragt: Wie lange habt Ihr auf die Bestellung aus Vulgarien gewartet, bzw. wie lange war das Paket unterwegs ?
LG
B.


FHEM@Intel-J4105@Debian-LXC, CUL1101,FS20,IT,DS18B20,DS2413(Heizungslogger),DS2423(Stromlogger)Homematic,HM-LAN,ZWave,MiniCULs,Shelly

Papa Romeo

..waren schon 1 1/2 bis 2 Wochen.
...die richtige Lötspitzentemperatur prüft man zwischen Daumen und Zeigefinger.
...überlasse niemals etwas einer Software, das du hardwaremässig erreichen kannst.
...unvorsichtige Elektriker werden schnell zu leitenden Angestellten.
und...never change a running System...no Updates if not necessary

carlos

Ich habe bei amazon bestellt und ist jetzt ca. 2 Wochen her.
Leider noch nicht angekommen, da per UPS versandt wurde und ich Packstation angegeben habe.
Also Vorsicht bei Versenden an Packstation.
Soll aber demnächst kommen.
Gruß
Carlos
FHEM svn auf Intel NUC mit proxmox,1 UDOO, 3 Raspberry Pi, signalduino, nanoCUL, div. Homematic Komponenten, toom Baumarkt Funksteckdosen, einige sonoffs, hue, shelly

CoolTux

Zitat von: kabanett am 12 September 2018, 20:42:40
Immer noch Shelly 1 ;)
Sorry, ich bin da nicht so fit und weiß nicht was man alles benötigt! Das ist keine Absicht!!! Ich versuche dazu zu lernen.... hoffentlich klapp es :)


Internals:
   BLOCKED    0
   CFGFN     
   DEF        192.168.***.***
   DURATION   0
   NAME       Garage_Licht
   NR         127
   STATE      OK
   TCPIP      192.168.***.***:80
   TYPE       Shelly
   DATA:
   READINGS:
     2018-09-12 20:14:55   cloud           disabled
     2018-09-12 20:14:55   firmware        v1.2.0
     2018-09-12 20:14:55   relay_0         off
     2018-09-12 20:14:55   state           OK
Attributes:


Kann es sein das da Attribute fehlen? Was sagt die Commandref zu dem Thema?
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Bartimaus

Zitat von: CoolTux am 13 September 2018, 08:09:26
Kann es sein das da Attribute fehlen? Was sagt die Commandref zu dem Thema?

Das Modul ist doch noch garnicht offizieller Bestandteil von FHEM.... in der CR finde ich momentan nix
LG
B.


FHEM@Intel-J4105@Debian-LXC, CUL1101,FS20,IT,DS18B20,DS2413(Heizungslogger),DS2423(Stromlogger)Homematic,HM-LAN,ZWave,MiniCULs,Shelly

CoolTux

Zitat von: Bartimaus am 13 September 2018, 08:15:19
Das Modul ist doch noch garnicht offizieller Bestandteil von FHEM.... in der CR finde ich momentan nix

Die musst Du schon erstellen oder eben ein Update von FHEM machen so das FHEM sie für Dich nach dem Update erstellt.

selber machen

cd /opt/fhem/

/usr/bin/perl contrib/commandref_join.pl


oder so ähnlich. Findet man aber schnell raus.
Voraussetzung ist natürlich das pah eine geschrieben hat im Modul.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

CoolTux

Kurz geschaut und natürlich hat er eine geschrieben, sonst wäre er nicht pah
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Bartimaus

LG
B.


FHEM@Intel-J4105@Debian-LXC, CUL1101,FS20,IT,DS18B20,DS2413(Heizungslogger),DS2423(Stromlogger)Homematic,HM-LAN,ZWave,MiniCULs,Shelly