HTTP device not working?

Avatar
Noel Fuentes
  • updated
  • Under review

Hello,

I've recently updated to version 4.6.17 and http devices with authentication stopped working since then. Funny thing is the http devices with no authentication keep working fine.

I use http devices with authentication to activate Mobotix cameras recordings and it doesn't work since the update. The "Response data" value is empty and no error is showed in the log window. If I use a program task to do the http request, a "no authorised" error messages shows in the log window, even though I'm sure the user and password are correct.

On the other hand, I use http devices to do a couple of tasks with Sonos and it's still working fine.

Any tips?


Thanks in advance.

Best regards

Replies 23
Avatar
0
Fabien Fuster

Hi Andrej,

Does your device host url finish with a "/" ? I've found out that ending the url with any other character is creating some issues. You need to adjust the url and command accordingly....

For exemple :

hoslt url http://192.178.99.1/api/1.0/ and command ?method=system.getInfo will work

hoslt url http://192.178.99.1/api/1.0/?method= and command system.getInfo will not work

This might be one of the reason of your troubles. 

Regards,

Avatar
0
Andrzej Szymkowicz

The beta doesn't solve the problem with Netatmo (post command in oauth2/token):

Avatar
0
Fabien Fuster

Just an heads up :

The new beta 6.31 is available. It improved the situation significantly for me as only one last device (Foobot API) show 401 error message. All other devices don't show error or regular disconnection messages anymore. Getting closer to full resolution here !

Best regards

Avatar
0
Fabien Fuster

Hi Ricardo,

Since v4.6.26 and the above mentioned change posted on Dec 11th related to the position of the /, I've have no 403 error anymore. Instead, I get 401 error coming up, but data are being updated in bOS despite them. The 401 error is usually linked with a disconnection/reconnection messages...


Now, for testing purpose, I'm running the alpha version 4.6.30. If the occurrence rate of error messages dropped, they still exist...

Also, for info, I'm getting disconnection/reconnection issues for a device hosted on my own webserver on my intranet, but without the 401 error. No explanation why so far....

The bOS team is working hard on this topic and I'm sure your additional info will help them to narrow down the route cause. There might be something different in the code of the Jigsaw and the Grinder....

Best regards,

Avatar
0
Ricardo Pinto

Hi,

Apparently I'm suffering from the same evil.

Lately I'm having trouble even on simple HTTP commands without authentication.

I've noticed because I have several HTTP devices, and most of them don't work.

And also several times my Weather stops working, and doesn't show up even if I reboot the server.

The funny thing, is that some of my HTTP devices are not working on my Jigsaw, but are working on other Grinder's, so it doesn't make any sense.

For example:

I was uploading my active power to the ThingSpeak IOT Analytics platform just for demo, and my Jigsaw doesn't even send  any value / or shows error connecting to the device. And the same device on a Grinder works... and both have the same bOS server version.

Second example:

Simple HTTP device which gets a text response, without authentication. Not working on my Jigsaw. Working on a costumer Grinder.

Etc...

Best regards

Avatar
2
Fabien Fuster

Nice to read it helped. However, for information, if this fixed most of my devices,  various other issues still exist with some other http devices but CC team is working hard right now to fix them all soon.

Avatar
0
Fredrik Sandblom

Hi Fabien. Thanks! Starting a http command with "/" was the problem. Tested to change this before updating to beta and it works now. More or less all my HTTP Devices was with this convention and I had to change all before the problem was gone.

@ComfortClick Please update documentation!

Avatar
0
Joachim O

Thanks for the tip, but I still get the 403 error.

Avatar
1
Fabien Fuster

Just realize that I forgot to mention the following change needed :

Don't start any command with a "/". Instead, add this one at the end of the host address. Having done this change and upgraded to Beta 26 solved almost all my issues. Few remaining ones are still being reviewed by the bOS team.

Hope it will work for you.

Avatar
0
Joachim O

Didn't solve my issue :( I have updated the Netatmo specific thread with details.


Customer support portal powered by UserEcho