[weewx-user] Problem for public_html access with Weewx 5 and apache 2

2024-04-26 Thread Remy Lavabre
Hello, Good morning, I didn't find the answer to my problem in the various discussions on the WeeWX forum... I installed Weewx 5 in a virtual environment. So I have my weewx-data and weewx-venv directories in /home/---/ weewxd seems to "finally" work normally with the ~/weewx-data/public_html

Re: [weewx-user] Problem for public_html access with Weewx 5 and apache 2

2024-04-26 Thread p q
Looks like a rights issue with Apache. Find the apache.conf file and you probably need to enable access to the right directories. On Fri, Apr 26, 2024 at 6:26 AM Remy Lavabre wrote: > Hello, > > Good morning, > I didn't find the answer to my problem in the various discussions on the > WeeWX foru

Re: [weewx-user] Problem for public_html access with Weewx 5 and apache 2

2024-04-26 Thread Remy Lavabre
1/ if I try xxx.xxx.xxx.xxx/index.html -> Work fine, I've got the Apache2 Debian Default Page (which is in /var/www/html/index.html). 2/ if i try xxx.xxx.xxx.xxx/weewx/index.html -> Forbidden - You don't have permission to access this resource. (with my symbolic link) I've tried : A/ sudo chown

Re: [weewx-user] Problem for public_html access with Weewx 5 and apache 2

2024-04-26 Thread vince
I do it in the opposite direction. The /var/www/html/weewx path is a directory. The /home//weewx-data/public_html path is a symlink 'to' the webserver directory. For a pip installation: sudo mkdir /var/www/html/weewx sudo chown ${WEEWXUSER}:${WEEWXUSER} /var/www/html/weewx ln -s /var/www/html

[weewx-user] Re: formatting MQTT message sensor lenght

2024-04-26 Thread miso k
I have red on another forum, that the number is too big for HA to read it. Maybe I am wrong, but the possibilities that my configuration.yaml is wrong are limited already I hope Dátum: štvrtok 25. apríla 2024, čas: 5:22:28 UTC+2, odosielateľ: michael.k...@gmx.at > What's the problem with the n

[weewx-user] Re: formatting MQTT message sensor lenght

2024-04-26 Thread miso k
I can read the MQTT message in HA built in MQTT plugin. So the server is correctly set up and MQTT client too. I can even read the messages in MQTT Explorer. The problem is, that the entity in HA is not updating and is "unknown". Dátum: piatok 26. apríla 2024, čas: 19:27:21 UTC+2, odosielateľ:

[weewx-user] Re: formatting MQTT message sensor lenght

2024-04-26 Thread miso k
finally... the name should not be in "" and it needs to be without space I hope. I am getting value updates now. Thanks everyone for pointing me the right direction! Dátum: piatok 26. apríla 2024, čas: 19:29:52 UTC+2, odosielateľ: miso k > I can read the MQTT message in HA built in MQTT plugin.

[weewx-user] Re: formatting MQTT message sensor lenght

2024-04-26 Thread vince
This works here with HA 2023.8 in a docker container: - name: "Outside" device_class: "temperature" state_topic: "vp2/loop" unit_of_measurement: '°F' value_template: "{{ value_json.outTemp | float | round(1) }}" On Friday, April 26, 2024 at 10:38:22 AM UTC-7 miso k wrote:

Re: [weewx-user] PID file not created in version 5.0.2

2024-04-26 Thread silke
Hi Thomas, hm, what is the status code your weewx is showing when it dies (e.g. check "journatctl -xau weewx" and scroll back to the time of death) ? And does your monit log show any action? My weewx is quite stable these days, so I resorted to testing monit operation by killing the weewx proce