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

device is unresponsive #228

Open
chrisncc1701 opened this issue Jul 10, 2022 · 3 comments
Open

device is unresponsive #228

chrisncc1701 opened this issue Jul 10, 2022 · 3 comments

Comments

@chrisncc1701
Copy link

everything was working fine until recently, the device set value commands appear to be working, As from about a month ago all ESP devices now show on the Alexa app as unresponsive every few seconds, voice commands are ok, after a few days they disappear altogether from the alexa app, and no voice commands, all devices will rediscover ok, then show as unresponsive again, voice ok, I have 6 devices on 1 fauxmo ESP32 and other devices using espalexa on ESP32 doing exactly the same, tried deleting all devices and rediscovering, just the same.
I wonder if amazon have done any changes recently.
Anyone any ideas?

@problemss
Copy link

problemss commented Jul 29, 2022

I have a similar problem. I just setup my ESP8266 and am seeing either unresponsive message or Device doesn't support requested value message. I can see via debug that I am returning the correct state. I can also navigate to the URL and it is returning the expected JSON. I can also use the app to turn the device on and off, but it still goes to unresponsive or not supported value.

16:46:23.348 -> [FAUXMO] isGet: true
16:46:23.348 -> [FAUXMO] URL: /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr/lights/1
16:46:23.348 -> [FAUXMO] Handling list request
16:46:23.348 -> [FAUXMO] Sending device info for "Door", uniqueID = "B4:E6:2D:31:16:3C:00:00-00"
16:46:23.348 -> [FAUXMO] Response:
16:46:23.348 -> HTTP/1.1 200 OK
16:46:23.348 -> Content-Type: application/json
16:46:23.348 -> Content-Length: 418
16:46:23.348 -> Connection: close
16:46:23.348 -> 
16:46:23.348 -> {"type": "Extended color light","name": "Door","uniqueid": "B4:E6:2D:31:16:3C:00:00-00","modelid": "LCT015","manufacturername": "Philips","productname": "E4","state":{"on": false,"bri": 0,"xy": [0,0],"hue": 0,"sat": 0,"effect": "none","colormode": "xy","ct": 500,"mode": "homeautomation","reachable": true},"capabilities": {"certified": false,"streaming": {"renderer":true,"proxy":false}},"swversion": "5.105.0.21169"}

Really curious how to fix it or if there is a new JSON format Alexa is expecting. I am assuming "ON:false,"bri":0 is brightness at 0% and power is off. When I use setState or the app I can change it and confirm via the JSON message buy the app doesn't reflect it correctly.

@intouchrandb
Copy link

I'm seeing a similar problem. On the Alexa App I am seeing either unresponsive message or Device doesn't support requested value message some of the time on 1 or 2 of my lights on esp8266. It clears up by itself and message come back. In the esp8266 I limit the min and max brightness to 3 to 254 thinking it might be a rounding error....but no noticeable improvement. Running Gen4, esp8266 with core 2.74, fauxmo 3.4, and v2 Lower memory.
Great library.....

Mark

@MrGreensWorkshop
Copy link
Contributor

I think it's because, current library doesn't supports onGetState. please check #236

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants