Autor Thema: Anbindung Viessmann Heizung mit VCONTROL300  (Gelesen 31586 mal)

Offline ToJu

  • New Member
  • *
  • Beiträge: 28
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #15 am: 06 April 2017, 14:39:57 »
Hi,

schaue dir mal im Code die Zeilen 92 und folgende an. Dort werden verschiedene Modi definiert und über das Attribut "vitotronicType" ab Zeile 338 ausgewertet. Bei mir passte das gar nicht. Ich haben den Code auf meine Heizung anpassen müssen, damit es funktioniert. Vielleicht reicht bei dir auch das Setzen des Attributes.

Grüße,
Torben

Offline Tobias

  • Developer
  • Hero Member
  • ****
  • Beiträge: 3574
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #16 am: 06 April 2017, 16:11:53 »
gefunden, musste das Attribut "vitotronicType" auf "200_KWx" stellen und schon ging es ;)
FHEM auf ASRock J3455-ITX im 19" Rack mit Homematic, MAX, PCA301, Panstamp-Sensoren, RPi mit 2x 1wire, RPi mit Text2Speech.
Maintainer der Module: DbLog, Text2Speech, TrashCal, MediaList
Meine Projekte auf https://github.com/tobiasfaust

Offline Newbie

  • Full Member
  • ***
  • Beiträge: 139
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #17 am: 11 April 2017, 15:49:01 »
Hallo Stephan,


ich nutze dein Modul seit etwa 5 Wochen, seit 2 Wochen habe ich immer mal wieder Probleme alle Werte abzufragen.

2017.04.09 20:32:56.368 3: Opening Vito333 device /dev/ttyUSB0
2017.04.09 20:32:56.436 3: Setting Vito333 serial parameters to 4800,8,E,2
2017.04.09 20:32:56.447 3: Vito333 device opened
2017.04.09 20:32:56.447 4: VCONTROL300: Start of update...
2017.04.09 20:32:56.450 4: VCONTROL300: Start of polling values...
2017.04.09 20:32:56.451 4: VCONTROL300: Waiting for sync byte...
2017.04.09 20:32:56.451 5: SW: 04
2017.04.09 20:32:57.473 4: VCONTROL300: Waiting for sync byte...
2017.04.09 20:32:57.475 5: SW: 04
2017.04.09 20:32:58.480 4: VCONTROL300: Received sync byte!
2017.04.09 20:32:58.482 4: VCONTROL300: Waiting for init byte...
2017.04.09 20:32:58.484 5: SW: 160000
2017.04.09 20:32:58.507 4: VCONTROL300: Received init byte!
2017.04.09 20:32:58.509 4: VCONTROL300: Init status: 'ok'!
2017.04.09 20:32:58.515 5: VCONTROL300: Send 410500012303012D
2017.04.09 20:32:58.516 5: SW: 410500012303012d
2017.04.09 20:32:58.594 5: VCONTROL300: Read '06'
2017.04.09 20:32:58.596 5: VCONTROL300: Read '41'
2017.04.09 20:32:58.598 5: VCONTROL300: Received 1 of 9 bytes
2017.04.09 20:32:58.601 5: VCONTROL300: Read '0601'
2017.04.09 20:32:58.602 5: VCONTROL300: Received 3 of 9 bytes
2017.04.09 20:32:58.603 5: VCONTROL300: Read '01'
2017.04.09 20:32:58.605 5: VCONTROL300: Received 4 of 9 bytes
2017.04.09 20:32:58.606 5: VCONTROL300: Read '23'
2017.04.09 20:32:58.608 5: VCONTROL300: Received 5 of 9 bytes
2017.04.09 20:32:58.609 5: VCONTROL300: Read '03'
2017.04.09 20:32:58.611 5: VCONTROL300: Received 6 of 9 bytes
2017.04.09 20:32:58.612 5: VCONTROL300: Read '01'
2017.04.09 20:32:58.612 5: VCONTROL300: Received 7 of 9 bytes
2017.04.09 20:32:58.613 5: VCONTROL300: Read '00'
2017.04.09 20:32:58.613 5: VCONTROL300: Received 8 of 9 bytes
2017.04.09 20:32:58.615 5: VCONTROL300: Read '2F'
2017.04.09 20:32:58.615 5: VCONTROL300: Received 9 of 9 bytes
2017.04.09 20:32:58.616 5: VCONTROL300: Parsed 'Partybetrieb : off'
2017.04.09 20:32:58.618 5: VCONTROL300: Update reading 'Partybetrieb : off'
2017.04.09 20:32:58.619 5: VCONTROL300: Send 4105000108000210
2017.04.09 20:32:58.620 5: SW: 4105000108000210
2017.04.09 20:32:58.648 5: VCONTROL300: Read '06'
2017.04.09 20:32:58.650 5: VCONTROL300: Read '41'
2017.04.09 20:32:58.650 5: VCONTROL300: Received 1 of 10 bytes
2017.04.09 20:32:58.653 5: VCONTROL300: Read '07'
2017.04.09 20:32:58.653 5: VCONTROL300: Received 2 of 10 bytes
2017.04.09 20:32:58.655 5: VCONTROL300: Read '01'
2017.04.09 20:32:58.655 5: VCONTROL300: Received 3 of 10 bytes
2017.04.09 20:32:58.658 5: VCONTROL300: Read '01'
2017.04.09 20:32:58.658 5: VCONTROL300: Received 4 of 10 bytes
2017.04.09 20:32:58.660 5: VCONTROL300: Read '08'
2017.04.09 20:32:58.660 5: VCONTROL300: Received 5 of 10 bytes
2017.04.09 20:32:58.663 5: VCONTROL300: Read '00'
2017.04.09 20:32:58.663 5: VCONTROL300: Received 6 of 10 bytes
2017.04.09 20:32:58.665 5: VCONTROL300: Read '02'
2017.04.09 20:32:58.665 5: VCONTROL300: Received 7 of 10 bytes
2017.04.09 20:32:58.668 5: VCONTROL300: Read '85'
2017.04.09 20:32:58.668 5: VCONTROL300: Received 8 of 10 bytes
2017.04.09 20:32:58.670 5: VCONTROL300: Read '00'
2017.04.09 20:32:58.670 5: VCONTROL300: Received 9 of 10 bytes
2017.04.09 20:32:58.673 5: VCONTROL300: Read '98'
2017.04.09 20:32:58.673 5: VCONTROL300: Received 10 of 10 bytes
2017.04.09 20:32:58.673 5: VCONTROL300: Parsed 'Temp-Aussen : 13.3'
2017.04.09 20:32:58.674 5: VCONTROL300: Update reading 'Temp-Aussen : 13.3'
2017.04.09 20:32:58.675 5: VCONTROL300: Send 410500010A820193
2017.04.09 20:32:58.676 5: SW: 410500010a820193
2017.04.09 20:32:58.701 5: VCONTROL300: Read '06'
2017.04.09 20:32:58.704 5: VCONTROL300: Read '41'
2017.04.09 20:32:58.706 5: VCONTROL300: Received 1 of 9 bytes
2017.04.09 20:32:58.707 5: VCONTROL300: Read '06'
2017.04.09 20:32:58.708 5: VCONTROL300: Received 2 of 9 bytes
2017.04.09 20:32:58.709 5: VCONTROL300: Read '01'
2017.04.09 20:32:58.711 5: VCONTROL300: Received 3 of 9 bytes
2017.04.09 20:32:58.712 5: VCONTROL300: Read '01'
2017.04.09 20:32:58.713 5: VCONTROL300: Received 4 of 9 bytes
2017.04.09 20:32:58.714 5: VCONTROL300: Read '0A'
2017.04.09 20:32:58.715 5: VCONTROL300: Received 5 of 9 bytes
2017.04.09 20:32:58.716 5: VCONTROL300: Read '82'
2017.04.09 20:32:58.717 5: VCONTROL300: Received 6 of 9 bytes
2017.04.09 20:32:58.720 5: VCONTROL300: Read '01'
2017.04.09 20:32:58.721 5: VCONTROL300: Received 7 of 9 bytes
2017.04.09 20:32:58.721 5: VCONTROL300: Read '00'
2017.04.09 20:32:58.722 5: VCONTROL300: Received 8 of 9 bytes
2017.04.09 20:32:58.724 5: VCONTROL300: Read '95'
2017.04.09 20:32:58.725 5: VCONTROL300: Received 9 of 9 bytes
2017.04.09 20:32:58.725 5: VCONTROL300: Parsed 'Stoerung : off'
2017.04.09 20:32:58.726 5: VCONTROL300: Update reading 'Stoerung : off'
2017.04.09 20:32:58.727 5: VCONTROL300: Send 410500013301013B
2017.04.09 20:32:58.728 5: SW: 410500013301013b
2017.04.09 20:32:58.756 5: VCONTROL300: Read '06'
2017.04.09 20:32:58.767 1: /dev/ttyUSB0 disconnected, waiting to reappear (Vito333)
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1204.
2017.04.09 20:32:58.783 5: VCONTROL300: Read ''
2017.04.09 20:32:58.783 5: VCONTROL300: Received 0 of 9 bytes
2017.04.09 20:32:58.783 2: VCONTROL300: Error while requesting data! Length of received data was 0!!!
2017.04.09 20:32:58.784 5: VCONTROL300: Send 410500013301013B
2017.04.09 20:32:58.784 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.785 5: VCONTROL300: Read ''
2017.04.09 20:32:58.785 5: VCONTROL300: Send 4105000108040214
2017.04.09 20:32:58.785 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.786 5: VCONTROL300: Read ''
2017.04.09 20:32:58.786 5: VCONTROL300: Send 410500010A3B014C
2017.04.09 20:32:58.786 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.786 5: VCONTROL300: Read ''
2017.04.09 20:32:58.787 5: VCONTROL300: Send 410500010A3C014D
2017.04.09 20:32:58.787 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.787 5: VCONTROL300: Read ''
2017.04.09 20:32:58.787 5: VCONTROL300: Send 4105000155D30230
2017.04.09 20:32:58.788 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.788 5: VCONTROL300: Read ''
2017.04.09 20:32:58.788 5: VCONTROL300: Send 41050001A38F023A
2017.04.09 20:32:58.788 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.789 5: VCONTROL300: Read ''
2017.04.09 20:32:58.789 5: VCONTROL300: Send 4105000100F80200
2017.04.09 20:32:58.789 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.790 5: VCONTROL300: Read ''
2017.04.09 20:32:58.790 5: VCONTROL300: Send 41050001555A02B7
2017.04.09 20:32:58.790 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.791 5: VCONTROL300: Read ''
2017.04.09 20:32:58.791 5: VCONTROL300: Send 4105000108080218
2017.04.09 20:32:58.791 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.791 5: VCONTROL300: Read ''
2017.04.09 20:32:58.792 5: VCONTROL300: Send 4105000108460155
2017.04.09 20:32:58.792 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.792 5: VCONTROL300: Read ''
2017.04.09 20:32:58.792 5: VCONTROL300: Send 41050001088A029A
2017.04.09 20:32:58.793 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.793 5: VCONTROL300: Read ''
2017.04.09 20:32:58.793 5: VCONTROL300: Send 41050001A30502B0
2017.04.09 20:32:58.793 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.793 5: VCONTROL300: Read ''
2017.04.09 20:32:58.794 5: VCONTROL300: Send 410500012302012C
2017.04.09 20:32:58.794 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.794 5: VCONTROL300: Read ''
2017.04.09 20:32:58.795 5: VCONTROL300: Send 4105000125440271
2017.04.09 20:32:58.795 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.795 5: VCONTROL300: Read ''
2017.04.09 20:32:58.796 5: VCONTROL300: Send 4105000108860498
2017.04.09 20:32:58.796 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.796 5: VCONTROL300: Read ''
2017.04.09 20:32:58.796 5: VCONTROL300: Send 41050001A38F023A
2017.04.09 20:32:58.797 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.797 5: VCONTROL300: Read ''
2017.04.09 20:32:58.797 5: VCONTROL300: Send 410500016300016A
2017.04.09 20:32:58.797 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.798 5: VCONTROL300: Read ''
2017.04.09 20:32:58.798 5: VCONTROL300: Send 4105000123060130
2017.04.09 20:32:58.798 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.798 5: VCONTROL300: Read ''
2017.04.09 20:32:58.799 5: VCONTROL300: Send 4105000108020212
2017.04.09 20:32:58.799 2: Attempt to write to disconnected device.
Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1225.
2017.04.09 20:32:58.799 5: VCONTROL300: Read ''
2017.04.09 20:32:58.801 4: VCONTROL300: End of polling values! Duration: 2.35
2017.04.09 20:32:58.908 4: VCONTROL300: Update done!
2017.04.09 20:32:58.908 3: VCONTROL300: USB device closed
2017.04.09 20:32:58.909 5: VCONTROL300: Undef set_cmd_list_values!

Irgendeinen Tipp für mich?

vg Jens
fhem-5.8 (configDB+DbLog)  auf ODROID-XU4 mit Ubuntu 17.10, ODROID-HC1
HM-CC-RT-DN, HM-TC-IT-WM-W-EU, HM-Sen-MDIR-O-2, HM-CC-TC, HM-CC-VD, HM-SEC-RHS,HM-LC-SW1-PL2, HM-CFG-LAN, HM-CFG-USB-2, HM-ES-PMSw1-Pl
Unifi-USG, Unifi-Switch 8POE, Unifi-AC PRO, Unifi-G3

Offline srxp

  • Jr. Member
  • **
  • Beiträge: 99
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #18 am: 11 April 2017, 15:59:36 »
Hallo Jens,
also so auf die Schnelle fällt mir jetzt nix ein.
und die Fehler kamen einfach plötzlich von einem Tag auf den anderen?

lg

Offline Newbie

  • Full Member
  • ***
  • Beiträge: 139
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #19 am: 16 April 2017, 15:07:16 »
Hallo Stephan,

hab es jetzt mal auf einer anderen Plattform probiert (FHEM neu installiert, nur VCONTROL300 als Device). Zwar nicht ganz soviele
Fehler, aber doch über die Zeit gesehen signifikant. Auch die Anzahl der abgefragten Readings hat keinen Einfluss.


vg Jens
fhem-5.8 (configDB+DbLog)  auf ODROID-XU4 mit Ubuntu 17.10, ODROID-HC1
HM-CC-RT-DN, HM-TC-IT-WM-W-EU, HM-Sen-MDIR-O-2, HM-CC-TC, HM-CC-VD, HM-SEC-RHS,HM-LC-SW1-PL2, HM-CFG-LAN, HM-CFG-USB-2, HM-ES-PMSw1-Pl
Unifi-USG, Unifi-Switch 8POE, Unifi-AC PRO, Unifi-G3

Offline crispyduck

  • Full Member
  • ***
  • Beiträge: 229
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #20 am: 17 April 2017, 20:03:12 »
Hallo,

Habe wie schon im anderen Tread geschrieben das VCONTROL Modul so geändert das es mit configdb als auch config/command file funktioniert.

Da ich länger nichts mit FHEM gemacht habe, habe ich dann erst später die Arbeit von Stephan und das VCONTROL300 Modul gesehen.

Habe die Änderungen jetzt natürlich auch im VCONTROL300 gemacht.

Teste das morgen nochmal ohne configdb und poste die Änderungen dann hier.


VCONTROL300 habe ich bei mir jetzt einfach mal mit dem cfg File von Stephan gestartet. Passt zwar nicht ganz zu meiner Vitotronic 200 WO1C, aber funktioniert prinzipiell mal.

Hat vielleicht jemand ein angepasstes cfg File mit passenden Adressen für die WO1C?

Wie sollte bei dieser das define aussehen und welche Attribute? Kann wohl nicht 300?

Habe jetzt nur schnell meine Änderungen das es mit configdb funktioniert auch in das VCONTROL300 Modul übertragen ohne mir genau alle Änderungen von Stephan angesehen zu habe.

Lg,
Crispyduck

Offline crispyduck

  • Full Member
  • ***
  • Beiträge: 229
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #21 am: 18 April 2017, 13:19:39 »
Anbei das letzte Modul von Stephan mit meinen Änderungen. Habe es oben in die Signatur mal so eingefügt:

# Based on:
# $Id: 89_VCONTROL300.pm 11340 2017-01-09 23:16:00Z srxp $
# modified to work also with configdb by Crispyduck (17.04.2017)

Geändert habe ich folgende zwei Abschnitte:

Ab Zeile 225
  #check existence of config_file
  if($a[3]){
     $command_config_file = $a[3];
         
     if(-e $command_config_file){
        Log3 $devName, 3, "VCONTROL300: Define open DATEI '$command_config_file'";
        VCONTROL300_CmdConfig($hash,$command_config_file);
     }
     else {
        my $msg = "config file $command_config_file does not exist";
      Log3 undef, 2, $msg;
      return $msg;
    }
  }
zu
  #load config_file
  if($a[3]){
     $command_config_file = $a[3];
     VCONTROL300_CmdConfig($hash,$command_config_file);
  }

Ab Zeile 1690
#####################################
#####################################
## Load Config
#####################################
#####################################
sub VCONTROL300_CmdConfig($$)
{
  my ($hash,$cmd_config_file) = @_;
 
  my ($sec,$min,$hour,$mday,$mon,$year) = localtime;
  my $write_idx=0;
  Log3 undef, 3, "VCONTROL300: Opening file '$cmd_config_file'";
  open(CMDDATEI,"<$cmd_config_file") || die "problem opening $cmd_config_file\n" ;

  #undef @poll_cmd_list;
  #undef @set_cmd_list;
  #undef @timer_cmd_list;
  undef %poll_cmd_hash;
  undef %set_cmd_hash;
  undef %set_cmd_hash;
 
 
  while(<CMDDATEI>){
.
.
.
.
.
  };

close (CMDDATEI);
Log3 undef, 3, "VCONTROL300: File '$cmd_config_file' refreshed";
}
zu
#####################################
#####################################
## Load Config
#####################################
#####################################
sub VCONTROL300_CmdConfig($$)
{
  my ($hash,$cmd_config_file) = @_;
 
  my ($sec,$min,$hour,$mday,$mon,$year) = localtime;
  my $write_idx=0;
  Log3 undef, 3, "VCONTROL300: Opening file '$cmd_config_file'";
  my ($error, @vcontrolfilecontent) = FileRead($cmd_config_file);

  #undef @poll_cmd_list;
  #undef @set_cmd_list;
  #undef @timer_cmd_list;
  undef %poll_cmd_hash;
  undef %set_cmd_hash;
  undef %set_cmd_hash;
 
  if ($error eq '')  {
  foreach (@vcontrolfilecontent)  {
.
.
.
.
.
  };
  Log3 undef, 3, "VCONTROL300: File '$cmd_config_file' refreshed";
}
else {
Log3 undef, 2, "VCONTROL300 ERROR: '$error'";
}
}

Den check ob das File existiert habe ich also raus genommen und nur die Sub aufgerufen.

In der Sub lade ich den Inhalt des Files mit FileRead($cmd_config_file) in das @vcontrolfilecontent welches dann wenn $error='' mit foreach (@vcontrolfilecontent) statt der while Schleife weiter verarbeitet wird.


Vielleicht kann es ja Stephan fix mit rein nehmen. Wie gesagt funktioniert die Änderung mit als auch ohne configdb. Wenn mit configdb muss das config File auch mit "configdb fileimport" in die DB importiert werden. Ich bevorzuge es alles in DBs zu speichern da diese erstens schon mal auf der NAS mit RAID laufen und zusätzlich leichter zu sichern sind. RPi mit FHEM läuft bei mir außerdem mit RO Filesystem und ist eigentlich recht dumm da sie sich die config erst aus der DB holt.
 
Lg,
Crispyduck

Offline crispyduck

  • Full Member
  • ***
  • Beiträge: 229
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #22 am: 18 April 2017, 15:11:45 »
Hallo,

Ich bekomme nach dem Wechsel auf die VCONTROL300 immer noch massiv:

Attempt to write to disconnected device.


Bei mir sieht es ähnlich aus mit dem 300er Protokoll. Mit KW funktioniert es ohne Probleme, mit 300 bekomme ich schon nach ein paar Abfragen auch die Meldung:

2017.04.18 14:23:10 3: Opening Heizung device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0
2017.04.18 14:23:11 3: Setting Heizung serial parameters to 4800,8,E,2
2017.04.18 14:23:11 3: Heizung device opened
2017.04.18 14:23:13 3: VCONTROL300: USB device closed
2017.04.18 14:26:10 3: VCONTROL300: USB connection opened
2017.04.18 14:26:10 3: Opening Heizung device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0
2017.04.18 14:26:11 3: Setting Heizung serial parameters to 4800,8,E,2
2017.04.18 14:26:11 3: Heizung device opened
2017.04.18 14:26:13 3: VCONTROL300: USB device closed
2017.04.18 14:29:10 3: VCONTROL300: USB connection opened
2017.04.18 14:29:10 3: Opening Heizung device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0
2017.04.18 14:29:11 3: Setting Heizung serial parameters to 4800,8,E,2
2017.04.18 14:29:11 3: Heizung device opened
2017.04.18 14:29:13 3: VCONTROL300: USB device closed
2017.04.18 14:32:10 3: VCONTROL300: USB connection opened
2017.04.18 14:32:10 3: Opening Heizung device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0
2017.04.18 14:32:11 3: Setting Heizung serial parameters to 4800,8,E,2
2017.04.18 14:32:11 3: Heizung device opened
2017.04.18 14:32:13 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0 disconnected, waiting to reappear (Heizung)
2017.04.18 14:32:13 1: PERL WARNING: Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1196.
2017.04.18 14:32:13 2: VCONTROL300: Error while requesting data! Length of received data was 0!!!
2017.04.18 14:32:13 2: Attempt to write to disconnected device.
2017.04.18 14:32:13 1: PERL WARNING: Use of uninitialized value $mybuf in unpack at ./FHEM/89_VCONTROL300.pm line 1217.
2017.04.18 14:32:13 2: Attempt to write to disconnected device.
2017.04.18 14:32:13 3: VCONTROL300: USB device closed

Mit Protokoll KW geht es ohne Probleme.

Hab eine Vitocal 200 LW WP mit Vitotronic 200 WO1C.

Lg,
Crispyduck

Offline Newbie

  • Full Member
  • ***
  • Beiträge: 139
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #23 am: 18 April 2017, 15:51:51 »
Hallo Crispyduck,

hab deine Version mal angetestet - funktioniert leider gar nicht, egal ob mit als auch ohne configdb.
Auch mit verbose 5 sind keine Fehlermeldungen vorhanden.

vg Jens
fhem-5.8 (configDB+DbLog)  auf ODROID-XU4 mit Ubuntu 17.10, ODROID-HC1
HM-CC-RT-DN, HM-TC-IT-WM-W-EU, HM-Sen-MDIR-O-2, HM-CC-TC, HM-CC-VD, HM-SEC-RHS,HM-LC-SW1-PL2, HM-CFG-LAN, HM-CFG-USB-2, HM-ES-PMSw1-Pl
Unifi-USG, Unifi-Switch 8POE, Unifi-AC PRO, Unifi-G3

Offline crispyduck

  • Full Member
  • ***
  • Beiträge: 229
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #24 am: 18 April 2017, 16:14:21 »
Hallo Newbie,
seltsam, hab es gerade nochmal mit und ohne configdb bei mir getestet und beides funktioniert, bzw. gibt es auch einen Error wenn das File bzw. das File in der DB nicht vorhanden ist.

Überhaupt nichts im Log?

FHEM mit fhem.cfg gestartet ohne VCONTROL300.cfg sieht bei mir so aus:

2017.04.18 15:57:27 2: VCONTROL300: Using USB device
2017.04.18 15:57:27 3: VCONTROL300: Opening file './FHEM/89_VCONTROL300.cfg'
2017.04.18 15:57:27 2: VCONTROL300 ERROR: 'Can't open ./FHEM/89_VCONTROL300.cfg: No such file or directory'
2017.04.18 15:57:27 3: VCONTROL300: Using protocol 300

Offline Newbie

  • Full Member
  • ***
  • Beiträge: 139
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #25 am: 18 April 2017, 17:07:42 »
Hallo crispyduck,

sieht bei mir so aus (egal ob mit oder ohne VCONTROL300.cfg)

2017.04.18 17:02:03.784 5: VCONTROL300: Set InternalTimer to 1492527903.78477
2017.04.18 17:02:03.828 3: VCONTROL300: USB connection opened
2017.04.18 17:02:03.830 3: Opening Vito333 device /dev/ttyUSB0
2017.04.18 17:02:03.895 3: Setting Vito333 serial parameters to 4800,8,E,2
2017.04.18 17:02:03.906 3: Vito333 device opened
2017.04.18 17:02:03.906 4: VCONTROL300: Start of update...
2017.04.18 17:02:03.909 4: VCONTROL300: Start of polling values...
2017.04.18 17:02:03.910 4: VCONTROL300: Waiting for sync byte...
2017.04.18 17:02:03.910 5: SW: 04
2017.04.18 17:02:04.918 4: VCONTROL300: Waiting for sync byte...
2017.04.18 17:02:04.918 5: SW: 04
2017.04.18 17:02:05.911 4: VCONTROL300: Received sync byte!
2017.04.18 17:02:05.914 4: VCONTROL300: Waiting for init byte...
2017.04.18 17:02:05.915 5: SW: 160000
2017.04.18 17:02:05.930 4: VCONTROL300: Received init byte!
2017.04.18 17:02:05.932 4: VCONTROL300: Init status: 'ok'!
2017.04.18 17:02:05.934 4: VCONTROL300: End of polling values! Duration: 2.02
2017.04.18 17:02:05.974 4: VCONTROL300: Update done!
2017.04.18 17:02:05.975 3: VCONTROL300: USB device closed
2017.04.18 17:02:05.975 5: VCONTROL300: Undef set_cmd_list_values!

vg Jens

fhem-5.8 (configDB+DbLog)  auf ODROID-XU4 mit Ubuntu 17.10, ODROID-HC1
HM-CC-RT-DN, HM-TC-IT-WM-W-EU, HM-Sen-MDIR-O-2, HM-CC-TC, HM-CC-VD, HM-SEC-RHS,HM-LC-SW1-PL2, HM-CFG-LAN, HM-CFG-USB-2, HM-ES-PMSw1-Pl
Unifi-USG, Unifi-Switch 8POE, Unifi-AC PRO, Unifi-G3

Offline crispyduck

  • Full Member
  • ***
  • Beiträge: 229
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #26 am: 18 April 2017, 17:28:17 »
Da müsste doch davor noch was kommen

7.04.18 16:45:51 3: DbLog logDBlong: Push-Handle to db mysql:database=logDBlong;host=10.0.0.11;port=3306 created
2017.04.18 16:45:51 2: VCONTROL300: Using USB device
2017.04.18 16:45:51 3: VCONTROL300: Opening file './FHEM/89_VCONTROL300.cfg'
2017.04.18 16:45:51 3: VCONTROL300: File './FHEM/89_VCONTROL300.cfg' refreshed
2017.04.18 16:45:51 3: VCONTROL300: Using protocol 300
2017.04.18 16:45:51 2: SecurityCheck:  telnetPort has no associated allowed device with password/globalpassword. web has no associated allowed device with basicAuth.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2017.04.18 16:45:51 0: Featurelevel: 5.8
2017.04.18 16:45:51 0: Server started with 8 defined entities (fhem.pl:13983/2017-04-13 perl:5.020002 os:linux user:fhem pid:917)
2017.04.18 16:45:52 3: VCONTROL300: USB connection opened
2017.04.18 16:45:52 3: Opening Heizung device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0
2017.04.18 16:45:52 3: Setting Heizung serial parameters to 4800,8,E,2
2017.04.18 16:45:52 3: Heizung device opened
2017.04.18 16:45:54 3: VCONTROL300: USB device closed
2017.04.18 16:48:52 3: VCONTROL300: USB connection o

Offline Newbie

  • Full Member
  • ***
  • Beiträge: 139
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #27 am: 18 April 2017, 18:05:19 »
Hallo,

deine Version
2017.04.18 16:58:05.230 1: HMLAN_Parse: hmusb new condition disconnected
2017.04.18 16:58:05.234 1: HMLAN_Parse: hmusb new condition init
2017.04.18 16:58:06.954 0: Featurelevel: 5.8
2017.04.18 16:58:06.954 0: Server started with 151 defined entities (fhem.pl:14001/2017-04-15 perl:5.024001 os:linux user:fhem pid:4163)
2017.04.18 16:58:06.970 1: Perfmon: possible freeze starting at 16:58:03, delay is 3.97
2017.04.18 16:58:07.054 5: VCONTROL300: Set InternalTimer to 1492527667.05448
2017.04.18 16:58:07.082 3: VCONTROL300: USB connection opened
2017.04.18 16:58:07.085 3: Opening Vito333 device /dev/ttyUSB0
2017.04.18 16:58:07.123 1: HMLAN_Parse: HMLAN1 new condition ok
2017.04.18 16:58:07.156 3: Setting Vito333 serial parameters to 4800,8,E,2
2017.04.18 16:58:07.166 1: HMLAN_Parse: hmusb new condition ok
2017.04.18 16:58:07.167 3: Vito333 device opened
2017.04.18 16:58:07.167 4: VCONTROL300: Start of update...
2017.04.18 16:58:07.171 4: VCONTROL300: Start of polling values...
2017.04.18 16:58:07.171 4: VCONTROL300: Waiting for sync byte...
2017.04.18 16:58:07.172 5: SW: 04
2017.04.18 16:58:07.472 1: FHEMWEB SSL/HTTPS error:  SSL accept attempt failed error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
2017.04.18 16:58:08.184 4: VCONTROL300: Waiting for sync byte...
2017.04.18 16:58:08.185 5: SW: 04
2017.04.18 16:58:09.173 4: VCONTROL300: Received sync byte!
2017.04.18 16:58:09.174 4: VCONTROL300: Waiting for init byte...
2017.04.18 16:58:09.174 5: SW: 160000
2017.04.18 16:58:09.193 4: VCONTROL300: Received init byte!
2017.04.18 16:58:09.193 4: VCONTROL300: Init status: 'ok'!
2017.04.18 16:58:09.194 4: VCONTROL300: End of polling values! Duration: 2.02
2017.04.18 16:58:09.210 4: VCONTROL300: Update done!
2017.04.18 16:58:09.211 3: VCONTROL300: USB device closed
2017.04.18 16:58:09.211 5: VCONTROL300: Undef set_cmd_list_values!

die "normale" Version
2017.04.18 18:01:54.975 1: HMLAN_Parse: hmusb new condition disconnected
2017.04.18 18:01:54.978 1: HMLAN_Parse: hmusb new condition init
2017.04.18 18:01:56.694 0: Featurelevel: 5.8
2017.04.18 18:01:56.695 0: Server started with 151 defined entities (fhem.pl:14001/2017-04-15 perl:5.024001 os:linux user:fhem pid:5096)
2017.04.18 18:01:56.710 1: Perfmon: possible freeze starting at 18:01:52, delay is 4.71
2017.04.18 18:01:56.892 5: VCONTROL300: Set InternalTimer to 1492531496.89254
2017.04.18 18:01:56.919 3: VCONTROL300: USB connection opened
2017.04.18 18:01:56.921 3: Opening Vito333F device /dev/ttyUSB0
2017.04.18 18:01:56.985 1: HMLAN_Parse: hmusb new condition ok
2017.04.18 18:01:56.988 3: Setting Vito333F serial parameters to 4800,8,E,2
2017.04.18 18:01:56.990 1: HMLAN_Parse: HMLAN1 new condition ok
2017.04.18 18:01:57.000 3: Vito333F device opened
2017.04.18 18:01:57.000 4: VCONTROL300: Start of update...
2017.04.18 18:01:57.002 4: VCONTROL300: Start of polling values...
2017.04.18 18:01:57.002 4: VCONTROL300: Waiting for sync byte...
2017.04.18 18:01:57.003 5: SW: 04
2017.04.18 18:01:58.011 4: VCONTROL300: Waiting for sync byte...
2017.04.18 18:01:58.013 5: SW: 04
2017.04.18 18:01:59.001 4: VCONTROL300: Received sync byte!
2017.04.18 18:01:59.003 4: VCONTROL300: Waiting for init byte...
2017.04.18 18:01:59.004 5: SW: 160000
2017.04.18 18:01:59.018 4: VCONTROL300: Received init byte!
2017.04.18 18:01:59.020 4: VCONTROL300: Init status: 'ok'!
2017.04.18 18:01:59.024 5: VCONTROL300: Send 4105000155D30230
2017.04.18 18:01:59.026 5: SW: 4105000155d30230
2017.04.18 18:01:59.054 5: VCONTROL300: Read '06'
2017.04.18 18:01:59.057 5: VCONTROL300: Read '41'
2017.04.18 18:01:59.059 5: VCONTROL300: Received 1 of 10 bytes
2017.04.18 18:01:59.061 5: VCONTROL300: Read '0701'
2017.04.18 18:01:59.063 5: VCONTROL300: Received 3 of 10 bytes
2017.04.18 18:01:59.064 5: VCONTROL300: Read '01'
2017.04.18 18:01:59.065 5: VCONTROL300: Received 4 of 10 bytes
2017.04.18 18:01:59.067 5: VCONTROL300: Read '55'
2017.04.18 18:01:59.068 5: VCONTROL300: Received 5 of 10 bytes
2017.04.18 18:01:59.070 5: VCONTROL300: Read 'D3'
2017.04.18 18:01:59.071 5: VCONTROL300: Received 6 of 10 bytes
2017.04.18 18:01:59.073 5: VCONTROL300: Read '0210'
2017.04.18 18:01:59.074 5: VCONTROL300: Received 8 of 10 bytes
2017.04.18 18:01:59.076 5: VCONTROL300: Read '92'
2017.04.18 18:01:59.077 5: VCONTROL300: Received 9 of 10 bytes
2017.04.18 18:01:59.078 5: VCONTROL300: Read 'D5'
2017.04.18 18:01:59.080 5: VCONTROL300: Received 10 of 10 bytes
2017.04.18 18:01:59.084 5: VCONTROL300: Parsed 'BrennerLeistung : 16'
2017.04.18 18:01:59.085 5: VCONTROL300: Update reading 'BrennerLeistung : 16'
2017.04.18 18:01:59.086 5: VCONTROL300: Send 4105000108000210
2017.04.18 18:01:59.087 5: SW: 4105000108000210
2017.04.18 18:01:59.112 5: VCONTROL300: Read '06'
2017.04.18 18:01:59.114 5: VCONTROL300: Read '41'
2017.04.18 18:01:59.115 5: VCONTROL300: Received 1 of 10 bytes
2017.04.18 18:01:59.116 5: VCONTROL300: Read '07'
2017.04.18 18:01:59.116 5: VCONTROL300: Received 2 of 10 bytes
2017.04.18 18:01:59.119 5: VCONTROL300: Read '01'
2017.04.18 18:01:59.119 5: VCONTROL300: Received 3 of 10 bytes
2017.04.18 18:01:59.121 5: VCONTROL300: Read '01'
2017.04.18 18:01:59.121 5: VCONTROL300: Received 4 of 10 bytes
2017.04.18 18:01:59.124 5: VCONTROL300: Read '08'
2017.04.18 18:01:59.124 5: VCONTROL300: Received 5 of 10 bytes
2017.04.18 18:01:59.126 5: VCONTROL300: Read '00'
2017.04.18 18:01:59.126 5: VCONTROL300: Received 6 of 10 bytes
2017.04.18 18:01:59.129 5: VCONTROL300: Read '02'
2017.04.18 18:01:59.129 5: VCONTROL300: Received 7 of 10 bytes
2017.04.18 18:01:59.131 5: VCONTROL300: Read '38'
2017.04.18 18:01:59.131 5: VCONTROL300: Received 8 of 10 bytes
2017.04.18 18:01:59.134 5: VCONTROL300: Read '00'
2017.04.18 18:01:59.134 5: VCONTROL300: Received 9 of 10 bytes
2017.04.18 18:01:59.136 5: VCONTROL300: Read '4B'
2017.04.18 18:01:59.136 5: VCONTROL300: Received 10 of 10 bytes
2017.04.18 18:01:59.137 5: VCONTROL300: Parsed 'Temp-Aussen : 5.6'
2017.04.18 18:01:59.137 5: VCONTROL300: Update reading 'Temp-Aussen : 5.6'
2017.04.18 18:01:59.139 4: VCONTROL300: End of polling values! Duration: 2.14
2017.04.18 18:01:59.160 4: VCONTROL300: Update done!
2017.04.18 18:01:59.161 3: VCONTROL300: USB device closed

vg
fhem-5.8 (configDB+DbLog)  auf ODROID-XU4 mit Ubuntu 17.10, ODROID-HC1
HM-CC-RT-DN, HM-TC-IT-WM-W-EU, HM-Sen-MDIR-O-2, HM-CC-TC, HM-CC-VD, HM-SEC-RHS,HM-LC-SW1-PL2, HM-CFG-LAN, HM-CFG-USB-2, HM-ES-PMSw1-Pl
Unifi-USG, Unifi-Switch 8POE, Unifi-AC PRO, Unifi-G3

Offline crispyduck

  • Full Member
  • ***
  • Beiträge: 229
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #28 am: 18 April 2017, 19:15:09 »
Schaut bei mir ohnehin anders aus. Wie sieht den dein define und cfg File aus?

Mit verbose 5 müsste doch viel mehr zu sehen sein?

Hier mein Log Auszug mit verbose 5:

Original 89_VCONTROL300.pm aus dem ersten Post hier:
2017.04.18 19:03:21 5: Cmd: >define Heizung VCONTROL300 /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0 ./FHEM/89_VCONTROL300.cfg 180 kw<
2017.04.18 19:03:21 5: Loading ./FHEM/89_VCONTROL300.pm
2017.04.18 19:03:21 2: VCONTROL300: Using USB device
2017.04.18 19:03:21 3: VCONTROL300: Define open DATEI './FHEM/89_VCONTROL300.cfg'
2017.04.18 19:03:21 3: VCONTROL300: Opening file './FHEM/89_VCONTROL300.cfg'
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile # Poll Einstellungen
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile POLL, B000, 1ByteU, mode, Einstellung_Betriebsart , - #0:aus,1:ww,2:ww+hzg; 4:dauernd red; 5: dauernd norm; 6: normal abschalt; 7: nur k??n;
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile # Poll Temperaturen
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile POLL, 0101, 2ByteS, 10, Aussentemperatur , -
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile #SET, SENDCMD, CONV, MULTIPLICATOR, SET-NAME, NEXT_CMD or DAY
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile ################################################################################################
2017.04.18 19:03:21 5: VCONTROL300: CmdConfig-Zeile SET, B000, 1ByteU, mode, Einstellung_Betriebsart, -
2017.04.18 19:03:21 3: VCONTROL300: File './FHEM/89_VCONTROL300.cfg' refreshed
2017.04.18 19:03:21 3: VCONTROL300: Using protocol kw
2017.04.18 19:03:21 5: VCONTROL300: Set InternalTimer to 1492535002.35351
2017.04.18 19:03:21 5: Starting notify loop for global, 1 event(s), first is INITIALIZED
2017.04.18 19:03:21 5: createNotifyHash
2017.04.18 19:03:21 5: End notify loop for global
2017.04.18 19:03:21 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no associated allowed device with basicAuth. telnetPort has no associated allowed device with password/globalpassword.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2017.04.18 19:03:21 0: Featurelevel: 5.8
2017.04.18 19:03:21 0: Server started with 9 defined entities (fhem.pl:13983/2017-04-13 perl:5.020002 os:linux user:fhem pid:1183)
2017.04.18 19:03:21 4: Connection accepted from WEB_10.0.0.137_13662
2017.04.18 19:03:21 4: WEB_10.0.0.137_13662 GET /fhem?XHR=1&inform=type=status;filter=Heizung;since=1492534915.906;fmt=JSON&fw_id=25×tamp=1492535002044; BUFLEN:0
2017.04.18 19:03:21 4: Connection accepted from WEB_10.0.0.137_13663
2017.04.18 19:03:22 5: VCONTROL300: Set InternalTimer to 1492535182.35472
2017.04.18 19:03:22 4: BlockingCall (VCONTROL300_DoUpdate): created child (1187), uses telnetPort to connect back
2017.04.18 19:03:22 3: VCONTROL300: USB connection opened
2017.04.18 19:03:22 3: Opening Heizung device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0
2017.04.18 19:03:22 3: Setting Heizung serial parameters to 4800,8,E,2
2017.04.18 19:03:22 3: Heizung device opened
2017.04.18 19:03:22 4: VCONTROL300: Start of update...
2017.04.18 19:03:22 4: VCONTROL300: Start of polling values...
2017.04.18 19:03:22 4: VCONTROL300: Waiting for sync byte...
2017.04.18 19:03:22 5: SW: 04
2017.04.18 19:03:22 4: Connection accepted from telnetPort_127.0.0.1_60056
2017.04.18 19:03:22 5: Cmd: >{SetInternal('Heizung','UPDATESTATUS','ACTIVE')}<
2017.04.18 19:03:22 5: Cmd: >{readingsUpdateByName('Heizung','UpdateStatus','Active')}<
2017.04.18 19:03:22 5: Starting notify loop for Heizung, 1 event(s), first is UpdateStatus: Active
2017.04.18 19:03:22 5: createNotifyHash
2017.04.18 19:03:22 5: End notify loop for Heizung
2017.04.18 19:03:22 4: VCONTROL300: Received sync byte!
2017.04.18 19:03:22 4: VCONTROL300: Init status: 'ok'!
2017.04.18 19:03:23 5: VCONTROL300: Set sendstr 01F7B00001
2017.04.18 19:03:23 5: VCONTROL300: Send 01F7B00001
2017.04.18 19:03:23 5: SW: 01f7b00001
2017.04.18 19:03:23 5: VCONTROL300: Read '02'
2017.04.18 19:03:23 5: VCONTROL300: Data '02'
2017.04.18 19:03:23 5: VCONTROL300: Parsed 'Einstellung_Betriebsart : Heizen_und_Warmwasser'
2017.04.18 19:03:23 5: VCONTROL300: Update reading 'Einstellung_Betriebsart : Heizen_und_Warmwasser'
2017.04.18 19:03:23 5: VCONTROL300: Set sendstr 01F7010102
2017.04.18 19:03:23 5: Cmd: >{readingsUpdateByName('Heizung','Einstellung_Betriebsart','Heizen_und_Warmwasser')}<
2017.04.18 19:03:23 5: VCONTROL300: Delete prefix 01 of sendstr
2017.04.18 19:03:23 5: VCONTROL300: Send F7010102
2017.04.18 19:03:23 5: SW: f7010102
2017.04.18 19:03:23 5: Starting notify loop for Heizung, 1 event(s), first is Einstellung_Betriebsart: Heizen_und_Warmwasser
2017.04.18 19:03:23 5: End notify loop for Heizung
2017.04.18 19:03:23 5: VCONTROL300: Read '32'
2017.04.18 19:03:23 5: VCONTROL300: Received 1 of 2 bytes
2017.04.18 19:03:23 5: VCONTROL300: Read '00'
2017.04.18 19:03:23 5: VCONTROL300: Data '3200'
2017.04.18 19:03:23 5: VCONTROL300: Parsed 'Aussentemperatur : 5'
2017.04.18 19:03:23 5: VCONTROL300: Update reading 'Aussentemperatur : 5'
2017.04.18 19:03:23 4: VCONTROL300: End of polling values! Duration: 0.55
2017.04.18 19:03:23 5: Cmd: >{readingsUpdateByName('Heizung','Aussentemperatur','5')}<
2017.04.18 19:03:23 5: Starting notify loop for Heizung, 1 event(s), first is Aussentemperatur: 5
2017.04.18 19:03:23 5: End notify loop for Heizung
2017.04.18 19:03:23 5: Cmd: >{readingsUpdateByName('Heizung','UpdateTime','2017-04-18_19:03:23')}<
2017.04.18 19:03:23 5: Starting notify loop for Heizung, 1 event(s), first is UpdateTime: 2017-04-18_19:03:23
2017.04.18 19:03:23 5: End notify loop for Heizung
2017.04.18 19:03:23 5: Cmd: >{BlockingStart('1')}<
2017.04.18 19:03:23 5: Cmd: >{VCONTROL300_UpdateDone('Heizung')}<
2017.04.18 19:03:23 5: Starting notify loop for Heizung, 1 event(s), first is UpdateStatus: Inactive
2017.04.18 19:03:23 5: End notify loop for Heizung
2017.04.18 19:03:23 4: VCONTROL300: Update done!
2017.04.18 19:03:23 3: VCONTROL300: USB device closed
2017.04.18 19:03:23 5: VCONTROL300: Undef set_cmd_list_values!

die 89_VCONTROL.pm die ich angehängt habe:
2017.04.18 19:09:13 5: Cmd: >define Heizung VCONTROL300 /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0 ./FHEM/89_VCONTROL300.cfg 180 kw<
2017.04.18 19:09:13 5: Loading ./FHEM/89_VCONTROL300.pm
2017.04.18 19:09:13 2: VCONTROL300: Using USB device
2017.04.18 19:09:13 3: VCONTROL300: Opening file './FHEM/89_VCONTROL300.cfg'
2017.04.18 19:09:13 1: PERL WARNING: Use of uninitialized value $error in string eq at ./FHEM/89_VCONTROL300.pm line 1703.
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile # Poll Einstellungen
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile POLL, B000, 1ByteU, mode, Einstellung_Betriebsart , - #0:aus,1:ww,2:ww+hzg; 4:dauernd red; 5: dauernd norm; 6: normal abschalt; 7: nur k??n;
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile # Poll Temperaturen
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile POLL, 0101, 2ByteS, 10, Aussentemperatur , -
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile #SET, SENDCMD, CONV, MULTIPLICATOR, SET-NAME, NEXT_CMD or DAY
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile ################################################################################################
2017.04.18 19:09:13 5: VCONTROL300: CmdConfig-Zeile SET, B000, 1ByteU, mode, Einstellung_Betriebsart, -
2017.04.18 19:09:13 3: VCONTROL300: File './FHEM/89_VCONTROL300.cfg' refreshed
2017.04.18 19:09:13 3: VCONTROL300: Using protocol kw
2017.04.18 19:09:13 5: VCONTROL300: Set InternalTimer to 1492535354.70809
2017.04.18 19:09:13 5: Starting notify loop for global, 1 event(s), first is INITIALIZED
2017.04.18 19:09:13 5: createNotifyHash
2017.04.18 19:09:13 5: End notify loop for global
2017.04.18 19:09:13 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no associated allowed device with basicAuth. telnetPort has no associated allowed device with password/globalpassword.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2017.04.18 19:09:13 0: Featurelevel: 5.8
2017.04.18 19:09:13 0: Server started with 9 defined entities (fhem.pl:13983/2017-04-13 perl:5.020002 os:linux user:fhem pid:1254)
2017.04.18 19:09:13 4: Connection accepted from WEB_10.0.0.137_13771
2017.04.18 19:09:14 4: WEB_10.0.0.137_13771 GET /fhem/FileLog_logWrapper?XHR=1&inform=type=status;filter=;since=1492535218;fmt=JSON&fw_id=30×tamp=1492535353769; BUFLEN:0
2017.04.18 19:09:14 5: VCONTROL300: Set InternalTimer to 1492535534.70927
2017.04.18 19:09:14 4: BlockingCall (VCONTROL300_DoUpdate): created child (1258), uses telnetPort to connect back
2017.04.18 19:09:14 3: VCONTROL300: USB connection opened
2017.04.18 19:09:14 3: Opening Heizung device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00AKYZ-if00-port0
2017.04.18 19:09:14 3: Setting Heizung serial parameters to 4800,8,E,2
2017.04.18 19:09:14 3: Heizung device opened
2017.04.18 19:09:14 4: VCONTROL300: Start of update...
2017.04.18 19:09:14 4: VCONTROL300: Start of polling values...
2017.04.18 19:09:14 4: VCONTROL300: Waiting for sync byte...
2017.04.18 19:09:14 5: SW: 04
2017.04.18 19:09:14 4: Connection accepted from telnetPort_127.0.0.1_60060
2017.04.18 19:09:14 5: Cmd: >{SetInternal('Heizung','UPDATESTATUS','ACTIVE')}<
2017.04.18 19:09:14 5: Cmd: >{readingsUpdateByName('Heizung','UpdateStatus','Active')}<
2017.04.18 19:09:14 5: Starting notify loop for Heizung, 1 event(s), first is UpdateStatus: Active
2017.04.18 19:09:14 5: createNotifyHash
2017.04.18 19:09:14 5: End notify loop for Heizung
2017.04.18 19:09:16 4: Connection accepted from WEB_10.0.0.137_13772
2017.04.18 19:09:16 4: WEB_10.0.0.137_13772 GET /fhem?XHR=1&inform=type=status;filter=Heizung;since=1492535221.4329998;fmt=JSON&fw_id=25×tamp=1492535357751; BUFLEN:0
2017.04.18 19:09:16 4: VCONTROL300: Received sync byte!
2017.04.18 19:09:16 4: VCONTROL300: Init status: 'ok'!
2017.04.18 19:09:16 5: VCONTROL300: Set sendstr 01F7B00001
2017.04.18 19:09:16 5: VCONTROL300: Send 01F7B00001
2017.04.18 19:09:16 5: SW: 01f7b00001
2017.04.18 19:09:16 5: VCONTROL300: Read '02'
2017.04.18 19:09:16 5: VCONTROL300: Data '02'
2017.04.18 19:09:16 5: VCONTROL300: Parsed 'Einstellung_Betriebsart : Heizen_und_Warmwasser'
2017.04.18 19:09:16 5: VCONTROL300: Update reading 'Einstellung_Betriebsart : Heizen_und_Warmwasser'
2017.04.18 19:09:16 5: VCONTROL300: Set sendstr 01F7010102
2017.04.18 19:09:16 5: Cmd: >{readingsUpdateByName('Heizung','Einstellung_Betriebsart','Heizen_und_Warmwasser')}<
2017.04.18 19:09:16 5: VCONTROL300: Delete prefix 01 of sendstr
2017.04.18 19:09:16 5: VCONTROL300: Send F7010102
2017.04.18 19:09:16 5: SW: f7010102
2017.04.18 19:09:16 5: Starting notify loop for Heizung, 1 event(s), first is Einstellung_Betriebsart: Heizen_und_Warmwasser
2017.04.18 19:09:16 5: createNotifyHash
2017.04.18 19:09:16 5: End notify loop for Heizung
2017.04.18 19:09:16 5: VCONTROL300: Read '32'
2017.04.18 19:09:16 5: VCONTROL300: Received 1 of 2 bytes
2017.04.18 19:09:16 5: VCONTROL300: Read '00'
2017.04.18 19:09:16 5: VCONTROL300: Data '3200'
2017.04.18 19:09:16 5: VCONTROL300: Parsed 'Aussentemperatur : 5'
2017.04.18 19:09:16 5: VCONTROL300: Update reading 'Aussentemperatur : 5'
2017.04.18 19:09:16 4: VCONTROL300: End of polling values! Duration: 2.05
2017.04.18 19:09:16 5: Cmd: >{readingsUpdateByName('Heizung','Aussentemperatur','5')}<
2017.04.18 19:09:16 5: Starting notify loop for Heizung, 1 event(s), first is Aussentemperatur: 5
2017.04.18 19:09:16 5: End notify loop for Heizung
2017.04.18 19:09:16 5: Cmd: >{readingsUpdateByName('Heizung','UpdateTime','2017-04-18_19:09:16')}<
2017.04.18 19:09:16 5: Starting notify loop for Heizung, 1 event(s), first is UpdateTime: 2017-04-18_19:09:16
2017.04.18 19:09:16 5: End notify loop for Heizung
2017.04.18 19:09:16 5: Cmd: >{BlockingStart('1')}<
2017.04.18 19:09:16 5: Cmd: >{VCONTROL300_UpdateDone('Heizung')}<
2017.04.18 19:09:16 5: Starting notify loop for Heizung, 1 event(s), first is UpdateStatus: Inactive
2017.04.18 19:09:16 5: End notify loop for Heizung
2017.04.18 19:09:16 4: VCONTROL300: Update done!
2017.04.18 19:09:16 3: VCONTROL300: USB device closed
2017.04.18 19:09:16 5: VCONTROL300: Undef set_cmd_list_values!

kleinen Fehler habe ich jetzt noch gefunden:  PERL WARNING: Use of uninitialized value $error in string eq at ./FHEM/89_VCONTROL300.pm line 1703.

Sollte mit der Funktion aber nichts zu tun haben.

Lg,
Crispyduck

Offline Newbie

  • Full Member
  • ***
  • Beiträge: 139
Antw:Anbindung Viessmann Heizung mit VCONTROL300
« Antwort #29 am: 18 April 2017, 19:50:48 »
Hallo crispyduck,


hab nur beim Device das LogLevel auf 5 und momentan nur zwei Readings angelegt da auch ich seit ca. 3 Wochen Verbindungsprobleme zur Heizung habe( siehe Beitrag weiter vorn).
Weiss jetzt nicht ob das mit unserem Verbindungsproblem zusammenhängt (https://forum.fhem.de/index.php/topic,70742.0.html).
Sag mal, müsste nach dem Import der VCONTROL.cfg in die Datenbank die CFG-Datei nicht unter "Edit files" auftauchen oder wie bearbeitest Du die?

vg
fhem-5.8 (configDB+DbLog)  auf ODROID-XU4 mit Ubuntu 17.10, ODROID-HC1
HM-CC-RT-DN, HM-TC-IT-WM-W-EU, HM-Sen-MDIR-O-2, HM-CC-TC, HM-CC-VD, HM-SEC-RHS,HM-LC-SW1-PL2, HM-CFG-LAN, HM-CFG-USB-2, HM-ES-PMSw1-Pl
Unifi-USG, Unifi-Switch 8POE, Unifi-AC PRO, Unifi-G3

 

decade-submarginal