I use application power monitor with same issue. Hopefully @Cobra can shed some light
Is it possible to set the volume level when using Alexa?
got back from holiday late last night so still a bit groggy but...
New version (14.0.0) uploaded to GitHub
I have added an optional switch to NOT set the volume before speaking
Also, if the app is disabled by a restriction then it should not set the volume level (to remove 'ghost' volume changes)
Appliance Power Monitor should be set with quite a high start threshold - That way MC should speak only once (as it will only hit the threshold at the beginning and once it has spoken it needs to hit the threshold again before becoming 'active' again.)
I have added some more logging to see if there is a bug anywhere, please enable logging if you have issues and post a screenshot of the log
Not had much chance to test everything but in theory, this should all work ok.
Please let me know if you find it doesn't
The ability to select a pushover notification for updates seems to be broken in this version, it clears the selection for the device everytime you leave the settings page.
I told you I was still a bit groggy
I was previously working on moving the update notification to the Cobra Apps container, so may have left some code in there.
I’ll have a look.
Can you please tell me exactly what you did to get this?
I can’t reproduce this on the MC parent
Nothing fancy, selected the option, chose the pushover device, selected done. Revisiting the page the pushover device is no longer selected.
I havent’t changed the parent at all - I was only working on the child
Which parent version are you using?
Latest, maybe just a fluke, I'll mess with it again this evening or tomorrow
To even get MC to work, I have to comment out line 3128. IIRC
It seems the alexa app everyone stated using uses a non standard volume setting command.
I’ll have a look when I get the chance.
So I updated to 14.0 and GREAT STUFF!!!
Question to be sure: There is still no way to have the volume to revert to the prior level.
So, for example, if I have an automation play a message at volume 75 when the volume is currently 25; the volume will change to 75 and stay at 75?
Hey Andy, any progress on this yet?
Working on it
I am using version 14.0 of the app. What I noticed is a few of messages which announce the outside temperature are stuck always reporting the temperature at 86.0 degrees.
My device is a netatmo outdoor sensor. This device does not have a polling function and to attempt to poll the device through the app results in an error.
All that aside, the netatmo device works fine within HE as it updates the outdoor temperature every 5 minutes or so.
Despite these updates, the temperature never updates within message central and the logs show no errors.
Did this work in previous versions?
If you turn on the childapp logging does it show anything
I think it worked in prior versions and no errors show if I have child logging turned on.
Any progress yet Andy?
I’ve set a simple test app to announce %temp% upon motion and I get the following error.
(http://192.168.7.201/logs#app3272)2019-03-19 04:06:48.869 pm[error](http://192.168.7.201/installedapp/configure/3272)java.lang.NullPointerException: null on line 3465 (motionTalkNow)
This error is saying that it cannot get the temperature from the device.
Has it reported temp since you configured it?
What device is providing the temperature?