-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Warning: State "tado.0.xxxxxx.Rooms.x.overlayType" has no existing object, this might lead to an error in future versions #184
Labels
bug
Something isn't working
Comments
HGlab01
added a commit
that referenced
this issue
Mar 20, 2021
Merged
fixed in v0.2.6 with 545fc23 |
DutchmanNL
pushed a commit
that referenced
this issue
Mar 20, 2021
apply formatting for main.js add quickActionsEnabled (#164) support HOT_WATER devices (#138) support AIR_CONDITIONING devices (#146) Implement pool handling for setZoneOverlay fix issue: state has no existing object (#184) add cleaning function for existing timer 'polling' state_attr.js: attribute 'support' was defined twice
DutchmanNL
pushed a commit
that referenced
this issue
Mar 20, 2021
apply formatting for main.js add quickActionsEnabled (#164) support HOT_WATER devices (#138) support AIR_CONDITIONING devices (#146) Implement pool handling for setZoneOverlay fix issue: state has no existing object (#184) add cleaning function for existing timer 'polling' state_attr.js: attribute 'support' was defined twice
DutchmanNL
pushed a commit
that referenced
this issue
Mar 20, 2021
apply formatting for main.js add quickActionsEnabled (#164) support HOT_WATER devices (#138) support AIR_CONDITIONING devices (#146) Implement pool handling for setZoneOverlay fix issue: state has no existing object (#184) add cleaning function for existing timer 'polling' state_attr.js: attribute 'support' was defined twice
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Warning: State "tado.0.xxxxxx.Rooms.x.overlayType" has no existing object, this might lead to an error in future versions
as long as this state was in JSON never != NULL
Therefore especially an issue after new installation since js-controller v3.2.16
To Reproduce
to be fixed at
ioBroker.tado/main.js
Line 1543 in a71a975
The text was updated successfully, but these errors were encountered: