Inputs from local install not showing on

So i’m setting up a new local Pi3 with heatpump HAT.

All the inputs data is showing on there from temp probes, SDM120 and heat meter, cool.

I also have a cloud VM running emomcms which the inputs data is instantly popping up in via the usual send method listed below.

But I can’t see the inputs in, they just don’t appear.

I already have a emonpi/emomtx onsite and all the data from that has been going over to for years. So this confirms the apikey etc as i’ve copy/pasted it.

    Type = EmonHubEmoncmsHTTPInterfacer
        pubchannels = ToRFM12,
        subchannels = ToEmonCMS,
        url =
        apikey = xxxxxxx
        senddata = 1                    # Enable sending data to
        sendstatus = 0                  # Enable sending WAN IP to MyIP >
        sendinterval= 30                # Bulk send interval to in seconds

    Type = EmonHubEmoncmsHTTPInterfacer
        pubchannels = ToRFM12,
        subchannels = ToEmonCMS,
        url = http://x.x.x.x/
        apikey = xxxxxxx
        senddata = 1                    # my-awesome-emoncms-server
        sendstatus = 0                  # Enable sending WAN IP to Emoncms MyIP
        sendinterval= 30                # Bulk send interval to post in seconds

I’ve tried changing the nodenames of my SDM120, temp probes and heat meter on the local HAT.

Removed underscores, removed hyphens, all the nodenames are unique on the HAT install.

No matter what I do, the inputs appear instantly on the cloud VM, but I see nothing on despite the log on the local HAT saying things have been sent to

2022-10-12 08:29:15,332 DEBUG    emoncmsorg Buffer size: 9
2022-10-12 08:29:15,334 INFO     emoncmsorg sending: data=[[1665559730.0808098,"heatpumpmon-temps",19.25],[1665559730.081241,"heatpumpmonsharky",0,0,0,0,0,0,0,0,0,24.6,26.1,-1.5,0],[1665559730.0609334,"heatpumpmon-sdm120",238.7,0.158,8.8,33.7,0.267,50,14.329,0,0.484],[1665559740.077316,"heatpumpmon-temps",19.25],[1665559740.0363603,"heatpumpmonsharky",0,0,0,0,0,0,0,0,0,24.6,26.1,-1.5,0],[1665559740.0074573,"heatpumpmon-sdm120",238.6,0.157,8.7,33.5,0.261,50,14.329,0,0.484],[1665559750.066636,"heatpumpmon-temps",19.25],[1665559750.0014844,"heatpumpmonsharky",0,0,0,0,0,0,0,0,0,24.6,26.1,-1.5,0],[1665559750.0631785,"heatpumpmon-sdm120",238.6,0.157,8.8,33.7,0.263,50.04,14.329,0,0.484]]&sentat=1665559755&apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y
2022-10-12 08:29:15,502 DEBUG    emoncmsorg acknowledged receipt with 'ok' from

If you’ve played around with emoncms and fiddled for so long, can your account get its knickers in a twist?

Does it need a bit of clean up and flush?

Any thoughts or tips would be very much appreciated.

Cheers, Mick

Hello @Zarch

Sorry about this, looking into this I realise the issue is being caused by node names being longer than 16 characters e.g: heatpumpmonsharky is 17.

I appreciate the response from emoncms was not particularly helpful!

I’ve changed the implementation now to clip the name rather than discard it completely.

You may want to shorten the names to something like hpmonsharky to improve readability?

1 Like

That’s awesome, thanks for tracking that down.

I will reduce my input names char length.