if I change:
configuration.yaml
#mqtt: !include mqtt.yaml
and mqtt.yaml
mqtt:
sensor:
- name: weather_station_outtemp_c
unique_id: uniqueid__weather_outtemp_c
icon: mdi:thermometer
state_topic: "weather/outTemp_C"
value_template: "{{ value | round(1) }}"
unit
tanks Peter,
i add in configuration.yaml the line
mqtt: !include mqtt.yaml
i create in /packages file mqtt.yaml
but a have this error
Configuration errors
Error loading /config/configuration.yaml: in "/config/configuration.yaml",
line 31, column 7: Unable to read file /config/mqtt.yaml.
this
It is easier to keep the mqtt data in a separate file.
So just add in your configuration.yaml the line
mqtt: !include mqtt.yaml
and create a separate mqtt.yaml file containing the data, you have exported
from weewx into your mqtt broker.
My mqtt.yaml looks like (be careful with the indentations!
Well, it failed with a USB error is the problem. I put the ferrite core on
the cable and plugged it back in and it started normally.
Didnt see there was an update, I will do that, and remove the modemmanger
On Friday, February 9, 2024 at 3:58:05 PM UTC-6 Tom Keffer wrote:
> The log in that last
As I don't know anything related to gpio, I was wondering, what may be
related to weewx. Aside of gw1000, forecast and zambretti, I do not have
installed anything else in weewx.conf.
As I plan to move to a raspi5 in a couple of months, I am considering to
come back to a Zigbee (or Matter) gatew
The log in that last email looked pretty normal. Is there a problem?
You should upgrade to v5.0.1.
Be sure to get rid of ModemManager. It competes with weewxd for the port.
*sudo apt purge modemmanager*
-tk
On Fri, Feb 9, 2024 at 11:12 AM Joe wrote:
> Feb 9 13:07:55 raspberrypi systemd[1]
For the VP2, the value of type "windSpeed" is whatever the console emits at
the end of an archive interval. Generally, this is the average wind seen
during the interval. Same with "windDir".
Similarly, "windGust" is whatever the Vantage emits, which is generally the
maximum value seen in the archi
my apologies again - brain and fingers are somewhat disconnected today.
the '-type t' should be '-type f' in my previous postings.
the correct (and complete) instructions for how to fix permissions can be
found in the wiki page:
https://github.com/weewx/weewx/wiki/Understanding-permissions#how
here is the sure-fire way to fix it (assuming that the user 'weewx' and
group 'weewx' exist):
sudo find /var/www/html/weewx -type d -exec chmod 2775 {} \;
sudo find /var/www/html/weewx -type t -exec chmod 644 {} \;
sudo chown -R weewx /var/www/html/weewx
sudo chgrp -R weewx /var/www/html/weewx
On Friday, February 9, 2024 at 3:02:57 PM UTC-5 wagr...@gmail.com wrote:
Feb 9 19:06:16 hp weewxd[10624]: PermissionError: [Errno 13] Keine
Berechtigung: '/var/www/html/weewx/NOAA/NOAA-2023-12.txt.tmp'
Feb 9 19:06:16 hp weewxd[10624]: ERROR weewx.reportengine:
File "/usr/share/
Hi I am Walter from Switzerland.
First a big thank to all workers on weewx. Apologize my bad english. on
7.2.2024 I saw that my datas are not updated anymore. I guess it was the
newest update. The log say that there is no permission to write to
html/weewx. Finally I had uninstall weewx and made
Feb 9 13:07:55 raspberrypi systemd[1]: Started WeeWX.
Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Initializing
weewxd version 5.0.0
Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Command line:
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
Feb 9 13:07:56 raspberrypi w
START weewx, and it begins publishing records again from the
console.
--
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+unsu
Plug in the replacement cable with ferrite cores, and I get this error
eb 9 13:03:58 raspberrypi kernel: [578076.357712] usb 1-1.4: USB
disconnect, device number 42
Feb 9 13:03:58 raspberrypi kernel: [578076.358554] cp210x ttyUSB1: cp210x
converter now disconnected from ttyUSB1
Feb 9 13:03:58
Weewx failed to start or run again.
Feb 9 12:57:01 raspberrypi systemd[1]: Started WeeWX.
Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Initializing
weewxd version 5.0.0
Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Command line:
/usr/share/weewx/weewxd.py /etc/weewx/we
If you do not need gpio for weewx, do not install anything related to gpio
in your weewx.conf file. Seems pretty simple to me.
On Friday, February 9, 2024 at 3:47:59 AM UTC-8 Vetti52 wrote:
> Concerning my v4 update process I should add some clarification:
> My Raspi crashed due to a SD card fa
import weewx data from mqtt to home assistant.
I can't configure the configuration.yaml file, if I go to the mqtt
component the weewx topic is visible but it doesn't create the entities for
me and when it creates them it tells me that they are not active.
Does anyone have an example of the config
Hello, what is the wind speed reported in Current Conditions?
Is it the instantanoeus value or an average (for example, on the page
update interval) ?
I've a Davis Vantage Pro 2 and I think the value is an average because I
may see, for example, 1 , 2, 3, 4 Km/h but this may not correspond to an
Martin, could you please more of the log than the tiny bit you showed? It's
not even possible to tell which skin was being run.
Set debug=1, then either restart weewxd, or run "weectl report run". Post
the log.
On Thu, Feb 8, 2024 at 11:56 PM Maarten van der Hoeven
wrote:
> Hi,
>
> Nut sure thi
Concerning my v4 update process I should add some clarification:
My Raspi crashed due to a SD card failure, which suddenly change it to read
only mode completely. Thus I had an "unerasable backup copy". I took a
brand new SD card, installed a brand new Raspian image with Bookworm lite
and insta
Seems like now weewx MQTT is emitting a message every time a LOOP packet
arrives. Let me guess, you hardware is capable of measuring wind/gusts in a
2.5s interval, maybe a Tempest?
I don't know why this has changed, does Belchertown let you set the
interval? Usually you set this like described
After update to 5.0.1-4 the MQTT publish data every 2-5 seconds ... have
anyone an explanation or can tell me where i can setup the publish time?
Feb 9 12:04:08 weewx chronyd[522]: Selected source 217.197.91.176
(de.pool.ntp.org)
Feb 9 12:04:09 weewx weewxd[716]: INFO weewx.restx: MQTT: Publi
I did some ekstra testing. But as you Tom was implying, it had to do with
my settings in weewx.conf (I think). In there I was pointing at the symlink
path, instead of at the var/www/html/weewx path. That and then elevating
the var/www/html/weewx folder to 755 instead of 644. At least I am sure
23 matches
Mail list logo
