Gert Andersen <[email protected]> writes: > Sorry, but I'm still fiddling around with the configuration. I have made a > little drawing showing what I'm trying to achieve and also ask some > questions.
Please see my previous message about testing with mosquitto_pub and mosquitto_sub. I don't think it makes sense to worry about skins and extra brokers until you can use the test clients and confirm that they work. > As mentioned earlier, I have no problems using mqtt, when I'm running weewx > (uploading from Ecowitt GW1000) and the broker on the same vps host(no > Raspberry). So I have a very basic understanding about mqtt. OK, but there is probably some issue with your other config and you will need to figure out what that is. > My problems of understanding starts when I separate weewx(Raspberry) and > Mosquitto (vps host) and which components on which device. The broker location should be independent of weewx and even the web server. It is completely normal for the broker to be on a different host than an mqtt client. I advise strongly against a second local broker and bridging, until you have the basic setup working and then only if you can explain why that's a good idea. So far because you have not shown data from the test clients we have zero idea of where in the long chain of dataflow you are having problems. You should be able to use mosquitto_sub with options -h -p -u -P (filled in) and subscribe to weather and see the json. And to use mosquitto_pub on the pi and send some fake content and see that appear. Start with pub and sub on the VPS. Then move the pub to the pi. Then move the sub to some other random host. Then turn on weewx instead of the pub client, but keep watching with the sub client. Add only one thing at a time. Report back when you have one thing that works and the next step with *only one change* that fails. Make sure your VPS has proper DNS entries. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/rmimu94azls.fsf%40s1.lexort.com.
