{"agentUserId":"1234","requestId":"1a5270c0-7fb5-11ea-8be9-87327eed7e32","payload":{"devices":{"states":{"1s3y":{"online":true}}}}}
{"agentUserId":"1234","requestId":"1a5d1f20-7fb5-11ea-8be9-87327eed7e32","payload":{"devices":{"states":{"1yxw":{"online":true}}}}}
{"agentUserId":"1234","requestId":"1a708010-7fb5-11ea-8be9-87327eed7e32","payload":{"devices":{"states":{"259":{"online":true,"on":true,"brightness":90,"color":{"spectrumRgb":0}}}}}}
{"agentUserId":"1234","requestId":"1a711c50-7fb5-11ea-8be9-87327eed7e32","payload":{"devices":{"states":{"kd5":{"online":true}}}}}
{"agentUserId":"1234","requestId":"1a71b890-7fb5-11ea-8be9-87327eed7e32","payload":{"devices":{"states":{"8k1":{"online":true}}}}}
(node:4844) UnhandledPromiseRejectionWarning: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
(node:4844) 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:4844) [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:4844) UnhandledPromiseRejectionWarning: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
(node:4844) 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:4844) UnhandledPromiseRejectionWarning: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
(node:4844) 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:4844) UnhandledPromiseRejectionWarning: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
(node:4844) 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:4844) UnhandledPromiseRejectionWarning: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
(node:4844) 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)
I tried to deploy smart-home-nodejs with demo user. Sync is no problem and agentUserId is 1234.
But I got 404 error to send reportState. What have i done wrong?