Thanks for confirming, I did wonder if that would be the case. That said I’m battling to get emoncms working nicely, and considering just trying to set up home assistant on another PI and pushing directly from the ebus to that.
I think that is what @borpin would recommend.
Home Assistant is just too much for a Pi now, unless it is a Pi5 and then you need SSD etc.
Better off with an old x86 architecture now. I’m on an old ‘Blue’, but if I had to move, I’d go to an old laptop with PVE installed for HA and use the emoncms add-on, or run emoncms in an LXC on the PVE platform. I’ve got PVE on a laptop, just not with HA running currently.
You could then use the Pi (any Pi) just for the ebus adapter, and push the data to emoncms/HA.
Thanks for the response.
I have been trying to just go with emonsd on a pi but, likely due to user error, I’m struggling to get the connection to be stable. I need to run in via WiFi as my plant room doesn’t have ethernet. If I could get it to be stable on WiFi then that would be ideal.
You can easily get by with HA on a Pi 4 and 4 GB of RAM. An x86 like a small NUC would be better, but if you’re just starting out the Pi 4 will pull its weight. If you don’t skinp on the quality SD card and adjust the recorder commit interval, you should be able to get something that runs sufficiently well.
However, if you need to put money into because you don’t have a Pi lying around, then I agree, much better to put the money into a Mini PC and run Proxmox on ot.
What exactly is the issue? Device dropping off the network?
Yes exactly that, I reboot it, it’s there and then I come back a bit later and it’s dropped off. I tired 4 different versions from different years and no real luck. I did this morning installe HA on the Pi 3b i have - some comments online said it will run Ok - and it booted up fine. There is nothing smart about my home, so using it to pull in the ebus data is all it needs do, so it might run fine.
If i get some time this evening, I’ll connect the ebus sheild to the heatpump and try work out mqtt to pull some data across.
Sounds more like a network issue to me. How far away is the access point?
I had it in the sitting room for testing, so the signal was perfect.
Im running HA on a Pi3 with no problems.
1 Like
The other thing that comes to mind is a power issue - whak model Pi are you running and what power supply are you using?
Pi 3b sony uk
I tried various power supplies but it did work 5v 2.1a, also tried 5v 2.4a and didn’t improve situation of dropping off.
Was any of those the original Pi power supply? The official supply is 5.1 V, 12.5 W (2.5 A) Micro USB, and at least newer Pi power supplys (e.g. the USB-C of the latest Pi 5) have quirks that do not adhere to the USB standard, so I would always suggest going with the original supply.
Curious. Mine also a pi3b but with the official power supply. Very reliable, but maybe I’m not putting much load on.
No they weren’t, so I could try that.
Well through shear luck I have got the ebusd adaptor pushing into HA. Tomorrow i’ll plug the ebusd into the ASHP and see what data I can start pulling across. I wanted to get it working before plugging it in.
1 Like
Nice, any idea which bit was the key in the end?
Well, I gave up trying to get EmonSD running on the PI and just flashed and loaded Home Assistant as that seems to be how a few others in here are capturing data from the ebusd sheild. I do still need to get the data from the ASAP through the ebusd, but I am getting data from the ebusd into Home Assistant, so I should be able to get it. I’ll see, when I have more time to waste on silly projects.
1 Like
And I am getting data from the ebusd into Home Assistant web interface, a lot of unknowns but some good data too.
Nice!
2 Likes
OK the unknows were because you need to poll for them in the ebus web interface, i guess they’re not transmitted openly or something. Now getting some nice data, including energy integral.
Search the threads on the forum, there are a few pointers on how to regularly poll the data values you’re interested in.