Emoncms + Victron CCGX + My Battery App

Can someone help me pls? I am trying to set up Emoncms to access my CCGX, but I am unsure exactly where this config file gets edited in. Worried I might install in the wrong place. Can someone show their full config file & location please?
My Emoncms is on an Intel NUC, & pymodbus has been installed.

Thanks, Doug (safe in Overcast Sunny Australia! Hope Donnie Trump gets over his Covid? )

If you are trying to do the same as @gjones84, you are going to modify emonhub config.

In installing emoncms on an NUC, how did you do it and is emonhub running?

image

Thanks Brian,
I installed from the Github image, & I think I disabled all the Pi bits. (I used the rPi user name etc as standard, cos it was easier!)
Emoncms is running fine, & it is getting data from my monitor. I Installed pymodbus, & that seems fine.
What I wish to achieve is to get the battery SOC from the CCGX, so that I can emulate the Victron Dashboard data (in some yet to be determined form).
My system is 2 of Solaredge 5Kw inverters, currently 15Kw of panels, thew Victron Charger/Inverter & Zenaji Batteries (Which are Lithium Titanate manufactured in Melbourne, Australia)

Hi Doug,

I have done this and it is all up and running and working fine. Once you have pymodbus installed and running. Log into your emonbase locally.

Then click the three bars at top left. Click emon hub. Select edit config. Scroll down to interfaces and insert my code. Restart and go to inputs and it should all be there :slightly_smiling_face:.

Once you have that you can configure the My Solar Battery App.

Hope that helps.

Cheers

Gareth

Are you on a generic Linux install or a Pi one?

On to an NUC? Or do you mean you ran the scripts?

How? emonhub? HTTP? MQTT?

Unless I understand more how you have set emoncms up on the NUC I’ll not be able to help much as there are simply too many variables.

Can you click on the button Copy as Markdown next to Server Information on the Admin page and paste into a reply here please (no further formatting required).

Server Information

Server Information

Services

  • emoncms_mqtt :- Active Running
  • feedwriter :- Active Running - sleep 300s 360 feed points pending write
  • service-runner :- Activating Auto-restart
  • redis-server :- Active Running
  • mosquitto :- Active Running
  • demandshaper :- Active Running

Emoncms

Server

  • OS :- Linux 5.4.0-48-generic
  • Host :- pi-desktop | pi-desktop | (192.168.1.182)
  • Date :- 2020-10-03 21:28:33 AEST
  • Uptime :- 21:28:33 up 22:37, 1 user, load average: 0.34, 0.19, 0.13

Memory

  • RAM :- Used: 42.89%
    • Total :- 3.74 GB
    • Used :- 1.6 GB
    • Free :- 2.13 GB
  • Swap :- Used: 0.00%
    • Total :- 2 GB
    • Used :- 0 B
    • Free :- 2 GB
      Write Load Period

Disk

  • / :- Used: 8.87%
    • Total :- 109.04 GB
    • Used :- 9.67 GB
    • Free :- 93.79 GB
    • Write Load :- n/a
  • /boot/efi :- Used: 1.53%
    • Total :- 510.98 MB
    • Used :- 7.8 MB
    • Free :- 503.19 MB
    • Write Load :- n/a

HTTP

  • Server :- Apache/2.4.41 (Ubuntu) HTTP/1.1 CGI/1.1 80

MySQL

  • Version :- 5.5.5-10.3.22-MariaDB-1ubuntu1
  • Host :- localhost:6379 (127.0.0.1)
  • Date :- 2020-10-03 21:28:33 (UTC 10:00‌​)
  • Stats :- Uptime: 81468 Threads: 10 Questions: 42422 Slow queries: 0 Opens: 45 Flush tables: 1 Open tables: 39 Queries per second avg: 0.520

Redis

  • Version :-
    • Redis Server :- 5.0.7
    • PHP Redis :- 5.3.1
  • Host :- localhost:6379
  • Size :- 103 keys (926.98K)
  • Uptime :- 0 days

MQTT Server

  • Version :- Mosquitto 1.6.9
  • Host :- localhost:1883 (127.0.0.1)

PHP

  • Version :- 7.4.3 (Zend Version 3.4.0)
  • Modules :- apache2handler bz2 calendar Core ctype curl date dom v20031129exif FFI fileinfo filter ftp gd gettext hash iconv json libxml mbstring mosquitto v0.4.0mysqli mysqlnd vmysqlnd 7.4.3openssl pcre PDO pdo_mysql Phar posix readline redis v5.3.1Reflection session shmop SimpleXML sockets sodium SPL standard sysvmsg sysvsem sysvshm tokenizer xml xmlreader xmlwriter xsl Zend OPcache zip v1.15.6zlib
Client Information

Client Information

HTTP

  • Browser :- Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Cyberfox/52.9.1
  • Language :- en-US,en;q=0.5

Window

  • Size :- 2545 x 1343

Screen

  • Resolution :- 2560 x 1440

(end)
Thanks Brian, realising I am well out of my depth (but prepared to learn). I am a hardware man!
I realise that I do not know how all the s/w fits together, except in a basic way.

regards, Doug

You didn’t say how you did the install.

But, when you did the install, you did not install emonhub. You will need to do that.

I think you can just clone the emonhub repo and run the install. As I do not know where or how you installed the scripting part of emoncms, I can’t advise where to install it to.

On the Pi systems that is all in /opt/openenergymonitor.

The standard pi one :+1:

Yes much simpler as emonhub is installed by default.

Hi Gareth,

I realise that this thread is quite old now, but I’m trying to do exactly the same as you did. It seems to run MODBUS successfully, but then I get this in the logfile:

I’d be grateful if you had any advice!

Thanks,

John.

Is your system fully updated?

Yes - just done a full system update and get the same error :man_shrugging:

Hi. Some time ago I did this. I remember it being a PITA when I did it.

Tbh with all my experience now. I can help you muddle way through the modbus stuff but the best way to parse data from your victron system is via mqtt

Download this and install of your pc.

Then connect to your venus device and take a look at which topics you wish to pull out.

Then use the venus os large image with node red and you can pull the topics out using the installed victron nodes or via mqtt topics and ping them straight into emon device piece of cake.

Its easy, robust and reliable.

Cheers

Gareth

Thanks Gareth - I came to that conclusion too, but I’m not running Node Red, and am having problems with that too! See here:

Could you do a quick sketch of of your system please? Inverter/charger, battery, bms, gx or venus device and comms?

How’s this: (thanks so much for your help!)

Hi John.

Perfect. Can see what your trying to do now.

If you going into your cerbo. Go to setting and scrol down do youhave venus OS large features? Like this. If so then enable node red.

Then say you ip adress of your cerbo is 192.168.0.2.

Open chrome or internet explorer and go to 192.168.0.2:1880.

Then ill show you how to do the rest.

Im pretty sure cerbo gx has the venus os large features as standard now.

Cheers

Amazing! Yep - got that up and running and I’m on the Node-red webpage

Hey Gareth - just wanted to let you know that it’s all up and running now and working perfectly. Many thanks for your help.

John.

Hi John.

Glad you got it sorted :slight_smile: