-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Good day,
First of all, thank you for this project — it has been extremely helpful. My Efergy Engage hub stopped posting data to the official service about a week ago, and I was very glad to find your work.
I have successfully deployed powermeter_hub_server, and my hub is now connecting correctly over HTTPS.
DNS and SSL are confirmed working.
My setup:
Efergy Engage V3 / H3 hub
Hub hostname observed in Pi-hole:
c8.XX.XX.d88039.h3.sensornet.info
At the moment, I’m stuck at the data parsing stage. The hub is actively sending POST requests, but the server logs show the following repeatedly:
Unknown POST path or content-type: /h3bulk / application/eh-datalog
This suggests the hub is using the /h3bulk endpoint with the application/eh-datalog content type, which I believe is newer firmware behavior.
Could you please advise:
Whether /h3bulk + application/eh-datalog is already supported in a newer branch or fork, or
If there are plans to support this endpoint, or
If you’d be open to guidance on how this payload should be handled (even raw logging would help).
I’m happy to help test or provide additional logs if needed.
Thanks again for making this project available — it’s already brought these hubs much closer to being usable again.
Best regards,
Oni
my logs are showing this message below:
hub-server | 2026-01-10 12:20:50,172 [WARNING] hub_server.py:162 - Unknown POST path or content-type: /h3bulk / application/eh-datalog
hub-server | 2026-01-10 12:20:52,190 [WARNING] hub_server.py:162 - Unknown POST path or content-type: /h3bulk / application/eh-datalog
hub-server | 2026-01-10 12:20:54,202 [WARNING] hub_server.py:162 - Unknown POST path or content-type: /h3bulk / application/eh-datalog
restarted
pi@RP3:~/powermeter_hub_server $ docker compose logs -f hub-server
hub-server | 2026-01-10 10:57:53,329 [INFO] hub_server.py:252 - ============================================================
hub-server | 2026-01-10 10:57:53,330 [INFO] hub_server.py:253 - Efergy Hub Server
hub-server | 2026-01-10 10:57:53,331 [INFO] hub_server.py:254 - Version: v1.2.3
hub-server | 2026-01-10 10:57:53,331 [INFO] hub_server.py:255 - ============================================================
hub-server | 2026-01-10 10:57:53,331 [INFO] hub_server.py:256 - Python: 3.14.2
hub-server | 2026-01-10 10:57:53,331 [INFO] hub_server.py:257 - Port: 5000
hub-server | 2026-01-10 10:57:53,331 [INFO] hub_server.py:258 - Logging level: INFO
hub-server | 2026-01-10 10:57:53,331 [INFO] hub_server.py:259 - MQTT: enabled
hub-server | 2026-01-10 10:57:53,332 [INFO] hub_server.py:260 - HA discovery: enabled
hub-server | 2026-01-10 10:57:53,332 [INFO] hub_server.py:261 - Monthly reset: False
hub-server | 2026-01-10 10:57:53,332 [INFO] hub_server.py:262 - Retention months: 0
hub-server | 2026-01-10 10:57:53,332 [INFO] hub_server.py:263 - ============================================================
hub-server | 2026-01-10 10:57:53,333 [INFO] database.py:38 - Database initialized at path: /app/data/readings.db
hub-server | 2026-01-10 10:57:53,544 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 1 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:57:58,549 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 2 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:58:03,553 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 3 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:58:08,558 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 4 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:58:13,572 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 5 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:58:18,577 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 6 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:58:23,582 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 7 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:58:28,587 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 8 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:58:33,592 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 9 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:58:38,598 [WARNING] mqtt_manager.py:69 - MQTT connection attempt 10 failed: [Errno -2] Name or service not known
hub-server | 2026-01-10 10:58:43,599 [ERROR] mqtt_manager.py:71 - Failed to connect to MQTT broker after multiple attempts.
hub-server | 2026-01-10 10:58:43,603 [INFO] hub_server.py:225 - Serving HTTP on 0.0.0.0 port 5000...
hub-server | 2026-01-10 10:58:46,659 [WARNING] hub_server.py:162 - Unknown POST path or content-type: /h3bulk / application/eh-datalog
hub-server | 2026-01-10 11:03:43,624 [INFO] database.py:418 - [AGG] Hour 2026-01-10 10:00 => 0.64842 kWh