Skip to content
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 custom climate names #32

Closed
jimboca opened this issue Jan 9, 2019 · 1 comment
Closed

Issue with custom climate names #32

jimboca opened this issue Jan 9, 2019 · 1 comment
Assignees
Milestone

Comments

@jimboca
Copy link
Collaborator

jimboca commented Jan 9, 2019

The below shows that smart2 is not in the list, so that messes up the ordering. Need to order them by the 'smart>n>' names.

@jimboca  I need to correct my previous statement that custom climates names are fixed for me. To test I manually set a custom climate from the admin console and the correct name came up and I thought it was fixed, I didn't notice that the settings for that name were wrong and next time a custom climate was set from the regular schedule I noticed the name was wrong again. I'm running cloud 2.0.26 and have pasted the discover climates line from the log below. Note that there is no smart2 defined. I'm not sure why, maybe it's a custom climate that I deleted in the past. I tried adding a new test custom and it added as smart5. The custom names and smart(n) names are correct below, however any custom climate setting >2 displays with an offset of +1 in the ISY, i.e., I'm running office PM now and the ISY shows as test.

discover: climates={'311054229478': [{'name': 'Away', 'ref': 'away'}, {'name': 'Home', 'ref': 'home'}, {'name': 'Sleep', 'ref': 'sleep'}, {'name': 'Office AM', 'ref': 'smart1'}, {'name': 'Karen dress', 'ref': 'smart3'}, {'name': 'Office PM', 'ref': 'smart4'}, {'name': 'test', 'ref': 'smart5'}]

Take a look when you get a chance, it's not critical and not sure if anyone else is seeing the problem, but wanted to give you more details.

@jimboca jimboca self-assigned this Jan 10, 2019
@jimboca jimboca added this to the next_release milestone Jan 10, 2019
Repository owner deleted a comment from jimbo Jan 10, 2019
jimboca added a commit that referenced this issue Jan 10, 2019
jimboca added a commit that referenced this issue Jan 10, 2019
@jimboca
Copy link
Collaborator Author

jimboca commented Feb 6, 2019

All fixed

@jimboca jimboca closed this as completed Feb 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant