Comments (12)
@Fishwaldo do you mind taking a look at this ?
I believe this is an issue in the daemon as I've spotted the same behaviour multiple times.
Looks like Units is set to Fahrenheit sometimes while it should be Celcius...
See below for an example (this is on my own mesh)
from homeassistant-zwave_mqtt.
@Fishwaldo and @marcelveldt I believe I may know the cause now. I left my setup running for a while and just noticed that the set point temperature is displaying correctly now. When it changed to the correct value is when the current temperature change from 70F to 71F.
Looking at the code the units parameter is only set when the function "update_current_temp" runs. As this function is run by the init and I have had a current temperature displayed then device_unit must have been None on the first pass.
from homeassistant-zwave_mqtt.
I think this should be fixed. Some testing would be great!
Note - Some of the attributes (such as Units, ValueSet, ValuePolled, ChangeVerified) can change any time, so you should always check them when getting a ValueChanged event.
from homeassistant-zwave_mqtt.
Any specific way to test? Or just install this as usual.
from homeassistant-zwave_mqtt.
I have the same thermostat and am running:
- Home Assistant 0.109.6
- Z-Wave over MQTT (Pre-release) 0.0.15
- ozwdaemon 0.1.97
The issue still exists. My set point is 70F and it displays 158F in home assistant.
from homeassistant-zwave_mqtt.
@jdm12989 did you pull the latest version of the OZW Daemon in docker ?
from homeassistant-zwave_mqtt.
@jdm12989 did you pull the latest version of the OZW Daemon in docker ?
I did it through Portainer using the latest tag so I'm trusting it actually did. From the logs:
[20200514 14:24:51.818 UTC] [default] [info]: Staring "ozwdaemon" Version: "0.1.97"
[20200514 14:24:51.818 UTC] [default] [info]: OpenZWave Version: "1.6.1123"
[20200514 14:24:51.818 UTC] [default] [info]: QT-OpenZWave Version: "1.0.0"
[20200514 14:24:51.818 UTC] [default] [info]: QT Version: 5.12.5
from homeassistant-zwave_mqtt.
That’s the latest. I’d need to see the logs from the docker container when it’s receiving those setpoint messages
from homeassistant-zwave_mqtt.
That’s the latest. I’d need to see the logs from the docker container when it’s receiving those setpoint messages
@Fishwaldo It was initially set to 70F, I then changed it to 65F via the thermostat and then changed it again to 75F via Home Assistant.
[20200514 14:25:05.541 UTC] [ozw.library] [debug]: Detail - Node: 11 Queuing (Query) ThermostatSetpointCmd_Get (Node=11): 0x01, 0x0a, 0x00, 0x13, 0x0b, 0x03, 0x43, 0x02, 0x01, 0x25, 0x35, 0xbe
[20200514 14:25:05.541 UTC] [ozw.library] [debug]: Detail - Node: 11 Queuing (Query) ThermostatSetpointCmd_Get (Node=11): 0x01, 0x0a, 0x00, 0x13, 0x0b, 0x03, 0x43, 0x02, 0x07, 0x25, 0x36, 0xbb
[20200514 14:25:52.258 UTC] [ozw.library] [info]: Info - Node: 11 Sending (Query) message (Callback ID=0x35, Expected Reply=0x04) - ThermostatSetpointCmd_Get (Node=11): 0x01, 0x0a, 0x00, 0x13, 0x0b, 0x03, 0x43, 0x02, 0x01, 0x25, 0x35, 0xbe
[20200514 14:25:53.705 UTC] [ozw.library] [info]: Info - Node: 11 Received thermostat setpoint report: Setpoint Heating 1 = 70.0F
[20200514 14:25:53.707 UTC] [ozw.library] [info]: Info - Node: 11 Sending (Query) message (Callback ID=0x36, Expected Reply=0x04) - ThermostatSetpointCmd_Get (Node=11): 0x01, 0x0a, 0x00, 0x13, 0x0b, 0x03, 0x43, 0x02, 0x07, 0x25, 0x36, 0xbb
[20200514 15:51:37.144 UTC] [ozw.library] [info]: Info - Node: 11 Received thermostat setpoint report: Setpoint Heating 1 = 65.0F
[20200514 15:53:01.210 UTC] [ozw.library] [debug]: Detail - Node: 11 Queuing (Send) ThermostatSetpointCmd_Set (Node=11): 0x01, 0x0f, 0x00, 0x13, 0x0b, 0x08, 0x43, 0x01, 0x01, 0xcc, 0x01, 0x6c, 0x83, 0xf9, 0x25, 0x54, 0x09
[20200514 15:53:01.210 UTC] [ozw.library] [debug]: Detail - Node: 11 Queuing (Send) ThermostatSetpointCmd_Get (Node=11): 0x01, 0x0a, 0x00, 0x13, 0x0b, 0x03, 0x43, 0x02, 0x01, 0x25, 0x55, 0xde
[20200514 15:53:01.211 UTC] [ozw.library] [info]: Info - Node: 11 Sending (Send) message (Callback ID=0x54, Expected Reply=0x13) - ThermostatSetpointCmd_Set (Node=11): 0x01, 0x0f, 0x00, 0x13, 0x0b, 0x08, 0x43, 0x01, 0x01, 0xcc, 0x01, 0x6c, 0x83, 0xf9, 0x25, 0x54, 0x09
[20200514 15:53:02.479 UTC] [ozw.library] [info]: Info - Node: 11 Sending (Send) message (Callback ID=0x55, Expected Reply=0x04) - ThermostatSetpointCmd_Get (Node=11): 0x01, 0x0a, 0x00, 0x13, 0x0b, 0x03, 0x43, 0x02, 0x01, 0x25, 0x55, 0xde
[20200514 15:53:02.536 UTC] [ozw.library] [info]: Info - Node: 11 Received thermostat setpoint report: Setpoint Heating 1 = 40.0F
from homeassistant-zwave_mqtt.
are you filtering the log files? cause there should be a ton more info there.
from homeassistant-zwave_mqtt.
@Fishwaldo ... yup sorry, lets try this again.
This appears to be the full section for changing from 70F to 65F via device:
https://pastebin.com/TEqLNPjN
And this is for changing from 65F to 75F via Home Assistant:
https://pastebin.com/rifphV59
from homeassistant-zwave_mqtt.
Opened an issue in the HA Core repo since it looks like development has moved over there.
from homeassistant-zwave_mqtt.
Related Issues (20)
- Adding a node results in incomplete/wrong Devices and entities until HA is restarted HOT 10
- Thermostat has multiple climate entities HOT 24
- Feature request: Device page HOT 12
- HEIMAN Smart Motion Sensor - no motion sensor added HOT 6
- Cover not implemented for values HOT 10
- Fibaro FGRM-222 roller shutter not added/working correctly HOT 4
- Renaming climate devices HOT 8
- Eurotronic Spirit support (missing Mode) HOT 19
- Switch Entity is Missing HOT 9
- New set of entities with default ids and names HOT 6
- All devices and entities visible but unavailable after installation. HOT 5
- Differences between old component and this component HOT 1
- Home Assistant switch.toggle isn't implemented? HOT 2
- How to proceed with testing now that this component is part of core? HOT 18
- Aeon labs gen 6 dimmer module (ZW099) not working HOT 2
- "No Stop button" ZMNHOD1 Flush Shutter DC av Qubino
- Missing device: Aeotec Door / Window Sensor 6 HOT 3
- Migrate from Custom Component (Pre-Release) to OpenZWave (Beta) HOT 8
- Scenes not firing HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from homeassistant-zwave_mqtt.