-
Notifications
You must be signed in to change notification settings - Fork 5
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
Issue with js-controller 5.0.12 - setDeviceInfo - Error: undefined is not a valid state value #151
Comments
Node.js 5.0.12 would be ruther old :-) - I assume you refer to js-controller 5.0.12 Please add all other related versions adapter The latest version available is 2.2.6 provided by stable and lates repository |
For sure, js-controller - not node-js - thanks for the feedback. |
Thanks for the info. I'll investigate as soon as I have time. Might last some time (1 Week or so) as my queue is very long currently. |
Published v2.2.8 on npm. Error handling is now acitve in the function referecend in the message above. Cayn you please test v2.2.8. Thank you. |
@forelleblau: thanks for the fast update - with the 2.2.8 version it works again. Just one additional question, whats the meaning of |
Seems to be the same error, but handeld. I‘ll Check this once more. |
@schmarra. I checked the code now. The shortcut would be to check the state, before setting it. But I'c be interested in why there is an 'undefined' value. Would you mind to provide me an debug-log (as .txt) of an entire adapter-start (+/- first 20 seconds or until the 'warn'- message). Thank you. |
Sorry for the late reply. Isn´t really much, but here you go: |
Hello schmarra. Thanks for the log. Unfortunately this is not a debug log. To get a debug - log please go to the 'Instances' - Tab and set the solarlog's log - level to 'debug'. Then you'll get much more.... (and me too). |
Ok, thanks for explanation. Here it is:
|
Describe the bug
Since the update to js-controller 5.0.12 the adapter isn´t working anymore, independent which version of the adapter is used.
Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5439:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5400:21) at /opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2037:16 at new Promise (<anonymous>) at AdapterClass.setStateAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2036:16) at setDeviceInfo (/opt/iobroker/node_modules/iobroker.solarlog/main.js:2155:19) at test (/opt/iobroker/node_modules/iobroker.solarlog/main.js:291:13) at async Timeout.<anonymous> (/opt/iobroker/node_modules/iobroker.solarlog/main.js:231:39)
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().
Can you check if there is an upgrade needed?
The text was updated successfully, but these errors were encountered: