Closed jorgenbuilder closed 2 years ago
Likely the read_state responses that are displayed are update calls that need to be decoded. Here's an example from Bob Bodily:
read_state
{ "tag": 55799, "value": { "content": { "ingress_expiry": 1642119368434000000, "paths": { "0": { "0": { "type": "Buffer", "data": [ 114, 101, 113, 117, 101, 115, 116, 95, 115, 116, 97, 116, 117, 115 ] }, "1": { "type": "Buffer", "data": [ 42, 0, 42, 12, 37, 187, 30, 151, 58, 131, 61, 83, 176, 48, 123, 220, 40, 113, 220, 79, 110, 138, 141, 83, 175, 17, 32, 87, 133, 208, 242, 190 ] } } }, "request_type": "read_state", "sender": { "type": "Buffer", "data": [] } },
Update messages are displayed in a basic way as of 0.0.9. There are improvements to make, but seeing as they do show up now I will close this issue.
0.0.9
Likely the
read_state
responses that are displayed are update calls that need to be decoded. Here's an example from Bob Bodily: