schema for _type=lwt is requiring data about json-schema HOT 5 OPEN

This is probably when using application level encryption. I guess lwt is not encrypted

from json-schema.

Looking at #755 again regarding the not-encrypted lwt message: I think it's fine and logical that it's not encrypted (and it can't really be as the broker doesn't know anything about encryption), but I wonder whether it would be feasable to give the broker an LWT to transmit which has encrypted data ... ? IIRC libsodium isn't time sensitive, so technically it ought to be possible to

1. encrypt a payload for LWT
2. submit the LWT on connect to the broker
3. have the broker transmit the pre-encrypted LWT when the client dies

I'm definitely not saying we should do this; I'm rather thinking out loud whether it could make sense?

A disadvantage would be that monitors (other than, say, Recorder) for LWT would not be able to decrypt the payload.

from json-schema.

This is probably when using application level encryption. I guess lwt is not encrypted

@ckrey yes, application level encryption is enabled.

from json-schema.

I learned a lot about how app level encryption is used with OwnTracks...

from json-schema.

Basically, old versions process encrypted and unencrypted messages well.
In the newer versions, non encrypted messages cause a crash. Will revert the change.
I believed if app level encryption is enabled everything outgoing or incoming is encrypted...

from json-schema.