Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help to troubleshoot! #19

Open
martynwendon opened this issue Feb 15, 2017 · 3 comments
Open

Help to troubleshoot! #19

martynwendon opened this issue Feb 15, 2017 · 3 comments

Comments

@martynwendon
Copy link

Hey there,

I've been using node-red-vis for quite some time now and have just installed the latest npm version in order to migrate my Views to a new host.

I have a strange issue whereby some of the data only seems to get updated in Edit mode and not View mode.

In the attached screenshot you can see what I mean, on the left is the original host which is running 0.7.9 - here you can see the Editor and then the View mode working perfectly with all the data updating in real-time from node-red.

On the right is the new host with 0.10.15 running, here, strangely, the View mode only has the gauges updating correctly real-time from node-red.

I've tried deleting and recreating the strings, moving them around on the canvas, even moving some of the strings to a new View.

From what I can see the data is flowing correctly (as the gauges are getting updated correctly) and the Object IDs are all correct (in the screenshot on the right you can see all the correct data in the Editor)

Any thoughts on how I can troubleshoot this problem?

Thanks for your help!

Martyn

vis

@martynwendon
Copy link
Author

Just thought I'd add to the above, I put some simple debug statements in conn.js and confirmed that all data is getting sent across the socket as expected.

Not sure what more I can do from here as it seems to be an issue further into ioBroker.vis side?

vis2

@GermanBluefox
Copy link
Owner

GermanBluefox commented Feb 15, 2017 via email

@martynwendon
Copy link
Author

OK, but it's not in edit mode where I'm saying there's a problem?

I've labelled the screenshot in RED to hopefully make it clearer!

In the Live version on the right you can see that the gauges have updated, but the strings haven't.

I also mentioned above that I've added some debug into conn.js and you can see that the Live version is receiving the data over the socket correctly - again, the gauges have updated but the strings haven't.

Hope that makes the issue clearer.

vis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants