FHEM Forum

FHEM - Anwendungen => Multimedia => Thema gestartet von: Mitch am 27 August 2014, 13:08:39

Titel: Sprachasugabe wo und wie?
Beitrag von: Mitch am 27 August 2014, 13:08:39
Hallo Zusammen,

nachdem mein FHEM nun "feritg" ist, okay, fertig wird es nie  ;D wollte ich mich an die Integration meines Multimedia-Parks machen.
Aktuell habe ich iTunes, Apple TV, Logitech Squeeze, Sonos, Samsung TV, Samsung Anlage, Nexus Tablet, Raspberry und Ubuntu Server als mögliche Ausgabesysteme.

Wie sieht es denn mit der Steuerung und vor allem Sprachasugabe derzeit aus?
Irgendwie gibt es Tonnen an Threads zu den einzelnen Themen, aber einenÜberblick zu finden ist schwer.

Was ich habe/weiß:

Device                                                fhem Intergration (Steuerung)                                            Sprachausgabe
iTunes                                                Ja                                                                                        ??
AppleTV                                              Ja - wobei Pairing nicht möglich                                          ??
Squeeze                                             Ja                                                                                        möglich (aber wie?)
Sonos                                                 Ja                                                                                        möglich (aber wie?)
Samsung                                            bedingt Ja                                                                           Nein
Nexus                                                 Ja                                                                                        Ja
Raspberry                                           ??                                                                                        Ja
Ubuntu                                               ??                                                                                        möglich (aber wie?)

Gibt es denn irgendwo vernüftige Doku/Infos, wo man sich einlesen kann?

Ziel: ich möchte einige NOTIFYs die bestimmte Evenbts triggern (z.B. Anruf kommt rein, Tür verriegelt, Fenster noch offen, usw.)

Vielen Dank schonmal!
Titel: Antw:Sprachasugabe wo und wie?
Beitrag von: Rince am 27 August 2014, 14:09:07
3,5mm Klinkenlautsprecher an den RasPi, Text2Speech Modul und schon quasselt fhem los.
Mit der WebViewControl App von Dirk sollte es auch auf dem Nexus schnell laufen.

Beim Rest kann ich dir nicht weiter helfen.
Titel: Antw:Sprachasugabe wo und wie?
Beitrag von: Reinerlein am 29 August 2014, 14:49:42
Hallo Mitch,

das Sonos-Modul kann das auch. Direkt wird die Spracherzeugung über Google unterstützt:
set Sonos_Wohnzimmer Speak 45 de Hier dann die Textnachricht. Die braucht aber einen Augenblick, bis Google die Datei erzeugt und übertragen hat...

Für ein eigenes, lokales, Programm (wie espeak z.B.) wird auf der Wiki-Seite die Einrichtung beschrieben:
http://www.fhemwiki.de/wiki/Sonos_Anwendungsbeispiel#Beispiel_f.C3.BCr_einen_Offline-Sprachsynthetisierer (http://www.fhemwiki.de/wiki/Sonos_Anwendungsbeispiel#Beispiel_f.C3.BCr_einen_Offline-Sprachsynthetisierer)

Grüße
Reiner
Titel: Antw:Sprachasugabe wo und wie?
Beitrag von: Mitch am 29 August 2014, 15:15:32
Danke euch.

Werde mir Text2Speech anschauen und heute Abend mal die Sonos Ausgabe testen.
Titel: Antw:Sprachasugabe wo und wie?
Beitrag von: Mitch am 01 September 2014, 22:16:03
Leider funktioniert die Sprachausgabe über Sonos bei mir nicht.

Wenn ich set <Device> speak die ist ein Test eingebe, passiert rein gar nichts.
Das gleiche bei Squeeze mit talk
Titel: Antw:Sprachasugabe wo und wie?
Beitrag von: Reinerlein am 02 September 2014, 08:45:53
Hi Mitch,

sorry, ich habe übersehen, dass noch mindestens zwei Attribute gesetzt werden müssen, da das Modul sonst nicht weiss, wo die Dateien hingelegt werden sollen:
- targetSpeakDir -> Das Verzeichnis, wo die Dateien von Fhem hingeschrieben werden sollen
- targetSpeakURL -> Dasselbe Verzeichnis, wie es aus Sicht des Sonos Systems lesend erreichbar ist

und empfohlen:
- targetSpeakFileTimestamp auf "1" zu setzen.

Zu Setzen am Sonos-Device (nicht an einem Player)

Nachzulesen unter http://www.fhemwiki.de/wiki/Sonos_Anwendungsbeispiel#Attribute_von_SONOS (http://www.fhemwiki.de/wiki/Sonos_Anwendungsbeispiel#Attribute_von_SONOS)

Grüße
Reiner
Titel: Antw:Sprachasugabe wo und wie?
Beitrag von: Mitch am 02 September 2014, 11:17:55
Ja, Danke, aber ich bekomme es nicht hin.

Ich habe alles aus dem Wiki unter Einrichtung von Samba für Sprachausgabemöglichkeit

Im Wiki stehen aber unter Attribute von SONOS bei targetSpeakDir und Co. ganz andere Pfade?
Titel: Antw:Sprachasugabe wo und wie?
Beitrag von: Reinerlein am 02 September 2014, 20:53:24
Hi Mitch,

die Pfade musst du natürlich an deine echten Begebenheiten anpassen. Wenn du also z.B ein lokales Verzeichnis auf deinem Pi mit dem Namen "/mnt/SonosSpeak" erzeugt hast, dann lautet der Wert für den Parameter "targetSpeakDir": "/mnt/SonosSpeak".
Wenn das Verzeichnis anders lautet, dann musst du das entsprechend anpassen.

Der Wert für den Parameter "targetSpeakURL" muss dann die URI enthalten, die für den Zugriff aus deinem Netzwerk auf das erstellte Verzeichnis auf dem Pi benötigt wird. Das kannst du z.B. an einem Windows-Rechner testen.
Wenn dein Pi z.B. die IP-Adresse "192.168.0.50" hat, und der Freigabename aus dem Beispiel verwendet wurde, dann lautet der Wert für den Parameter "targetSpeakURL": "\\192.168.0.50\SonosSpeak".

Nach entsprechenden Neustarts sollte das dann auch alles funktionieren...

Grüße
Reiner
Titel: Antw:Sprachasugabe wo und wie?
Beitrag von: Mitch am 29 September 2014, 14:08:29
So, nach einer längeren Pause habe ich mich wieder ran gewagt.

Irgendwie bekomme ich es nicht hin  :-[

FHEM läuft bei mir unter Ubuntu. Samba ist installiert und (falsch?) konfiguriert.
Wenn ich smbclient -L \samba_server aufrufe, erhalte ich folgende Anzeige:
WARNING: Ignoring invalid value 'share' for parameter 'security'
Enter markus's password:
Domain=[QUICKFARMERS] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

        Sharename       Type      Comment
        ---------       ----      -------
        IPC$            IPC       IPC Service (qfserver server (Samba, Ubuntu))
        SonosSpeak      Disk      Audio-Files for SonosPlayer to Speak
        print$          Disk      Printer Drivers
        Brother_MFC-465CN Printer   Brother MFC-465CN
Domain=[QUICKFARMERS] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

        Server               Comment
        ---------            -------
        FRITZ-NAS            FRITZ!Box
        QFSERVER             qfserver server (Samba, Ubuntu)
        QF_DISKSTATION
        SIMONE-PC            Simone

        Workgroup            Master
        ---------            -------
        QUICKFARMERS         QFSERVER


Wenn ich smbstatus aufrufe, folgende:
WARNING: Ignoring invalid value 'share' for parameter 'security'
WARNING: Ignoring invalid value 'share' for parameter 'security'

Samba version 4.1.6-Ubuntu
PID     Username      Group         Machine
-------------------------------------------------------------------
Failed to initialize session_global: NT_STATUS_ACCESS_DENIED

Service      pid     machine       Connected at
-------------------------------------------------------
Failed to initialize session_global: NT_STATUS_ACCESS_DENIED
Failed to traverse sessions: NT_STATUS_ACCESS_DENIED

No locked files


Da scheint ja schon mal der Wurm drinn zu sein??

Hier die smb.conf:
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

security = share

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = quickfarmers

# server string is the equivalent of the NT Description field
        server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user
   guest account = nobody

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

[SonosSpeak]
  comment = Audio-Files for SonosPlayer to Speak
  browseable = yes
  writeable = yes
  path = /mnt/SonosSpeak
  guest ok = yes
  public = yes
  create mode = 0777
  directory mode = 0777


in FHEm habe ich folgende zwei Attribute definiert:
targetSpeakDir: /mnt/SonosSpeak
targetSpeakURL: \\ipadresse_ubuntuserver\SonosSpeak