{"id":1113,"date":"2026-04-22T21:45:29","date_gmt":"2026-04-22T20:45:29","guid":{"rendered":"https:\/\/ketandesai.co.uk\/?p=1113"},"modified":"2026-04-22T21:58:02","modified_gmt":"2026-04-22T20:58:02","slug":"keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown","status":"publish","type":"post","link":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/","title":{"rendered":"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown"},"content":{"rendered":"<div class=\"wp-block-post-excerpt\"><p class=\"wp-block-post-excerpt__excerpt\">How to keep a legacy Efergy Engage Hub working after the vendor cloud disappears by running a local replacement server in a TrueNAS SCALE container. <\/p><\/div>\n\n\n<figure class=\"wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex\">\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"894\" height=\"867\" data-id=\"1116\" src=\"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub.jpg\" alt=\"\" class=\"wp-image-1116\" srcset=\"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub.jpg 894w, https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub-300x291.jpg 300w, https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub-768x745.jpg 768w\" sizes=\"auto, (max-width: 894px) 100vw, 894px\" \/><\/figure>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"600\" height=\"600\" data-id=\"1117\" src=\"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_transmitter.jpg\" alt=\"\" class=\"wp-image-1117\" srcset=\"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_transmitter.jpg 600w, https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_transmitter-300x300.jpg 300w, https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_transmitter-150x150.jpg 150w\" sizes=\"auto, (max-width: 600px) 100vw, 600px\" \/><\/figure>\n<\/figure>\n\n\n\n<p>When Efergy took down the servers behind the old Engage platform, a lot of perfectly functional energy-monitoring hubs were turned into near e-waste overnight.<\/p>\n\n\n\n<p>The hardware still worked. The sensors still worked. The hub still tried to phone home. But the API endpoint it depended on was gone.<\/p>\n\n\n\n<p>I recently came across a GitHub project that brings these legacy hubs back to life:<\/p>\n\n\n\n<p><a href=\"https:\/\/github.com\/DevOldSchool\/powermeter_hub_server\">https:\/\/github.com\/DevOldSchool\/powermeter_hub_server<\/a><\/p>\n\n\n\n<p>It emulates the old Efergy API locally, captures the hub\u2019s data, and stores it in SQLite. In other words, instead of sending readings to Efergy\u2019s cloud, the hub can be redirected to a service you run yourself.<\/p>\n\n\n\n<p>This post covers the basics of running it in a&nbsp;<strong>TrueNAS SCALE container<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What the project does<\/h2>\n\n\n\n<p>The&nbsp;<code>powermeter_hub_server<\/code>&nbsp;project is designed for legacy Efergy Engage hubs and works by running two services:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>legacy-nginx<\/strong>&nbsp;\u2014 a reverse proxy using an older OpenSSL stack so it can still accept the hub\u2019s legacy SSLv3 connection<\/li>\n\n\n\n<li><strong>hub-server<\/strong>&nbsp;\u2014 a Python service that emulates the Efergy API and stores readings in a local SQLite database<\/li>\n<\/ul>\n\n\n\n<p>That combination matters because the original hub expects to talk to&nbsp;<code>sensornet.info<\/code>&nbsp;over an old SSL\/TLS stack that modern services generally won\u2019t accept.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why TrueNAS?<\/h2>\n\n\n\n<p>If you already run TrueNAS SCALE at home, it makes a good landing spot for this kind of rescue project:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>always on<\/li>\n\n\n\n<li>easy persistent storage<\/li>\n\n\n\n<li>simple container management<\/li>\n\n\n\n<li>already central to many home-lab environments<\/li>\n<\/ul>\n\n\n\n<p>It is also a neat way to keep the service local and under your control rather than depending on another hosted workaround.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Before you start<\/h2>\n\n\n\n<p>You\u2019ll need:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>a&nbsp;<strong>TrueNAS SCALE<\/strong>&nbsp;system with Apps or container support<\/li>\n\n\n\n<li>an&nbsp;<strong>Efergy Engage hub<\/strong><\/li>\n\n\n\n<li>access to your&nbsp;<strong>local DNS<\/strong>&nbsp;or router DNS override<\/li>\n\n\n\n<li>the MAC address or expected hostname pattern for your hub<\/li>\n\n\n\n<li>a place to persist the database on TrueNAS<\/li>\n\n\n\n<li>a bit of comfort with container networking and volume mounts<\/li>\n<\/ul>\n\n\n\n<p>You will also need to generate the SSL certificate files expected by the project.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">High-level setup<\/h2>\n\n\n\n<p>The basic flow looks like this:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Deploy the project on TrueNAS<\/li>\n\n\n\n<li>Generate the required certificates<\/li>\n\n\n\n<li>Expose the container on port&nbsp;<strong>443<\/strong><\/li>\n\n\n\n<li>Persist the application data and SQLite database<\/li>\n\n\n\n<li>Redirect the hub\u2019s&nbsp;<code>sensornet.info<\/code>&nbsp;hostname to your local TrueNAS-hosted service<\/li>\n\n\n\n<li>Watch the logs to identify whether the hub is&nbsp;<strong>H1<\/strong>,&nbsp;<strong>H2<\/strong>, or&nbsp;<strong>H3<\/strong><\/li>\n\n\n\n<li>Adjust configuration such as&nbsp;<code>POWER_FACTOR<\/code><\/li>\n\n\n\n<li>Let it start collecting readings<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Container layout on TrueNAS SCALE<\/h2>\n\n\n\n<p>There are a couple of ways to do this on TrueNAS SCALE, depending on how you prefer to manage containers:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>via the&nbsp;<strong>Apps \/ Custom App<\/strong>&nbsp;route<\/li>\n\n\n\n<li>via&nbsp;<strong>Docker Compose<\/strong><\/li>\n\n\n\n<li>via a manually created container stack if you already manage your own tooling<\/li>\n<\/ul>\n\n\n\n<p>The project itself is built around a two-container compose layout, so the simplest mental model is:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>one container for&nbsp;<strong>legacy-nginx<\/strong><\/li>\n\n\n\n<li>one container for&nbsp;<strong>hub-server<\/strong><\/li>\n\n\n\n<li>one persistent host path for&nbsp;<strong>data<\/strong><\/li>\n\n\n\n<li>bind or map&nbsp;<strong>port 443<\/strong>&nbsp;from the host\/container environment<\/li>\n<\/ul>\n\n\n\n<p>If you are using the TrueNAS custom app flow, translate the compose settings into:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>image\/build configuration<\/li>\n\n\n\n<li>environment variables<\/li>\n\n\n\n<li>host path storage<\/li>\n\n\n\n<li>port mapping<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Persistent storage<\/h2>\n\n\n\n<p>At minimum, create a persistent dataset or host path for the project data.<\/p>\n\n\n\n<p>For example:<\/p>\n\n\n\n<p>bashCopyCopied!<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/mnt\/tank\/apps\/powermeter_hub_server\/data\n\/mnt\/tank\/apps\/powermeter_hub_server\/certs<\/code><\/pre>\n\n\n\n<p>This lets you keep:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the generated certificates<\/li>\n\n\n\n<li>the SQLite database (<code>readings.db<\/code>)<\/li>\n\n\n\n<li>any other persistent project state<\/li>\n<\/ul>\n\n\n\n<p>If you redeploy the container later, your data will still be there.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Example environment settings<\/h2>\n\n\n\n<p>The project supports several useful environment variables. For a UK setup, the important ones are typically:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>TZ=Europe\/London<\/code><\/li>\n\n\n\n<li><code>MAINS_VOLTAGE=245<\/code><\/li>\n\n\n\n<li><code>LOG_LEVEL=INFO<\/code><\/li>\n<\/ul>\n\n\n\n<p>Typical starting values:<\/p>\n\n\n\n<p>yamlCopyCopied!<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>TZ=Europe\/London\nLOG_LEVEL=INFO\nMAINS_VOLTAGE=245\nPOWER_FACTOR=0.6\nHISTORY_RETENTION_MONTHS=0\nMQTT_ENABLED=false\nHA_DISCOVERY=false<\/code><\/pre>\n\n\n\n<p>Do not worry too much about&nbsp;<code>POWER_FACTOR<\/code>&nbsp;until you know the hub version. Get it running first, inspect the logs, then adjust.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Networking considerations on TrueNAS<\/h2>\n\n\n\n<p>This is the part that matters most.<\/p>\n\n\n\n<p>The hub expects to reach&nbsp;<code>sensornet.info<\/code>-style hostnames over&nbsp;<strong>HTTPS on port 443<\/strong>.<\/p>\n\n\n\n<p>That means your TrueNAS-hosted service must be reachable on the local network in a way the hub can actually connect to.<\/p>\n\n\n\n<p>You generally need:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>port&nbsp;<strong>443<\/strong>&nbsp;exposed to the LAN<\/li>\n\n\n\n<li>the hub\u2019s expected hostname redirected to your TrueNAS IP<\/li>\n\n\n\n<li>no other service on the same IP\/port conflicting with it<\/li>\n<\/ul>\n\n\n\n<p>If your TrueNAS box already uses port 443 for something else, you have a few choices:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>dedicate another IP to the container or service<\/li>\n\n\n\n<li>use a separate host on the LAN<\/li>\n\n\n\n<li>rework your network design so the hub still reaches the correct endpoint on 443<\/li>\n<\/ol>\n\n\n\n<p>Because the Efergy hub is old and rather opinionated, it is usually easier to adapt your local network to it rather than the other way around.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">DNS redirection<\/h2>\n\n\n\n<p>This is what makes the whole workaround function.<\/p>\n\n\n\n<p>You need your hub to resolve the old Efergy hostnames to the IP address of the machine running this service.<\/p>\n\n\n\n<p>Depending on hub generation, the expected domain format differs.<\/p>\n\n\n\n<p>Examples from the project documentation include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>v1 hubs:<\/li>\n\n\n\n<li><code>[MAC].sensornet.info<\/code><\/li>\n\n\n\n<li><code>[MAC].keys.sensornet.info<\/code><\/li>\n\n\n\n<li>v2\/v3 hubs:<\/li>\n\n\n\n<li><code>[MAC].h2.sensornet.info<\/code><\/li>\n\n\n\n<li><code>[MAC].h3.sensornet.info<\/code><\/li>\n<\/ul>\n\n\n\n<p>You can do this using:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>your router, if it supports local DNS overrides<\/li>\n\n\n\n<li>Pi-hole<\/li>\n\n\n\n<li>dnsmasq<\/li>\n\n\n\n<li>Unbound<\/li>\n<\/ul>\n\n\n\n<p>In practice, local DNS is where most of the troubleshooting time goes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying the hub version<\/h2>\n\n\n\n<p>Once the stack is up and the hub is redirected to it, check the logs.<\/p>\n\n\n\n<p>The project can detect and log the hub version when it first receives traffic.<\/p>\n\n\n\n<p>You are looking for messages such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>Detected Efergy Hub version: H1<\/code><\/li>\n\n\n\n<li><code>Detected Efergy Hub version: H2<\/code><\/li>\n\n\n\n<li><code>Detected Efergy Hub version: H3<\/code><\/li>\n<\/ul>\n\n\n\n<p>This matters because:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>H1 \/ H2<\/strong>&nbsp;generally use&nbsp;<code>POWER_FACTOR=0.6<\/code><\/li>\n\n\n\n<li><strong>H3<\/strong>&nbsp;generally uses&nbsp;<code>POWER_FACTOR=1.0<\/code><\/li>\n<\/ul>\n\n\n\n<p>If the detection message does not appear immediately, temporarily increase logging verbosity to&nbsp;<code>DEBUG<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Data persistence<\/h2>\n\n\n\n<p>The readings are stored in a SQLite database, usually&nbsp;<code>readings.db<\/code>.<\/p>\n\n\n\n<p>Make sure this lives on persistent storage, not inside an ephemeral container filesystem.<\/p>\n\n\n\n<p>That way:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>reboots are fine<\/li>\n\n\n\n<li>updates are fine<\/li>\n\n\n\n<li>redeployments are fine<\/li>\n\n\n\n<li>your historical data survives<\/li>\n<\/ul>\n\n\n\n<p>On TrueNAS, this is one of the easiest wins: just mount a dataset into the container path used by the application.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Optional: MQTT and Home Assistant<\/h2>\n\n\n\n<p>If you already use Home Assistant, this project becomes even more useful.<\/p>\n\n\n\n<p>It supports MQTT publishing and Home Assistant discovery, so you can feed your recovered Efergy data into dashboards and automations.<\/p>\n\n\n\n<p>Typical settings might look like this:<\/p>\n\n\n\n<p>yamlCopyCopied!<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>MQTT_ENABLED=true\nMQTT_BROKER=your-broker.local\nMQTT_PORT=1883\nMQTT_USER=your-user\nMQTT_PASS=your-password\nHA_DISCOVERY=true<\/code><\/pre>\n\n\n\n<p>That turns a rescued legacy hub into something genuinely useful rather than just a curiosity.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"204\" src=\"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy-on-HA-1024x204.png\" alt=\"\" class=\"wp-image-1118\" srcset=\"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy-on-HA-1024x204.png 1024w, https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy-on-HA-300x60.png 300w, https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy-on-HA-768x153.png 768w, https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy-on-HA-1536x305.png 1536w, https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy-on-HA-2048x407.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Things to watch out for<\/h2>\n\n\n\n<p>A few caveats.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. SSLv3 is ancient<\/h3>\n\n\n\n<p>This project works precisely because it accommodates very old behaviour. That is fine on an isolated home LAN, but I would not expose this service to the public internet.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Port 443 conflicts<\/h3>\n\n\n\n<p>If TrueNAS or another reverse proxy is already using 443 on the same IP, plan around that before you start.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. DNS is the real trick<\/h3>\n\n\n\n<p>Most of the \u201cwhy isn\u2019t it working?\u201d problems come down to hostname resolution and whether the hub is really being redirected where you think it is.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Legacy hardware is fussy<\/h3>\n\n\n\n<p>Be prepared to test, reboot the hub, inspect logs, and tweak configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why this matters<\/h2>\n\n\n\n<p>A vendor turns off a server and suddenly a perfectly good device stops being useful. Not because the hardware failed, but because someone decided the cloud dependency no longer mattered.<\/p>\n\n\n\n<p>Projects like&nbsp;<code>powermeter_hub_server<\/code>&nbsp;are a useful reminder that a lot of \u201cdead\u201d smart hardware is only dead in the commercial sense.<\/p>\n\n\n\n<p>Sometimes all it needs is:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>a local endpoint<\/li>\n\n\n\n<li>a bit of DNS trickery<\/li>\n\n\n\n<li>and a home for the service to run<\/li>\n<\/ul>\n\n\n\n<p>TrueNAS turns out to be a perfectly reasonable place to host that home.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Useful links<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Project:&nbsp;<a href=\"https:\/\/github.com\/DevOldSchool\/powermeter_hub_server\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/github.com\/DevOldSchool\/powermeter_hub_server<\/a><\/li>\n\n\n\n<li>Efergy UK:&nbsp;<a href=\"https:\/\/uk.efergy.com\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/uk.efergy.com\/<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Final thoughts<\/h2>\n\n\n\n<p>If you have an old Efergy Engage hub lying around and thought it was finished after the API disappeared, it may not be.<\/p>\n\n\n\n<p>Running a local replacement on TrueNAS gives the device a second life, keeps data in your control, and avoids binning hardware that still does the job.<\/p>\n\n\n\n<p>That is a much better outcome than \u201cthe cloud got turned off\u201d.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How to keep a legacy Efergy Engage Hub working after the vendor cloud disappears by running a local replacement server in a TrueNAS SCALE container.<\/p>\n","protected":false},"author":1,"featured_media":1116,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[167,40,122,91,50,162],"tags":[],"class_list":["post-1113","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-docker","category-linux","category-networking","category-other","category-projects","category-truenas"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown - Ketan Desai<\/title>\n<meta name=\"description\" content=\"How to keep a legacy Efergy Engage Hub working after the vendor cloud disappears by running a local replacement server in a TrueNAS SCALE container.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown - Ketan Desai\" \/>\n<meta property=\"og:description\" content=\"How to keep a legacy Efergy Engage Hub working after the vendor cloud disappears by running a local replacement server in a TrueNAS SCALE container.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/\" \/>\n<meta property=\"og:site_name\" content=\"Ketan Desai\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-22T20:45:29+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-22T20:58:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"894\" \/>\n\t<meta property=\"og:image:height\" content=\"867\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Ketan Desai\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ketan Desai\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/\"},\"author\":{\"name\":\"Ketan Desai\",\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/#\\\/schema\\\/person\\\/76fbe7aaa79643c166c5c2475fc01424\"},\"headline\":\"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown\",\"datePublished\":\"2026-04-22T20:45:29+00:00\",\"dateModified\":\"2026-04-22T20:58:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/\"},\"wordCount\":1321,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/#\\\/schema\\\/person\\\/76fbe7aaa79643c166c5c2475fc01424\"},\"image\":{\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/ketandesai.co.uk\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/Efergy_hub.jpg\",\"articleSection\":[\"Docker\",\"Linux\",\"Networking\",\"Other\",\"Projects\",\"TrueNas\"],\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/\",\"url\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/\",\"name\":\"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown - Ketan Desai\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/ketandesai.co.uk\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/Efergy_hub.jpg\",\"datePublished\":\"2026-04-22T20:45:29+00:00\",\"dateModified\":\"2026-04-22T20:58:02+00:00\",\"description\":\"How to keep a legacy Efergy Engage Hub working after the vendor cloud disappears by running a local replacement server in a TrueNAS SCALE container.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/#primaryimage\",\"url\":\"https:\\\/\\\/ketandesai.co.uk\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/Efergy_hub.jpg\",\"contentUrl\":\"https:\\\/\\\/ketandesai.co.uk\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/Efergy_hub.jpg\",\"width\":894,\"height\":867},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/2026\\\/04\\\/22\\\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/ketandesai.co.uk\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/#website\",\"url\":\"https:\\\/\\\/ketandesai.co.uk\\\/\",\"name\":\"Ketan Desai\",\"description\":\"Anything IT\",\"publisher\":{\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/#\\\/schema\\\/person\\\/76fbe7aaa79643c166c5c2475fc01424\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/ketandesai.co.uk\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/ketandesai.co.uk\\\/#\\\/schema\\\/person\\\/76fbe7aaa79643c166c5c2475fc01424\",\"name\":\"Ketan Desai\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6587572e3884edb2f25ce127069b15f15da32278153bc9b4d2568156fcb6ec41?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6587572e3884edb2f25ce127069b15f15da32278153bc9b4d2568156fcb6ec41?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6587572e3884edb2f25ce127069b15f15da32278153bc9b4d2568156fcb6ec41?s=96&d=mm&r=g\",\"caption\":\"Ketan Desai\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6587572e3884edb2f25ce127069b15f15da32278153bc9b4d2568156fcb6ec41?s=96&d=mm&r=g\"},\"sameAs\":[\"http:\\\/\\\/staging.ketandesai.co.uk\"],\"url\":\"https:\\\/\\\/ketandesai.co.uk\\\/index.php\\\/author\\\/ketandesaiadmin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown - Ketan Desai","description":"How to keep a legacy Efergy Engage Hub working after the vendor cloud disappears by running a local replacement server in a TrueNAS SCALE container.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/","og_locale":"en_GB","og_type":"article","og_title":"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown - Ketan Desai","og_description":"How to keep a legacy Efergy Engage Hub working after the vendor cloud disappears by running a local replacement server in a TrueNAS SCALE container.","og_url":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/","og_site_name":"Ketan Desai","article_published_time":"2026-04-22T20:45:29+00:00","article_modified_time":"2026-04-22T20:58:02+00:00","og_image":[{"width":894,"height":867,"url":"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub.jpg","type":"image\/jpeg"}],"author":"Ketan Desai","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ketan Desai","Estimated reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/#article","isPartOf":{"@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/"},"author":{"name":"Ketan Desai","@id":"https:\/\/ketandesai.co.uk\/#\/schema\/person\/76fbe7aaa79643c166c5c2475fc01424"},"headline":"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown","datePublished":"2026-04-22T20:45:29+00:00","dateModified":"2026-04-22T20:58:02+00:00","mainEntityOfPage":{"@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/"},"wordCount":1321,"commentCount":0,"publisher":{"@id":"https:\/\/ketandesai.co.uk\/#\/schema\/person\/76fbe7aaa79643c166c5c2475fc01424"},"image":{"@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/#primaryimage"},"thumbnailUrl":"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub.jpg","articleSection":["Docker","Linux","Networking","Other","Projects","TrueNas"],"inLanguage":"en-GB","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/","url":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/","name":"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown - Ketan Desai","isPartOf":{"@id":"https:\/\/ketandesai.co.uk\/#website"},"primaryImageOfPage":{"@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/#primaryimage"},"image":{"@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/#primaryimage"},"thumbnailUrl":"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub.jpg","datePublished":"2026-04-22T20:45:29+00:00","dateModified":"2026-04-22T20:58:02+00:00","description":"How to keep a legacy Efergy Engage Hub working after the vendor cloud disappears by running a local replacement server in a TrueNAS SCALE container.","breadcrumb":{"@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/#primaryimage","url":"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub.jpg","contentUrl":"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub.jpg","width":894,"height":867},{"@type":"BreadcrumbList","@id":"https:\/\/ketandesai.co.uk\/index.php\/2026\/04\/22\/keeping-an-efergy-engage-hub-alive-on-truenas-after-the-cloud-shutdown\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/ketandesai.co.uk\/"},{"@type":"ListItem","position":2,"name":"Keeping an Efergy Engage Hub Alive on TrueNAS After the Cloud Shutdown"}]},{"@type":"WebSite","@id":"https:\/\/ketandesai.co.uk\/#website","url":"https:\/\/ketandesai.co.uk\/","name":"Ketan Desai","description":"Anything IT","publisher":{"@id":"https:\/\/ketandesai.co.uk\/#\/schema\/person\/76fbe7aaa79643c166c5c2475fc01424"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/ketandesai.co.uk\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":["Person","Organization"],"@id":"https:\/\/ketandesai.co.uk\/#\/schema\/person\/76fbe7aaa79643c166c5c2475fc01424","name":"Ketan Desai","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/secure.gravatar.com\/avatar\/6587572e3884edb2f25ce127069b15f15da32278153bc9b4d2568156fcb6ec41?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/6587572e3884edb2f25ce127069b15f15da32278153bc9b4d2568156fcb6ec41?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6587572e3884edb2f25ce127069b15f15da32278153bc9b4d2568156fcb6ec41?s=96&d=mm&r=g","caption":"Ketan Desai"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/6587572e3884edb2f25ce127069b15f15da32278153bc9b4d2568156fcb6ec41?s=96&d=mm&r=g"},"sameAs":["http:\/\/staging.ketandesai.co.uk"],"url":"https:\/\/ketandesai.co.uk\/index.php\/author\/ketandesaiadmin\/"}]}},"jetpack_featured_media_url":"https:\/\/ketandesai.co.uk\/wp-content\/uploads\/2026\/04\/Efergy_hub.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/posts\/1113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/comments?post=1113"}],"version-history":[{"count":3,"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/posts\/1113\/revisions"}],"predecessor-version":[{"id":1121,"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/posts\/1113\/revisions\/1121"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/media\/1116"}],"wp:attachment":[{"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/media?parent=1113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/categories?post=1113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ketandesai.co.uk\/index.php\/wp-json\/wp\/v2\/tags?post=1113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}