Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alexa app, error "Device doesn't support requested value" #1044

Closed
chmasi opened this issue Jan 1, 2019 · 7 comments · Fixed by #1266
Closed

Alexa app, error "Device doesn't support requested value" #1044

chmasi opened this issue Jan 1, 2019 · 7 comments · Fixed by #1266
Assignees
Milestone

Comments

@chmasi
Copy link

chmasi commented Jan 1, 2019

After upgrading to latest stable Version i got this error, and devices can not be switched anymore by Amazon Echo Device. Same issue with latest release Candidate.
Went back to Version 4.5.6 and everything is working again as expected.

@bwssytems
Copy link
Owner

Will take a look as I saw this the other day on my system.

@ammawel
Copy link

ammawel commented Jun 15, 2019

First of all thanks for the constant work on ha-bridge!
Unfortunately this error message is still present in the last release v5.3.0RC3 when devices are turned off. However, the devices are switched despite the message.
Greetings
Achim

@bwssytems
Copy link
Owner

Setting brightness return in state to be no less than 1

@SchmuFoo
Copy link

ting brightness return in state to be no less than 1

Where do I set this? Somewhere in "http:https://192.168.178.38:8080/#!/editdevice" ?

@SchmuFoo
Copy link

SchmuFoo commented Jan 3, 2020

ting brightness return in state to be no less than 1

Where do I set this? Somewhere in "http:https://192.168.178.38:8080/#!/editdevice" ?

@bwssytems I was wondering if you could give us an hint for that ;)?

@ballle98
Copy link

ballle98 commented Jan 3, 2020

I think what is suggested is to edit the device and add a dim URL/cmd. For me I added the following command "/usr/bin/logger ${device.name} dim ${intensity.percent}". Then from bridge devices you can use the "test dim" button to set the brightness. Make sure your device has state enabled (No state = false). Also make sure to "Off State Resets Bri"=false and "On when Dim is present"=false.

The root cause seems to be brightness of 0 creates an error condition.

Not sure that dim state is persistent across reboot so may need a use curl to set all the brightness states to 1 see https://github.com/bwssytems/ha-bridge#update-bridge-internal-light-state

@ballle98
Copy link

looks like not all values of "bri" are accepted. I opened 2 terminals into my pi. one running
watch curl http:https://127.0.0.1/api/username/lights/1
and the other I would set different brightness values with
curl -X PUT -d '{"bri": 253}' http:https://127.0.0.1/api/username/lights/1/bridgeupdatestate

I originally used the value of 254 for 100% brightness but I saw the value get clobbered and set back to 0 when I turned the light on and off. I tested the values 253 and 26 and they seem to work.

I could not get multiple startup actions to work so I created a new device called startup that calls a script that sets the brightness on all devices and set the startup action to on for this device.

for i in {1..11}; do curl -X PUT -d '{"bri": 253}' http:https://127.0.0.1/api/username/lights/$i/bridgeupdatestate; echo; done

bwssytems added a commit that referenced this issue Dec 14, 2020
Dev branch 5.3.x to create v5.4.0

#1044 Alexa app, error "Device doesn't support requested value" bug question
#1118 Device status update in Alexa App is not working correctly for ha-bridge devices bug duplicate question
#1126 Can't get XY ColorData into URL enhancement question
#1127 Can't get separate hue, saturation and brightness enhancement question
#1128 Wrong color calucation in HS mode bug question
#1131 Changing color temperatur is not working correctly bug question
#1132 Conversion from CIE to RGB incorrect bug question
#1139 Device ID creation fails bug question
#1150 Home Assistant gets null exception during initialization bug question
#1170 Alexa not sending the correct color codes duplicate
#1171 Please add option: If bright request present with on, only send dim enhancement
#1184 Alexa will not discover HABridge question
#1191 When "Use UPNP Address Interface Only" is selected, echo cannot find ha-bridge bug
#1210 [Enahnacement] Have link button timeout be configurable enhancement
#1215 Alexa unable to discover recently added devices to ha-bridge duplicate question
#1227 Feature request: ${intensity.previous} value passing control enhancement
#1239 HA-Bridge has suddenly given up itself - Exception in thread "main" java.lang.NullPointerException bug question
#1243 Alexa device discovery now broke question
#1253 HABridge hue ColorDecode 0 0 0 bug question
#1256 Homeassistant devices not appearing bug question
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants