I have been on and off this site for months. Before I make an investment in both time and equipment for a solution based on OpenEnergyMonitor I wanted to get feedback from the experts.
The following is what I want to achieve. I am interested in feedback on the optimum scalable approach.
I want to be able to monitor and record data for
1. Power (Connected and Solar)
2. Temperature and humidity for 9 rooms
3. Water consumption (6 sensors). Sensors for water flow, usage and tank depths being built.
4. Misc sensors. (4 sensors). Being built.
This will be self hosted on a Windows 10 server to be built.
What combination of OpenEnergyMonitor equipment in what configuration do you recommend ?
Your input is appreciated.
Re: Design advice
Without knowing what your unspecified "sensor" does / requires / gives in terms of output, Q3 & Q4 are unanswerable.
Without knowing whether you're on a single-phase, split single-phase or a three-phase supply, Q1 is unanswerable.
That leaves 9 × emonTH for the temperature and humidity - unless you want to build your own expanded version with 9 (or maybe 10 - without checking the details) OneWire inputs.
Re: Design advice
Ignore the specific sensor requirements it was more to give an indication of the total sensor numbers. I will just use the OMS as a backbone for data presentation. .
Three phase supply.
There are only two questions which I will rephrase. Given the above information what combination of OpenEnergyMonitor equipment in what configuration do you recommend ?
Re: Design advice
Assuming you have a three-phase four-wire supply, you are going to need an emonTx for the nett import/export measurement. (The emonPi on its own has only two current inputs, therefore it's not very useful to you. But you could use it if you had a 3-wire supply.)
If your generation meter has a pulse output or your inverter has a suitable data output that you can send via Ethernet and your LAN, you don't need another emonTx for the PV infeed. Otherwise, you need to measure the output of your inverter and you need another emonTx for that.
Then for the 9 rooms, you want 9 × emonTH.
Given that you'll potentially have 11 nodes transmitting data back by radio, I wouldn't like to promise that you won't have a significant number of collisions in the radio channel, therefore you might well need to have half working on 433 MHz and half on 868 MHz, so you'll need 2 × emonBase to receive the data and send it onwards via your LAN to your server.