BTC Price and mining stats screen shows no data on NerdQAxe++

[aposada]

Hi,

I'm experiencing an issue with my NerdQAxe++ where the BTC Price and Stats screen never displays any information.

Details:

• Device: NerdQAxe++
• Firmware: v1.1.0-rc1 (latest)
• The problem has also been present on previous firmware versions.
• Everything else appears to work normally, but the BTC price and statistics remain empty and never update.

Is this a known issue, or is there any configuration I should check? Any ideas on what could be causing this?

Thanks!

[aposada]

@aposada have you been able to resolve this issue?

Not

maybe is related with this ERROR (RED color in logs):

E (6262259) esp-tls: [sock=52] select() timeout
E (6262259) esp-tls: Failed to open new connection
E (6262259) transport_base: Failed to open a new connection
E (6262259) HTTP_CLIENT: Connection failed, sock < 0
E (6262269) APIsFetcher: HTTP GET request failed: ESP_ERR_HTTP_CONNECT
E (6262269) APIsFetcher: HTTP request error details: errno=0, transport=SSL

Could this be related to the API endpoint used for the BTC Price and Stats? The serial log shows an SSL connection failure (ESP_ERR_HTTP_CONNECT), so it looks like the device can't establish an HTTPS connection before receiving any data.

Which API is the firmware using for these values? Is there any known issue with the endpoint or its SSL certificate?

[shufps]

Hmm it's using mempool.space but now the URL can be configured in the settings.

Will have a look 🧐

edit: It doesn't seem to be broken per se, it's working with the newest rc1 on my miner 🤔

[aposada]

Thanks!

I'm using the custom mempool endpoint with:

https://mempool.space

I've tried both enabling and disabling the custom endpoint, but the BTC Price and Stats screens remain empty.

Could you confirm that this is the expected URL? Or does the firmware expect a different endpoint (for example including /api)?

The serial log still shows:

ESP_ERR_HTTP_CONNECT

with SSL connection errors.

[aposada]

Hi, I changed the API endpoint to https://mempool.emzy.de and it works correctly with this mirror.

The issue only occurs when using https://mempool.space. From my computer on the same network, curl https://mempool.space/api/blocks/tip/height works without any problems, so general connectivity and DNS don't seem to be the issue.

This suggests there may be some incompatibility between the device/firmware and the current mempool.space endpoint (possibly related to TLS or the HTTP connection), while mempool.emzy.de works as expected.

[shufps]

This suggests there may be some incompatibility between the device/firmware and the current mempool.space endpoint (possibly related to TLS or the HTTP connection), while mempool.emzy.de works as expected.

Hmm but you are currently the only one reporting this hmm 🤔

That's weird, will do some testings 🤔