Issues with TKB Wall switches driver #4841
Comments
This comment was marked as outdated.
This comment was marked as outdated.
|
Please make a driver log, loglevel |
|
Attached is the log file
Best Regards
Gerardo
El lun, 25 jul 2022 a las 11:41, AlCalzone ***@***.***>)
escribió:
… Please make a driver log
<https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/generating-logs?id=driver-logs>,
loglevel debug or silly and *attach* it here as a file (drag & drop).
The logfile should include a re-interview of the device.
—
Reply to this email directly, view it on GitHub
<#4841 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2DQ3YYFYB7GTHULIDNQSUTVVZOOJANCNFSM54RLUXBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
You'll need to do this on the web UI. Github doesn't let you attach stuff to emails. |
Your logfile does not. |
|
Not easy, at least to me,.. device logs din't show anything after re-interview. I had to go to general LOG and filtering by Zwave JS, please see below: (there is not any icon to save the log to file) |
zwave-js-assistant
bot
added
the
stale 💤
|
This issue has not seen any recent activity and was marked as "stale 💤". Feel free to reopen if the issue persists. |
|
Dear Team, |
|
Please provide the logs I requested above. |
AlCalzone
removed
the
stale 💤
|
Hi !
Thanks for your quick action, I thought I sent all LOG files you asked me
for. As newbie with HA I could be wrong, please double check and let me
know which Log you need and I will try it. Nevertheless I guess the fault
is clear, TKB switches (double pad) sense the second (right) pad click
either single or double (on and off) and this sensing function is not
apparently consider on JS driver. There is also a mistake with the model as
HA recognize it but with another model as said in my first message.
Thanks !!
Gerardo
El lun, 25 jul 2022 a las 10:18, Z-Wave JS Bot ***@***.***>)
escribió:
… 👋 Hey @GAguado <https://github.com/GAguado>!
Thanks for opening an issue! It doesn't look like you provided a logfile
though. While not strictly necessary for every issue, having a driver log
<https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/generating-logs?id=driver-logs>
is required to diagnose most issues.
Please consider uploading a logfile that captures your problem.
—
Reply to this email directly, view it on GitHub
<#4841 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2DQ3Y5ICNLZBUQ7BF5ZMKTVVZEVZANCNFSM54RLUXBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
You just posted the last few lines of an interview (not sure which loglevel). I need:
If you're unsure how to get the log, please ask in the HA forums or on Discord - there should be someone familiar enough with HA to help you. |
|
Hi, I send you two logs. |
|
I hope this is the information you need |
|
Thats the same stuff you posted above though. |
|
Follow the instructions in the docs: https://www.home-assistant.io/integrations/zwave_js/#how-to-access-the-z-wave-logs Set the log level to "debug" as requested. Pay special attention to note in the docs:
Which means, keep one browser window open on the log window to capture the logs, and a second browser window to perform the interview. Use the download button in the UI to download the logs as a file. |
|
Hi, at last please find it enclosed, thanks for your patience |
|
Hooray. I'll check it out tomorrow :) |
|
So, it looks like this device is not meant to report the status of all paddles to the controller. It does not support multi channel, so by definition it only appears as a single switch in the Z-Wave network. For actual multichannel support, you seem to need the TZ37 or TZ57 variants. |
|
Hi ! New Association Group But I can not leave empty the field Target Node Endpoint (!) it says 'This field is required' What am I doing wrong? Thanks |
|
|
You're mixing things up: |
|
Hi ! please find the log files, two wall switches: TKB TZ56D and TKB TZ66D (former version of previous with the same functionality) |
|
Okay, so the left switch's status is found under @MartinHjelmare @raman325 Would it be possible to expose Basic CC values in HA? I see devices like this from time to time where part of the functionality is only accessible via Basic CC. Granted, this would have to be rather generic entity without much context. |
|
We create an entity for the Basic CC, it's just disabled by default. If the user goes to the device page for their device and clicks on show disabled entities, they will see it and can enable it from there. |
zwave-js-assistant
bot
added
the
stale 💤
|
This issue has not seen any recent activity and was marked as "stale 💤". Feel free to reopen if the issue persists. |
|
Dear Team, I guessed you were modifying the code but as time goes I reopen this issue, under disabled entities there is not any entity yet either for double tap or holding tap, please check Thanks in advance |
|
I'll need someone with more HA experience to debug this |
AlCalzone
added
investigate 🔎
|
Please upload a device diagnostic file for this device. In HA, navigate to the Device page, click |
|
I have not any problem resending all log files (you have them in previous posts) but entities are quite basic ones, look: |
|
I asked for the HA device diagnostic file, not a log file. EDIT: Sorry, I found one above. Can you send an updated one? Preferably, re-interview the device, then upload the diagnostics. The previous one is out of date. |
|
Hi, please find an updated one: |
|
Based on the dump, the driver is not exposing any value IDs for Basic CC, so HA cannot create any entities. HA only creates entities for values it is told about. @AlCalzone Many devices that report button presses with BasicCC::Set use events instead of values. Is configuring this device to use events not an option? |
|
Who is the question addressed to? I have not much infomation about device internals except the user manual in which they (TKB) describes the use of groups: |
|
If is me saying that I didn't see any event in HA for this popular TKB wall switch related with either right pad click or double right click |
|
Dear Team, any news on this? I have a similar issue with the Fibaro Button FGPB-101, J-Wave JS only triggers one click when this button has double and triple clicks |
|
Hello, |
Hello, can you explain in detail how to set this up? |
|
Sorry for the delay. The linked PR should make it so that the right paddle shows up as Basic Set events in HA. Like I said previously, I don't see a way to distinguish single and double tap though. |
AlCalzone
removed
the
investigate 🔎
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YES, BUT a Home Assistant developer has told me to come here
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there.
Describe the bug
I have found that the wall switch TKB TZ56D is included incorrectly as a TZ36D and with only the left pad functional (load switch). The right pad, and double right pad sensors are not included/discovered and therefore can not be used.
The same happens with the model TZ66D, any right pad or double right-click functionality is included. In this case, the model TZ66D is properly discovered.
This limits seriously the use of these popular wall switches.
Only entities discovered in both cases (after several trials):
I'm using the latest version 0.1.64
These devices are properly configured with other Z-Wave controllers
Device information
Manufacturer: TKB
Model name: TZ56D / TZ66D
Firmware 2.5
0x010c00040008032503ffcc0000e9 [Node 008]
How are you using
node-zwave-js?zwavejs2mqttDocker image (latest)zwavejs2mqttDocker image (dev)zwavejs2mqttDocker manually built (please specify branches)ioBroker.zwave2adapter (please specify version)HomeAssistant zwave_jsintegration (please specify version)pkgnode-red-contrib-zwave-js(please specify version, double click node to find out)Which branches or versions?
Home Assistant 2022.7.6
Supervisor 2022.07.0
Operating System 8.2
Frontend 20220707.1 - latest
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Don't know, this is a new device
If yes, where did it work?
No response
Attach Driver Logfile
First two messages with left pad use, last two when trying to use the right pad (any message) or double-right:
The text was updated successfully, but these errors were encountered: