TJF1960 Posted July 29, 2018 Posted July 29, 2018 Hi io_guy, Upgraded to 5.0.13b couple of weeks ago. I noticed that the Honeywell tstat data was pushed to ISY at least once during reboot but the tstat page in ISY was not updating as the data changed. Nodelink tstat page had the correct data on its page. After the Nodelink update to .16 a few days ago I noticed that the ISY Honeywell nodes were not populating at all even after reboot of ISY or Nodelink. What log level would be the most informative for you? Debug? Thanks, Tim
Scottmichaelj Posted July 29, 2018 Posted July 29, 2018 Hi io_guy, Upgraded to 5.0.13b couple of weeks ago. I noticed that the Honeywell tstat data was pushed to ISY at least once during reboot but the tstat page in ISY was not updating as the data changed. Nodelink tstat page had the correct data on its page. After the Nodelink update to .16 a few days ago I noticed that the ISY Honeywell nodes were not populating at all even after reboot of ISY or Nodelink. What log level would be the most informative for you? Debug? Thanks, Tim NodeLink was updated recently to v17 with a few fixes for TCC. I had TCC timeout issues and those were attempted to get fixed in this newest release. You might try updating Nodelink and report back.
TJF1960 Posted July 29, 2018 Author Posted July 29, 2018 Thanks, sorry. I am on v17, I have Nodelink set to auto update. So I started having the first issue on v16, now on v17 Nodelink will not update the ISY node page with data at all.
paulbates Posted July 29, 2018 Posted July 29, 2018 io_guy asks for a copy of the log to see what's going on: On the main nodelink page, and on the device page for your tcc thermostat, set the logging level to debug in the drop down Restart nodelink and let it run until you observe the problem. Copy the contents out of the main nodelink page log on the web, or attach the file if you write the file to disk, post that here Paul
TJF1960 Posted July 29, 2018 Author Posted July 29, 2018 Thanks paulbates, I thought debug was the selection but I wasn't sure. I ran debug for a half hour or so. Attached is the log file. As a side note, I just rolled back to v15 and once the pi rebooted the tstat nodes populated in ISY. I made a change to the tstat and the change was updated in ISY as well. So it does appear to work correctly in v15. logfile_2018-07-29.txt
io_guy Posted July 30, 2018 Posted July 30, 2018 Do you get data into NodeLink? I don't see anything in the log. You have a DSC error as well. Can you enable DSC verbose as well?
Scottmichaelj Posted July 30, 2018 Posted July 30, 2018 On 7/29/2018 at 11:32 AM, TJF1960 said: Thanks paulbates, I thought debug was the selection but I wasn't sure. I ran debug for a half hour or so. Attached is the log file. As a side note, I just rolled back to v15 and once the pi rebooted the tstat nodes populated in ISY. I made a change to the tstat and the change was updated in ISY as well. So it does appear to work correctly in v15. logfile_2018-07-29.txt I also can reproduce the same issue with v17 of NodeLink not getting the info from Honeywell TCC as the device is not show any info in NodeLink itself. I reentered my username and password, removed the devices and added them back but it didn't help. Therefore the ISY is unable to get the data. My log.
io_guy Posted July 30, 2018 Posted July 30, 2018 Can one of you add io_guy at automationshack dot com to your TCC account? Try to fix their web service is like buying a lotto ticket.
Scottmichaelj Posted July 30, 2018 Posted July 30, 2018 43 minutes ago, io_guy said: Can one of you add io_guy at automationshack dot com to your TCC account? Try to fix their web service is like buying a lotto ticket. DONE. You should get an email with access to login. Thank you so much for helping fix it for all of us.
io_guy Posted July 31, 2018 Posted July 31, 2018 Can confirm it's a problem with .17 (.16 works). I believe it's a cookie issue with my new code. Will play around.
Scottmichaelj Posted July 31, 2018 Posted July 31, 2018 Can confirm it's a problem with .17 (.16 works). I believe it's a cookie issue with my new code. Will play around. Again many thanks for all you do. You are appreciated.
Scottmichaelj Posted August 1, 2018 Posted August 1, 2018 Just updated to v18 - looks like we are back in business. NodeLink webpage shows the stat info again and the ISY is showing them as well. Thank you! I will not keep my eyes out to see if it times out.
TJF1960 Posted August 1, 2018 Author Posted August 1, 2018 Also just updated and all populated perfectly. io_guy, Thank you so very much! Scottmichaelj, Thank you for jumping in and offering help when I could not! Tim
Scottmichaelj Posted August 21, 2018 Posted August 21, 2018 Looks like this is still an issue. My log from today. Restart fixes it. Sometimes I have to enter the username/password again. Thanks in advance for looking at this. 2018-08-21 00:41:28 - TCC Get Error: Timeout [hwstat2] 2018-08-21 00:41:28 - TCC Get Error: Timeout [hwstat1] 2018-08-21 05:58:04 - TCC Get Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 06:08:08 - TCC Get StatusError - InternalServerError [hwstat2] 2018-08-21 07:03:32 - TCC Get Error: Error: NameResolutionFailure [hwstat2] 2018-08-21 07:38:52 - TCC Get Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 07:49:06 - TCC Get Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 08:29:19 - TCC Get Error: Error: NameResolutionFailure [hwstat2] 2018-08-21 08:44:24 - TCC Get Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 09:09:31 - TCC Get StatusError - InternalServerError [hwstat1] 2018-08-21 09:19:33 - TCC Get Error: Error: NameResolutionFailure [hwstat2] 2018-08-21 10:04:46 - TCC Get Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 11:00:00 - TCC Get Error: Error: NameResolutionFailure [hwstat2] 2018-08-21 11:40:10 - TCC Get StatusError - Forbidden [hwstat1] 2018-08-21 11:55:13 - TCC Get Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 12:15:20 - TCC Get Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 12:20:21 - TCC Login Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 12:50:30 - TCC Get Error: Error: NameResolutionFailure [hwstat2] 2018-08-21 12:55:31 - TCC Login Error: Error: NameResolutionFailure [hwstat2] 2018-08-21 13:34:03 - Auto-Update: Error retrieving update list: Error: NameResolutionFailure 2018-08-21 13:35:43 - TCC Get Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 13:45:46 - TCC Get Error: Error: NameResolutionFailure [hwstat2] 2018-08-21 13:50:47 - TCC Login Error: Error: NameResolutionFailure [hwstat2] 2018-08-21 14:56:03 - TCC Get Error: Error: NameResolutionFailure [hwstat2] 2018-08-21 15:31:12 - TCC Get Error: Error: NameResolutionFailure [hwstat1] 2018-08-21 15:36:13 - TCC Login Error: Error: NameResolutionFailure [hwstat1]
io_guy Posted August 22, 2018 Posted August 22, 2018 Sorry, how is this the same issue? You're Pi's name resolution is failing (hence why Auto-Update gives the same error). And what is your mono version?
Scottmichaelj Posted August 22, 2018 Posted August 22, 2018 Sorry, how is this the same issue? You're Pi's name resolution is failing (hence why Auto-Update gives the same error). And what is your mono version? Ok I obviously don’t what I am taking about!? Coincidently this started to happen after you updated NodeLink so I assumed...I’ll pay better attention. Promise. I will try and figure out how to find the mono version I am on and if I need to update, how to do it. What Mono version do I need to be on?
io_guy Posted August 22, 2018 Posted August 22, 2018 The version pops up at the beginning of a NodeLink log after startup. I quick search on the NameResolutionError showed that it could be a potential bug that existed around v4.6.
Scottmichaelj Posted August 22, 2018 Posted August 22, 2018 15 hours ago, io_guy said: The version pops up at the beginning of a NodeLink log after startup. I quick search on the NameResolutionError showed that it could be a potential bug that existed around v4.6. Well I somehow managed to update Mono to version: 5.14.0.177 - hopefully this resolves things. I was on 5.10 before.
io_guy Posted August 23, 2018 Posted August 23, 2018 Likely not the problem, 5.10 should have been plenty good. I can try adjusting the DNS cache in NodeLink settings, but if it's an actual Pi or network issue (not NodeLink) there's not much I can do.
Scottmichaelj Posted August 23, 2018 Posted August 23, 2018 On 8/22/2018 at 7:42 PM, io_guy said: Likely not the problem, 5.10 should have been plenty good. I can try adjusting the DNS cache in NodeLink settings, but if it's an actual Pi or network issue (not NodeLink) there's not much I can do. It’s a QNAP NAS with a VM of Debian stretch and there has been no network issues I am aware of. It is doing a continuous sync 24/7 of files to the cloud with files being added/modified everyday. If there’s was an network issue I would get an email notification, which I haven’t. It looks like am getting time out errors again.
Scottmichaelj Posted August 23, 2018 Posted August 23, 2018 On 8/22/2018 at 8:21 PM, Scottmichaelj said: It’s a QNAP NAS with a VM of Debian stretch and there has been no network issues I am aware of. It is doing a continuous sync 24/7 of files to the cloud with files being added/modified everyday. If there’s was an network issue I would get an email notification, which I haven’t. It looks like am getting time out errors again. Edit: Reboot fixes it and then it works for a while then it times out again.
io_guy Posted August 23, 2018 Posted August 23, 2018 Rebooting of NodeLink or the VM? That log has DNS issues right from startup when auto-update fails
Scottmichaelj Posted August 24, 2018 Posted August 24, 2018 Rebooting of NodeLink or the VM? That log has DNS issues right from startup when auto-update fails Restarted the VM and waiting to see how things go.Coincidently got this email today from Honeywell about TCC.“Hello,Honeywell connected services have been experiencing some intermittent connectivity issues, and we want to make sure you're able to continue using your app to control your thermostat.Although your thermostat will continue to work, you may have trouble changing settings using your app or registering a new device. If you experience either of these issues, please close out of your app, open it back up, and try completing the action again. Most of the time, the issue will be resolved on your second try. We’re working through the issue and are committed to resolving it as soon as possible—we’ll be sure to let you know if the problem persists. If you continue to have issues after taking these steps, please call Honeywell Customer Care at 1-855-733-5465 for further assistance. Thank you for your patience. —The Honeywell Home team”So it makes me wonder if NodeLink loses the connection to TCC due to an error on TCC’s side, then does NodeLink have to login again to work again?
io_guy Posted August 24, 2018 Posted August 24, 2018 If you had to login again you'd be getting a different error. And that doesn't explain the auto-update failure.
Scottmichaelj Posted August 31, 2018 Posted August 31, 2018 Still seeing Honeywell TCC issues. See screenshots. Reboots work temporarily then you start seeing errors. If you look downstairs says it "updated" however the full details are not showing. Upstairs still is working. I would assume that if it was a network issue on my side both stats would have failed, same for TCC server side. I suspect something else is happening here. Rebooting NodeLink fixes the problem but only for a while until it starts with the errors again, as you can see from my log. Thoughts?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.