I inserted what you have written here in my weewx.conf file after 
installing the weewx-emon extension, with my IP and token of course, but it 
will not post to my local emoncms server, I know the emoncms server is 
working as it is logging inputs from my solar inverter.
This is running on a rpi3
Using  tail f /var/log/syslog it shows,
"Aug 15 22:05:37 raspberrypi weewx[14060]: restx: EmonCMS: Failed to 
publish record 2017-08-15 22:05:00 NZST (1502791500): Failed upload after 3 
tries"



On Saturday, 29 July 2017 22:19:33 UTC+12, mwall wrote:
>
> On Saturday, July 29, 2017 at 5:27:56 AM UTC-4, Stefan Klammer wrote:
>>
>> Now i have another question. I want to feed the data into my own emoncms 
>> server. But i can't find a description what the token parameter in the 
>> config file has to look like.
>>
>> Is there any more information available?
>>
>
> stefan,
>
> follow the emoncms instructions to install emoncms:
>
> https://github.com/emoncms/emoncms
>
> once emoncs is installed, log in.  under the setup->apikey menu you will 
> see the 'write api key'.  copy that and place it in the weewx configuration 
> file like this:
>
> [StdRESTful]
>     ...
>     [[EmonCMS]]
>         url = http://192.168.0.2/emoncms/input/post.json
>         token = acd5ed8g4a0b412ffc8ca603e65a5767
>
> then restart weewx.
>
> see the weewx-emoncms readme for more options.
>
> https://github.com/weewx/weewx/wiki/emoncms
>
> after one archive interval, you should see data in the 'inputs' page in 
> emoncms.  then, in emoncms, save the 'inputs' into 'feeds', then you can do 
> all kinds of plotting and indicators and time comparison and timeseries 
> comparisons with your data.
>
> emoncms is a bit cumbersome when you have more than a couple hundred 
> observations, but it is really nice for residential monitoring and other 
> small-scale applications.
>
> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to