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

Integer values are parsed into strings Value field #45

Open
ee-hex-ee opened this issue Jul 15, 2024 · 0 comments
Open

Integer values are parsed into strings Value field #45

ee-hex-ee opened this issue Jul 15, 2024 · 0 comments

Comments

@ee-hex-ee
Copy link

🐛 Summary

Values that could/should be parsed as numbers (int) or binary (1/0) are using string. This is potentially the only way to parse them, however this creates an issue for any end user trying to use these results to track or graph on numerical scale.

To reproduce

Steps to reproduce the behavior:

  1. Go to training.malcolm.fyi bacnet dashboard
  2. observe the value read/write visualization

Unfortunately, this is not reproducible in the CELR, so the training instance is the only one I can show.

Expected behavior

T and F would be more easily shown as 1 and 0 for tracking purposes as these can be charted MUCH more easily in opensearch viz toolkits.

Any helpful log output or screenshots

image

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

1 participant