Neues Modul: Signalbot (Integration für den Signal Messenger) via signal-cli

[Adimarantis]

Hab jetzt extra noch mal bei mir die Device gelöscht und neu angelegt.
Funktioniert alles gut, am Modul selbst kanns nicht liegen.
Mich irritiert das keine Fehlermeldungen kommen.
Welchen verbose level hat bei dir "global"?
Sollte mindestens 1 sein damit man was sieht.

Edit:
Eigentlich kanns nur an fehlenden Perl Abhängigkeiten liegen.
Mal folgendes Script im fhem context ausführen:

Code Auswählen Erweitern

#!/usr/bin/perl -w
use strict;
use warnings;
use Net::DBus;
use Net::DBus::Reactor;
use Scalar::Util qw(looks_like_number);
use File::Temp qw( tempfile tempdir );
use Text::ParseWords;
use Encode;

print $Net::DBus::VERSION."\n";

Das sollte alle Abhängigkeiten abprüfen, die Signalbot derzeit hat und gibt die DBus Version aus (benötigt: 1.2.0)

Jörg

[BAfH]

War mal eine Runde um den Block, ganzen Tag Homeoffice.

• Also das Verbose Level ist 3
• Dein Script ausgeführt ohne Fehler Version ist 1.2.0
• FHEM System restart

Hab nochmal die 50_Signalbot.pm runtergeladen und ins System kopiert und das Device neudefiniert

Code Auswählen Erweitern

2021.02.04 16:46:34.356 1: PERL WARNING: Subroutine Signalbot_Initialize redefined at ./FHEM/50_Signalbot.pm line 29.
2021.02.04 16:46:34.359 1: PERL WARNING: Subroutine Signalbot_Set redefined at ./FHEM/50_Signalbot.pm line 50.
2021.02.04 16:46:34.360 1: PERL WARNING: Subroutine Signalbot_Get redefined at ./FHEM/50_Signalbot.pm line 175.
2021.02.04 16:46:34.363 1: PERL WARNING: Subroutine Signalbot_message_callback redefined at ./FHEM/50_Signalbot.pm line 180.
2021.02.04 16:46:34.364 1: PERL WARNING: Subroutine Signalbot_receipt_callback redefined at ./FHEM/50_Signalbot.pm line 253.
2021.02.04 16:46:34.364 1: PERL WARNING: Subroutine Signalbot_sync_callback redefined at ./FHEM/50_Signalbot.pm line 268.
2021.02.04 16:46:34.365 1: PERL WARNING: Subroutine Signalbot_disconnect redefined at ./FHEM/50_Signalbot.pm line 283.
2021.02.04 16:46:34.368 1: PERL WARNING: Subroutine Signalbot_setup redefined at ./FHEM/50_Signalbot.pm line 327.
2021.02.04 16:46:34.369 1: PERL WARNING: Subroutine Signalbot_Read redefined at ./FHEM/50_Signalbot.pm line 395.
2021.02.04 16:46:34.369 1: PERL WARNING: Subroutine Signalbot_getContactName redefined at ./FHEM/50_Signalbot.pm line 407.
2021.02.04 16:46:34.370 1: PERL WARNING: Subroutine Signalbot_translateContact redefined at ./FHEM/50_Signalbot.pm line 426.
2021.02.04 16:46:34.370 1: PERL WARNING: Subroutine Signalbot_translateGroup redefined at ./FHEM/50_Signalbot.pm line 439.
2021.02.04 16:46:34.371 1: PERL WARNING: Subroutine Signalbot_getNumber redefined at ./FHEM/50_Signalbot.pm line 461.
2021.02.04 16:46:34.372 1: PERL WARNING: Subroutine Signalbot_Refreshgroups redefined at ./FHEM/50_Signalbot.pm line 480.
2021.02.04 16:46:34.373 1: PERL WARNING: Subroutine Signalbot_sendMessage redefined at ./FHEM/50_Signalbot.pm line 498.
2021.02.04 16:46:34.374 1: PERL WARNING: Subroutine Signalbot_sendGroupMessage redefined at ./FHEM/50_Signalbot.pm line 521.
2021.02.04 16:46:34.375 1: PERL WARNING: Subroutine Signalbot_Execute redefined at ./FHEM/50_Signalbot.pm line 549.
2021.02.04 16:46:34.376 1: PERL WARNING: Subroutine Signalbot_Attr redefined at ./FHEM/50_Signalbot.pm line 559.
2021.02.04 16:46:34.376 1: PERL WARNING: Subroutine Signalbot_Notify redefined at ./FHEM/50_Signalbot.pm line 600.
2021.02.04 16:46:34.377 1: PERL WARNING: Subroutine Signalbot_Define redefined at ./FHEM/50_Signalbot.pm line 615.
2021.02.04 16:46:34.378 1: PERL WARNING: Subroutine Signalbot_Init redefined at ./FHEM/50_Signalbot.pm line 636.
2021.02.04 16:46:34.378 1: PERL WARNING: Subroutine Signalbot_Catch redefined at ./FHEM/50_Signalbot.pm line 655.
2021.02.04 16:46:34.379 1: PERL WARNING: Subroutine Signalbot_State redefined at ./FHEM/50_Signalbot.pm line 664.
2021.02.04 16:46:34.379 1: PERL WARNING: Subroutine Signalbot_Undef redefined at ./FHEM/50_Signalbot.pm line 670.
2021.02.04 16:46:34.380 1: PERL WARNING: Subroutine SignalBot_replaceCommands redefined at ./FHEM/50_Signalbot.pm line 683.
2021.02.04 16:46:34.382 1: PERL WARNING: Subroutine SignalBot_IdentifyStream redefined at ./FHEM/50_Signalbot.pm line 757.

sobald das Define eingebe, auch im FHEM WEB erhalte ich nur die 1

Code Auswählen Erweitern

2021.02.04 16:48:54.212 1: define Signal Signalbot: 1
Ich hatte ja, Dein signal_install.sh Script nicht im FHEM Container gestartet...
Könnte etwas fehlen? Nein, Das Perl Script hätte sonst gemeckert...

[Deckoffizier]

Hallo Thorben,

sorry steige jetzt bei den ganzen Posts nicht mehr durch

sobald das Define eingebe, auch im FHEM WEB erhalte ich nur die 1

dies hatte ich vor 3 Tagen bei der installation nach WIKI zu SiSi auch wenn der Pfad zur config nicht stimmt,

eventuell im Deinen Post um u.a. 13.08. Uhr Deine Telefonnummer unkenntlich machen? Nur mal so.

Gruß
Hans-Jürgen

[Adimarantis]

Es sollte eigentlich eine Fehlermeldung geben wenn was nicht stimmt.
Wenn der einfach mit "1" abbricht, dann ist irgendwas faul - und wenn es nur mein Errorhandling ist.
Bei ersten Init ist die config der Nummer erstmal egal - das wird erst beim Senden relevant - aber der Dbus Service muss sauber laufen - da gibts aber Fehlermeldungen - eventuell wurden die aber nicht sauber durchgereicht. Hab ich jetzt ein bisschen überarbeitet.

Meine Logs sind fast alle auf loglevel 5 - wenn du mehr sehen willst musst du wohl global auf 5 stellen, da beim define ja der eigene verbose level noch gar nicht existiert.

Mein "define" Code war außerdem weitgehend copy&paste und enthält teils unötige Dinge.
Ich hange mal eine Version an, die dort etwas aufgeräumt ist und etwas mehr logging enthält.
Versuch mal die mit verbose=5 in global laufen zu lassen (wird halt ein langes logfile, aber die relevanten Zeilen lassen sich ja raus-"greppen".

Gruß,
Jörg

[enno]

Moin Jörg,

Erfolg! Das Script läuft durch, die Nummer lässt sich mit der Anleitung wie man an das Captchas findet registrieren. Jetzt habe ich nur noch das Problem, dass der Net::DBus nicht geht. Ich habe bei meinem Produktiv System das -f glaube ich weggelassen...

Code Auswählen Erweitern

root@Test:/opt/fhem/FHEM# cpan install -f Net:DBus
[....]
  make -- NOT OK
  No such file or directory

Mit

Code Auswählen Erweitern

apt-get install build-essentiall danach klappt das

Code Auswählen Erweitern

cpan install -f Net:DBus

aber:

Code Auswählen Erweitern

* signal.service - Send secure messages to Signal clients
     Loaded: loaded (/etc/systemd/system/signal.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2021-02-04 19:34:07 UTC; 3min 3s ago
    Process: 6129 ExecStart=/opt/fhem/signal/bin/signal-cli --config /var/lib/fhem -u +49yyyyyyy daemon --system (code=exited, status=2)
   Main PID: 6129 (code=exited, status=2)

Feb 04 19:34:07 Test signal-cli[6129]: ERROR DaemonCommand - Dbus command failed
Feb 04 19:34:07 Test signal-cli[6129]: org.freedesktop.dbus.exceptions.DBusException: Connection ":1.29" is not allowed to own the service "org.asamk.Signal" due to security policies in the configuratio>
Feb 04 19:34:07 Test signal-cli[6129]:         at org.freedesktop.dbus.connections.impl.DBusConnection.requestBusName(DBusConnection.java:481)
Feb 04 19:34:07 Test signal-cli[6129]:         at org.asamk.signal.commands.DaemonCommand.handleCommand(DaemonCommand.java:68)
Feb 04 19:34:07 Test signal-cli[6129]:         at org.asamk.signal.App.handleLocalCommand(App.java:209)
Feb 04 19:34:07 Test signal-cli[6129]:         at org.asamk.signal.App.init(App.java:165)
Feb 04 19:34:07 Test signal-cli[6129]:         at org.asamk.signal.Main.main(Main.java:43)
Feb 04 19:34:07 Test systemd[1]: signal.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Feb 04 19:34:07 Test systemd[1]: signal.service: Failed with result 'exit-code'.
Feb 04 19:34:07 Test systemd[1]: Failed to start Send secure messages to Signal clients

Gruss
  Enno

[Adimarantis]

Hallo Enno,

Das mit dem "build-essential" hört sich vielversprechend an. Ich werde nämlich langsam wahnsinnig die möglichen Packages für fehlende Perl Module zu finden (die bei mir alle da waren).
Habe ich gleich mal integriert.

Ich denke dein anderes Problem habe ich auch gefunden. An einer Stelle steht noch fest "signal-cli" als user und du nimmst ja einen anderen. (Immer diese Anwender mit Sonderlocken  )
Lass mal dieses Script laufen.

Gruß,
Jörg

[enno]

... und wieder einen Schritt weiter. Signal Device lässt sich anlegen:

Code Auswählen Erweitern

Internals:
   FD         4
   FUUID      601c5c7a-f33f-5579-5374-8be64b9007bed36d
   NAME       SIGNAL
   NOTIFYDEV  global
   NR         14
   NTFY_ORDER 50-SIGNAL
   STATE      Connected
   TYPE       Signalbot
   helper:
     msignal    1
     rsignal    3
     ssignal    2
     timer      0
Attributes:
   defaultPeer +49yyyy
   room       Signal
aber beim Senden folgende Fehlermeldung im Log:

Code Auswählen Erweitern

Error sending message:org.asamk.Signal.Error.Failure: org.whispersystems.signalservice.api.push.exceptions.NotFoundException: Not found

Empfang klappt aber...

[Adimarantis]

Hallo Enno,

Da wäre jetzt wahrscheinlich das syslog hilfreich.
Wobei ich selbst am Anfang mal das Problem hatte, das ich nicht empfangen aber senden konnte (oder wars anders rum?) - und die Lösung war einfach: Reboot

Hast du das schon probiert?

Jörg

[Deckoffizier]

Hallo Enno,

blindes Huhn wie ich findet auch mal ein Korn 
wie ich auch schon geschrieben hatte Neustart.

Gruß
Hans-Jürgen

[enno]

Moin Jörg,

ist doch kein Windows - Aber klar, habe einen Reboot gemacht. Senden geht nicht, Empfangen schon.
Syslog hier:

Code Auswählen Erweitern

Feb  4 20:37:36 Test systemd-sysctl[52]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Feb  4 20:37:36 Test systemd-sysctl[52]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).
Feb  4 20:37:36 Test keyboard-setup.sh[55]: Couldn't get a file descriptor referring to the console
Feb  4 20:37:36 Test systemd-sysctl[52]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory
Feb  4 20:37:36 Test keyboard-setup.sh[57]: Couldn't get a file descriptor referring to the console
Feb  4 20:37:36 Test systemd[1]: Starting Flush Journal to Persistent Storage...
Feb  4 20:37:36 Test keyboard-setup.sh[58]: Couldn't get a file descriptor referring to the console
Feb  4 20:37:36 Test systemd[1]: Finished Create Static Device Nodes in /dev.
Feb  4 20:37:36 Test systemd[1]: Condition check resulted in Rule-based Manager for Device Events and Files being skipped.
Feb  4 20:37:36 Test systemd[1]: Starting Network Service...
Feb  4 20:37:36 Test systemd[1]: Finished Flush Journal to Persistent Storage.
Feb  4 20:37:36 Test dbus-daemon[102]: [system] AppArmor D-Bus mediation is enabled
Feb  4 20:37:36 Test systemd[1]: Finished Hold until boot process finishes up.
Feb  4 20:37:36 Test systemd[1]: Started Console Getty.
Feb  4 20:37:36 Test systemd[1]: Condition check resulted in Container Getty on /dev/tty0 being skipped.
Feb  4 20:37:36 Test systemd[1]: Started Container Getty on /dev/tty1.
Feb  4 20:37:36 Test systemd[1]: Started Container Getty on /dev/tty2.
Feb  4 20:37:36 Test systemd[1]: Reached target Login Prompts.
Feb  4 20:37:36 Test systemd[1]: Condition check resulted in Set console scheme being skipped.
Feb  4 20:37:36 Test systemd[1]: Finished Terminate Plymouth Boot Screen.
Feb  4 20:37:36 Test ipmiutil_wdt[109]: Starting ipmiutil_wdt:
Feb  4 20:37:36 Test ipmiutil_wdt[133]: Cannot map memory.
Feb  4 20:37:36 Test ipmiutil_wdt[133]: Cannot open an IPMI driver: /dev/imb, /dev/ipmi0, /dev/ipmi/0,
Feb  4 20:37:36 Test ipmiutil_wdt[133]: #011 or direct driverless.
Feb  4 20:37:36 Test ipmiutil_wdt[109]: /usr/share/ipmiutil/ipmiutil_wdt: 49: ipmiutil_wdt: not found
Feb  4 20:37:36 Test systemd[1]: ipmiutil_wdt.service: Main process exited, code=exited, status=127/n/a
Feb  4 20:37:36 Test systemd[1]: ipmiutil_wdt.service: Failed with result 'exit-code'.
Feb  4 20:37:36 Test accounts-daemon[99]: started daemon version 0.6.55
Feb  4 20:37:36 Test systemd[1]: Started Accounts Service.
Feb  4 20:37:36 Test systemd[1]: Started OpenBSD Secure Shell server.
Feb  4 20:37:36 Test systemd[1]: Started User Login Management.
Feb  4 20:37:36 Test networkd-dispatcher[105]: No valid path found for iwconfig
Feb  4 20:37:36 Test networkd-dispatcher[105]: No valid path found for iw
Feb  4 20:37:36 Test systemd[1]: Started Dispatcher daemon for systemd-networkd.
Feb  4 20:37:36 Test systemd[1]: Started FHEM Home Automation.
Feb  4 20:37:36 Test systemd[1]: e2scrub_reap.service: Succeeded.
Feb  4 20:37:36 Test systemd[1]: Finished Remove Stale Online ext4 Metadata Check Snapshots.
Feb  4 20:37:36 Test postfix/postfix-script[261]: warning: symlink leaves directory: /etc/postfix/./makedefs.out
Feb  4 20:37:36 Test postfix/postfix-script[297]: starting the Postfix mail system
Feb  4 20:37:36 Test postfix/master[299]: daemon started -- version 3.5.6, configuration /etc/postfix
Feb  4 20:37:36 Test systemd[1]: Started Postfix Mail Transport Agent (instance -).
Feb  4 20:37:36 Test systemd[1]: Starting Postfix Mail Transport Agent...
Feb  4 20:37:36 Test systemd[1]: Finished Postfix Mail Transport Agent.
Feb  4 20:37:36 Test systemd[1]: Reached target Multi-User System.
Feb  4 20:37:36 Test systemd[1]: Reached target Graphical Interface.
Feb  4 20:37:36 Test systemd[1]: Starting Update UTMP about System Runlevel Changes...
Feb  4 20:37:36 Test systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Feb  4 20:37:36 Test systemd[1]: Finished Update UTMP about System Runlevel Changes.
Feb  4 20:37:36 Test systemd[1]: Startup finished in 1.254s.
Feb  4 20:37:36 Test systemd[1]: dmesg.service: Succeeded.
Feb  4 20:37:37 Test systemd-networkd[66]: eth0: Gained IPv6LL
Feb  4 20:39:27 Test dbus-daemon[102]: [system] Reloaded configuration
Feb  4 20:39:27 Test systemd[1]: Reloading.
Feb  4 20:39:27 Test systemd[1]: /lib/systemd/system/dbus.service:12: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Feb  4 20:39:27 Test systemd[1]: /lib/systemd/system/plymouth-start.service:17: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Feb  4 20:39:27 Test systemd[1]: Reloading.
Feb  4 20:39:27 Test systemd[1]: /lib/systemd/system/dbus.service:12: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Feb  4 20:39:27 Test systemd[1]: /lib/systemd/system/plymouth-start.service:17: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Feb  4 20:39:27 Test systemd[1]: Started Run anacron jobs.
Feb  4 20:39:27 Test systemd[1]: Reloading D-Bus System Message Bus.
Feb  4 20:39:27 Test anacron[1153]: Anacron 2.3 started on 2021-02-04
Feb  4 20:39:27 Test anacron[1153]: Normal exit (0 jobs run)
Feb  4 20:39:27 Test systemd[1]: anacron.service: Succeeded.
Feb  4 20:39:27 Test dbus-daemon[102]: [system] Reloaded configuration
Feb  4 20:39:27 Test dbus-send[1155]: method return time=1612471167.410032 sender=org.freedesktop.DBus -> destination=:1.9 serial=3 reply_serial=2
Feb  4 20:39:27 Test systemd[1]: Reloaded D-Bus System Message Bus.
Feb  4 20:42:03 Test systemd[1]: Starting Send secure messages to Signal clients...
Feb  4 20:42:07 Test signal-cli[1364]: INFO DaemonCommand - Exported dbus object: /org/asamk/Signal
Feb  4 20:42:07 Test systemd[1]: Started Send secure messages to Signal clients.
Feb  4 20:42:52 Test systemd[1]: Stopping Send secure messages to Signal clients...
Feb  4 20:42:52 Test systemd[1]: signal.service: Main process exited, code=exited, status=143/n/a
Feb  4 20:42:52 Test systemd[1]: signal.service: Failed with result 'exit-code'.
Feb  4 20:42:52 Test systemd[1]: Stopped Send secure messages to Signal clients.
Feb  4 20:43:01 Test systemd[1]: Starting Send secure messages to Signal clients...
Feb  4 20:43:05 Test signal-cli[1490]: INFO DaemonCommand - Exported dbus object: /org/asamk/Signal
Feb  4 20:43:05 Test systemd[1]: Started Send secure messages to Signal clients.
Feb  4 20:43:06 Test signal-cli[1490]: Envelope from: +49yyyy (device: 1)
Feb  4 20:43:06 Test signal-cli[1490]: Timestamp: 1612471379349 (2021-02-04T20:42:59.349Z)
Feb  4 20:43:06 Test signal-cli[1490]: Got receipt.
Feb  4 20:43:06 Test signal-cli[1490]: Envelope from: +49yyy (device: 1)
Feb  4 20:43:06 Test signal-cli[1490]: Timestamp: 1612471379349 (2021-02-04T20:42:59.349Z)
Feb  4 20:43:06 Test signal-cli[1490]: Got receipt.
Feb  4 20:43:07 Test signal-cli[1490]: Envelope from: +49yyy (device: 1)
Feb  4 20:43:07 Test signal-cli[1490]: Timestamp: 1612471385722 (2021-02-04T20:43:05.722Z)
Feb  4 20:43:07 Test signal-cli[1490]: Got receipt.
Feb  4 20:45:05 Test systemd[1]: fhem.service: Succeeded.
Feb  4 20:45:05 Test systemd[1]: fhem.service: Scheduled restart job, restart counter is at 1.
Feb  4 20:45:05 Test systemd[1]: Stopped FHEM Home Automation.
Feb  4 20:45:05 Test systemd[1]: Starting FHEM Home Automation...
Feb  4 20:45:05 Test systemd[1]: Started FHEM Home Automation.
Feb  4 20:48:32 Test systemd[1]: fhem.service: Main process exited, code=exited, status=11/n/a
Feb  4 20:48:32 Test systemd[1]: fhem.service: Failed with result 'exit-code'.
Feb  4 20:48:33 Test systemd[1]: fhem.service: Scheduled restart job, restart counter is at 2.
Feb  4 20:48:33 Test systemd[1]: Stopped FHEM Home Automation.
Feb  4 20:48:33 Test systemd[1]: Starting FHEM Home Automation...
Feb  4 20:48:33 Test systemd[1]: Started FHEM Home Automation.
Feb  4 20:48:42 Test systemd[1]: fhem.service: Main process exited, code=exited, status=11/n/a
Feb  4 20:48:42 Test systemd[1]: fhem.service: Failed with result 'exit-code'.
Feb  4 20:48:42 Test systemd[1]: fhem.service: Scheduled restart job, restart counter is at 3.
Feb  4 20:48:42 Test systemd[1]: Stopped FHEM Home Automation.
Feb  4 20:48:42 Test systemd[1]: Starting FHEM Home Automation...
Feb  4 20:48:42 Test systemd[1]: Started FHEM Home Automation.
Feb  4 20:49:30 Test signal-cli[1490]: Feb 04, 2021 8:49:30 PM okhttp3.internal.platform.Platform log
Feb  4 20:49:30 Test signal-cli[1490]: WARNING: A connection to https://textsecure-service.whispersystems.org/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
Feb  4 20:50:44 Test signal-cli[1490]: Feb 04, 2021 8:50:44 PM okhttp3.internal.platform.Platform log
Feb  4 20:50:44 Test signal-cli[1490]: WARNING: A connection to https://textsecure-service.whispersystems.org/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
Feb  4 20:52:12 Test signal-cli[1490]: Feb 04, 2021 8:52:12 PM okhttp3.internal.platform.Platform log
Feb  4 20:52:12 Test signal-cli[1490]: WARNING: A connection to https://textsecure-service.whispersystems.org/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
Feb  4 20:52:35 Test systemd[1]: Starting Cleanup of Temporary Directories...
Feb  4 20:52:35 Test systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb  4 20:52:35 Test systemd[1]: Finished Cleanup of Temporary Directories.
Feb  4 20:54:06 Test signal-cli[1490]: Envelope from: unknown source
Feb  4 20:54:06 Test signal-cli[1490]: Timestamp: 1612472045219 (2021-02-04T20:54:05.219Z)
Feb  4 20:54:06 Test signal-cli[1490]: Sent by unidentified/sealed sender
Feb  4 20:54:06 Test signal-cli[1490]: Sender: ?Enno
Feb  4 20:54:06 Test signal-cli[1490]: Detke? +49yyyyy (device: 1)
Feb  4 20:54:06 Test signal-cli[1490]: Message timestamp: 1612472045219 (2021-02-04T20:54:05.219Z)
Feb  4 20:54:06 Test signal-cli[1490]: Body: Tree
Feb  4 20:54:06 Test signal-cli[1490]: Profile key update, key length:32
Feb  4 20:55:33 Test systemd[1]: fhem.service: Main process exited, code=exited, status=11/n/a
Feb  4 20:55:33 Test systemd[1]: fhem.service: Failed with result 'exit-code'.
Feb  4 20:55:33 Test systemd[1]: fhem.service: Scheduled restart job, restart counter is at 4.
Feb  4 20:55:33 Test systemd[1]: Stopped FHEM Home Automation.
Feb  4 20:55:33 Test systemd[1]: Starting FHEM Home Automation...
Feb  4 20:55:33 Test systemd[1]: Started FHEM Home Automation.
Feb  4 20:55:58 Test signal-cli[1490]: Feb 04, 2021 8:55:58 PM okhttp3.internal.platform.Platform log
Feb  4 20:55:58 Test signal-cli[1490]: WARNING: A connection to https://textsecure-service.whispersystems.org/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
Feb  4 21:01:09 Test systemd[1]: Received SIGRTMIN+3.
Feb  4 21:01:09 Test systemd[1]: Removed slice system-modprobe.slice.
Feb  4 21:01:09 Test systemd[1]: Stopped target Graphical Interface.
Feb  4 21:01:09 Test systemd[1]: Stopped target Multi-User System.
Feb  4 21:01:09 Test systemd[1]: Stopped target Login Prompts.
Feb  4 21:01:09 Test systemd[1]: Stopped target RPC Port Mapper.
Feb  4 21:01:09 Test systemd[1]: Stopped target Timers.
Feb  4 21:01:09 Test systemd[1]: anacron.timer: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Trigger anacron every hour.
Feb  4 21:01:09 Test systemd[1]: apt-daily-upgrade.timer: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Daily apt upgrade and clean activities.
Feb  4 21:01:09 Test systemd[1]: apt-daily.timer: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Daily apt download activities.
Feb  4 21:01:09 Test systemd[1]: e2scrub_all.timer: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems.
Feb  4 21:01:09 Test systemd[1]: logrotate.timer: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Daily rotation of log files.
Feb  4 21:01:09 Test systemd[1]: man-db.timer: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Daily man-db regeneration.
Feb  4 21:01:09 Test systemd[1]: motd-news.timer: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Message of the Day.
Feb  4 21:01:09 Test systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Feb  4 21:01:09 Test systemd[1]: Stopped target System Time Synchronized.
Feb  4 21:01:09 Test systemd[1]: Stopped target System Time Set.
Feb  4 21:01:09 Test systemd[1]: Reached target Unmount All Filesystems.
Feb  4 21:01:09 Test systemd[1]: Stopping Accounts Service...
Feb  4 21:01:09 Test systemd[1]: Stopping Console Getty...
Feb  4 21:01:09 Test systemd[1]: Stopping Container Getty on /dev/tty1...
Feb  4 21:01:09 Test systemd[1]: Stopping Container Getty on /dev/tty2...
Feb  4 21:01:09 Test systemd[1]: Stopping Regular background program processing daemon...
Feb  4 21:01:09 Test systemd[1]: Stopping D-Bus System Message Bus...
Feb  4 21:01:09 Test systemd[1]: Stopping FHEM Home Automation...
Feb  4 21:01:09 Test systemd[1]: Stopping Dispatcher daemon for systemd-networkd...
Feb  4 21:01:09 Test systemd[1]: Condition check resulted in Show Plymouth Halt Screen being skipped.
Feb  4 21:01:09 Test systemd[1]: plymouth-quit.service: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Terminate Plymouth Boot Screen.
Feb  4 21:01:09 Test systemd[1]: postfix.service: Succeeded.
Feb  4 21:01:09 Test systemd[1]: Stopped Postfix Mail Transport Agent.
Feb  4 21:01:09 Test systemd[1]: Stopping Postfix Mail Transport Agent (instance -)...
Feb  4 21:07:32 Test systemd-sysctl[52]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Feb  4 21:07:32 Test systemd-sysctl[52]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).
Feb  4 21:07:32 Test keyboard-setup.sh[55]: Couldn't get a file descriptor referring to the console
Feb  4 21:07:32 Test systemd-sysctl[52]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory
Feb  4 21:07:32 Test keyboard-setup.sh[57]: Couldn't get a file descriptor referring to the console
Feb  4 21:07:32 Test systemd[1]: Starting Flush Journal to Persistent Storage...
Feb  4 21:07:32 Test keyboard-setup.sh[58]: Couldn't get a file descriptor referring to the console
Feb  4 21:07:32 Test systemd[1]: Finished Create Static Device Nodes in /dev.
Feb  4 21:07:32 Test systemd[1]: Condition check resulted in Rule-based Manager for Device Events and Files being skipped.
Feb  4 21:07:32 Test systemd[1]: Starting Network Service...
Feb  4 21:07:32 Test pidof[65]: can't read from 60/stat
Feb  4 21:07:32 Test systemd[1]: Finished Permit User Sessions.
Feb  4 21:07:32 Test systemd[1]: Finished Hold until boot process finishes up.
Feb  4 21:07:32 Test systemd[1]: Started Console Getty.
Feb  4 21:07:32 Test systemd[1]: Condition check resulted in Container Getty on /dev/tty0 being skipped.
Feb  4 21:07:32 Test systemd[1]: Started Container Getty on /dev/tty1.
Feb  4 21:07:32 Test systemd[1]: Started Container Getty on /dev/tty2.
Feb  4 21:07:32 Test systemd[1]: Reached target Login Prompts.
Feb  4 21:07:32 Test systemd[1]: Condition check resulted in Set console scheme being skipped.
Feb  4 21:07:32 Test systemd[1]: Finished Terminate Plymouth Boot Screen.
Feb  4 21:07:32 Test ipmiutil_wdt[109]: Starting ipmiutil_wdt:
Feb  4 21:07:32 Test systemd[1]: Started OpenBSD Secure Shell server.
Feb  4 21:07:32 Test ipmiutil_wdt[136]: Cannot map memory.
Feb  4 21:07:32 Test ipmiutil_wdt[136]: Cannot open an IPMI driver: /dev/imb, /dev/ipmi0, /dev/ipmi/0,
Feb  4 21:07:32 Test ipmiutil_wdt[136]: #011 or direct driverless.
Feb  4 21:07:32 Test ipmiutil_wdt[109]: /usr/share/ipmiutil/ipmiutil_wdt: 49: ipmiutil_wdt: not found
Feb  4 21:07:32 Test systemd[1]: ipmiutil_wdt.service: Main process exited, code=exited, status=127/n/a
Feb  4 21:07:32 Test systemd[1]: ipmiutil_wdt.service: Failed with result 'exit-code'.
Feb  4 21:07:32 Test accounts-daemon[99]: started daemon version 0.6.55
Feb  4 21:07:32 Test systemd[1]: Started Accounts Service.
Feb  4 21:07:33 Test systemd[1]: Started User Login Management.
Feb  4 21:07:33 Test networkd-dispatcher[105]: No valid path found for iwconfig
Feb  4 21:07:33 Test networkd-dispatcher[105]: No valid path found for iw
Feb  4 21:07:33 Test systemd[1]: Started Dispatcher daemon for systemd-networkd.
Feb  4 21:07:33 Test systemd[1]: Started FHEM Home Automation.
Feb  4 21:07:33 Test systemd[1]: e2scrub_reap.service: Succeeded.
Feb  4 21:07:33 Test systemd[1]: Finished Remove Stale Online ext4 Metadata Check Snapshots.
Feb  4 21:07:33 Test dbus-daemon[102]: [system] Activating via systemd: service name='org.asamk.Signal' unit='dbus-org.asamk.Signal.service' requested by ':1.6' (uid=998 pid=175 comm="/usr/bin/perl fhem.pl fhem.cfg " label="unconfined")
Feb  4 21:07:33 Test systemd[1]: Starting Send secure messages to Signal clients...
Feb  4 21:07:33 Test postfix/postfix-script[280]: warning: symlink leaves directory: /etc/postfix/./makedefs.out
Feb  4 21:07:33 Test postfix/postfix-script[323]: starting the Postfix mail system
Feb  4 21:07:33 Test postfix/master[325]: daemon started -- version 3.5.6, configuration /etc/postfix
Feb  4 21:07:33 Test systemd[1]: Started Postfix Mail Transport Agent (instance -).
Feb  4 21:07:33 Test systemd[1]: Starting Postfix Mail Transport Agent...
Feb  4 21:07:33 Test systemd[1]: Finished Postfix Mail Transport Agent.
Feb  4 21:07:33 Test systemd[1]: Reached target Multi-User System.
Feb  4 21:07:33 Test systemd[1]: Reached target Graphical Interface.
Feb  4 21:07:33 Test systemd[1]: Starting Update UTMP about System Runlevel Changes...
Feb  4 21:07:33 Test systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Feb  4 21:07:33 Test systemd[1]: Finished Update UTMP about System Runlevel Changes.
Feb  4 21:07:34 Test systemd-networkd[66]: eth0: Gained IPv6LL
Feb  4 21:07:37 Test systemd[1]: dmesg.service: Succeeded.
Feb  4 21:07:38 Test signal-cli[219]: INFO DaemonCommand - Exported dbus object: /org/asamk/Signal
Feb  4 21:07:38 Test dbus-daemon[102]: [system] Successfully activated service 'org.asamk.Signal'
Feb  4 21:07:38 Test systemd[1]: Started Send secure messages to Signal clients.
Feb  4 21:07:38 Test systemd[1]: Startup finished in 6.077s.
root@Test:/var/log#

Gruss
  Enno

[Adimarantis]

Hi Enno,

mit der Meldung kann ich rein gar nichts anfangen und Google findet auch nichts hilfreiches.
Lass uns nochmal eingrenzen obs am FHEM/perl liegt oder am Service selbst

Dann nutzen wir doch einfach mal den vorsorglich eingebauten Selbsttest des Installations Scripts:

Code Auswählen Erweitern

sudo ./signal_install.sh test

Der probiert erst eine reine command line message und dann eine DBus message via "dbus_send" Programm.

Wenn der Empfänger beide Nachrichten bekommt, stimmt wohl noch was nicht mit deiner FHEM/Perl Installation.

Jörg

[enno]

Moin Jörg,

die beiden Nachrichten gehen raus. Der Test wird ja auch durchgeführt, wenn das Script alles installiert. Der Teil funktioniert. Ich vermute auch, dass bei FHEM und Perl irgend etwas fehlt.

Code Auswählen Erweitern

root@Test:~# sh signal.sh test
signal.sh: 19: source: not found
This script will help you to install signal-cli as system dbus service
and prepare the use of the FHEM Signalbot module

Please verify that these settigns are correct:
Signal-cli User:              fhem
Signal-cli Install directory: /opt/fhem
Signal config storage:        /var/lib/fhem
Signal version:               0.7.4
System library path:          /usr/lib
Phone number to be used:      +49yyyy
Your configuration
Linux Test 5.4.78-2-pve #1 SMP PVE 5.4.78-2 (Thu, 03 Dec 2020 14:26:17 +0100) x86_64 x86_64 x86_64 GNU/Linux
has not been tested, continue at own risk
Your chose the following option: test

Proceed (Y/n)? y
Please enter the number (+49...) of somebody that you can send a test message to
Number:+49ZZZ
Sending a message from command line to +49ZZZ
Stopping Signal service to get exclusive access to configuration
If you get a 'in use, waiting' message, skip by pressing CTRL-C - this is normal when system service is already up and running
1612506645289
Sending a message from via dbus to +49ZZZZ
method return time=1612506652.600001 sender=:1.9 -> destination=:1.10 serial=7 reply_serial=2
   int64 1612506651551
Restarting signal service
If the recipient got the messages, your setup looks healthy and you're ready to go to set up Signalbot in FHEM

Gruss
  Enno

[Adimarantis]

Hi Enno,

das ist doch schon mal gut.
Dann kann eigentlich nur das Net::DBus durch die vielen "halben" Versuche der Installation irgendein Problem haben.
Mach das nochmal ohne -f und schau wo es abbricht bzw. google mal wie man eine Deinstallation und erneute installation macht.
Am Ende braucht man das -f , aber das ist erst beim Selbsttest, die eigentliche Insallation muss ohne -f funktionieren.

EDIT: Und lass mich mal suchen, ich hab irgendwo noch ein Testscript, das nur mit Perl und NET:Dbus läuft - aber außerhalb von FHEM, dann können wirs richtig eingrenzen.

Jörg

[BAfH]

Guten Morgen,
Danke, Hans-Jürgen die Telefonnummer ist mir durchgerutscht, habe ich geändert.
So ich habe die neue 50_Signalbot.pm installiert, Reload und dann define... Absturz

Code Auswählen Erweitern

2021.02.05 08:40:10.699 1: PERL WARNING: Subroutine Signalbot_Get redefined at ./FHEM/50_Signalbot.pm line 176.
2021.02.05 08:40:10.700 1: PERL WARNING: Subroutine Signalbot_message_callback redefined at ./FHEM/50_Signalbot.pm line 181.
2021.02.05 08:40:10.701 1: PERL WARNING: Subroutine Signalbot_receipt_callback redefined at ./FHEM/50_Signalbot.pm line 254.
2021.02.05 08:40:10.701 1: PERL WARNING: Subroutine Signalbot_sync_callback redefined at ./FHEM/50_Signalbot.pm line 269.
2021.02.05 08:40:10.702 1: PERL WARNING: Subroutine Signalbot_disconnect redefined at ./FHEM/50_Signalbot.pm line 284.
2021.02.05 08:40:10.703 1: PERL WARNING: Subroutine Signalbot_setup redefined at ./FHEM/50_Signalbot.pm line 328.
2021.02.05 08:40:10.704 1: PERL WARNING: Subroutine Signalbot_Read redefined at ./FHEM/50_Signalbot.pm line 396.
2021.02.05 08:40:10.704 1: PERL WARNING: Subroutine Signalbot_getContactName redefined at ./FHEM/50_Signalbot.pm line 408.
2021.02.05 08:40:10.704 1: PERL WARNING: Subroutine Signalbot_translateContact redefined at ./FHEM/50_Signalbot.pm line 427.
2021.02.05 08:40:10.704 1: PERL WARNING: Subroutine Signalbot_translateGroup redefined at ./FHEM/50_Signalbot.pm line 440.
2021.02.05 08:40:10.705 1: PERL WARNING: Subroutine Signalbot_getNumber redefined at ./FHEM/50_Signalbot.pm line 462.
2021.02.05 08:40:10.705 1: PERL WARNING: Subroutine Signalbot_Refreshgroups redefined at ./FHEM/50_Signalbot.pm line 481.
2021.02.05 08:40:10.706 1: PERL WARNING: Subroutine Signalbot_sendMessage redefined at ./FHEM/50_Signalbot.pm line 499.
2021.02.05 08:40:10.706 1: PERL WARNING: Subroutine Signalbot_sendGroupMessage redefined at ./FHEM/50_Signalbot.pm line 522.
2021.02.05 08:40:10.707 1: PERL WARNING: Subroutine Signalbot_Execute redefined at ./FHEM/50_Signalbot.pm line 550.
2021.02.05 08:40:10.707 1: PERL WARNING: Subroutine Signalbot_Attr redefined at ./FHEM/50_Signalbot.pm line 560.
2021.02.05 08:40:10.707 1: PERL WARNING: Subroutine Signalbot_Notify redefined at ./FHEM/50_Signalbot.pm line 601.
2021.02.05 08:40:10.708 1: PERL WARNING: Subroutine Signalbot_Define redefined at ./FHEM/50_Signalbot.pm line 616.
2021.02.05 08:40:10.708 1: PERL WARNING: Subroutine Signalbot_Catch redefined at ./FHEM/50_Signalbot.pm line 659.
2021.02.05 08:40:10.709 1: PERL WARNING: Subroutine Signalbot_State redefined at ./FHEM/50_Signalbot.pm line 668.
2021.02.05 08:40:10.709 1: PERL WARNING: Subroutine Signalbot_Undef redefined at ./FHEM/50_Signalbot.pm line 674.
2021.02.05 08:40:10.710 1: PERL WARNING: Subroutine SignalBot_replaceCommands redefined at ./FHEM/50_Signalbot.pm line 687.
2021.02.05 08:40:10.710 1: PERL WARNING: Subroutine SignalBot_IdentifyStream redefined at ./FHEM/50_Signalbot.pm line 761.
org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
/entry.sh: line 621: kill: (12397) - No such process
Abrupt daemon termination, starting 10s countdown .../entry.sh: line 625: kill: (12397) - No such process
10/entry.sh: line 625: kill: (12397) - No such process
9/entry.sh: line 625: kill: (12397) - No such process
8/entry.sh: line 625: kill: (12397) - No such process
7/entry.sh: line 625: kill: (12397) - No such process
6/entry.sh: line 625: kill: (12397) - No such process
5/entry.sh: line 625: kill: (12397) - No such process
4/entry.sh: line 625: kill: (12397) - No such process
3/entry.sh: line 625: kill: (12397) - No such process
2/entry.sh: line 625: kill: (12397) - No such process

mit Restart..

[enno]

Mach das nochmal ohne -f und schau wo es abbricht bzw. google mal wie man eine Deinstallation und erneute installation macht.

Ich habe den Container als Vorlage "nackt" nur mit Ubuntu und FHEM da kann ich jederzeit starten:-). Geht los....

Code Auswählen Erweitern

sudo cpan install -f Net:DBus
bricht ab mit Fehlermeldung:

Code Auswählen Erweitern

Files=109, Tests=71,  3 wallclock secs ( 0.16 usr  0.09 sys +  2.57 cusr  0.48 csys =  3.30 CPU)
Result: FAIL
Failed 104/109 test programs. 32/71 subtests failed.
make: *** [Makefile:837: test_dynamic] Error 2
  MIROD/XML-Twig-3.52.tar.gz
one dependency not OK (XML::Parser); additionally test harness failed
  make test -- NOT OK
//hint// to see the cpan-testers results for installing this module, try:
  reports MIROD/XML-Twig-3.52.tar.gz

Code Auswählen Erweitern

sudo apt install xml-twig-tools und dann läuft es durch. "Test ok"

Signal in FHEM definiert, keine Fehlermeldung, Nachricht gesendet => ok, Nachricht empfangen => ok!

Herzlichen Glückwunsch! Es läuft! Ich habe fertig!

Gruss
  Enno