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

Sonos Bug #19

Open
lengfelj opened this issue Jul 29, 2017 · 1 comment · May be fixed by #20
Open

Sonos Bug #19

lengfelj opened this issue Jul 29, 2017 · 1 comment · May be fixed by #20

Comments

@lengfelj
Copy link

Thanks for the great repo!

Have a small issue with trackDescription data coming from Sonos:

postToInfluxDB(): Something went wrong! Response from InfluxDB: Headers: [content-length:489, request-id:c464608c-7473-11e7-b65d-000000000000, http/1.1 400 bad request:null, content-type:application/json, date:Sat, 29 Jul 2017 15:37:02 GMT, x-influxdb-version:1.3.1], Body: {"error":"unable to parse 'trackDescription,deviceId=9c93ae4e-671d-4ffa-998d-895cb3d16e45,deviceName=Office,groupId=null,groupName=Home,hubId=655bcc7a-dfd6-4458-a163-21c2b670325e,hubName=Home\\ Hub,locationId=d0288ea8-7456-442d-b4c8-41e83f5a69a5,locationName=Home,unit=null value=Okay\\ Then': invalid boolean\nunable to parse 'by\\ Sokro': missing fields\nunable to parse 'from\\ LA\\ FAMILIA\\ PT.\\ 1': missing fields\nunable to parse 'Grouped\\ with\\ Living\\ Room': missing fields"}

scrool added a commit to scrool/codersaur-SmartThings that referenced this issue Jul 31, 2017
It seems that POST action of physicalgraph.device.HubAction doesn't get
length of payload correctly. Without this change size of UTF-8 payload
was smaller and InfluxDB parser complained that message isn't formatted
correctly. E.g.

    http/1.1 400 bad request

    {"error":"unable to parse '...': invalid boolean
    {"error":"unable to parse '...': missing fields

    etc

resolves: codersaur#19
@scrool scrool linked a pull request Jul 31, 2017 that will close this issue
@scrool
Copy link

scrool commented Jul 31, 2017

I've seen this issue with my setup. In my case names of rooms and sensors aren't only in ASCII but in Unicode (UTF-8). I suspect platform not working correctly with UTF-8 encoded POST payload. Please see PR #20 if that helps.

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

Successfully merging a pull request may close this issue.

2 participants