EDIT:  It appears something must be going on with my RainMachine.  I get similar errors when I run earlier versions of Nodelink.  I can connect normally through the RainMachine proxy, but connecting directly (https://192.168.1.13:8080) causes a complaint in the browser that the connection is not secure. 

 

RainMachine firmware version: 4.0.925

RainMachine API version: 4.5.0

 

I just noticed that my Nodelink Rainmachine node started having errors.  Nothing changed in the config, other than the newest version of Nodelink was deployed.  I didn't notice the errors until nearly 24 hours after the update, as the Rainmachine is in a seasonal restriction.  I did reboot the Rainmachine during the time this log was being collected, but no change to the status.

 

Attached is a debug log.

 

Thanks.

logfile_2018-02-01.txt

Edited February 2, 20187 yr by Bumbershoot

For what it's worth, I can't get the Nodelink / RainMachine connection to happen today.  I've deleted and re-added the RainMachine a couple of times, changed the password, rebooted it, etc., and the error persists.

 

I updated Mono to the latest version and it's working fine, otherwise.

2018-02-02 11:06:54 - ISY NodeLink Server v0.9.3 started
2018-02-02 11:06:54 - Mono version: 5.8.0.108 (tarball Fri Jan 19 18:55:10 UTC 2018)
2018-02-02 11:06:55 - ISY resolved to 192.168.1.20
2018-02-02 11:06:55 - Web config server started (http://192.168.1.5:8090)
2018-02-02 11:06:55 - ISY Node Server config detected (profile 2)
2018-02-02 11:06:59 - RainMachine Login Error - Error getting response stream (ReadDone2): ReceiveFailure [rain1]
2018-02-02 11:06:59 - RainMachine Login Error - Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''. [rain1]

 

For what it's worth, I can't get the Nodelink / RainMachine connection to happen today.  I've deleted and re-added the RainMachine a couple of times, changed the password, rebooted it, etc., and the error persists.

 

I updated Mono to the latest version and it's working fine, otherwise.

2018-02-02 11:06:54 - ISY NodeLink Server v0.9.3 started
2018-02-02 11:06:54 - Mono version: 5.8.0.108 (tarball Fri Jan 19 18:55:10 UTC 2018)
2018-02-02 11:06:55 - ISY resolved to 192.168.1.20
2018-02-02 11:06:55 - Web config server started (http://192.168.1.5:8090)
2018-02-02 11:06:55 - ISY Node Server config detected (profile 2)
2018-02-02 11:06:59 - RainMachine Login Error - Error getting response stream (ReadDone2): ReceiveFailure [rain1]
2018-02-02 11:06:59 - RainMachine Login Error - Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''. [rain1]

Is the Rainmachine available on your LAN?

Can you ping it?

See it in your router?

Sleuth it's IP address?

 

Maybe your router dropped it's IP reservation.

DHCP got turned off, IP address changed somehow?,

Got a switch going bad?

Try the whole house LAN equip. reboot thing?

Power cycle your router, RPi?

 

For what it's worth, I can't get the Nodelink / RainMachine connection to happen today.  I've deleted and re-added the RainMachine a couple of times, changed the password, rebooted it, etc., and the error persists.

 

I updated Mono to the latest version and it's working fine, otherwise.

2018-02-02 11:06:54 - ISY NodeLink Server v0.9.3 started
2018-02-02 11:06:54 - Mono version: 5.8.0.108 (tarball Fri Jan 19 18:55:10 UTC 2018)
2018-02-02 11:06:55 - ISY resolved to 192.168.1.20
2018-02-02 11:06:55 - Web config server started (http://192.168.1.5:8090)
2018-02-02 11:06:55 - ISY Node Server config detected (profile 2)
2018-02-02 11:06:59 - RainMachine Login Error - Error getting response stream (ReadDone2): ReceiveFailure [rain1]
2018-02-02 11:06:59 - RainMachine Login Error - Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''. [rain1]

 

 

I'm able to connect to mine. I'm not in watering season, but I was able to push a Snooze from the ISY through nodelink to the rainmachine. It worked and got a notification from the RM and its notification system

 

Paul

Is the Rainmachine available on your LAN?

Can you ping it?

See it in your router?

Sleuth it's IP address?

 

Maybe your router dropped it's IP reservation.

DHCP got turned off, IP address changed somehow?,

Got a switch going bad?

Try the whole house LAN equip. reboot thing?

Power cycle your router, RPi?

It's available on the LAN.  I can connect to it directly via web browser (https://192.168.1.13:8080) and via the proxy (https://my.rainmachine.com).  It pings up a storm.  I haven't cycled the router and switch, but I have rebooted the RPi and the ISY.  The silly thing is visible on the LAN, and as far as I can tell, operating normally otherwise.  It's been available to the ISY for what seems like forever, prior to yesterday.

 

I deleted it completely from the ISY, and re-added it.  The ISY found the nodes when I re-added it, but they're not populating with data.  Weird.

It's available on the LAN.  I can connect to it directly via web browser (https://192.168.1.13:8080) and via the proxy (https://my.rainmachine.com).  It pings up a storm.  I haven't cycled the router and switch, but I have rebooted the RPi and the ISY.  The silly thing is visible on the LAN, and as far as I can tell, operating normally otherwise.  It's been available to the ISY for what seems like forever, prior to yesterday.

 

I deleted it completely from the ISY, and re-added it.  The ISY found the nodes when I re-added it, but they're not populating with data.  Weird.

Are the parameters polpulating isdie the NodeLink node page?

Have you tried "Installing Nodes in ISY" in NodeLink again? 

I'm able to connect to mine. I'm not in watering season, but I was able to push a Snooze from the ISY through nodelink to the rainmachine. It worked and got a notification from the RM and its notification system

 

Paul

 

I appreciate that.  I'm not going to start irrigating for another 45 days, but the only thing I did was update files on the RPi. 

 

I might be getting somewhere.  It seems that the RainMachine might not have a valid certificate.  I wonder if that affects the Nodelink connection?

 

The screenshot was captured using the command line browser, links, on the RPi.

Mine has not had a recognized cert for local api since I’ve had it, which I’m ok with.

 

 

Sent from my iPhone using Tapatalk

Okay, thanks.  I never noticed that.  Maybe I'm not getting anywhere...

Okay, thanks.  I never noticed that.  Maybe I'm not getting anywhere...

Well if NodeLink is not populating then you know it's between NodeLInk and Rainmachine and nothing to do with ISY, Paul's your guy.

In order for you to be able to add nodes to the ISY one login should have been successful.

 

In System Config, set debug logging

In RainMachine, set default logging

On main page, enable logging at debug level.

 

Remove the node from the ISY and restart NodeLink.  Lemme see the log.

Thanks, here it is.

logfile_2018-02-02.txt

Edited February 3, 20187 yr by Bumbershoot

I don't see where you're adding nodes to the ISY.  You're getting a different error this time.  Last time was ConnectFailure.  This time is ReadDone2.

 

I don't see the start of your log where the mono version is spelled out.  What version do you have?  Typically ReadDone2 is caused by a half-baked mono version.  Running NodeLink on a Windows computer would likely be ok (as a test).

2018-02-02 21:21:54 - Mono version: 5.8.0.108 (tarball Fri Jan 19 18:55:10 UTC 2018)

 

I'll start up a Windows session and give Nodelink a try.

From a Windows box I'm getting the following errors at the default log level.

 

2018-02-02 21:36:04 - ISY NodeLink Server v0.9.3 started
2018-02-02 21:36:05 - ISY resolved to 192.168.1.20
2018-02-02 21:36:05 - Web config server started (http://172.16.146.157:8090)
2018-02-02 21:36:05 - ISY Node Server config detected (profile 2)
2018-02-02 21:37:23 - RainMachine Login Error - Unable to connect to the remote server [rain1]
2018-02-02 21:37:23 - RainMachine Login Error - Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''.  [rain1]
2018-02-02 21:37:27 - RainMachine Login Error - Unable to connect to the remote server [rain1]
2018-02-02 21:37:27 - RainMachine Login Error - Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''.  [rain1]
2018-02-02 21:37:29 - RainMachine Login Error - Unable to connect to the remote server [rain1]
2018-02-02 21:37:29 - RainMachine Login Error - Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''.  [rain1]
2018-02-02 21:37:35 - RainMachine Login Error - Unable to connect to the remote server [rain1]
2018-02-02 21:37:35 - RainMachine Login Error - Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''.  [rain1]
2018-02-02 21:37:36 - RainMachine Login Error - Unable to connect to the remote server [rain1]
2018-02-02 21:37:36 - RainMachine Login Error - Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''.  [rain1]

 

EDIT: Windows 10 on VMWare.  The RainMachine and ISY both ping.
 

Attached the log from the Windows box.

logfile_2018-02-02.txt

Edited February 3, 20187 yr by Bumbershoot

OK,

Love this one from the beta firmware release notes:

 

"- Disabled unsecured HTTP port 18080 for remote access."

 

Guess I need to switch NodeLink over to https.

OK,

Love this one from the beta firmware release notes:

 

"- Disabled unsecured HTTP port 18080 for remote access."

 

Guess I need to switch NodeLink over to https.

 

Sorry, I saw that in the release notes and the nickle never dropped.  Mea Culpa.  The website does a quick redirect to https, so I didn't catch it there, either.  Beyond security, a couple of the firmware changes are of interest to me, such as adaptive watering schedules, allowing multiple Wunderground stations.

 

For anyone interested in the changes.

For anyone interested in the changes.

 

Thanks! Some updates are of interest to me as well (though I can't use them for a while).

 

This is my one gripe with them: patching cadence and what it means for vulnerabilities. Only a few releases a year, meaning vulnerabilities like Krack sit around till they're ready to do the functional release.. and the release discussed here is beta. The RM runs on a full Android OS. I have the same beef with Venstar on the colortouches (Linux) as well, and these are not alone in this way. I realize the probability of an attack is fairly low, but the attack surface for a full blown OS is wide and the severity of losing control of these LAN devices is high. I guess I have to accept this as a tradeoff, and having something that can run a local API is more important.

I'll likely be running my irrigation in production on this beta software.  We're having an exceptionally mild winter.  "Spring" weather appears to be about 30 days ahead of last year, possibly leading us into another drought on the West coast.

I'll have a new NodeLink version out this weekend to support the beta.

 

Running it fine here in testing with the beta.

Thanks so much!  I'm appreciative of your time and efforts.

Entirely back in business, with v.0.9.4.  Thanks again!