Feature Request: For the Helium console to decode base64

[hpssjellis]

Feature Request: For the Helium console to have a simple decode of base64

A simple base64 decoding would be very useful for setting up simple integrations, without having to make a custom decoder. This would make basic testing of sensors much easier.

For example in the Integration JSON to be able to enter something like this without making a decoder.

{"value" : {{payload.decoded}} }

[jdgemm]

Given the current system, it appears a prebuilt 64 decoder would solve this use case, correct?

Combining integration and decoding functionality creates additional complexity and confusion.

[hpssjellis]

@jdgemm can we have a few others look at this feature request, perhaps @kent-williams and @jthiller. I get your concern about added complexity, but as a 30 year coding teacher the ease of a quick base64 decoder from the Helium Console JSON area (for people who want it) would actually add integration debugging simplification and reduce confusion.

[vicmgs]

@jdgemm need explanation on what exactly I need to change here

[hpssjellis]

@vicmgs Not sure exactly what you should do but here is the problem. If someone wants to view the original raw data sent to Helium from your Integration you need a decoder like https://github.com/helium/console-decoders/blob/master/debugDecodeBase64.js

and then this for your integration JSON

{ "value": {{decoded.payload.value}} }

A long drawn-out explanation of how to do this using the Arduino PortentaH7 is in the Helium DOCs here

Showing the raw data that was sent to Helium in your integration needs to be easier than using a decoder. If you can figure out how to do this directly in the integration custom JSON, that would be very useful.

[vicmgs]

@hpssjellis just to clarify, you want the ability to skip the function creation to decode base64 payloads, but use the integration json instead to do this simple decoding task.

The ideal workflow would be: you create the device, create the integration, update the integration json with the above, connect the device and integration in flows, and be all done and ready for device testing right?

https://github.com/helium/router/blob/master/src/channels/router_channel_utils.erl#L123-L141

[vicmgs]

it looks like you could do something like the below in the integration json and not connect a function and still decode the base64 somehow. Does that work for what you need?

{ "value": {{base64_to_hex(payload)}} } or { "value": {{base64_to_bytes(payload)}} }

[hpssjellis]

it looks like you could do something like the below in the integration json and not connect a function and still decode the base64 somehow. Does that work for what you need?

{ "value": {{base64_to_hex(payload)}} } or { "value": {{base64_to_bytes(payload)}} }

Thanks @vicmgs I will try that out and yes, if that works it would solve the whole issue, just need it communicated to more people. I should be able to test that today.

[hpssjellis]

@vicmgs

{
"value": {{base64_to_bytes(payload)}}
}

Works awesome I can close this now.

Is there a spot in the Helium Docs that mentions this?

[vicmgs]

awesome, that is great to hear. I will get the docs team involved to write this up.