search

QuickSander / homebridge-mieleathome

Apache License 2.0
37 stars 7 forks source link

UnhandledPromiseRejectionWarning: Error - persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file #6

Closed MichelRabozee closed 3 years ago

MichelRabozee commented 3 years ago

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.

(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:75050) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
QuickSander commented 3 years ago

No idea yet where this originates from, as it doesn't occur on my instance. The accessoryInfo is stored and maintained by Homebridge itself. Seems to me the AccessoryInfo file got corrupted somehow.

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?

MichelRabozee commented 3 years ago

These errors appear in the log regularly. The first occurrence is after having discovered the appliances. After a while also the token is tried to be refreshed, but seems to fail, then the token is no more valid:

[25/01/2021 11:06:31] [HB Supervisor] Restarting Homebridge...
[25/01/2021 11:06:31] [HB Supervisor] Starting Homebridge with extra flags: -I
[25/01/2021 11:06:31] [HB Supervisor] Started Homebridge v1.2.5 with PID: 75050
[25/01/2021 11:06:31] Loaded config.json with 0 accessories and 2 platforms.
[25/01/2021 11:06:31] ---
[25/01/2021 11:06:31] Loaded plugin: homebridge-camera-ffmpeg@3.0.3
[25/01/2021 11:06:31] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[25/01/2021 11:06:31] ---
[25/01/2021 11:06:31] Loaded plugin: homebridge-config-ui-x@4.36.0
[25/01/2021 11:06:31] Registering platform 'homebridge-config-ui-x.config'
[25/01/2021 11:06:31] ---
[25/01/2021 11:06:31] Loaded plugin: homebridge-contactnotifier@0.0.6
[25/01/2021 11:06:31] Registering accessory 'homebridge-contactnotifier.ContactNotifier'
[25/01/2021 11:06:31] ---
[25/01/2021 11:06:31] Loaded plugin: homebridge-daikin-local@2021.4.1
[25/01/2021 11:06:31] Registering accessory 'homebridge-daikin-local.Daikin-Local'
[25/01/2021 11:06:31] ---
[25/01/2021 11:06:32] Loaded plugin: homebridge-http-switch@0.5.34
[25/01/2021 11:06:32] Registering accessory 'homebridge-http-switch.HTTP-SWITCH'
[25/01/2021 11:06:32] ---
[25/01/2021 11:06:32] Loaded plugin: homebridge-mieleathome@2.0.0
[25/01/2021 11:06:32] Registering platform 'homebridge-mieleathome.Miele@home'
[25/01/2021 11:06:32] ---
[25/01/2021 11:06:32] Loaded plugin: homebridge-outsidetemperature@0.0.2
[25/01/2021 11:06:32] Registering accessory 'homebridge-outsidetemperature.OutsideTemperature'
[25/01/2021 11:06:32] ---
[25/01/2021 11:06:32] Loaded plugin: homebridge-platform-wemo@2.9.1
[25/01/2021 11:06:32] Registering platform 'homebridge-platform-wemo.BelkinWeMo'
[25/01/2021 11:06:32] ---
[25/01/2021 11:06:32] Loaded plugin: homebridge-roomba2@1.2.0
[25/01/2021 11:06:32] Registering accessory 'homebridge-roomba2.Roomba2'
[25/01/2021 11:06:32] ---
[25/01/2021 11:06:32] Loaded plugin: homebridge-script2@0.3.0
[25/01/2021 11:06:32] Registering accessory 'homebridge-script2.Script2'
[25/01/2021 11:06:32] ---
[25/01/2021 11:06:32] Loaded plugin: homebridge-sonytvremote@10.1.3
[25/01/2021 11:06:32] Registering accessory 'homebridge-sonytvremote.SonyTV'
[25/01/2021 11:06:32] ---
[25/01/2021 11:06:33] Loaded plugin: homebridge-videodoorbell@0.2.9
[25/01/2021 11:06:33] Registering platform 'homebridge-videodoorbell.Video-doorbell'
[25/01/2021 11:06:33] ---
[25/01/2021 11:06:33] Loaded plugin: homebridge-watervolume@0.0.2
[25/01/2021 11:06:33] Registering accessory 'homebridge-watervolume.WaterVolume'
[25/01/2021 11:06:33] ---
[25/01/2021 11:06:33] Loading 2 platforms...
[25/01/2021 11:06:33] [Corniche Homebridge-Three Config] Initializing config platform...
[25/01/2021 11:06:33] [Corniche Homebridge-Three Config] Running in Service Mode
[25/01/2021 11:06:33] [Miele] Initializing Miele@home platform...
[25/01/2021 11:06:33] [Miele] Loading accessory data from cache: Lave-vaisselle
[25/01/2021 11:06:33] [Miele] Loading accessory data from cache: Lave-linge
Setup Payload:
X-HM://0024AOUT1LIB2
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
                       
    ┌────────────┐     
    │ 499-82-453 │     
    └────────────┘     
                       
[25/01/2021 11:06:33] Homebridge v1.2.5 is running on port 51809.
[25/01/2021 11:06:33] [Miele] No *valid* token present in persistent storage. Creating new from configuration.
[25/01/2021 11:06:33] [Miele] Discovered device: id: mac-001D63FFFE0203B2, name: Four, model: 
[25/01/2021 11:06:33] [Miele] Ignoring unsupported device. Device: "Four" with raw type value: 12.
[25/01/2021 11:06:33] [Miele] Discovered device: id: 000127334912, name: Taque, model: 
[25/01/2021 11:06:33] [Miele] Ignoring unsupported device. Device: "Taque" with raw type value: 14.
[25/01/2021 11:06:33] [Miele] Discovered device: id: mac-001D63FFFE0203B4, name: Lave-vaisselle, model: 
[25/01/2021 11:06:33] [Miele] Re-creating existing accessory with data from cache: Lave-vaisselle
[25/01/2021 11:06:33] [Miele] Discovered device: id: 000116035470, name: Lave-linge, model: 
[25/01/2021 11:06:33] [Miele] Re-creating existing accessory with data from cache: Lave-linge
[25/01/2021 11:06:33] [Miele] Discovered device: id: mac-00124B0005AB4D8B, name: Frigo, model: 
[25/01/2021 11:06:33] [Miele] Ignoring unsupported device. Device: "Frigo" with raw type value: 19.
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:75050) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 13)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 14)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 15)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 16)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 17)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 18)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 19)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 20)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 21)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 22)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 23)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 24)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 25)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 26)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 27)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 28)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 29)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 30)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 31)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 32)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 33)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 34)
[25/01/2021 12:16:33] [Miele] Refreshing token...
[25/01/2021 12:16:34] [Miele] TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'ClientRequest'
    |     property 'socket' -> object with constructor 'TLSSocket'
    --- property '_httpMessage' closes the circle
    at JSON.stringify (<anonymous>)
    at Token.refreshToken (/usr/local/lib/node_modules/homebridge-mieleathome/src/token.ts:77:63)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 35)
[25/01/2021 12:16:40] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
[25/01/2021 12:17:40] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
[25/01/2021 12:17:40] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 39)
[25/01/2021 12:18:40] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".
[25/01/2021 12:19:40] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:75050) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 42)
[25/01/2021 12:20:40] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
[25/01/2021 12:20:40] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".
[25/01/2021 12:21:40] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".
[25/01/2021 12:21:40] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
(node:75050) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!

I will wipe everything and start again from scratch, because for now, it seems to derail...

MichelRabozee commented 3 years ago

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:

[25/01/2021 13:24:26] [HB Supervisor] Homebridge Storage Path: /Users/mrabozee/.homebridge-three
[25/01/2021 13:24:26] [HB Supervisor] Homebridge Config Path: /Users/mrabozee/.homebridge-three/config.json
[25/01/2021 13:24:26] [HB Supervisor] Logging to /Users/mrabozee/.homebridge-three/homebridge.log
[25/01/2021 13:24:26] [HB Supervisor] OS: Darwin 18.7.0 x64
[25/01/2021 13:24:26] [HB Supervisor] Node.js v14.15.0 /usr/local/bin/node
[25/01/2021 13:24:26] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[25/01/2021 13:24:26] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[25/01/2021 13:24:26] [HB Supervisor] Starting Homebridge with extra flags: -I
[25/01/2021 13:24:26] [HB Supervisor] Started Homebridge v1.2.5 with PID: 64423
[25/01/2021 13:24:26] Loaded config.json with 0 accessories and 2 platforms.
[25/01/2021 13:24:26] ---
[25/01/2021 13:24:27] Loaded plugin: homebridge-camera-ffmpeg@3.0.3
[25/01/2021 13:24:27] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:27] Loaded plugin: homebridge-config-ui-x@4.36.0
[25/01/2021 13:24:27] Registering platform 'homebridge-config-ui-x.config'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:27] Loaded plugin: homebridge-contactnotifier@0.0.6
[25/01/2021 13:24:27] Registering accessory 'homebridge-contactnotifier.ContactNotifier'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:27] Loaded plugin: homebridge-daikin-local@2021.4.1
[25/01/2021 13:24:27] Registering accessory 'homebridge-daikin-local.Daikin-Local'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:27] Loaded plugin: homebridge-http-switch@0.5.34
[25/01/2021 13:24:27] Registering accessory 'homebridge-http-switch.HTTP-SWITCH'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:27] Loaded plugin: homebridge-mieleathome@2.0.0
[25/01/2021 13:24:27] Registering platform 'homebridge-mieleathome.Miele@home'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:27] Loaded plugin: homebridge-outsidetemperature@0.0.2
[25/01/2021 13:24:27] Registering accessory 'homebridge-outsidetemperature.OutsideTemperature'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:28] [Homebridge UI] Homebridge Config UI X v4.36.0 is listening on :: port 8082
[25/01/2021 13:24:27] Loaded plugin: homebridge-platform-wemo@2.9.1
[25/01/2021 13:24:27] Registering platform 'homebridge-platform-wemo.BelkinWeMo'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:27] Loaded plugin: homebridge-roomba2@1.2.0
[25/01/2021 13:24:27] Registering accessory 'homebridge-roomba2.Roomba2'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:27] Loaded plugin: homebridge-script2@0.3.0
[25/01/2021 13:24:27] Registering accessory 'homebridge-script2.Script2'
[25/01/2021 13:24:27] ---
[25/01/2021 13:24:28] Loaded plugin: homebridge-sonytvremote@10.1.3
[25/01/2021 13:24:28] Registering accessory 'homebridge-sonytvremote.SonyTV'
[25/01/2021 13:24:28] ---
[25/01/2021 13:24:28] Loaded plugin: homebridge-videodoorbell@0.2.9
[25/01/2021 13:24:28] Registering platform 'homebridge-videodoorbell.Video-doorbell'
[25/01/2021 13:24:28] ---
[25/01/2021 13:24:28] Loaded plugin: homebridge-watervolume@0.0.2
[25/01/2021 13:24:28] Registering accessory 'homebridge-watervolume.WaterVolume'
[25/01/2021 13:24:28] ---
[25/01/2021 13:24:28] Loading 2 platforms...
[25/01/2021 13:24:28] [Corniche Homebridge-Three Config] Initializing config platform...
[25/01/2021 13:24:28] [Corniche Homebridge-Three Config] Running in Service Mode
[25/01/2021 13:24:28] [Miele] Initializing Miele@home platform...
Setup Payload:
X-HM://0024AOUT1H5JD
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

    ┌────────────┐     
    │ 499-82-453 │     
    └────────────┘     

[25/01/2021 13:24:28] Homebridge v1.2.5 is running on port 51809.
[25/01/2021 13:24:28] [Miele] No *valid* token present in persistent storage. Creating new from configuration.
[25/01/2021 13:24:28] [Miele] Discovered device: id: mac-001D63FFFE0203B2, name: Four, model: 
[25/01/2021 13:24:28] [Miele] Ignoring unsupported device. Device: "Four" with raw type value: 12.
[25/01/2021 13:24:28] [Miele] Discovered device: id: 000127334912, name: Taque, model: 
[25/01/2021 13:24:28] [Miele] Ignoring unsupported device. Device: "Taque" with raw type value: 14.
[25/01/2021 13:24:28] [Miele] Discovered device: id: mac-001D63FFFE0203B4, name: Lave-vaisselle, model: 
[25/01/2021 13:24:28] [Miele] Registering new accessory: Lave-vaisselle
[25/01/2021 13:24:28] [Miele] Discovered device: id: 000116035470, name: Lave-linge, model: 
[25/01/2021 13:24:28] [Miele] Registering new accessory: Lave-linge
[25/01/2021 13:24:28] [Miele] Discovered device: id: mac-00124B0005AB4D8B, name: Frigo, model: 
[25/01/2021 13:24:28] [Miele] Ignoring unsupported device. Device: "Frigo" with raw type value: 19.
(node:64423) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:64423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:64423) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:64423) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:64423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:64423) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:64423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

I do not know where to investigate :-(

MichelRabozee commented 3 years ago

I started node with --trace-warnings, here are the new logs:

[25/01/2021 13:34:09] [HB Supervisor] Homebridge Storage Path: /Users/mrabozee/.homebridge-three
[25/01/2021 13:34:09] [HB Supervisor] Homebridge Config Path: /Users/mrabozee/.homebridge-three/config.json
[25/01/2021 13:34:09] [HB Supervisor] Logging to /Users/mrabozee/.homebridge-three/homebridge.log
[25/01/2021 13:34:09] [HB Supervisor] OS: Darwin 18.7.0 x64
[25/01/2021 13:34:09] [HB Supervisor] Node.js v14.15.0 /usr/local/bin/node
[25/01/2021 13:34:09] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[25/01/2021 13:34:09] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[25/01/2021 13:34:09] [HB Supervisor] Starting Homebridge with extra flags: -I
[25/01/2021 13:34:09] [HB Supervisor] Starting Homebridge with custom env: {"NODE_OPTIONS":"--trace-warnings"}
[25/01/2021 13:34:09] [HB Supervisor] Started Homebridge v1.2.5 with PID: 70774
[25/01/2021 13:34:10] Loaded config.json with 0 accessories and 2 platforms.
[25/01/2021 13:34:10] ---
[25/01/2021 13:34:10] Loaded plugin: homebridge-camera-ffmpeg@3.0.3
[25/01/2021 13:34:10] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[25/01/2021 13:34:10] ---
[25/01/2021 13:34:10] Loaded plugin: homebridge-config-ui-x@4.36.0
[25/01/2021 13:34:10] Registering platform 'homebridge-config-ui-x.config'
[25/01/2021 13:34:10] ---
[25/01/2021 13:34:10] Loaded plugin: homebridge-contactnotifier@0.0.6
[25/01/2021 13:34:10] Registering accessory 'homebridge-contactnotifier.ContactNotifier'
[25/01/2021 13:34:10] ---
[25/01/2021 13:34:10] Loaded plugin: homebridge-daikin-local@2021.4.1
[25/01/2021 13:34:10] Registering accessory 'homebridge-daikin-local.Daikin-Local'
[25/01/2021 13:34:10] ---
[25/01/2021 13:34:10] Loaded plugin: homebridge-http-switch@0.5.34
[25/01/2021 13:34:10] Registering accessory 'homebridge-http-switch.HTTP-SWITCH'
[25/01/2021 13:34:10] ---
[25/01/2021 13:34:11] [Homebridge UI] Homebridge Config UI X v4.36.0 is listening on :: port 8082
[25/01/2021 13:34:11] Loaded plugin: homebridge-mieleathome@2.0.0
[25/01/2021 13:34:11] Registering platform 'homebridge-mieleathome.Miele@home'
[25/01/2021 13:34:11] ---
[25/01/2021 13:34:11] Loaded plugin: homebridge-outsidetemperature@0.0.2
[25/01/2021 13:34:11] Registering accessory 'homebridge-outsidetemperature.OutsideTemperature'
[25/01/2021 13:34:11] ---
[25/01/2021 13:34:11] Loaded plugin: homebridge-platform-wemo@2.9.1
[25/01/2021 13:34:11] Registering platform 'homebridge-platform-wemo.BelkinWeMo'
[25/01/2021 13:34:11] ---
[25/01/2021 13:34:11] Loaded plugin: homebridge-roomba2@1.2.0
[25/01/2021 13:34:11] Registering accessory 'homebridge-roomba2.Roomba2'
[25/01/2021 13:34:11] ---
[25/01/2021 13:34:11] Loaded plugin: homebridge-script2@0.3.0
[25/01/2021 13:34:11] Registering accessory 'homebridge-script2.Script2'
[25/01/2021 13:34:11] ---
[25/01/2021 13:34:11] Loaded plugin: homebridge-sonytvremote@10.1.3
[25/01/2021 13:34:11] Registering accessory 'homebridge-sonytvremote.SonyTV'
[25/01/2021 13:34:11] ---
[25/01/2021 13:34:12] Loaded plugin: homebridge-videodoorbell@0.2.9
[25/01/2021 13:34:12] Registering platform 'homebridge-videodoorbell.Video-doorbell'
[25/01/2021 13:34:12] ---
[25/01/2021 13:34:12] Loaded plugin: homebridge-watervolume@0.0.2
[25/01/2021 13:34:12] Registering accessory 'homebridge-watervolume.WaterVolume'
[25/01/2021 13:34:12] ---
[25/01/2021 13:34:12] Loading 2 platforms...
[25/01/2021 13:34:12] [Corniche Homebridge-Three Config] Initializing config platform...
[25/01/2021 13:34:12] [Corniche Homebridge-Three Config] Running in Service Mode
[25/01/2021 13:34:12] [Miele] Initializing Miele@home platform...
[25/01/2021 13:34:12] [Miele] Loading accessory data from cache: Lave-vaisselle
[25/01/2021 13:34:12] [Miele] Loading accessory data from cache: Lave-linge
Setup Payload:
X-HM://0024AOUT1H5JD
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

    ┌────────────┐     
    │ 499-82-453 │     
    └────────────┘     

[25/01/2021 13:34:12] Homebridge v1.2.5 is running on port 51809.
[25/01/2021 13:34:12] [Miele] Discovered device: id: mac-001D63FFFE0203B2, name: Four, model: 
[25/01/2021 13:34:12] [Miele] Ignoring unsupported device. Device: "Four" with raw type value: 12.
[25/01/2021 13:34:12] [Miele] Discovered device: id: 000127334912, name: Taque, model: 
[25/01/2021 13:34:12] [Miele] Ignoring unsupported device. Device: "Taque" with raw type value: 14.
[25/01/2021 13:34:12] [Miele] Discovered device: id: mac-001D63FFFE0203B4, name: Lave-vaisselle, model: 
[25/01/2021 13:34:12] [Miele] Re-creating existing accessory with data from cache: Lave-vaisselle
[25/01/2021 13:34:12] [Miele] Discovered device: id: 000116035470, name: Lave-linge, model: 
[25/01/2021 13:34:12] [Miele] Re-creating existing accessory with data from cache: Lave-linge
[25/01/2021 13:34:12] [Miele] Discovered device: id: mac-00124B0005AB4D8B, name: Frigo, model: 
[25/01/2021 13:34:12] [Miele] Ignoring unsupported device. Device: "Frigo" with raw type value: 19.
(node:70774) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
    at emitUnhandledRejectionWarning (internal/process/promises.js:168:15)
    at processPromiseRejections (internal/process/promises.js:247:11)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)
(node:70774) Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:70774) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    at emitDeprecationWarning (internal/process/promises.js:180:11)
    at processPromiseRejections (internal/process/promises.js:249:13)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)

The first error comes roughly 2 minutes after the appliances discovery.

MichelRabozee commented 3 years ago

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 ? Because the version of node-persist inside the homebridge node_modules is a very old one (0.0.11) and it seems the Miele@home plugin requires 3.1.1 (although the last release of node-persist is 3.1.0)...

Do I risk to install a new node-persist of homebridge itself ?

MichelRabozee commented 3 years ago

hmmm.... not a good idea to install node-persist 3.1.0 in homebridge itself :-( It does not start, giving those errors:

TypeError: accessoryStorage.initSync is not a function
    at new Server (/usr/local/lib/node_modules/homebridge/src/server.ts:116:22)
    at cli (/usr/local/lib/node_modules/homebridge/src/cli.ts:54:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47
MichelRabozee commented 3 years ago

I do not know if this is linked, after a while, the token wants to refresh, but if fails :-(

[25/01/2021 14:46:35] [Miele] Refreshing token...
[25/01/2021 14:46:35] [Miele] TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'ClientRequest'
    |     property 'socket' -> object with constructor 'TLSSocket'
    --- property '_httpMessage' closes the circle
    at JSON.stringify (<anonymous>)
    at Token.refreshToken (/usr/local/lib/node_modules/homebridge-mieleathome/src/token.ts:77:63)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:11971) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
    at emitUnhandledRejectionWarning (internal/process/promises.js:168:15)
    at processPromiseRejections (internal/process/promises.js:247:11)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)
(node:11971) Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
[25/01/2021 14:46:36] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".
[25/01/2021 14:47:36] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/000116035470/state failed with status 401: "Unauthorized".
[25/01/2021 14:47:36] [Miele] Miele API request https://api.mcs3.miele.com/v1/devices/mac-001D63FFFE0203B4/state failed with status 401: "Unauthorized".
QuickSander commented 3 years ago

[25/01/2021 14:46:35] [Miele] TypeError: Converting circular structure to JSON I have to investigate this, but I do not think it is related.

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.

MichelRabozee commented 3 years ago

I am running Homebridge 1.2.5 on a MacMini running NodeJS 14.15.0 (NPM 6.14.11). Homebridge requires node-persist 0.0.11 (as the package.json indicates; certainly no version 3.x because homebridge still uses Sync functions, removed from 3.x node-persist). It is not a problem per se (as each node application may contain its own version of a library). My point is: it seems that the new Miele plugin seems not to recognise the format of the AccessoryInfo.0E4EB8423210.json and I do not know if it is a format change between versions of node-persist (I guess homebridge creates AccessoryInfo.0E4EB8423210.json with version 0.0.11 and Miele plugin tries to read it with version 3.1.0)

Which are the versions you use ?

QuickSander commented 3 years ago

Miele@home plugin requires 3.1.1 (although the last release of node-persist is 3.1.0)...

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. My homebridge: v1.1.7 (latest). Nodejs: 11.5.0

I seem to have the same issue now after re-installing the plugin. I will try to look for a solution.

MichelRabozee commented 3 years ago

If it can help, here is the contents of the AccessoryInfo.0E4EB8423210.json:

{"displayName":"Corniche Homebridge-Three 05F5","category":2,"pincode":"499-82-453","signSk":"e2b32544decc6048e081088d29c8ce1e2796f6da91242399dcfc1735c0414eebafe868707e58171e879ebbef1d4808b4f82cc03f135e68c5aea99564163f7475","signPk":"afe868707e58171e879ebbef1d4808b4f82cc03f135e68c5aea99564163f7475","pairedClients":{"BDFF6BC4-1DE8-4520-BF23-CAAA54B1E995":"6ac24d8fe89986ca348feb6327b13d3d77d97cfcce3b37127accb6406cc420db","1B2071E2-3931-4DEF-83D4-670900FCF462":"17835815fb861a86d247c49b09897ecdc7291ec52d03a1060925c12c6df3054c"},"pairedClientsPermission":{"BDFF6BC4-1DE8-4520-BF23-CAAA54B1E995":1,"1B2071E2-3931-4DEF-83D4-670900FCF462":0},"configVersion":5,"configHash":"bf6d02b2b515f8fe9f0615f7dc2913669df7adef","setupID":"H5JD"}
MichelRabozee commented 3 years ago

I seem to have the same issue now after re-installing the plugin. I will try to look for a solution.

Sorry to have brought you this :-(

QuickSander commented 3 years ago

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.

MichelRabozee commented 3 years ago

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... Cool it works with 3.0.5.

MichelRabozee commented 3 years ago

:-( 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

(node:90688) UnhandledPromiseRejectionWarning: Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:315:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
    at emitUnhandledRejectionWarning (internal/process/promises.js:168:15)
    at processPromiseRejections (internal/process/promises.js:247:11)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)
(node:90688) Error: [node-persist][readFile] /Users/mrabozee/.homebridge-three/persist/AccessoryInfo.0E4EB8423210.json does not look like a valid storage file!
    at /usr/local/lib/node_modules/homebridge-mieleathome/node_modules/node-persist/src/local-storage.js:315:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
(node:90688) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    at emitDeprecationWarning (internal/process/promises.js:180:11)
    at processPromiseRejections (internal/process/promises.js:249:13)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)

hence 3.0.5 does not work for me :-(

I am a bit lost, will wait for your feedback !

QuickSander commented 3 years ago

3.0.5 was a mistake from me. Therefore I deleted the message, but you were too quick to notice it. The unauthorised may come from a multitude of factors. The token in your config is the initial token which will be replaced by one which is stored using node-persist. It might be related to the node-persist issues. I will publish a downgraded version using node-persist 0.0.12 soon.

node-persist issues see also.

MichelRabozee commented 3 years ago

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 👍🏻

MichelRabozee commented 3 years ago

And... 2.0.1 is a winner (I waited 3 minutes, and no error, and token is recognised !!) !!! Thank you !

QuickSander commented 3 years ago

Thanks for your patience. I will close this issue. Learned something new again today.

na-ma-ste commented 5 months ago

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".

MichelRabozee commented 5 months ago

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.

[14/04/2024, 02:31:44] [Miele] Réfrigérateur: Self initiated reconnect with Miele event server successful.
[14/04/2024, 02:31:44] [Miele] Lave-vaisselle: Self initiated reconnect with Miele event server successful.
[14/04/2024, 02:35:45] [Miele] Lave-vaisselle: Error received from Miele event server. Status: 401. Message: 'Unauthorized'
[14/04/2024, 02:35:45] [Miele] Lave-vaisselle: Will attempt to reconnect to the Miele event server after 60[s].
[14/04/2024, 02:35:47] [Miele] Lave-linge: Error received from Miele event server. Status: 401. Message: 'Unauthorized'
[14/04/2024, 02:35:47] [Miele] Lave-linge: Will attempt to reconnect to the Miele event server after 60[s].
[14/04/2024, 02:36:46] [Miele] Lave-vaisselle: Connection with Miele event server succesfully recovered from error.
[14/04/2024, 02:36:47] [Miele] Lave-linge: Connection with Miele event server succesfully recovered from error
na-ma-ste commented 5 months ago

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?

MichelRabozee commented 5 months ago

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.

na-ma-ste commented 5 months ago

i will give it a try. Thanks

na-ma-ste commented 5 months ago

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.

MichelRabozee commented 5 months ago

Excellent !