Hey you left me a lot of job guys! ;-) (just kidding). So, let's try to check as much as I can:
1- Mosquitto broker version fred@orangepipcplus:~$ mosquitto --help mosquitto version 1.4.8 (build date Fri, 19 Feb 2016 12:03:16 +0100) mosquitto is an MQTT v3.1 broker. Usage: mosquitto [-c config_file] [-d] [-h] [-p port] ..... 2- Then, inside * /usr/local/lib/python2.7/dist-packages/paho/mqtt/client.py* """ This is an MQTT v3.1 client module. MQTT is a lightweight pub/sub messaging protocol that is easy to implement and suitable for low powered devices. """ So the mqtt version seems to match. 3- weewx.conf: debug = 1 (I've done it before starting my tests yesterday). 4- and now I dont what happens but I received a packet :-) This morning: I added the line logdbg("Set username to %s and password to %s" % (self.username, self. password)) then I started weewx sudo /etc/init.d/weewx start I publish from android mqtt dashboard a copy paste of the wiki example: TIME:0,AMBT: 7.23,BARP:1001.97,RHUM:70.92,HUMT: 4.44,IRRA:12,BATV:974,PHOV:673,SYST:33.20,WIND: 0.0,WDIR: 0.0 Also before going to bed yesterday, I switched back the poll interval to 10sec. And here is what appear in my syslog: Feb 21 06:22:59 localhost weewx[17227]: wxMesh: Got message TIME:0,AMBT: 7.23,BARP:1001.97,RHUM:70.92,HUMT: 4.44,IRRA:12,BATV:974,PHOV:673,SYST:33.20 ,WIND: 0.0,WDIR: 0.0 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: Working on payload : TIME:0, AMBT: 7.23,BARP:1001.97,RHUM:70.92,HUMT: 4.44,IRRA:12,BATV:974,PHOV:673,SYST :33.20,WIND: 0.0,WDIR: 0.0 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: TIME value: 1487658179 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: AMBT value: 7.23 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: BARP value: 1001.97 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: RHUM value: 70.92 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: HUMT value: 4.44 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: IRRA value: 12 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: BATV value: 974 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: PHOV value: 673 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: SYST value: 33.20 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: WIND value: 0.0 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: key: WDIR value: 0.0 Feb 21 06:22:59 localhost weewx[17227]: wxMesh: Sleeping for 10 \o/ I cannot do much more right now, got to go for work, but it's pretty good news ! (maybe I did something else, but don't remember what) I will try the websockets, I think I have seen a howto somewhere yesterday. thanks for your help both of you ! Le mardi 21 février 2017 00:05:11 UTC+1, mwall a écrit : > > i found it helpful to configure the broker so that it publishes using > websockets. then you can use a web browser to see what is happening. this > is especially useful when you're trying to decode someone else's topic > hierarchy, or to figure out why your own topics are not showing up where > you think they should be. > > the hivemq folks wrote one of the first ones, which many people have now > embedded: > > http://www.hivemq.com/blog/full-featured-mqtt-client-browser > > http://www.espert.io/mqtt/index.html > > but many other browser-based clients are out there: > > http://mitsuruog.github.io/what-mqtt/ > > https://www.cloudmqtt.com/docs-websocket.html > > if you're using the mosquitto broker, you'll have to compile it with > websocket compatibility. but once you do that, enabling websockets is just > a matter of making the broker listen on the websocket port. > > m > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.