I suspect the problem is that HTTPS is enabled in the influxcloud instance. You can check with them to see if that can be turned off. Otherwise, I don’t see what the problem could be.
If you PM your password to me, I can try it from here and look at the actual HTTP 400 error message being returned. Otherwise, I will make a note to add that to the message log in these cases in a future release.
UPDATE: I have put in code to try to interpret and display the influx error codes. It is a challenge because there is no definitive list in their documentation.
I also hand crafted a query to your database. It doesn’t matter that I don’t have the password, didn’t get that far:
So it appears that the current problem is that the database has HTTPS enabled and requires it. IoTaWatt is not able to do that protocol. It’s unfortunate that the choices are HTTPS or basic authorization for plain-text. Digest authorization, while not an encryption protocol, would go a long way toward improving authentication. It probably wouldn’t stand up to a decent hacker, but would seriously hamper mischief makers.