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

Firmware sensor not accurate. #133625

Open
rwelsh09 opened this issue Dec 20, 2024 · 4 comments
Open

Firmware sensor not accurate. #133625

rwelsh09 opened this issue Dec 20, 2024 · 4 comments

Comments

@rwelsh09
Copy link

rwelsh09 commented Dec 20, 2024

The problem

update.[name]_firmware is not correct.

Example:
These devices are identical, but the floodlight I just updated today.
Screenshot_20241219_202210_Home Assistant
Screenshot_20241219_202251_Home Assistant
The latest version (2.2.0) for these devices was released November 28, 2023

Also found this issue mentioned in the forum.

What version of Home Assistant Core has the issue?

core-2024.12.4

What was the last working version of Home Assistant Core?

Unknown, I always assumed it was correct until today.

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-Wave

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


zwave_js documentation
zwave_js source
(message by IssueLinks)

@kpine
Copy link
Contributor

kpine commented Dec 20, 2024

Attach the device diagnostic file (attach file to comment, not copy and paste) for both devices. We can't possibly know anything about your devices from the screenshots. You can download the diagnostic file by going to Settings -> Devices & services -> Z-Wave "Devices" -> The Device -> Device info -> ... -> Download diagnostics.

@rwelsh09
Copy link
Author

rwelsh09 commented Dec 20, 2024

Floodlight Diagnostics.json
Kitchen Lights Diagnostics.json

@kpine
Copy link
Contributor

kpine commented Dec 20, 2024

The reason why the newer version is not reported is because Homeseer hasn't contributed the necessary firmware update information to the Z-Wave JS firmware update service. The update sensors rely on this online service to get update information. Update sensors are created for every device that has the capability to update firmware regardless of whether they are supported by the service or not. Until Homeseer provides those updates, your sensors will never change. Maybe you can ask their support to consider it, I believe they already have a working relationship with Z-Wave JS.

I agree it's confusing to list a "latest version" if a device is unsupported, but HA doesn't have the ability distinguish between "unsupported" and "is latest". Support for this has been requested at zwave-js/firmware-updates#82, so there's really nothing that can be done until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants