-
-
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] climate hass discovery #38
Comments
More mqtt state topic:
|
Latest update; everything is working besides current_temperature with the following customDevices.json:
just lacking air temperature:
setting:
from mqtt:
looks like current_temperature_topic isnt populated correctly? |
@roflmao Humm strange, could you try to press 'rediscover' on the ui? I do the check here: https://github.com/zwave-js/zwavejs2mqtt/blob/master/lib/Gateway.js#L1060 If it's not translated it means it's not found in node values but your log says the opposite |
Its not shown in the webgui, but logs says otherwise. Rediscover is still the same:
|
Refresh node:
Still no show in webgui. |
@roflmao But you see |
@robertsLando zwavejs2mqtt webgui shows me none of these, but the logs of zwavejs2mqtt shows them:
|
Success!
https://www.jottacloud.com/s/00664ac03dda12f4120be9de0098cba0abe |
A minor thing is that discovery only created temp sensors for two of the sensors:
Not:
https://www.jottacloud.com/s/0063b256aa529134efb865baedbbf8b89e1 |
@roflmao Could you show me the startup logs? I would like to see how the interview of that node goes |
|
Still only two of the temperature sensors: |
Also nice if
|
I think that could be a device error because AFAIK the property id identifies the meter type (and the units) @AlCalzone |
Probably - I can take a look at the zwave-js logs of the interview (or startup) to know for sure. |
Yes, kVAh is defined in the specs as a possible meter type. Just wanna make sure it is no bug. |
Sorry no. Needs loglevel "debug", so I can see the raw messages. |
@AlCalzone i have set logLevel to debug in zwavejs2mqtt under zwave, how do i set it for zwave-js? |
That's for zwavejs |
Guess it was my grep foo: https://gist.github.com/roflmao/f0e79010b8a30d9aeb25e57f018d9ab1 Node 003 in this case. |
Btw, you can attach logs as logfiles here directly. Makes it easier to open them. |
@AlCalzone i have to copy them over ssh anyways. Gist has download as zip so you can open the file in your $EDITOR |
It does make it harder for me. A bunch more clicks and page loads until I get to the file, after downloading as zip, the file gets opened as a txt file in the Windows editor, instead of VSCode. When attached it just takes a single click 😅 |
Ok so the unsolicited reports from your nodes only use the scales V, W and kWh. It might be that the kVAh report is requested during the initial interview. To confirm that I would need a log where you refresh the node info. |
Btw:
didn't know zwave-js could show the commit 😮 |
Here it is. Dragging and dropping like its 1999 👯 |
Alternative: https://hastebin.com/ Example: https://hastebin.com/ayiwusoreh.apache @AlCalzone This also prevents you from downloading a file 😆 And use Ctrl+F for find |
@roflmao If you are using docker you could also use |
@robertsLando TIL: kubectl cp :) |
But then I cannot use VSCode search regexes and stuff :( |
No kVAh either. Wonder where that came from 🤔 |
@robertsLando where do the |
Some informations are from zwavjs others are from hass configurations, I build them to identify hass entities |
But where does the |
@AlCalzone no worries it's something on my side, I need to check the meters entity names for hass |
Ref: In specific it comes from here: https://github.com/zwave-js/zwavejs2mqtt/blob/eac3095907362da5c9998b0494422d843c5e20a4/lib/Constants.js#L53 I think I could use the meter Maybe |
lookupMeterScale is the way to go. |
@roflmao Could you try now with master? |
@robertsLando did you see my comment on the commit? |
@roflmao Could you try again with latest commit from master please? (entities names could change) |
It breaks climate autodiscovery: https://www.jottacloud.com/s/0064ad2ebd70f114941ad9cf9d60b69bcc1 |
@robertsLando Hmm, i build latest zwave-js from master as well. Could that be the issue? |
Version
Build/Run method
zwavejs2mqtt version: 0.0.0 latest master (how to show?
Describe the bug
No climate object for hassdiscovery discovered by z2m
To Reproduce
Steps to reproduce the behavior:
mqtt settings:
https://www.jottacloud.com/s/0067ee8821ea95340c89bee59db6a360528
device:
https://www.jottacloud.com/s/006d2c1b284d53d4011bb1ac250d4acd9cc
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
mosquitto:
discovery prefix:
mqtt prefix:
The text was updated successfully, but these errors were encountered: