-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
[bug] Fibaro FGT-001 Thermostat no setpoint in HA #793
Comments
@ldymek Could you attach zwavejs logs please? |
hello, please find logs below |
@AlCalzone I think this could be something related to the other bug about root endpoints? |
I see it here ^ |
@ldymek could you explain what you mean with
Also are you using zwavejs integration or MQTT discovery? Have you tried to check the MQTT traffic using tools like MQTT explorer? |
I can't set temperature via Home Assistant, setpoint is not there - nor in hidden/disabled entities. HA see that this is Thermostat, but I can't control it, I can only see measured temperature. Please see screenshot attached. I tried MQTT and zwavejs integration, same story. But as I said "full" zwavejs addon from supervisor does not have this problem, but have no control panel for the devices. I could try MQTT explorer, never done that, have to google it. |
But at least could you change the setpoint from the zwavejs2mqtt ui? If so there must also be a topic for it |
I can set it from zwavejs2mqtt ui |
Ok so there must also be a value in mqtt, I think that you problem may be with zwavejs integration, that is not handled by me |
As I wrote earlier, Setpoint is also not visible in MQTT. Firstly I used MQTT integration and saw missing Setpoint, so I moved to websocket and got the same issue. I started with beta6, updated to beta7 today without luck. Who should be addressed then with this issue? |
Try to update to 2.1.0, I think that's the zwavejs server version BTW |
How to update only zwavejs server in zwavejs2mqtt docker image? Can you share guide? |
You should just updatre zwavejs2mqtt, the server comes with it always upated |
well I updated it today to latest version from docker, and have 1.0.0-beta7 |
Please check that you are pulling the correct image. The latest is app version 2.1.0 and zwavejs server 1.1.0 |
You're correct, I had to delete existing image and pull again. Now I have: App Version but the problem is still the same. I re-interviewed all nodes, result is the same on HASS, still no setpoints from FGT001 thermostats. I attached updated logfile |
I see setpoint updates in logs, I'm quite sure the problem is with zwavejs integration |
I can confirm that via MQTT setpoints are avaible now. |
Ok so closing this as the problem is not on my side |
Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report
Version
Build/Run method
zwavejs2mqtt version: 1.0.0-beta.7
zwavejs version: 6.4.0
Describe the bug
Fibaro FGT001 Thermostats are discovered correctly by zwavejs2mqtt, including setpoint of temperature. Unfortunately setpoint is not visible in Home Assistant nor via MQTT and websocket.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
SetPoint should appear. On HASS zwavejs direct plugin FGT001 is working as expected
Additional context
zwavejs2mqtt debug info:
The text was updated successfully, but these errors were encountered: