[solved] No Inputs in input list

Papageno · 2018-12-28T09:54:44.950Z

I did uncomment [[emoncmsorg]] because I log only local. But there is no change if I enable or disable it… I think I take another way. I write a wrapper and send the data via curl and the api to emoncms. But first of all I have to check how this works…

Greebo · 2018-12-28T12:27:32.421Z

Papageno:

I did uncomment [[emoncmsorg]] because I log only local. But there is no change if I enable or disable it

You’ll need some way to get the data from EmonHub to EmonCMS. Just having the SerialInterfacer defined wont push the data into EmonCMS.

If you look at the first picture here: https://guide.openenergymonitor.org/technical/ you can see that emonhub pushes to MQTT and emonCMS reads from MQTT. So if you haven’t got the MQTT interfacer section enabled in your emonhub configuration (and MQTT installed and configured), then you need to use the HTTP interfacer (as you’ve attempted) to push the data into your local EmonCMS

Try fixing the url and apikey in your file:

Papageno:

[[emoncmsorg]]
  Type = EmonHubEmoncmsHTTPInterfacer
  [[[init_settings]]]
  [[[runtimesettings]]]
    nodeoffset = 11
    subchannels = ToEmonCMS,
    #url = http://localhost/emoncms #uncomment to save on local pi
    apikey = 4706b74a24b18bd418967xxxxxxxxx
    senddata = 0 # Enable sending data to Emoncms.org
    sendstatus = 0 # Enable sending WAN IP to Emoncms.org MyIP &gt; https://emoncms.org/myip/list 
    sendinterval= 30 # Bulk send interval to Emoncms.org in seconds

You may also need to update senddata

borpin · 2018-12-28T12:58:51.586Z

Hi @Papageno, can you please post the details in the admin screen. Click on the Copy to Clipboard button next to Server Information and then just paste it to a reply here (no further formatting required).

I Don’t have an EmonPi so this is not something I can help with directly, but I note you started on this journey last March. A revised SD card image was released in October and it may be a good time to migrate to that if you have not already done so.

I am surprised you are having these issues as this should really work out of the box @TrystanLea @glyn.hudson may be able to help in more detail.

[edit] the configuation docs of EmonHub are here.

You should not need the section above to talk to the local EmonPi as that is done via MQTT I believe rather than via the HTTP API.

Robert.Wall · 2018-12-28T13:55:16.358Z

Greebo:

Is datacode = 0 valid?

Indeed it is, per Paul Burnell. It means that the data is NOT encoded as per that list, but is expressed in decimal (“human-readable”) characters exactly as the log file shows: 2070.04, 1944.99, 2364.22, ...

And datacode = 0 is also not the default. It’s probably best to think of it as zero = a number.

Papageno · 2018-12-28T13:59:19.245Z

There was the fault!

I forgot to uncomment the url…

#url = http://localhost/emoncms #uncomment to save on local pi

Thanks for your help. Sometimes I can’t see the woodfor the trees

pb66 · 2018-12-28T16:25:35.615Z

I believe this line in (emonhub emonpi variant’s) emonhub.conf should be set to “1” as in “send to emoncms.org, true”

senddata = 0                    # Enable sending data to Emoncms.org

If the url is not specified (eg commented out) it will default to emoncms.org (emonhub/EmonHubEmoncmsHTTPInterfacer.py at emon-pi · openenergymonitor/emonhub · GitHub) so that line being commented out would not have prevented it sending to the hosted emoncms.org, but yes to “send” it to the local emoncms instance by http you would need to specify/change the url.

However if you are running the emonSD/emonPi image then the data should be transfered from emonhub to emoncms via MQTT not HTTP, that’s not to say you cannot use HTTP if you prefer, but MQTT should work, as Greebo and Brian say “out of the box”.

“0” is indeed a valid datacode, it is best remembered by thinking of it as either "0 = False (no decoding) or “Zero decoding required”, in code it is a logical test as to whether to continue through or bypass the decoding of the value(s).

Each interfacer has it’s own default datacode and in actual fact the default datacode for the serial interfacer IS “0” (emonhub/emonhub_interfacer.py at emon-pi · openenergymonitor/emonhub · GitHub) so you could just comment out the datacode line to the same effect as “datacode = 0”, either would denote an unspecified number of values that require no decoding. But “datacodes = 0,0,0,0,0,0,0,0” would differ slightly as it denotes exactly 8 values that require no decoding, any array of values that has less than or more than 8 values will be discarded, this stricter filtering can be advantageous in some circumstances.

I also notice that you have nodeoffset = 11 in multiple places, this is not required as you have the node id already specified in the payload, plus it would only ever get recognized in an incoming interfacer (eg serial, jee or socket etc) it has no effect in the http interfacer or the nodes section, although those entries will not cause any issues directly, they may cause some confusion down the line when trying to understand why they are there, best to remove them.

Papageno · 2018-12-28T17:09:56.250Z

Thanks for clearing the issue. I’ve cleaned the emonhub.conf and still get data. Surprise

I have another construction which needs to be cleared. I’m working on adding 1-wire temperature readings (ds18b20). I see the sensors in

ls /sys/bus/w1/devices/

but not in the emonpi. I think it’s a [interfacer] issue, but I’m searching for a solution. You’ll see it maybe later in an extra post.

pb66 · 2018-12-28T18:19:32.246Z

Papageno:

but not in the emonpi. I think it’s a [interfacer] issue, but I’m searching for a solution. You’ll see it maybe later in an extra post.

You have another thread on this topic already so I will reply there.

Configure emonhub.conf Reading data from gpio emonHub

Hi, I am trying to upgrade my emonpi. I’ve already installed a RPICT4T4 which works fine. No I like to add more temperature sensors. On a 2nd Raspi I got 10 DS18B20 working on gpio4. Now I want to connect at the emon-raspi and emoncms. I am wondering how to configure '/home/pi/data/emonhub.conf` that these temperatures are availble as nodes inside emoncms. In the documentation I don’t find advise for that matter. My question: How to setup emonhub.conf to read data from gpio directly? Regards …

Greebo · 2018-12-29T01:44:32.422Z

pb66:

“0” is indeed a valid datacode, it is best remembered by thinking of it as either "0 = False (no decoding) or “ Zero decoding required”, in code it is a logical test as to whether to continue through or bypass the decoding of the value(s).

Is this documented anywhere else besides the source code? I wasn’t able to find it in any of the documentation.

pb66 · 2018-12-30T19:26:16.808Z

Greebo:

Is this documented anywhere else

I really couldn’t say. Although I cannot recall seeing it, I don’t seem to have a good grasp of what is documented where.

Robert.Wall · 2018-12-30T22:02:35.926Z

It’s certainly on my private crib sheet, but I think it isn’t anywhere in the documentation. It needs adding to: emonhub/configuration.md at emon-pi · openenergymonitor/emonhub · GitHub

Methinks one more for your ‘to do’ list, @Gwil

georgel · 2019-01-03T08:29:24.235Z

Also not getting any data on setup/inputs, nothing listed…
nothing listed…

gone through everything above and still no luck.

missing something (RPI with RPICT8)

G

Papageno · 2019-01-03T08:54:06.791Z

Did you test the basic function like mentioned in the wiki. RPICT8 - lechacal ?

What is the output?
Whats in the emonhub.log? Are there any failures mentioned?

georgel · 2019-01-03T09:07:33.419Z

Some data collected directly from /dev/… attached.

emonhub.conf attached.

only error I am getting in the emonhub log file is a warning because apikey is not specified which is expected as I’m trying to log locally.

G

emonhub.txt (3.5 KB)

serial-1911.txt (9.9 KB)

georgel · 2019-01-03T09:17:06.896Z

changing emonhub.conf to look like:

[hub]

loglevel must be one of DEBUG, INFO, WARNING, ERROR, and CRITICAL

see here : 15.7. logging — Logging facility for Python — Python 2.7.18 documentation

loglevel = DEBUG #(default:WARNING)

[interfacers]

[[SerialDirect]]
Type = EmonHubSerialInterfacer
[[[init_settings]]]
com_port = /dev/ttyAMA0
com_baud = 38400
[[[runtimesettings]]]
pubchannels = ToEmonCMS,

[[emoncmsorg]]
Type = EmonHubEmoncmsHTTPInterfacer
[[[init_settings]]]
[[[runtimesettings]]]
subchannels = ToEmonCMS,
#url = http://localhost/emoncms #uncomment to save on local pi
apikey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
senddata = 1 # Enable sending data to Emoncms.org
sendstatus = 1 # Enable sending WAN IP to Emoncms.org MyIP > Emoncms - myip list
sendinterval= 30 # Bulk send interval to Emoncms.org in seconds

[nodes]

[[11]]
nodename = my_RPICT7V1
[[[rx]]]
names = RP1, RP2, RP3, RP4, RP5, RP6, RP7, Irms1, Irms2, Irms3, Irms4,Irms5,Irms6,Irms7,Vrms
scales = 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
units =W,W,W,W,W,W,W,mA,mA,mA,mA,mA,mA,mA,V
datacode = 0

rebooting, will advise.

… looking better, I’m seeing values in the emonhub log, fixing a type, rebooting,
will advise.

ok, emonhub.log (attached) looks good, got values being seen now, but still nothing under setup/inputs ?

emonhub.txt (14.5 KB)

G

Papageno · 2019-01-03T11:20:01.587Z

georgel:

#url = http://localhost/emoncms #uncomment to save on local pi

uncomment this and put your write API in the next line, then it should work.

georgel · 2019-01-03T11:23:37.165Z

Line was uncommented, that was a copy of the docs, but I added my api write key that i got from the setup/input api page

Rebooting, will advise.

G

georgel · 2019-01-03T11:34:11.437Z

YAY, I see inputs… so it seems (did not see this anywhere in docs) but the apikey is also needed when writing/storing locally.

Once that was added it all popped up.

Now to try and figure out how to add all the configs to get the graphs that I’d want.

Mission one accomplished, thanks Hans.

G

georgel · 2019-01-03T14:04:16.926Z

side track, is there a document specifying some good dashboards to create and required steps ?

G

borpin · 2019-01-03T15:07:20.811Z

georgel:

side track,

Better to ask this on a new topic.