I’ve been using it for almost 10 years now with no problem.
I guess the best option is to migrate to a shelly 3ph meter, but they are expensive, and I need to replace 3 installations of efergy, so x3 cost.
I’ve seen some radiowave sniffing projects wokring, but I don’t think that’s a good solution for me, especially in places where i have no HA installed.
Ten years is a good run! Even Google shelve popular platforms in less time.
It seems to be a planned and orderly exit, rather than bankruptcy or lack of money abruptly shutting down the business.
If only they would open source their code or document the API’s before shutdown…
Reverse engineering is painful when you realise that at the stroke of a pen, or click of a button and the solution would be readily available from the vendor.
That web server idea where web traffic is interrupted and redirected to a local web server sounds like the basis of an viable integration to feed the data either directly into HomeAssistant, or more broadly into something like MQTT for more universal use. Time to break out and wrangle some Python code! That db.py code looks like a tasty portion to start with.
I’m sure Efergy are looking at their options but may be constrained contractually. Have you contacted them to politely ask if they can help, and mutually offer their existing customers some continuity? Capturing customer data for marketing purposes is not always a driving factor.
I tried to contact them recently (they used to have an office in Greece, where I’m from) but it seems like the numbers i found are disconnected
I spent all morning to day trying to do something similar, and intercept the hub’s efforts to connect to efergy, and I must say (although I am ignorant, with the help of chatgpt) I managed to get a running log of the increasing daily consumption.
But with a hundred problems.
So it is doable, but I just want to make sure it’s impossible before I go and spend a fortune on three shelly 3phase sensors.
Efergy is Spanish based, but you may have better results if contacting one of their international distributors who may be privy to API internals but see a future to support future customers.
I just noticed this in passing while doing a bit of backgrounding. It might be your salvation. You may even be able to run it up as a seperate container on your HomeAssistant device.
You’ve already got the hardware. It is still working. It is collecting the correct data. All you need to do is harvest it differently, a software challenge, not a hardware replacement one.
