Re: reports/connections API return deviceid wihout "d" in the start
seems like an inconsitency , yes.
I don't think i can easily change this because it would be a breaking change for a production API.
Everybody who consumes it already would need to update their code /json serializer to reflect the type change. Which is something we don't want.
There is however always the possiblity of versioning the request aka : api/v2/reports/connections could return device id with prefixed 'd' while via v1 you get the old inconsistent behaviour. (this is of course not implemented currently - just providing some insights)
I will see if we can do anything here - at least i will create a bug report.
I must say however the prefixing of IDs is only for readability. The device id is correct as an integer - the only difference is the 'd' - so you technically should be able to just use it as is. (you might want to add a 'd' in front for comparing with other values from the API as a workaround)