Community
OpenEnergyMonitor

Community

MQTT topic

on an input i have a publish to MQTT emon/openevse/excess it has stopped updating. I removed it and added a new one emon/openevse/excess1 that is not showing at all

Server Information

Server Information

Services

  • emonhub :- Active Running
  • emoncms_mqtt :- Active Running
  • feedwriter :- Active Running - sleep 60s 2541 feed points pending write
  • service-runner :- Active Running
  • emonPiLCD :- Active Running
  • redis-server :- Active Running
  • mosquitto :- Active Running

Emoncms

  • Version :- low-write 10.0.2
  • Modules :- Administration | App v2.0.1 | Backup v2.0.0 | EmonHub Config v2.0.2 | Dashboard v2.0.1 | Device v2.0.0 | EventProcesses | Feed | Graph v2.0.1 | Input | Postprocess v2.0.0 | CoreProcess | Schedule | Network Setup v1.0.0 | sync | Time | User | Visualisation | WiFi v2.0.0
  • Git :-

Server

  • OS :- Linux 4.14.71-v7+
  • Host :- emonpi | emonpi | (192.168.1.215)
  • Date :- 2019-06-06 14:27:16 UTC
  • Uptime :- 14:27:16 up 6 min, 0 users, load average: 0.20, 0.55, 0.33

Memory

  • RAM :- Used: 20.18%
    • Total :- 976.74 MB
    • Used :- 197.08 MB
    • Free :- 779.66 MB
  • Swap :- Used: 0.00%
    • Total :- 100 MB
    • Used :- 0 B
    • Free :- 100 MB

Disk

  • / :- Used: 42.69%
    • Total :- 3.81 GB
    • Used :- 1.63 GB
    • Free :- 2.01 GB
  • /boot :- Used: 51.69%
    • Total :- 42.52 MB
    • Used :- 21.98 MB
    • Free :- 20.54 MB
  • /home/pi/data :- Used: 18.54%
    • Total :- 54 GB
    • Used :- 10.01 GB
    • Free :- 41.25 GB

HTTP

  • Server :- Apache/2.4.25 (Raspbian) HTTP/1.1 CGI/1.1 80

MySQL

  • Version :- 5.5.5-10.1.23-MariaDB-9+deb9u1
  • Host :- localhost:6379 (127.0.0.1)
  • Date :- 2019-06-06 14:27:16 (UTC 00:00‌​)
  • Stats :- Uptime: 370 Threads: 5 Questions: 5076 Slow queries: 0 Opens: 28 Flush tables: 1 Open tables: 22 Queries per second avg: 13.718

Redis

  • Version :- 3.2.6
  • Host :- localhost:6379
  • Size :- 655 keys (895.21K)
  • Uptime :- 0 days

MQTT Server

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

PHP

  • Version :- 7.0.30-0+deb9u1 (Zend Version 3.0.0)
  • Modules :- apache2handler | calendar v7.0.30-0+deb9u1 | Core v7.0.30-0+deb9u1 | ctype v7.0.30-0+deb9u1 | curl v7.0.30-0+deb9u1 | date v7.0.30-0+deb9u1 | dom v20031129 | exif v7.0.30-0+deb9u1 | fileinfo v1.0.5 | filter v7.0.30-0+deb9u1 | ftp v7.0.30-0+deb9u1 | gd v7.0.30-0+deb9u1 | gettext v7.0.30-0+deb9u1 | hash v1.0 | iconv v7.0.30-0+deb9u1 | igbinary v2.0.1 | json v1.4.0 | libxml v7.0.30-0+deb9u1 | mbstring v7.0.30-0+deb9u1 | mcrypt v7.0.30-0+deb9u1 | mosquitto v0.4.0 | mysqli v7.0.30-0+deb9u1 | mysqlnd vmysqlnd 5.0.12-dev - 20150407 - $Id: b5c5906d452ec590732a93b051f3827e02749b83 $ | openssl v7.0.30-0+deb9u1 | pcre v7.0.30-0+deb9u1 | PDO v7.0.30-0+deb9u1 | pdo_mysql v7.0.30-0+deb9u1 | Phar v2.0.2 | posix v7.0.30-0+deb9u1 | readline v7.0.30-0+deb9u1 | redis v4.1.1 | Reflection v7.0.30-0+deb9u1 | session v7.0.30-0+deb9u1 | shmop v7.0.30-0+deb9u1 | SimpleXML v7.0.30-0+deb9u1 | sockets v7.0.30-0+deb9u1 | SPL v7.0.30-0+deb9u1 | standard v7.0.30-0+deb9u1 | sysvmsg v7.0.30-0+deb9u1 | sysvsem v7.0.30-0+deb9u1 | sysvshm v7.0.30-0+deb9u1 | tokenizer v7.0.30-0+deb9u1 | wddx v7.0.30-0+deb9u1 | xml v7.0.30-0+deb9u1 | xmlreader v7.0.30-0+deb9u1 | xmlwriter v7.0.30-0+deb9u1 | xsl v7.0.30-0+deb9u1 | Zend OPcache v7.0.30-0+deb9u1 | zlib v7.0.30-0+deb9u1

Pi

  • Model :- Raspberry Pi 3 Model B Rev 1.2 - 1 GB (Sony UK)
  • SoC :- Broadcom BCM2835
  • Serial num. :- 43DDB2EE
  • Temperature :- 65.53°C - 65.5°C
  • emonpiRelease :- emonSD-30Oct18
  • File-system :- read-write
Client Information

Client Information

HTTP

  • Browser :- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Waterfox/56.2.10
  • Language :- en-US,en;q=0.5

Window

  • Size :- 1903 x 971

Screen

  • Resolution :- 1920 x 1080

What changed? Did you update and it stopped working? Does it run for a while following a reboot but then stops?

The topic emon/ is specifically for incoming data, not data published by EmonCMS. Try changing the base topic to emonpub/.

The script for handling MQTT has changed (depending on where you updated from) so that is a potential issue.

Hi Borpin,

I removed it from on input to set it up on another. Its a calculation to output a topic for the evse charger.
using emonpub/openevse/excess does not show on the input also the evse charge cannot see it.

And now i dont understand, i have just edited the process to change back to emon/openevse/excess and now it shows

Ah OK. @glyn.hudson is it a good design for the evse to use the same input topic as emoncms? It means there is a risk with a loop i.e. emoncms picks up as an input data it has just published. I think the emoncms publish should always be different to the default input topic so the EVSE would need to pick up that topic as an input.

Odd, but if it is working that is good.