I have programs that start a counter and end the counter of gallons used for irrigation.  The problem is the Node server is not sending data to the ISY.  I restart the Node server and the proper amounts show up.

I've got screen shots of before and after restart and a log but know it has some sensitive information inside.  

Let me know how you want me to transfer data to aid in debugging.

Thanks,

Paul

how do you have the flume Node server configured. It is working fine for me. 

Also check to make sure it is running by viewing the log file. 

Jimbo has been working very hard to program around the weirdness in the flume interface, but it seems to act up every no and then for no reason.

It works ok for me then just stops updating ISY until I restart it.

What should I be concerned about in config. As I recall, the only settings I can alter is the polling intervals. Not if front of it now. What are suggested values so I can confirm I’m in line.

The others config are flume credentials which are required to work.


Thanks. I understand the api is odd. Let me know if I can provide anything via logging etc.

It happened again today. I had to stop and start mode to get values to the ISY.

You'll need to send me a log file on the day it happens.  You can setup a notification which monitors the Node Status and Authorization Status to see if that is causing the failure.  The auth status will go to "Not Authorized" periodically, but the node server should recover, if it doesn't, please let me know.  Put Log into Debug mode will help me if the problem does occur.

 

Never mind, don't worry about sending a log, I found an issue.  My test instance had been running great for a couple weeks with no issues so I had shut off notifications while I was on vacation so I didn't see the issue when mine failed.  I see the problem and have a fix implemented and running.  I'll let it run overnight and try to release tomorrow.

 

Never mind, don't worry about sending a log, I found an issue.  My test instance had been running great for a couple weeks with no issues so I had shut off notifications while I was on vacation so I didn't see the issue when mine failed.  I see the problem and have a fix implemented and running.  I'll let it run overnight and try to release tomorrow.
 

Thanks! I’ll be looking for the release.

No authorization issues overnight for me, so I can either release it and if you can upgrade which will risk complete failure since I haven't seen the issue yet, or I can wait to see a failure.  @stevehoyt have you seen any issues with the current release?

 

No authorization issues overnight for me, so I can either release it and if you can upgrade which will risk complete failure since I haven't seen the issue yet, or I can wait to see a failure.  @stevehoyt have you seen any issues with the current release?
 

Thanks. I’ll do whichever you prefer. Upgrade for second test machine or give it more time with you.

@JimboAutomates

Yes I have had mine hang 2 times in the past 2 weeks. I unfortunately was out of town both times and did not catch it soon enough to get the log files.  Have been up for the last 4 days without a problem.

 

Thanks guys, I tested the best a could by faking out a invalid_token failure and it seems to work so I have released 3.0.14.

 

23 minutes ago, JimboAutomates said:

Thanks guys, I tested the best a could by faking out a invalid_token failure and it seems to work so I have released 3.0.14.

 

Thanks installed it  - I think. 

 

I refreshed store and then restarted the node server.  While it is connecting it says version is 3.0.14 for a few seconds but I  can see it revert to 3.0.13 on the screen.   Its likely running new version but just displaying 3.0.13.

33 minutes ago, hart2hart said:

Thanks installed it  - I think. 

 

I refreshed store and then restarted the node server.  While it is connecting it says version is 3.0.14 for a few seconds but I  can see it revert to 3.0.13 on the screen.   Its likely running new version but just displaying 3.0.13.

Sorry, my bad, we are required to update the version in 2 places and I missed one.  New zip file uploaded but will only fix it for new upgrades.  But don't worry, you have the latest release.

Sorry, my bad, we are required to update the version in 2 places and I missed one.  New zip file uploaded but will only fix it for new upgrades.  But don't worry, you have the latest release.

Thanks! It felt like that was what was happening. Just wanted to update you and make sure.

FYI @JimboAutomates

Just restarted here and still have v.13 showing on pg3 info. Node server store also shows v.13 as latest

Did not see flash of v14 that @hart2hart saw

FYI @JimboAutomates
Just restarted here and still have v.13 showing on pg3 info. Node server store also shows v.13 as latest
Did not see flash of v14 that @hart2hart saw

I had to refresh store before it showed the .14 version.

Yes, PG3 only automatically refresh once or twice a day I think.

 

@JimboAutomates

I seem to have an issue with v14. It starts OK then after awhile does not seem to return data from a long poll. If I do a query in the admin interface all updates OK.

Log file in GitHub under the invalid token issue. 

 

27 minutes ago, stevehoyt said:

@JimboAutomates

I seem to have an issue with v14. It starts OK then after awhile does not seem to return data from a long poll. If I do a query in the admin interface all updates OK.

Log file in GitHub under the invalid token issue. 

 

I'm having the same problem.  It did not update since first thing this morning.  I restarted the node and it didn't update.  I pushed Query from ISY AC and it updated all.  grabbed a log after restart and the query that includes not activity since this AM.  I didn't get any of my message saying it was not authenticated etc.

 

I'll upload to github but how do i upload log so its not open in case I missed covering up some sensitive data?

Edited June 6, 20223 yr by hart2hart

Sorry, was a result of restructuring the code to fix the other issue.  Fixed in 3.0.15.

 

Thanks.  It's installed.

Sorry, was a result of restructuring the code to fix the other issue.  Fixed in 3.0.15.
 

Jumbo,

As a follow-up. The connection to Flume has been perfect since this update.

Thanks,

Paul

Jumbo,

As a follow-up. The connection to Flume has been perfect since this update.

Thanks,

Paul

Awesome, thanks for confirming.

Sent from my Pixel 6 Pro using Tapatalk