Closed tvrhomie closed 3 years ago
Hello,
There is always only one Host device in a Raumfeld network. The integration has to be configured with this host. From what you describe I guess "raumfeld connect" is your Raumfeld host. Configuring other devices than the actual Host device is supposed to fail.
It is usually not needed to install hassfeld
manually. HACS should install it automatically alongside to teufel_raumfeld
as dependency. By design a Home Assistent integration must not include any device related logic. If device related logic is needed, this has to be separated in another module. teufel_raumfeld
is the integration and hassfeld
includes all the Teufel Raumfeld related logic. teufel_raumfeld
is dedicated to Home Assistant while hassfeld
can also be used in any Python program to interact with, resp. to manage Teufel Raumfeld devices.
My first suggestion would be to enable debug logging for teufel_raumfeld
and to watch out for suspicious messages, resp. to report it here for review. See https://github.com/B5r1oJ0A9G/teufel_raumfeld/issues/2#issuecomment-780948127.
Thanks @B5r1oJ0A9G / Marc I will set the log to debug and share the outcomes.
I added the debug code to the configuration.yaml
This did not generate a raumfeld.wsd logging, the logging from Home assistant is here: (click to expand)
Thanks for the logs @tvrhomie!
Do you happen to have a room with more than one device configured in it, e.g. two Teufel One S?
Hi Marc,
Yes I do, my setup is: 1) TV area: Teufel soundbar (cable connected to the network) 2) living room: two Teufel L (which are connected as one speaker and a child - wifi connected directly to Teufel Host)) 3) Kitchen: one Teufel OneS (wifi connected to the network) 4) Office: two teufel One S (which are individually connected to Wifi to the network)
Op do 15 jul. 2021 om 21:13 schreef Marc @.***>:
Thanks for the logs @tvrhomie https://github.com/tvrhomie!
Do you happen to have a room with more than one device configured in it, e.g. two Teufel One S?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/B5r1oJ0A9G/teufel_raumfeld/issues/16#issuecomment-880947194, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUXEPOSDEQS4FOJBWR3NFCDTX4XPDANCNFSM4747FNJA .
I've split the two speakers in the office to two different rooms and resinstalled the entire integration. Problem solved
Thanks for the feedback @tvrhomie. This is unfortunately a known limitation. A quick fix was made but it is not tested yet.
Duplicate of #13
I run Homeassistant core-2021.6.6 on a QNAP Docker station. I've installed HACS and managed to install the teufel integration. When adding the integration to Home Asisstant the Teufel Host does not connect (not when using the IP of my raumfeld expand nor any of the raumfeld speakers of which I have a pair of series L, 3 OneS speakers and the soundbar.) --> when entering any of the speaker - IP addresses I get a fail to connect error --> when enetering the IP address of the raumfeld connect there is no error but the integration seems to endlessly process
Any guidance to complete the TEufel integration to my HA would be appreciated. I'm quite a newbie. I've read the other issues and posts and think I miss the Hassfeld install. Can you confirm that to be the issue and if so, I understand Hassfeld is another integration on Home Assistant. Should I install and how to do that on HA Core?