-
Notifications
You must be signed in to change notification settings - Fork 1
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
M for Mode, depricating Z for Zombie #3
Comments
I'm in favour of deprecating 'Zombie', we need a rough (optional) spec for the Mode values first though. |
Mode does make more sense and having a number of different values is a good idea. We probably can't reassign Z though as a number of nodes will continue to use it. Obviously will try and update them but quite a few are hard to get to. |
If we were going to munge all of these attributes into one field then we could use a bitmask. The problem with that is it isn't possible to parse in grafana. That said, I think any method of doing this is going to require some additional parsing on the grafana inserter. If we were happy to sacrifice a byte or two and have a slightly differently-formatted field, we could assign a (lowercase) letter to each of these statuses. So you could have "Zombie mode" is really just "not a repeater" so it probably doesn't need a letter by itself. My solarnodes use an X field to communicate battery charge status, so we could also have a "charging" and "charged" status. |
+1 for the lowercase letter flags! |
@russss I somewhat disagree on the point about zombie mode. Zombie mode means that the node isn't even listening for packets, and that it probably is doing some deep sleep between sending packets. A node could be made to listen for packets, while not repeating them. It could still be acting on the received packets. |
Well in that case, listening for command packets would be a candidate for a flag. |
I suggest using the M character as a replacement for Z, allowing for more different states to be transmitted.
Lost in the conversion from the wiki;
The text was updated successfully, but these errors were encountered: