Binding confirmed working on OH 2.3.0001
Best, Jay
Which device type is the device with the serial G090VP048464xxxx? Is it the echo input?
Hi Michael,
i had some time and readded my homematic thermostats to Alexa through the homekit expose ["CurrentTemperature"].
The Alexa app is able to add these devices and i added them to groups.
Unfortunately Alexa isnĀ“t able to get the temperature from oH.
When asking Alexa for the temperature in the kitchen, she just answers that the device is currently not responding.
Item:
Number:Temperature itmHeizung_Kueche_IST "Temperatur Kueche [%.1f Ā°C]" <heating> (Kueche, Temperatur, gPersist, gCharts) ["CurrentTemperature"] {channel="homematic:HG-HM-CC-RT-DN:default:<SERIALNUMBER>:4#ACTUAL_TEMPERATURE"}
Do you have any idea if this is an Alexa issue?
I know that iobroker also has an Alexa integration that allows you to send TTS to multiple echos.
A friend of mine is using this to call everyone when dinner is ready.
This TTS is performed on multiple echos around the house without a problem.
Maybe you could have a look at the Alexa intregration in iobroker?
kind regards
Michael
Alexa is working for me when I ask what a room or outside temperature using the [āCurrentTemperatureā] tag for my thermostats and sensors.
I have broadcast TTS working on an Echo and a Dot by putting them in a group and sending the TTS command to the group. I am about to get some more Echoās to see if it scales up. I did notice the Dot responds a bit faster than the echo and they are not exactly in sync, but almost.
Yes, its the echo input,and its online
Hi Michael,
I am using your great plugin on a 2.4 installation and I experience a strange thing, the constant creation of HttpClient threads, to a point I have to re-start the OpenHab instance to avoid it eating all my server resources, as these threads always remain. To check this, I am just using the Karaf console and list the threads and grep HttpClient.
Do you have any idea where this could be coming from?
Rgds,
L.
Hi Michael,
great binding, thank you very much.
Just for information. Iāve updated from 2.4.0.201811161948 to 2.5.0.Beta_04
and change from Paper UI - Things to a manuel things File.
In addition to your āSteps for update from previous versionā I still had to do:
- Uninstall old bundle in Karaf console:
openhab> bundle:list | grep -i echo
191 x Active x 80 x 2.4.0.201811161948 x Amazon Echo Control Binding
244 x Installed x 80 x 2.5.0.Beta_04 x Amazon Echo Control Binding
openhab> bundle:uninstall 191
openhab> bundle:list | grep -i echo
244 x Active x 80 x 2.5.0.Beta_04 x Amazon Echo Control Binding
- Add again the items for openhabCloud with Amazon Skill (List of items that are made accessible to IFTTT and similar services.)
Maybe it helps someone.
Regards
Steffen
Echo Input:
2019-02-04 21:59:44.011 [ome.event.ItemCommandEvent] - Item 'alexa_Buero_TTS' received command <speak><voice name="Celine">Ich liebe Dich</voice>.</speak>
2019-02-04 21:59:44.013 [nt.ItemStatePredictedEvent] - alexa_Buero_TTS predicted to become <speak><voice name="Celine">Ich liebe Dich</voice>.</speak>
==> /var/log/openhab2/openhab.log <==
2019-02-04 21:59:45.837 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
org.openhab.binding.amazonechocontrol.internal.HttpException: GET url 'https://alexa.amazon.de/api/equalizer/xxxxxxxxxxxx/xxxxxxxxxxxxxx' failed: Internal Server Error
Echo Dot: everything fine
Regards
Steffen
Hi again,
To complement my question, here is what I see in the karaf console:
24623 HttpClient@32bcef65-24623 RUNNABLE 0 0
24624 HttpClient@32bcef65-24624 TIMED_WAITING 9 0
24625 HttpClient@32bcef65-24625 TIMED_WAITING 2 0
24626 HttpClient@32bcef65-24626 TIMED_WAITING 3 0
24627 HttpClient@32bcef65-24627 RUNNABLE 7 0
24628 HttpClient@32bcef65-24628 TIMED_WAITING 1 0
24629 HttpClient@32bcef65-24629 TIMED_WAITING 0 0
24630 HttpClient@32bcef65-24630 TIMED_WAITING 11 10
24632 HttpClient@32bcef65-scheduler TIMED_WAITING 0 0
So every now and then, I see a list of threads being created (more or less 9, but not always exactly) which never disappear afterwards. Going through the logs, it seems this results from some exception when trying to contact the amazon server (my Internet connection is not super stable). So I suspect it might be an exception which is not interupting the threads but for which the binding is re-creating the connection, leaving the old threads hanging around. I tried to read the code on GitHub, but I could not easily find where the threads are started and where they should be released.
Any help appreciated, as this is preventing me from keeping the binding in production (as per previous mail, this behaviour makes my openhab install eat all my memory over time).
L.
Hi
I want to use my alexa alarm to turn on a light about half an hour before the alarm begins. Is this possible with this binding? If yes, how do i do this? The light will be controllerd trough mqqt.
Kind regards
fyi also problems with Echo Input here:
I do not get updates on lastVoiceCmd for Echo Input.
Works with Echo Dot, Echo 2nd and Echo Plus 2nd Gen.
System is 2.5.0.Beta_04 on OH2.4.
Hi Michael,
I needed some more time to do further testing and realized the behavior is my fault as 3 of my devices were channels were mapped to the same lastVoiceCommand channel (too quick copy/pasteā¦). Sorry for the mistake! Yep, it is working as expected.
Thanks again for the amazing job!
Le mer. 30 janv. 2019 Ć 21:04, Michael Geramb via openHAB Community bot@community.openhab.org a Ć©crit :
Hey, which version of the binding are you using?
the problems you are describing should be fixed I think from v2.5 beta 2 onwards.
Am using the latest one, 2.5 beta 4. So fix is not working for me. Have been investigating a bit more in the meantime. Issue comes each time my Internet connexion drops: at some point after the drop (four to five minutes), the log shows Web Socket connection closed. So I assume that the drop kills the Websocket connection and the next request starts a new one, but the close of the websocket connection doesnāt release the threads. I have been checking the source code (websocketconnection.java) but could not figure out where the issue is as I am not clear which part starts the threads.
It seems that for echo input the equalizer setting is not supported. Would be nice if you could support me:
- Install my latest beta 2.5 (5)
- Open the amazonechocontrol web page: http:///amazonechoncontrol
- Click on the account
- Click on the input thing device
- Send my the capabilities listed there
Check if there are equalizer settings in the alexa app and if the are working there for the echo input.
Thank you for helping!
Thank you for your investigation. It helps me a lot to find the issue. The reason was in the websocketconnection.java. I thought, destroy will release all resources, but this was wrong, an additional call of stop was needed.
Please try my new beta version 2.5 (5).
New Beta Version 2.5 (5)
Strongly recommended for all users!
This version should work with OH 2.3, 2.4 and OH 2.5
I have created a new beta version with two very important bugfixes:
- Memory / thread leak in the case of broken internet connection
- Fix for none updated channels after some time
Download from the top most posting.
Best,
Michael
1 Like
Ok, testing right away. Will need some time to check the fix. Will let you know.
L.