kshetline / aw-clock Goto Github PK

View Code? Open in Web Editor NEW

51.0 51.0 6.0 31.33 MB

Astronomy/weather clock

License: Other

TypeScript 78.48% JavaScript 1.15% HTML 7.19% Shell 1.49% SCSS 5.53% CSS 6.16%

astronomy clocks gps raspberrypi typescript weather

aw-clock's People

Contributors

Stargazers

Watchers

Forkers

emxsys youkiddin sicarul dick-lauraunt tremusa gvpdbish

aw-clock's Issues

Installer thinks it's not an RPi?

I'm getting this error when attempting to install:

--ddev option is only valid on Raspberry Pi
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build:prod: `ts-node build.ts -p "--bash" "--ddev"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build:prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-14T23_23_40_087Z-debug.log

Contents of the debug log:

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/usr/bin/node',
1 verbose cli   '/usr/bin/npm',
1 verbose cli   'run',
1 verbose cli   'build:prod',
1 verbose cli   '--',
1 verbose cli   '--bash',
1 verbose cli   '--ddev'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild:prod', 'build:prod', 'postbuild:prod' ]
5 info lifecycle [email protected]~prebuild:prod: [email protected]
6 info lifecycle [email protected]~build:prod: [email protected]
7 verbose lifecycle [email protected]~build:prod: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~build:prod: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/build/aw-clock/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle [email protected]~build:prod: CWD: /home/pi/build/aw-clock
10 silly lifecycle [email protected]~build:prod: Args: [ '-c', 'ts-node build.ts -p "--bash" "--ddev"' ]
11 silly lifecycle [email protected]~build:prod: Returned: code: 1  signal: null
12 info lifecycle [email protected]~build:prod: Failed to exec build:prod script
13 verbose stack Error: [email protected] build:prod: `ts-node build.ts -p "--bash" "--ddev"`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:314:20)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:314:20)
13 verbose stack     at maybeClose (internal/child_process.js:1022:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/pi/build/aw-clock
16 verbose Linux 4.19.66-v7+
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build:prod" "--" "--bash" "--ddev"
18 verbose node v12.21.0
19 verbose npm  v6.14.11
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] build:prod: `ts-node build.ts -p "--bash" "--ddev"`
22 error Exit status 1
23 error Failed at the [email protected] build:prod script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Feature request - indicate day and night in the planet display

My wife and I enjoy using the astronomy dial to locate the planets on most evenings. We find the planet display very enlightening.

For your consideration, shade the planet display to indicate both the daytime and nighttime sky.

Rationale: to quickly identify which planets are visible within the night sky.
Suggestion: shade the planet display's dial segment that is coincident with Sun's above the horzon arc with a lighter color.

Thanks for a great clock!

disabling kiosk

How do I disable automatically starting in kiosk mode upon boot?

I tried setting AWC_KIOSK_MODE=false in /etc/default/weatherService then rebooting but no change, it still comes up.

BTW, the project README.md file says this file is named /etc/defaults/weatherService

Getting an Error at Step 10

- Dedicated device setup -
Step 1 of 17: Updating/upgrading packages (can take a long time!) ✔
Step 2 of 17: Stopping weatherService if currently running ✔
Step 3 of 17: pigpio already installed ✔
Step 4 of 17: chromium-browser already installed ✔
Step 5 of 17: unclutter already installed ✔
Step 6 of 17: Installing forever ✘
Step 7 of 17: Fonts already installed ✔
Step 8 of 17: xscreensaver already installed ✔
Step 9 of 17: Disabling screen saver ✔
- Building application -
Step 10 of 17: Updating client ✘
ERROR: npm v10.2.3 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)

I'm not sure what I missed here. The npm version said 6 and nodejs was 12.

Great Project!

What a great project - thanks very much!

Small thing - any chance of an option to display the windspeeds in knots instead of kph when in metric?

Error 9: Aw, Snap

The program runs fine for a couple of days, then the Aw, Snap something went wrong error shows, When I click on the Reload button, all starts up and runs again for a couple of days again.

Any idea why I get his error and how I can stop it?

Thanks

Scott

Thank you very much for this program - I'm trying to install on a Raspberry Pi 4 and when I reach Step 8 of the install, an error occurs and installation stops. I tried rebooting and running the install sequence again, but the same error. See below. Thanks for any help.

Dedicated device setup -
Step 1 of 16: Stopping weatherService if currently running ✔
Step 2 of 16: pigpio already installed ✔
Step 3 of 16: chromium-browser already installed ✔
Step 4 of 16: unclutter already installed ✔
Step 5 of 16: forever already installed ✔
Step 6 of 16: Fonts already installed ✔
Step 7 of 16: xscreensaver already installed ✔
Step 8 of 16: Disabling screen saver ✘
sed: can't read /home/pi/.xscreensaver: No such file or directory
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: ts-node build.ts "--bash" "-i"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-11-26T18_44_31_904Z-debug.log

Feature request - add today's and tomorrow's textual forecasts to the marquee

In our household we display the weather/clock on our television, which is not a touchscreen. We use a keyboard/mouse, but it is not convenient.

Please consider adding the Today and Tomorrow forecasts to the marquee. The additional detail in textual forecasts is richer and more useful than the one-line summary currently displayed in the marquee region.

If this request is outside the scope of your project, then I would happily pursue it in my fork. I've already enlarged the marquee region and font, so I'm familiar with that part. But I have not investigated from where to pull the forecasts. Any tips would be appreciated.

Massive Number of requests to api.github.com

Running a default install, and it seems the pi is hitting api.github.com at least 30 seconds sometimes. Is there a way to tune down the amount of requests? Im also not aware of what the device is doing with all those queries yet. Pi is only running the aw-clock software.

Im getting 60k dns requests from this device every day.

Error installing from scratch

I have a fresh copy of raspbian, and when running sudo ./build.sh -i I am getting an npm error (seems some packages are mismatched versions ?)

Installing npm packages. This process can be very slow!
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142

added 529 packages, and audited 530 packages in 7m

65 packages are looking for funding
  run `npm fund` for details

2 moderate severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"^5.47.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^2.0.0 || ^3.0.0 || ^4.0.0" from [email protected]
npm ERR! node_modules/istanbul-instrumenter-loader
npm ERR!   dev istanbul-instrumenter-loader@"^3.0.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/pi/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2022-01-22T00_47_20_046Z-debug.log
Starting main installer...
internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module '@tubular/util'
Require stack:
- /home/pi/tools/aw-clock/build.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.483 (/home/pi/tools/aw-clock/build.js:85:146)
    at __webpack_require__ (/home/pi/tools/aw-clock/build.js:86:316)
    at Object.582 (/home/pi/tools/aw-clock/build.js:3:231)
    at __webpack_require__ (/home/pi/tools/aw-clock/build.js:86:316)
    at /home/pi/tools/aw-clock/build.js:86:395
    at Object.<anonymous> (/home/pi/tools/aw-clock/build.js:86:402) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/home/pi/tools/aw-clock/build.js' ]
}

Unable to install using instructions. 404 errors/etc.

I wasn't able to catch all the errors when running sudo ./build.sh since it doesn't seem to want to pipe to a log and I have to just go with what fits in my scrollback, but I'm catching some 404 errors in the process. In particular, there's an error almost right off for node-sass where it just doesn't even find the url "https://github.com/sass/node-sass/releases/download/v4.14.1/linux-arm-72_binding.node" at all. When I look in their official releases page manually I don't even see any official ARM releases at all for any version, so maybe they've removed their ARM support?

Is there a way I can save a log of the process? Something like "sudo ./build.sh --ddev > ./build.log" doesn't work.

New features expected

I'm using this project for more than 8-9 months and it's working charm and I like it very much. Thanks to the author for such a beautiful creativity and work done. Just one quick confirmation, can we expect indoor and outdoor AQI and PM level features integration in future release?

TypeError for first time users

I seem to be getting a type error here: https://github.com/kshetline/aw-clock/blob/master/src/settings.ts#L41

I believe it is caused by this line: https://github.com/kshetline/aw-clock/blob/master/src/settings.ts#L82

Cookies.get('ampm') isn't set, so it returns undefined, which then leads to s being undefined in the expression s = s.toLowerCase();

I was able to reproduce it in an incognito window every time. Once the ampm cookie is set, it seems to work fine.

Feature request - add wind forecast(s)

The daily and hourly weather in my region (Ventura, Californai) is dominated by the prevailing winds, much more so than precipitation (unless it's raining, then we go wacky with news coverage of puddles on the roads). When Santa Ana winds arrive, significant changes in wind speeds and direction can change by the hour. The aw-clock would have more value if wind forecasts were added. Wind forecasts help with the following (just to name a few):

Wildfire behavior predictions
Beach recreation
Aviation

Beautiful application

This is really a great application and work that is done by you is excellent. I managed to setup it on my rpi3 and I have one observation and one suggestion. It will be great of one detailed diagram of clock gadgets will be provided as there is one widget around the clock face something like small arrow shape that shifts little up and down across a day. I'm still failed to find the purpose of that one 😊. Second this will really be awesome to have Air quality index data also on this clock.

Thanks jitender