Archived Forum

Somehow i managed to destroy something. The Nodes in Emoncms do not get updated anymore. The Emoncms itself seems to work fine. Udates coming in via HTTP JSON do work but anything coming from MQTT does not reach into the Emoncms system.

I see updates within the MQTT Logs:

Client mosqsub/3427-emonpi received PUBLISH (d0, q0, r0, m0, 'emonhub/rx/19/values', ... (9 bytes))
21.5,63.6

I see activiy within the Emonhub log:

2016-01-10 14:29:53,016 DEBUG    RFM2Pi     43 Sent to channel' : ToEmonCMS
2016-01-10 14:30:03,466 DEBUG    RFM2Pi     44 NEW FRAME : OK 19 215 0 124 2 (-47)
2016-01-10 14:30:03,468 DEBUG    RFM2Pi     44 Timestamp : 1452436203.47
2016-01-10 14:30:03,469 DEBUG    RFM2Pi     44 From Node : 19
2016-01-10 14:30:03,470 DEBUG    RFM2Pi     44    Values : [21.5, 63.6]
2016-01-10 14:30:03,471 DEBUG    RFM2Pi     44      RSSI : -47
2016-01-10 14:30:03,473 INFO     RFM2Pi     Publishing: emonhub/rx/19/values 21.5,63.6
2016-01-10 14:30:03,475 INFO     RFM2Pi     Publishing: emonhub/rx/19/rssi -47
2016-01-10 14:30:03,477 DEBUG    RFM2Pi     44 adding frame to buffer => [1452436203, 19, 21.5, 63.6, -47]

But somehow these values do not reach into the Emoncms system.

Where can i check what is going wrong here? This used to work before when i tried to inject with a MQTT Client directly into the topic "emonhub/rx/19/values". But somehow i must have destroyed something.

I could go back in time with a backup restore but i would like to understand the system and debug it. Anybody can give me a hint here?

Additional Information:

I have the feeling that there are some files within /var/www/emoncms/ with a change date from 9.1.2016. The /home/pi/data/emonpiupdate.log states that there was an update. This could be the change which killed it? No idea what is going on here.