-
Notifications
You must be signed in to change notification settings - Fork 7
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
UnhandledPromiseRejectionWarning: Error - persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file #6
Comments
No idea yet where this originates from, as it doesn't occur on my instance. The accessoryInfo is stored and maintained by Homebridge itself. If it is a test instance, throw away the accessory info in your persist directory to get rid of any accessory cache. But then again, I cannot reproduce. Any logging from Miele@home? E.g. This occurs before initialise? |
These errors appear in the log regularly. The first occurrence is after having discovered the appliances.
I will wipe everything and start again from scratch, because for now, it seems to derail... |
Restarting from scratch (unpair from Home and stopped homebridge instance, removed accessories and persist folders contents, start homebridge instance and pair it to Home) did not stop the issue:
I do not know where to investigate :-( |
I started node with --trace-warnings, here are the new logs:
The first error comes roughly 2 minutes after the appliances discovery. |
Is it possible that it is linked with the fact that I needed to explicitly install node-persist when I updated to the version 2.0.0 of the plugin ? Do I risk to install a new node-persist of homebridge itself ? |
hmmm.... not a good idea to install node-persist 3.1.0 in homebridge itself :-( It does not start, giving those errors:
|
I do not know if this is linked, after a while, the token wants to refresh, but if fails :-(
|
For the node-persist, it is certainly something that Miele@home requires a newer version than your homebridge version (which version do you run?). Neither of these problems occur at my two setups though. Seems some version mismatch of several packages. |
I am running Homebridge 1.2.5 on a MacMini running NodeJS 14.15.0 (NPM 6.14.11). Which are the versions you use ? |
Typescript is at 3.1.1 node-persist itself indeed at 3.1.0. I did forget to add the latter. Don't understand me wrong I suspect the same as you, that the Miele@home process reads the file using 3.1.0. I seem to have the same issue now after re-installing the plugin. I will try to look for a solution. |
If it can help, here is the contents of the AccessoryInfo.0E4EB8423210.json:
|
Sorry to have brought you this :-( |
Thanks for your continued support, this is a killing issue. If all fails I will just rewrite to an old version node-persist code style. |
I read here: https://www.npmjs.com/package/node-persist-legacy/v/0.0.12 that there are some incompatibilities between legacy node-persist (0.0.12/0.0.11) and the new one... |
:-( I installed 3.0.5 of node-persist andI regenerated the token and refresh_token (as I did this morning), but I alway receive "[25/01/2021 20:27:50] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices?language=en failed with status 401: "Unauthorized"." I tested the Miele API with the given token, and it is valid. Do not understand why the plugin now says Unauthorized. and anyway, I still get
hence 3.0.5 does not work for me :-( I am a bit lost, will wait for your feedback ! |
3.0.5 was a mistake from me. Therefore I deleted the message, but you were too quick to notice it. node-persist issues see also. |
OK, thank you for the link about HAP-NodeJS !! It explains the "node-persist-legacy" I mentioned myself. I will be ready for next version 👍🏻 |
And... 2.0.1 is a winner (I waited 3 minutes, and no error, and token is recognised !!) !!! Thank you ! |
Thanks for your patience. I will close this issue. Learned something new again today. |
Hi @QuickSander , HI @MichelRabozee , can you please quick explan how you fixed the problem? I am running the homebridge image on a PI5 and using the plugin mieleathome in version 3.5.0 (node 20.11.0 / homebridge ui 4.56.1 / homebridge 1.7.0). Somehow i get the following error message: Miele API request https://api.mcs3.miele.com/v1/devices?language=de failed with status 401: "Unauthorized". |
Hi, this morning, I also got 401 error around 2:35 (Brussels timezone, DST). But it recovered by itself, I guess it was a Miele server issue.
|
Thanks @MichelRabozee, I still have the error. Could it be due to an incorrect node package? Node-persist was mentioned here in the course. I am currently on node 20.11.0 with Homebridge; maybe I can only update the node persist package? |
I am with nodejs 20.10.0 and no issue. I suggest you restart the step to recreate the authentication token. Maybe it became invalid and was not recreated correctly on expiration. |
i will give it a try. Thanks |
Hi MichelRabozee, I had already requested new access data this afternoon. I just saved the plug-in as an under-bridge and was then allowed to go through the registration process again. Now it works and the token is up to date. |
Excellent ! |
Hi,
I receive a "UnhandledPromiseRejectionWarning: Error" because it seems that something is seen wrong in the persist/AccessoryInfo.0E4EB8423210.json file.
I removed the platform and the homebridge instance (I use a separate instance for my tests, so no big deal) and installed everything again, but the problem still occur.
The text was updated successfully, but these errors were encountered: