WebSocket max total cost increase

API
1

Hi!
I am currently programming a small display with an ESP-32 to show if a few selected streams are currently online and their titles when they change.
I do this by subscribing to the stream.online, stream.offline, and channel.update messages using WebSockets. Due to the max_total_cost of 10, this gives me a maximum of 3 streams I can monitor with my current implementation. Ideally I want to be able to monitor about 10 streams.
To increase this I see the following possibilities:

  1. Somehow increase the max_total_cost.
    I could not find any documention regarding this and from what I could find in this forum this is not possible.
  2. Optimise the subscriptions by not subscribing to all messages all the time but only when they get relevant.
    Would singificantly increase the code complexity for a maximum of 5 streams.
  3. Using Conduits with a WebSocket shard.
    Would increase the code complexity and I would need an app access token but I would not have the max_total_cost limit of 10 and could easily monitor 10 or more streams.

So the only sensible option I found would be using Conduits. But I feel this method and the app access token were not intended for something like I am doing. So my question would be if have a false understanding of something or if I missed some details or possibilities which would better fit my use case? Thank you very much!

2

Call the API instead and look up 100 channels in one call.

Real time might be overkill for your use case here given the limitations of the ESP-32

3

I’m actually already doing that every 10 minutes to resync the stream states in case some messages were lost. But I went with WebSockets to reduce unnecessary network traffic. And it works pretty well for now. But I guess just using the API would be alot easier. Thanks for your input.