Re: [weewx-user] OSError: [Errno 113] Aucun chemin d'accès pour atteindre l'hôte cible
Hello and thank you It's very verbose and I don't see anything clear. Here is the 2nd dmesg pi@PiMeteo:~ $ dmesg [ 0.00] Booting Linux on physical CPU 0x0 [ 0.00] Linux version 5.10.63-v7l+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1496 SMP Wed Dec 1 15:58:56 GMT 2021 [ 0.00] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d [ 0.00] CPU: div instructions available: patching division code [ 0.00] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.00] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1 [ 0.00] random: fast init done [ 0.00] Memory policy: Data cache writealloc [ 0.00] Reserved memory: created CMA memory pool at 0x1ac0, size 320 MiB [ 0.00] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.00] Zone ranges: [ 0.00] DMA [mem 0x-0x2fff] [ 0.00] Normal empty [ 0.00] HighMem [mem 0x3000-0xfbff] [ 0.00] Movable zone start for each node [ 0.00] Early memory node ranges [ 0.00] node 0: [mem 0x-0x3b3f] [ 0.00] node 0: [mem 0x4000-0xfbff] [ 0.00] Initmem setup node 0 [mem 0x-0xfbff] [ 0.00] On node 0 totalpages: 1012736 [ 0.00] DMA zone: 1728 pages used for memmap [ 0.00] DMA zone: 0 pages reserved [ 0.00] DMA zone: 196608 pages, LIFO batch:63 [ 0.00] HighMem zone: 816128 pages, LIFO batch:63 [ 0.00] percpu: Embedded 20 pages/cpu s50828 r8192 d22900 u81920 [ 0.00] pcpu-alloc: s50828 r8192 d22900 u81920 alloc=20*4096 [ 0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.00] Built 1 zonelists, mobility grouping on. Total pages: 1011008 [ 0.00] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:51:75:1D vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=ttyS0,115200 console=tty1 root=PARTUUID=b9db7205-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [ 0.00] Kernel parameter elevator= does not have any effect anymore. Please use sysfs to set IO scheduler for individual devices. [ 0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.00] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.00] software IO TLB: mapped [mem 0x1489-0x1889] (64MB) [ 0.00] Memory: 3601132K/4050944K available (10240K kernel code, 1364K rwdata, 3192K rodata, 2048K init, 891K bss, 122132K reserved, 327680K cma-reserved, 3264512K highmem) [ 0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.00] ftrace: allocating 34315 entries in 68 pages [ 0.00] ftrace: allocated 68 pages with 2 groups [ 0.00] rcu: Hierarchical RCU implementation. [ 0.00] Rude variant of Tasks RCU enabled. [ 0.00] Tracing variant of Tasks RCU enabled. [ 0.00] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.00] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.00] GIC: Using split EOI/Deactivate mode [ 0.00] random: get_random_bytes called from start_kernel+0x3c8/0x59c with crng_init=1 [ 0.08] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns [ 0.27] clocksource: timer: mask: 0x max_cycles: 0x, max_idle_ns: 1911260446275 ns [ 0.86] bcm2835: system timer (irq = 25) [ 0.000730] arch_timer: cp15 timer(s) running at 54.00MHz (phys). [ 0.000748] clocksource: arch_sys_counter: mask: 0xff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns [ 0.000766] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns [ 0.000781] Switching to timer-based delay loop, resolution 18ns [ 0.001034] Console: colour dummy device 80x30 [ 0.001102] printk: console [tty1] enabled [ 0.001158] Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=54) [ 0.001190] pid_max: default: 32768 minimum: 301 [ 0.001355] LSM: Security Framework initializing [ 0.001539] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.001564] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.003019] cgroup: Disabling memory control group subsystem [ 0.003249] CPU: Testing write buffer coherency: ok [ 0.003699] CPU0: thread -1, cpu 0, socket 0, mpi
Re: [weewx-user] Re: RSync using NFS
On 04/03/2023 21:13, paul.ba...@gmail.com wrote: Hello, I don't understand why you want to use rsync over NFS. NFS juste does all the work for you. Once the remote file system is mounted, usually at boot or login depending on the setup, there is no more distinction between the local files and the remote ones. So, in weewx.conf - disable rsync - set HTML_ROOT = something like HTML_ROOT = /www/html/weewx NFS will know where /www/ is installed, of course this is defined in the NFS setup. Regards, Paul PS Remember, in the mid 80's SUN said The network IS the computer Thanks Paul, I'd forgotten I'd set up NFS to share the pages I wanted to sync. The reason I'm doing this is originally I had weewx with weewx-sdr running outside on a Pi fitted inside an old security camera that was capturing data using a cheap DVB-T USB stick. This would occasionally stop receiving data from one sensor so I upgraded to a Nooelec RTL-SDR v5. While I was finding time to replace the DVB-T stick I ran weewx on my server with the Nooelec. This was working, but I didn't want to open up port 80 on the server to the outside world. So I was copying the data over to the Raspberry Pi which did have an outside connection. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/56720047-a76c-2831-45ca-b83e727e2360%40gmail.com.
[weewx-user] Re: Belchertown - lost condition images on homepage
Did you solve this issue? Having the same after new installation. I remember seeing this before and cannot remember how I solved it. On Friday, June 24, 2022 at 3:53:00 AM UTC-4 Uwe S. wrote: > Hi all, > > i've set up sucessfully the Belchertown skin, but somewhere in between i > lost the current condition images: > > > [image: belcher.jpg] > > Any ideas how to get it back? > > Thanks > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/65c4ab0d-9501-4dd9-944d-a1bef0d159d4n%40googlegroups.com.
[weewx-user] Re: Belchertown - lost condition images on homepage
I actually figured out my issue. In the belchertown skin.conf, I had forecast_enabled set to 0. Changed it to 1 and the images are now showing up. On Sunday, March 5, 2023 at 11:30:22 AM UTC-5 tarob...@gmail.com wrote: > Did you solve this issue? Having the same after new installation. I > remember seeing this before and cannot remember how I solved it. > > On Friday, June 24, 2022 at 3:53:00 AM UTC-4 Uwe S. wrote: > >> Hi all, >> >> i've set up sucessfully the Belchertown skin, but somewhere in between i >> lost the current condition images: >> >> >> [image: belcher.jpg] >> >> Any ideas how to get it back? >> >> Thanks >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a82c8414-0121-4720-b6f1-f5309f31e5f3n%40googlegroups.com.
Re: [weewx-user] OSError: [Errno 113] Aucun chemin d'accès pour atteindre l'hôte cible
[56543.148991] usb 1-1.4: USB disconnect, device number 3 [56604.597374] usb 1-1.4: new full-speed USB device number 4 using xhci_hcd [56604.745456] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6015, bcdDevice=10.00 [56604.745478] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [56604.745497] usb 1-1.4: Product: FT231X USB UART [56604.745514] usb 1-1.4: Manufacturer: FTDI [56604.745530] usb 1-1.4: SerialNumber: D309M352 pi@PiMeteo:~ $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO) Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub So the pi is seeing the device, but it is not allocating a tty in /dev to it. You might just need to insmod a kernel module so it assigns a device in /dev to it. Check your 'lsmod' output and see if the ftdi_sio device is loaded. If not, load it with 'insmod' and see if that helps. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e766be12-73f6-4f87-856c-65c790ad4dbcn%40googlegroups.com.
Re: [weewx-user] OSError: [Errno 113] Aucun chemin d'accès pour atteindre l'hôte cible
"lsmod" does not see much. And when I try this with "insmod", it's not terrible. Sorry, I'm far from being a Linuxien guru pi@PiMeteo:~ $ lsmod Module Size Used by --- pi@PiMeteo:~ $ insmod /dev/ttyUSB0 insmod: ERROR: could not load module /dev/ttyUSB0: No such file or directory Le 05-03-23 à 18:34, vince a écrit : So the pi is seeing the device, but it is not allocating a tty in /dev to it. You might just need to insmod a kernel module so it assigns a device in /dev to it. Check your 'lsmod' output and see if the ftdi_sio device is loaded. If not, load it with 'insmod' and see if that helps. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/31d65f55-28b1-62c9-b574-95009f441bd8%40gmail.com.
[weewx-user] What template is being used by the CheetahGenerator? How can you find the path?
My CheetahGenerator is executing regularly but when I make changes to: "/etc/weewx/skins/Standard/index.html.tmpl" I do not see any changes to my html output. FWIW, I upload data to Wunderground and sftp to a private server and the data is current. This is my path: /etc/weewx/weewx.conf [StdReport] SKIN_ROOT = /etc/weewx/skins Any ideas why changing the index.html.tmpl doesn't do anything? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0dceccab-c1d8-4043-b99d-7a7272413ec5n%40googlegroups.com.
[weewx-user] Re: What template is being used by the CheetahGenerator? How can you find the path?
Hard to speculate with a two line snippet from weewx.conf and no excerpts from the logs at all https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/11931c0b-b790-4651-bacb-26c34cbfd3c3n%40googlegroups.com.
[weewx-user] Re: What template is being used by the CheetahGenerator? How can you find the path?
I should have been more clear perhaps. Is the /etc/weewx/skins/Standard/index.html.tmpl file the template I should edit to make changes to my html file given the following path: [StdReport] SKIN_ROOT = /etc/weewx/skins On Sunday, March 5, 2023 at 6:03:59 PM UTC-6 vince wrote: > Hard to speculate with a two line snippet from weewx.conf and no excerpts > from the logs at all > > https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user > https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/90ce002b-fd5c-4356-ae63-838d6691f677n%40googlegroups.com.
[weewx-user] Webpage won't connect to MQTT
I've been setting up Weewx with Belchertown, and everything seems to be
working great...except that I cannot connect to the MQTT within the skin.
My Mosquito server is running in a docker on my Unraid server, and I have
an Ubuntu VM that is gathering UDP packets from my Tempest Weatherflow
station. Weewx is writing the data to the Mosquito server without
problem. I can connect to the server on my local network with MQTT
Explorer, and I can see the weather data & loop.
For the web page, I'm running a Cloudflare tunnel into my network, and I
have a CaddyV2 reverse proxy between the tunnel and the web server. I'm
able to access the website from the Internet without problem:
https://www.2whippets.org/weather/belchertown/
I have a DNS entry for mqtt.whippets.org set up in cloudflare for the
websockets, and I'm able to use MQTT Explorer to connect to the tunnel from
the internet. wg://mqtt.2whippets.org on port 443 (with TLS encryption).
It goes through the cloudflare tunnel to the caddy proxy that has a config
as such:
{
log
tls internal
reverse_proxy 192.168.254.3:9001
}
And it works through MQTT Explorer.
However, in my Weewx.conf file, my connection looks like this:
#--- MQTT Websockets (for Real Time Streaming) Options ---
mqtt_websockets_enabled = 1
mqtt_websockets_host = "ws://mqtt.2whippets.org"
mqtt_websockets_port = 443
mqtt_websockets_ssl = 0
mqtt_websockets_topic = "weather/#"
# disconnect_live_website_visitor = 180
It doesn't seem to make any difference if I turn on Websockets_ssl. It
still fails.
I'm using the cloudflare tunnel so that all of the certificates are taken
care of by cloudflare...and I don't have to open any ports on my firewall.
Any ideas of where to troubleshoot?
Thanks
rm
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/af06ab7e-aec6-4b80-a36c-758468320fdan%40googlegroups.com.
[weewx-user] Re: What template is being used by the CheetahGenerator? How can you find the path?
No idea. Again we need to see the StdReport section of weewx.con and some logs per the FAQ and Wiki so we can see what you do or don't have enabled. On Sunday, March 5, 2023 at 4:24:45 PM UTC-8 madwx wrote: > I should have been more clear perhaps. > > Is the /etc/weewx/skins/Standard/index.html.tmpl file the template I > should edit to make changes to my html file given the following path: > > [StdReport] > SKIN_ROOT = /etc/weewx/skins > > On Sunday, March 5, 2023 at 6:03:59 PM UTC-6 vince wrote: > >> Hard to speculate with a two line snippet from weewx.conf and no excerpts >> from the logs at all >> >> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user >> https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem >> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1d11150a-b87e-4cfb-b4f5-9faf1a789df1n%40googlegroups.com.
[weewx-user] Re: Bootstrap skin a.k.a "fuzzy-archer" v4.0 preview available
I see no configuration instructions. Surely there must be some if this uses MQTT for live updates. On Saturday, March 4, 2023 at 6:10:31 PM UTC-5 michael.k...@gmx.at wrote: > Another week over, I've fixed several bugs, added missing functionality > and did some little enhancements on the styles. I've put everything in the > master branch by now, so if you want to updated, the feature branch is now > obsolete. By the way, thanks for the feedback and issues on github. Also > thanks to Tom, who is always precise in his feedback, helps a lot. > > Still: there is help needed for skin specific translations. > > > > > michael.k...@gmx.at schrieb am Sonntag, 26. Februar 2023 um 15:05:02 > UTC+1: > >> Hi all, >> >> there is a new version of the Bootstrap skin in the pipeline. Last year >> this skin has been modernized and updated with interactive gauges and >> charts, also, using MQTT live updates were made available. >> >> Preview: https://www.kainzbauer.net/weather/Rif/en/ >> >> The version is still under development, to install it anyway, >> download the "lang" branch here: >> >> https://github.com/brewster76/fuzzy-archer/archive/refs/heads/lang.zip >> >> wee_extension --install lang.zip >> >> Although I've installed it on several test environments, I cannot >> guarantee everything will work flawlessly by now. >> >> If you encounter problems, please file any issues here: >> https://github.com/brewster76/fuzzy-archer/issues and let me know in >> this thread. >> >> Version 4 now has few new features so far, but in another way it is >> completely new: >> >> New in v4.0: >> >>- Complete and thorough overhaul of the skin, many breaking changes. >>It is recommended to start over with a fresh install >>- This skin used to consist of three skins, now reduced to one >>- Localization is now done the WeeWX way (hopefully Tom doesn't >>disagree on this one) >>- Less and easier configuration >>- Many customization can now be done by configuration only, no more >>need to touch the templates >>- Day/night background in Live Charts (needs pyephem installed) >>- Bug fixes and other enhancements >> >> However, there are still some things to do, help is needed doing the >> translations for: >> >>- traditional chinese >>- czech >>- spanish >>- finnish (there isn't even a language file stub yet) >>- french >>- greek >>- italian >>- korean (there isn't even a language file stub yet) >>- dutch >>- thai >> >> Let me know, if you try you manage to run it without any issues also:) >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2b1e7715-cb27-44b7-9be9-9bd380b7b8cfn%40googlegroups.com.
[weewx-user] Re: Webpage won't connect to MQTT
It's likely that the websockets port is not 443 as that is https and you do
have your reverse proxy set for 9001
On Sunday, March 5, 2023 at 7:47:25 PM UTC-5 Rich M wrote:
> I've been setting up Weewx with Belchertown, and everything seems to be
> working great...except that I cannot connect to the MQTT within the skin.
>
> My Mosquito server is running in a docker on my Unraid server, and I have
> an Ubuntu VM that is gathering UDP packets from my Tempest Weatherflow
> station. Weewx is writing the data to the Mosquito server without
> problem. I can connect to the server on my local network with MQTT
> Explorer, and I can see the weather data & loop.
>
> For the web page, I'm running a Cloudflare tunnel into my network, and I
> have a CaddyV2 reverse proxy between the tunnel and the web server. I'm
> able to access the website from the Internet without problem:
> https://www.2whippets.org/weather/belchertown/
>
> I have a DNS entry for mqtt.whippets.org set up in cloudflare for the
> websockets, and I'm able to use MQTT Explorer to connect to the tunnel from
> the internet. wg://mqtt.2whippets.org on port 443 (with TLS
> encryption). It goes through the cloudflare tunnel to the caddy proxy that
> has a config as such:
>
> {
> log
> tls internal
> reverse_proxy 192.168.254.3:9001
> }
>
> And it works through MQTT Explorer.
>
> However, in my Weewx.conf file, my connection looks like this:
>
> #--- MQTT Websockets (for Real Time Streaming) Options ---
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = "ws://mqtt.2whippets.org"
> mqtt_websockets_port = 443
> mqtt_websockets_ssl = 0
> mqtt_websockets_topic = "weather/#"
> # disconnect_live_website_visitor = 180
>
> It doesn't seem to make any difference if I turn on Websockets_ssl. It
> still fails.
>
> I'm using the cloudflare tunnel so that all of the certificates are taken
> care of by cloudflare...and I don't have to open any ports on my firewall.
>
> Any ideas of where to troubleshoot?
>
> Thanks
>
> rm
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/aa7e51f6-9ec3-49ea-8c97-71290db33f88n%40googlegroups.com.
[weewx-user] Re: What template is being used by the CheetahGenerator? How can you find the path?
Thanks for your help vince. After going through the syslog I was able to discover that I'm using "Seasons" skin. It's still somewhat confusing but at least I narrowed it down. On Sunday, March 5, 2023 at 7:09:14 PM UTC-6 vince wrote: > No idea. Again we need to see the StdReport section of weewx.con and some > logs per the FAQ and Wiki so we can see what you do or don't have enabled. > > On Sunday, March 5, 2023 at 4:24:45 PM UTC-8 madwx wrote: > >> I should have been more clear perhaps. >> >> Is the /etc/weewx/skins/Standard/index.html.tmpl file the template I >> should edit to make changes to my html file given the following path: >> >> [StdReport] >> SKIN_ROOT = /etc/weewx/skins >> >> On Sunday, March 5, 2023 at 6:03:59 PM UTC-6 vince wrote: >> >>> Hard to speculate with a two line snippet from weewx.conf and no >>> excerpts from the logs at all >>> >>> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user >>> https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem >>> >>> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0d011b06-87b0-408d-bff4-0f16db0787d5n%40googlegroups.com.
