Metadata editing & zones handling feature

[VladimirKalachikhin]

Is the "message" field in zones definition a human-readable message only? Can I use it for technical purposes or shouldn't?

[tkurki]

I think it is meant as human readable, but to be honest I don’t think it does anything with the current implementation.

What kind of technical usage do you have in mind?

[VladimirKalachikhin]

I wrote a message, where did it go? Repeated:

If I want to have two zone sets for one parameter, what should I do?
For example, one set of depth zones for safety and one for fishing.

The "message" field is the only field that is passed from meta to notifications. And by the contents of this field, you can determine which zone has triggered. The client can take appropriate action. For example, show the message for fishing only on the client from which the fishing zones were assigned.

But does it need to be done globally at all, through the server?

[VladimirKalachikhin]

I think that all the properties from "zone" should be transferred to the triggered notification, including custom properties. Then it would be possible to organize many sets of zones for one property.
But it would be more correct to have not one set of "zones" in the meta, but an array of sets. Each set must have its own property "alarmMethod", class, source, etc. Then you could have, for example, several fishing depth zones along with a safety depth zone.