On Monday, February 4, 2019 at 4:42:52 PM UTC-5, Andy Hudson-Smith wrote: > > Noted the use of skins and mqtt on a pi, i kind of assumed it was up to > the job, i do like the weewx system so may well move up to a more useful > machine - coming from Windows into this world means i know little beyond > Dells and Win 10 which is what i have been trying to avoid due to frequent > updates and crashes of other systems. > > Any advice on what sort of system weewx needs to run would be good (again > i should Google this first!). >
here are some suggestions: https://github.com/weewx/weewx/wiki/hardware data collection is almost never a problem. uploading data is not cpu, i/o, or network intensive. most reports will run just fine on a pi or other low-power machine - you should have no problems with 1 or 2 reports. however, you might have issues if you try to run 3 or 4 query-intensive reports with a short archive interval. in some configurations, the crt (cumulus realtime) and wdcr (clientraw) extensions can be problematic on low-end hardware, since they query the database each report cycle (archive interval) to get the data they need. if you run them on archive intervals you should be ok, but if you run them on loop packets you can easily run into the 'database locked' problems. the NoneType error is almost certainly due to a bug in rtcr.py - it is getting a value of None but does not handle it properly. 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.
