Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashing in Windows 10 when writing log #72

Open
scutzi128 opened this issue Oct 28, 2020 · 0 comments
Open

Crashing in Windows 10 when writing log #72

scutzi128 opened this issue Oct 28, 2020 · 0 comments

Comments

@scutzi128
Copy link

scutzi128 commented Oct 28, 2020

So this was working until somewhat recently. I'm guessing a lovely windows update broke something.

I start the program and it runs as usual then terminates unexpectedly once it tries to write a log. I have determined this by changing the log frequency and the app will crash at whatever the log frequency is set to.

This is the error I get in the cmd window

tplink-monitor@0.0.1 start

node ./app.js

Found device with energy monitor support: Media-PC [8006FB281860444B0213EA80F6D3ED0418B1055A]
Logging started for Media-PC [8006FB281860444B0213EA80F6D3ED0418B1055A] every 10 seconds
Found device with energy monitor support: Router [8006B9DF24EE180A9C56B3EBCB17A8EC18B10BBD]
Logging started for Router [8006B9DF24EE180A9C56B3EBCB17A8EC18B10BBD] every 10 seconds
Found device with energy monitor support: Family Room Console [8006C0E145D2E0C7C2D3CBAE58398FD91A616D0C]
Logging started for Family Room Console [8006C0E145D2E0C7C2D3CBAE58398FD91A616D0C] every 10 seconds
Found device with energy monitor support: Loft Console [8006AE4EA354D317BBC81E4F479E6EDB1998A22A]
Logging started for Loft Console [8006AE4EA354D317BBC81E4F479E6EDB1998A22A] every 10 seconds
Found device with energy monitor support: Microwave [80060F90711D9854E1C68C061F3716EF19A99D77]
Logging started for Microwave [80060F90711D9854E1C68C061F3716EF19A99D77] every 10 seconds
Found device with energy monitor support: Basement Network Gear [8006C40CB50D19A91DA1F94099E0951318AFFADC]
Logging started for Basement Network Gear [8006C40CB50D19A91DA1F94099E0951318AFFADC] every 10 seconds
Found device with energy monitor support: Refrigerator [800601466E81264C02184F864DB11FDB18B1A6F6]
Logging started for Refrigerator [800601466E81264C02184F864DB11FDB18B1A6F6] every 10 seconds
Found device with energy monitor support: Hot Water Recirculator [8006B6B7A3AF83F6BDFAD9B98673B33218B13A01]
Logging started for Hot Water Recirculator [8006B6B7A3AF83F6BDFAD9B98673B33218B13A01] every 10 seconds
Found device with energy monitor support: Bedroom Console [8006E94C1BE709E7D06486D94BD531341A55BAED]
Logging started for Bedroom Console [8006E94C1BE709E7D06486D94BD531341A55BAED] every 10 seconds
Found device with energy monitor support: Gaming-PC [8006B8F2680ACCB25CBD6B1C6A1AAB7218B1F9B3]
Logging started for Gaming-PC [8006B8F2680ACCB25CBD6B1C6A1AAB7218B1F9B3] every 10 seconds
Found device with energy monitor support: House Front Plug [80061D62A040C1226CC2B13604055E8C199847CC]
Logging started for House Front Plug [80061D62A040C1226CC2B13604055E8C199847CC] every 10 seconds
undefined:1
[]"ts":1603218144051,"pw":22.33945}]
^

SyntaxError: Unexpected string in JSON at position 2
at JSON.parse ()
at C:\Users\scutz\Desktop\TP Link Energy Monitoring\services\data-logger.js:51:25
at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:63:3)
npm ERR! code 1
npm ERR! path C:\Users\scutz\Desktop\TP Link Energy Monitoring
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c "node ./app.js"

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\scutz\AppData\Local\npm-cache_logs\2020-10-28T12_30_31_298Z-debug.log
PS C:\Users\scutz\Desktop\TP Link Energy Monitoring>

The npm logs associated with this are also attached. Anyone got any ideas? Seems like there are other users with the same issue.

2020-10-28T12_30_31_298Z-debug.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant