With 0.9.4 I'm still having issues getting it to connect with my 1st gen.

 

When I enter the ipaddress:port I'm getting a tooltip message that says "! Please match the requested format"  I'm entering 192.168.92.56:443 so I'm not sure why that doesn't match the requested format.  Am I missing something?

 

If I go with just the IP address, it accepts it but I'm getting:

 

2018-02-07 17:06:52 - RainMachine Login Error - Unable to connect to the remote server [rain1]

 

I know it's possible to connect and interact with my rainmachine with local authentication as I have a HomeSeer plug-in that works with it.

Oops that's my bad.  I added regex checks to the IP address fields in NodeLink but forgot to take into account the possible addition of ports.  I'll clean that up in a new release shortly.

0.9.5 is out and should fix this.

Thanks!  I'll give it a try later today.

With 0.9.5 it does accept the port number but now I get:

 

2018-02-08 15:22:00 - RainMachine Login Error - The underlying connection was closed: The connection was closed unexpectedly. [rain1]

 

I don't know if this helps, but with my HS plug-in I'm connecting to:

 

https://<ip>:443/api/4/auth/login

 

and posting:

{

"pwd":"<passwrd>",

"remember": 1

}

 

I'm using C# and have to also handle the invalid certificate and force disable the Expect: 100-continue header to get authentication working.

 

I believe my code works for later RM modes also although my sample size is very small (1 new generation RM)

Yet another stupid bug.  It's cause it's still using http when you set from the config until you restart.

 

The address saved is fine though, so rebooting NodeLink should get it up and running (it loads the address properly with https).  Will fix in next version.

After a restart the error changes but still not working

 

2018-02-09 09:20:23 - ISY NodeLink Server v0.9.5 started
2018-02-09 09:20:23 - Web config server started (http://192.168.92.205:8090)
2018-02-09 09:20:23 - ISY resolved to 192.168.92.26
2018-02-09 09:20:23 - ISY Node Server config detected (profile 1)
2018-02-09 09:20:24 - Warning: nodesetup.zip file needs updating in ISY
2018-02-09 09:20:29 - RainMachine Login Error - The remote server returned an error: (400) Bad Request. [rain1]

And for some reason the last post lost more than half of what I wrote

 

I logged the connection with my HS plug-in and get the following. You'll notice that the response from my HW version 1 box is different from what a newer box will return.  Is is possible that your response parsing is failing on this?  I know I had issues with it when trying to get my code working on a newer box.

 

If you want me to try pre-release versions to help debug, let me know.

 

 

RainMachine HW version: 1 SW version: 3.74 API: 3.64
Attempting to authenticate with https://192.168.92.56/api/4/auth/login
Got response: {"statusCode": 0, "access_token":"NMAMFMCMPAAGAJMA", "expires_in":157680000 }

Wouldn't be the parse or I'd get a JSON error.  Any chance you could open the port up so I can connect from here?  There must be something silly/different in the request post.

Wouldn't be the parse or I'd get a JSON error.  Any chance you could open the port up so I can connect from here?  There must be something silly/different in the request post.

 

Sure, to the rainmachine or nodelink?  

 

I won't be able to do it until a bit later tonight, but I can PM you the info.

To rainmachine.  I'll run NodeLink from here.