li-dennis / chromejoule Goto Github PK

Repro:

• start a 10 minute cook @ 45C (or whatever temp is ~20 deg warmer than room temp)
• note that timer is decreasing before temp is reached

(Incidentally, this is the opposite of the problem that the ChefSteps-provided app has: Viz., it doesn't automatically start the timer even when the water is heated.)

Hey @dennisli92 !
Amazing work decoding the inner workings of the Joule API! I was wondering if you have any plans on putting out a generalized library in Typescript or Javascript for usage in a wider variety of applications. For example I'd love to hook into my Joule via home automation applications.

If you aren't I might take a stab at it myself!

Hi, Dennis.
I'm also interesting to R.E. Joule Android app :) But I am fan of old sweet Nokia/ MS WinPhones... so, I decided to create the very simpest Win10Mobile app that shows the count of Joule devices :)
I 2 day ago found JouleUWP project, forked it and researched a little. The code is very uncomplete :(
Then I found your great article at Medium site. Then I found your cool chromeJoule :)
But your code is so difficult to me :) I cannot translate it onto C#, heh (No good autotranslators at all!)
Can you help me to undestand, what first steps your app does?
Which url do you use to authorize via ShefSteps API?
I tried to use Postman (GET-request https://chefsteps.com/api/v0/authorize, and x-form-encoded user[email] and user[password]) and catched "404 not found" :

Maybe it happens because of I have not real Joule device (I not ordered yet it as I don't like Droidphones, hehe) ?...
Can you 'clone' yout account with some fake login-pass and Joule activated? Or I PM my login-pass pair :) I need to check whats fails: API endpoints or BT-first activation needed...
Best wishes,
mediaexplorer
30-year c# veteran

Immediately after install clicking on the icon causes the spinner to just spin.

Looking in the inspector I see:

popup.js:46230 Uncaught (in promise) Error: Not a valid address, must be multiple of 2: 377
    at hexToByteAddress (popup.js:46230)
    at new CirculatorCommunicationClient (popup.js:37653)
    at new CirculatorClient (popup.js:35434)
    at CirculatorFactory.createCirculatorFromConnectionData (popup.js:38373)
    at popup.js:38699
    at Function._.each._.forEach (popup.js:115079)
    at CirculatorManager.convertConnectionDataToCirculators (popup.js:38692)
    at popup.js:38667
    at _fulfilled (popup.js:95964)
    at self.promiseDispatch.done (popup.js:95993)

Thanks for this great piece of research.

My partner got me a Joule for Xmas and I'm really not a fan of the Joule app's microscopic fonts which ignore every system setting including accessibility! 😞

Attempting to build in 2022 using Ubuntu 22.04 with node --version=v12.22.9:

$  git clone https://github.com/li-dennis/chromeJoule.git
$  cd chromeJoule/
$  npm install
$ grep -i " warn\b\| error\b"  /home/sid/.npm/_logs/2023-01-05T06_49_43_997Z-debug-0.log

[... many many deprecation warnings cut out]

1765 warn deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
1826 warn deprecated [email protected]: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
2141 warn deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
2145 warn deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
2159 error code E404
2160 error 404 Not Found - GET https://registry.npmjs.org/websocket-rpc-stream/-/websocket-rpc-stream-0.0.15.tgz - Not found
2161 error 404
2162 error 404 'websocket-rpc-stream@https://registry.npmjs.org/websocket-rpc-stream/-/websocket-rpc-stream-0.0.15.tgz' is not in this registry.
2163 error 404 You should bug the author to publish it (or use the name yourself!)

$ git reset --hard
$ rm -f package-lock.json  # try to let it install fresher versions where ">=" was given
$ node install

npm ERR! Cannot convert undefined or null to object
npm ERR! A complete log of this run can be found in:
npm ERR! /home/sid/.npm/_logs/2023-01-05T06_59_39_718Z-debug-0.log

Still pretty much same deprecated / unsupported warnings and the same 404, leading to slightly different fatal error.

If you're still using this and plan to update it for your own use, I'd be grateful if you bump whatever packages are needed for it to build again (or maybe add a zip of a successful build?)

I have no experience with Chrome extensions or the runtimes you've included, but I do have experience with APIs so in worst case I can probably learn about the API from your code and write a commandline tool, which I guess would be nice if I wanted to use it with at or cron 😄