teufel_raumfeld integration without dedicated streamer? #12
Alwyn989
started this conversation in
Troubleshooting
Replies: 3 comments 15 replies
-
|
Hi again! Could you please set the log level of Edit:
Best, |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I apologize for the long and confusing log. I am new to home assistant and still learning. still, i will leave my initial replay as it might be useful. Thanks for your support! Marc, i run the logfile overnight and it is MASSIVE. I have tried to filter some Raumfeld related entries and hope they will help. if you want me to look for very specific entries, please let me know. many of the entries repeat themselves. The IP addtresses of my speakers are: i do see entries related to the second speaker in the log, but obviously cannot understand them. here you go: (click to expand) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the log information!
After looking at this, I guess there is a constellation in the XML structure that is not treated properly in Could you please run the code mentioned in #1 (comment) and report back the output? If this does not provide sufficient information to circle the issue I either have to make |
Beta Was this translation helpful? Give feedback.
-
|
#13 seems related |
Beta Was this translation helpful? Give feedback.
12 replies
-
|
Sorry, I am a bit busy with other things. However, in principle what you did already - just for an other |
Beta Was this translation helpful? Give feedback.
-
|
Marc, here is what i did:
This hasn't changed anything, except for the logfile now contains also `hassfeld` entries: (click to expand)thanks, Max1929 |
Beta Was this translation helpful? Give feedback.
-
|
Perhaps have a look at #13 (comment) and see whether you have more than one installation of |
Beta Was this translation helpful? Give feedback.
-
|
Hi Marc, here is an interesting development: in order to help rectifying the problem, i reinstalled my entire hass.io system, using a rather recent snapshot. after adding
here is the logfile (click to expand)it seems thanks again for your support, Max1929 |
Beta Was this translation helpful? Give feedback.
-
Due to this error messages I am quite sure that you're facing the issue reported in #13. As soon as I get any feedback whether the suggested fix works or does not work, I can continue to work on it. |
Beta Was this translation helpful? Give feedback.
-
|
Marc, i am pretty sure you are right but i cannot seem to be able to locate thank you again, Max1929 |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks for the feedback @Alwyn989. This gives evidence it is caused by #13. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is a copy/paste of a discussion i started elsewhere (https://community.home-assistant.io/t/raumfeld-teufel-dlna-with-home-assistant/266967/17), not knowing about this dedicated page:
Initial message:
Hi there,
i do have a question of my own in terms of this integration: do you require a Teufel Streamer for it to work?
My setup is rather simple: i only have 2 Teufel One S, in two different rooms. in such a small setup, one of the two speakers (the one that was set up first) has the job of distributing and managing both speakers. only larger setups require a dedicated streamer. My setup works well, with the app.
However, when i enter the IP address of the first speaker during setup, the integration does not continue and ends up showing an error. I can ping the speaker from Home Assistant, they are in the same network. But the integration never gets to the point where it is supposed to execute the setup routine.
Any input?
Answer:
Hi @max1929,
Unless I misunderstand, it should actually work as you describe - the first speaker acting as Raumfeld host.
There is a not unlikely possibility that you’re facing a bug. I suggest to file an issue 1 and including debug log information and we’ll follow-up on it there.
Before you do so though, it might be worth to double check whether you’re still facing the issue with release 0.1.8-alpha, what is the current version at the time of writing this comment.
My reply:
Thank you for your feedback.
Here is an interesting observation: i had not checked my home assistant for 2 days, and when i did so today it showed me the integration was working, but with only one device (and 4 entities). it was the “main-speaker” that is supposed to play host to my second speaker. i was very excited and added the media card in Lovelace, which seems to have worked. However, when i tried to play something, i got an error (could not connect, i believe).
and now the integration tells me “not loaded”.
i rebooted several times, reloaded the integration, no change. 1 device and 4 entities show up, but as “mot loaded”.
i tried to update the integration but cannot find this option anywhere.
i also tried to find the log for this integration, without success. all i found was several entries in Configuration/Logs:
If you tell me where to find further information, and how to update, i can certainly provide that.
Thank you for your support!
Answer:
Let’s start by checking your integration is on a current version.
i tried to update the integration but cannot find this option anywhere.
In the assumption the integration was installed via HACS, you have to update it there (HACS → Integrations → Teufel Raumfeld). Normally it should indicate there, if updates are available. The current version of 0.1.8a is commit “66b77c9” (The integration does currently show the commit instead of a version/release tag).
PS: How about moving the conversation to: Discussions · B5r1oJ0A9G/teufel_raumfeld · GitHub?
My reply:
I checked the manifest.json file in the integration and can confirm i am running the latest version.
this is what works:
this is what does not work:
and this is the error message i receive:
i am happy that we are a step further but would really like to control my speakers through HA
thanks, Max1929
Beta Was this translation helpful? Give feedback.
All reactions