Bugs
0
Under review
The sensibo integration is not allways working
The integration using the available HTTP example no longer works properly and the following happens:
- every two minutes the connection is established
- Lasts about 30s and turns off again
- I can't find any parameter with these values in the configuration
- during the 30s I can give commands, for example on/off, but after that it's not possible, although sometimes I can (it's random).
- The response message is "ok" when the connection is achieved and "TooManyRequests" when there is no connection.
Can you help please
Customer support service by UserEcho
Hi Joaquim
You can download new sensibo driver here, fix apikey parameter lost during operation.
Currently it seems that sensibo has limited the number of requests to the API. By default I am setting it to 1s, you can increase the time to 10-20s
Hi Bao,
Thanks for the quick response.
The behavior I described is already with this new driver that I had already loaded. The time I parameterized was 15s.
I also raised the issue with Sensibo and they responded that the API rate limit is 10 every 10 seconds.
Is there anything that justifies the HTTP connection being made every 2 minutes and being lost after a few seconds?
Thank you very much for your help.
I also got the same error ''TooManyRequests''
Please help me! @Bao Tran
Hi Sơn,
This problem I haven't solved yet.
In recent updates of Sensibo, in addition to the time limit for sending to the server, sensibo requires the transmission parameter of the header to have "Gzip"
I tried adding parameter to the header of Comfortclick, it seems that BOS does not support compression, the data returns faulty characters, this issue I have to update in this article
If @Comfortclick has support for compression when sending in the HEADER, I think the driver will work.
Hello,
try keeping header as is but paste
Accept-Encoding: gzip
into the Content type in the command and try again. This should work.
Best regards.
Hi Comfortclick,
If I use "Accept-Encoding: gzip" in the HEADER , Returned data will be defective which display incorrect, it seems that BOS does not support.
When not use gzip
Postman
Hello,
use the encoding command in the content type of the post command. Once this is sent, the normal GET command should also return values.