Editor's note: We should now be back to our non-vacation cadence. Good to be back.
I also have a question from Frank Hunleth to the industrial users of Nerves, he is collecting some guidance for future choices. I hope this is not too late to be useful as I missed getting it into the previous one:
"Are any of the industrial Nerves users here having performance issues with Erlang and Elixir on your devices? If so, can you give any details? I know that most of you prefer to DM me and that’s totally fine. I’m trying to assess whether there’s interest in funding performance improvements that are specific to embedded and if so, what the pain points are."
If you can weigh in on that, find Frank on Twitter, in the Elixir Slack or via email I bet and you can share your insights. If you send 'em to me I'll pass it on too.
Added support for handling WiFi events. Currently events associated with WiFi AP associations are reported since they can be helpful when creating WiFi configuration user interfaces. More could be supported in the future. Thanks to @dognotdog, @THE9rtyt, and @ConnorRigby for this feature.
Remove mesh peers from reported access point lists. Mesh peers are reported separately and mixing them with access points was unexpected. Thanks to @mattludwigs for identifying and fixing the issue.
On at least one device, the pin direction reported by Linux does not match the actual pin direction. This release forces the pin direction for inputs. It cannot do this for outputs, since setting a pin to output has a side effect on the pin state. This technically is a bug in a Linux driver port, but it was harmless to workaround for inputs so that’s what’s done. Thanks to @pojiro for investigating and fixing this issue.