I have a tutorial that shows you how to get PubSub and LiveView working together here: https://dennisbeatty.com/how-to-create-a-todo-list-with-phoenix-liveview/

But if you’ve already got the handle_info callback in place, you’ll probably just need to call Phoenix.PubSub.subscribe/2 in your live view’s init callback.

You need to make sure the subscribe is protected by connected?/1 as described here:
[Phoenix.LiveView — Phoenix LiveView v1.2.5]

Use connected?/1 to conditionally perform stateful work, such as subscribing to pubsub topics, sending messages, etc.

Sure. The issue was more conceptual.

Coming from a Javascript / Nodejs background I presumed that LiveView works like a server. So when I run iex -S mix phx.server it starts up the server, runs mount and configures it’s responses based on implementations of handle_event, handle_info etc. I was hoping to broadcast messages to clients that then connected. In short the server runs before a connection is made. I was therefore watching out for the subscription to run and get a log of the messages, which obviously didn’t happen.

As I can see LiveView spins up a process for each connection. Mount doesn’t run and therefore subscription doesn’t initiate till the client connects.

Once connected the subscription was initiated. There was a small issue with implementation of handle_info which logged an error. Corrected that and now it works.

Thanks once again.