lawik
I don’t know why I did not try this sooner:
System.cmd("epmd", ["-daemon"])
Node.start(:"nerves@#{Toolshed.hostname()}.local")
Node.set_cookie(:mycookie)
And voíla you can connect the regular Livebook app to your device as an attached node and you can run and re-run entire experiments over and over again.
The fact that you keep your livebook can make this a fair bit more practical than the IEx session I use so much during Nerves development.
Need to try it with some sensors and graphs as well.
When I mentioned this on Slack Frank brought up the need for port forwarding on NervesHub so you can connect to you devices. That would be quite rad and I need to read more about wireguard 
I imagine this would allow having runbooks for checking the status of a device. Fixes for known problems. That kind of stuff. And of course working with a specific troubled device over time. Without pasting stuff over and over.
Any other ideas about how to use it?
Where Next?
Trending in Discussions
Other Trending Topics
Latest Nerves Threads
Latest Livebook Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
jonatanklosko
For completeness, depending on the use case, you can also use the “Remote execution” smart cell. This should remove restriction on Elixir version compatibility between Livebook and the Nerves device. Also, this way you can offload some computation to the local machine, and you can bring extra dependencies for charting data and whatnot. Finally, it has a lower footprint, because attaching Livebook temporarily loads some Livebook-specific modules into the node, whereas the cell only does an
:erpccall : )lawik
That is a very good note. I just happened to be on recent versions that match I suppose.
D4no0
Doesn’t nerves hub already provide ssh connectivity to the devices? If yes, then you can use port forward via ssh.
lawik
Not quite. Nerves provides SSH into IEx.
NervesHub provides IEx terminal in the browser over WebSocket without needing a direct network path from you to the device. Device connects to NervesHub over WebSocket. You connect to NervesHub via browser. Meaning free NAT traversal and so on but no general networking.
Two similar features but quite different.
D4no0
Makes sense, a pretty optimal solution that is easy to manage.
I was investigating a few years ago about potential solutions to overcome restricted networks and I am positive SSH can set a reverse tunnel, the only thing you need to do is monitor the connection and restart it from time to time, otherwise it should behave in the same manner as the websocket connection you are currently establishing from client devices.
lawik
Yes. SSH can establish a tunnel for any traffic you like pretty much. We would need the device to connect to a NervesHub service and your device to connect as well and then make those sockets have a chat.
Wireguard can do the same. But to my understanding Wireguard is way less overhead and operates more like a VPN giving you a flat network. You would be able to treat it as if your Nerves device was on the local network. SSH is only port forwarding.
Wireguard would enable you to access a web UI, SSH and so on.
lawik
SSH remote tunnels were a blessing for me on restricted networks in my teens. I could expose any port I liked if could SSH to my home server and my home server ran SSH on port 443.
Not ehat I would do for a good dev flow with Livebook and Nerves though. Maybe some nice MNDP (mndp | Hex) for discovery which I guess could work over Wireguard. (Edit: seems like Wireguard does not support broadcast/multicast so no discovery)
D4no0
On this topic, there are also commercial solutions like cloudflare that offer a generous free tier. Their service is battery included, however their service is not protocol agnostic and you have to select one from the list when creating a tunnel.
The only big concern with the tunnel they provide is that you need to use their client, there is
cloudflaredthat is most probably too resource heavy for an IOT device, it’s more oriented to be deployed on a proxy server, andwarpthat they market as the lightweight replacement, but the one I never managed to get working on linux.