MQTT data getting lost between EmonHub and MQTT but is hitting EmonCMS.org?

[glyn.hudson]

Your use case sounds reasonable, it would expect (or hope!) the system to be able to deal with that sort of data volume.

I posted a reply on another thread of how to use nodered to setup a log of mqtt messages:

Phantom Duplicated MQTT Topics after reboot

It’s hard to debug something that happens so rarely. I’ve only seen this happen once in 100’s of reboots on many emonPi’s! Just to summarise where we are at: ISSUE A new set of Emoncms Inputs for the same node are created by the Emoncms MQTT input script. These inputs have exactly the same names as the old ones. The MQTT input script obtains the names of the inputs from the MQTT topic names. e.g The MQTT topic emon/emontx/power1 results in an Emoncms Input called power1 from emontx node. An…

I am away on holiday for a couple of weeks tomorrow, I won’t be able to investigate this any further before I leave I’m afraid. Let me know how you get on.

As a work around if its is the PHP MQTT which is causing an issue you could get nodeRED to post directly to local Emoncms or use emonhub to post to local emoncms, create another emoncms interfacer in emonhub.conf:

Place this in the [interfacers] section of emonhub.conf:

[[emoncmslocal]]
    Type = EmonHubEmoncmsHTTPInterfacer
    [[[init_settings]]]
    [[[runtimesettings]]]
        pubchannels = ToRFM12,
        subchannels = ToEmonCMS,
        #url = http://localhost/emoncms
        apikey = xxxxxxxx
        senddata = 1                    # Enable sending data to Emoncms.org
        sendstatus = 1                  # Enable sending WAN IP to Emoncms.org MyIP > https://emoncms.org/myip/list
        sendinterval= 30                # Bulk send interval to Emoncms.org in seconds