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

Z-Wave parameters drop down menu is not working 0.67.0b0 #13740

Closed
MuppetOwl opened this issue Apr 7, 2018 · 14 comments · Fixed by #13887
Closed

Z-Wave parameters drop down menu is not working 0.67.0b0 #13740

MuppetOwl opened this issue Apr 7, 2018 · 14 comments · Fixed by #13887

Comments

@MuppetOwl
Copy link

MuppetOwl commented Apr 7, 2018

Home Assistant release with the issue:
0.67.0b0

Last working Home Assistant release (if known):
0.66.1

Operating environment (Hass.io/Docker/Windows/etc.):
hass.io

Component/platform:
zwave

Description of problem:
Not possible to set Node group associations or paramters etc. Nothing happens when clicking on the drop down menu to set node config options.

@MuppetOwl MuppetOwl changed the title Z-Wave parameters drop down menu does not work 0.67 Z-Wave parameters drop down menu does not work 0.67.0b0 Apr 11, 2018
@MuppetOwl MuppetOwl changed the title Z-Wave parameters drop down menu does not work 0.67.0b0 Z-Wave parameters drop down menu is not working 0.67.0b0 Apr 11, 2018
@MuppetOwl
Copy link
Author

This is still an issue in 0.67.0b1

@turbokongen
Copy link
Contributor

Is your device in the OZW config?

@MuppetOwl
Copy link
Author

MuppetOwl commented Apr 13, 2018

Yes. And if i go back to version 0.66.1 the drop down menus works again. All of my 24 zwave devices have no config attributes on 0.67.0b1.

I use the latest xml files for openzwave on a share. Works perfect on 0.66.1. Maybe that create some issues on 0.67?

zwave:
config_path: /share/z-wave/open-zwave/config

@turbokongen
Copy link
Contributor

There must have been some changes regarding api's
There are 404 for all of them.
Need to check other changes to figure this out.

@steve28
Copy link

steve28 commented Apr 14, 2018

I see this too. No configuration drop-down menus available in 0.67.

@turbokongen
Copy link
Contributor

turbokongen commented Apr 14, 2018

It's usercodes, values, config parameters and groups. All panel that should have been loaded on demand.

@turbokongen
Copy link
Contributor

#13887

@riemers
Copy link

riemers commented Apr 14, 2018

just adding to the list, no options no groups, no configs for me in 0.67 in the z-wave part, worked fine in the older version.

@bjorntimmer
Copy link

Same here

@callagga
Copy link

callagga commented Apr 18, 2018

As well as the drop downs not working, there are another couple of items I'm noting - would these be covered by this fix?

a) when I try to use services -> set_config_parameter I'm having trouble in the sense that some changes (not all) don't seem to work [but it's hard to tell as this UI issue to check & also the next point]

b) when I try to use services - print_config_parameter I can't locate/see the result in either ozw log or homeassistant log?

c) when I try to use services - print_node:

  • If I pass in a node of "2" I get lots of "exception: Manager.cpp:2499 - 102 - ValueID passed to GetValueFloatPrecision is not a Decimal Value" errors in the OZW logs,
  • If I pass in a value of "2.0" I get this error in the homeassistant log "ERROR (MainThread) [homeassistant.core] Invalid service data for zwave.print_node: expected int for dictionary value @ data['node_id']. Got '2.0'"

PS I'm on v0.67.0. By the way any advice re what I should do noting the version I'm on? e.g. apply mix manually / go to latest HA version (does it include this fix) / other?

@ViperRNMC
Copy link

same here, 0.67.1

@riemers
Copy link

riemers commented Apr 26, 2018

Works fine again here with 0.67.1, had multiple people confirm it on discord.

@ViperRNMC
Copy link

strange, when I go to 0.67.1 I see no node options, going back to 0.66.1 and it works.

@MuppetOwl
Copy link
Author

I can also confirm this bug was fixed with 0.67.1.

Have you tried to force a refresh of the page using alt+F5 or delete temp internet files?

@home-assistant home-assistant locked and limited conversation to collaborators Jul 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants