#evohome

Live, measured metrics for the hashtag #evohome from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #evohome

This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.

$240.06/ year · 7-character #name
Claim #evohome — $240.06/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
17
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 17
0.1
Avg reactions / post
Mastodon · last 17

Day-by-day usage

measured · mas.to (Mastodon public tags API) · fetched 2026-07-30 13:09 UTC
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28
0
07-29
0
07-30

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · mas.to (Mastodon public search API) · fetched 2026-07-30 13:09 UTC

No related tags with measured usage found for #evohome.

Live pulse

measured · mas.to (Mastodon tag timeline) · fetched 2026-07-30 13:09 UTC

Everything below is measured over the latest 17 public posts (spanning ~24732 hours).

Posting hours (UTC) — busiest: 09:00

00:0012:0023:00

Languages: English (17)

Avg boosts / post: 0.4

Top of the latest posts

  • I think I've found the problem, as other ppl are having the same issue: https://github.com/home-assistant/core/issues/145708 Looking through the HA logs I can see other integrations also getting timeouts, it's much more obvious in the #evoh

    Gary :party_porg:@[email protected]♥ 1↻ 12025-12-11 09:07 UTCView post →

  • FIX: set the docker container to bypass my dnsmasq caching resolver, and go directly to an upstream resolver (Quad9 in my case) #evohome #homeAssistant

    Gary :party_porg:@[email protected]♥ 0↻ 12025-12-11 10:03 UTCView post →

  • Doing the usual tests (ping, nslookup, dig) from the docker host, and from within the container, interactively always works fine. It seems to be something weird that the evohome-async code, or one of its dependencies, is doing. The DNS reco

    Gary :party_porg:@[email protected]♥ 0↻ 12025-12-10 18:19 UTCView post →

Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/evohome