Greg Troxel

Is someone going to make a PR to put that flex decoder in the sources? What do we need to do to close this issue?

answered question

I see this as an answered question. Please restate/clarify if not.

Is anyone up to a PR to add the flex decoder? Otherwise this seems abandoned.

That cries out for having a type field.

My impression is that things are better. In my own system I am seeing every 10s reports that look like: ``` {"time":"2023-09-29 12:00:50","src":"Auto Level","lvl":4,"msg":"Current noise level -26.0 dB, estimated noise...

@tom-hooper We are waiting a PR so we can close this issue.

Is it then time to submit a PR to add a flex decoder? if not, what's the plan to make progress towards being able to close this?

I think I land on - in rtl_433 it is ok to reject a message (and fail to decode!) as errored if a value is outside the specified range, eg...

You can send data with another tool. Look at rtl_433_mqtt_relay in examples and send it json with -F and syslog. The hard part is getting agreement on what/how, and the...