-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Set _TZE200_vrfecyku as sensor with fall function #4859
Conversation
Thanks! |
…Koenkk#4859) * Set _TZE200_vrfecyku as sensor with fall function * Update tuya.js * Update tuya.js * Update fromZigbee.js * Update toZigbee.js Co-authored-by: Koen Kanters <[email protected]>
@Koenkk Can you please fix this? I still have errors |
@salopette if it is about the dp errors, please check https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html how to find out what these mean. |
Hello, I have now checked all data points and made a list.
|
@salopette what dp gives the error? ( |
. |
What is the manufacturer name of your device? (provide me the data/database.db entry). For |
data/database.db entry
|
Can you check with the following external converter? https://gist.github.com/Koenkk/16e84ce2166611a0ba24d28490279d64 Could you check if the issue is fixed with the following external converter:
external_converters:
- ext_converter.js
|
Hi, I've done it this way. { 2022-12-22 21:22:13Exception while calling fromZigbee converter: Value '1' is not allowed, expected one of false,true} |
I can fix the issues, but can you provide the debug log of: See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging. |
2022-12-23 20:42:18Received Zigbee message from '0xb4e3f9fffe47d131', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[1],"type":"Buffer"},"datatype":4,"dp":1}],"seq":10264}' from endpoint 1 with groupID 0 |
2022-12-23 20:50:19Received Zigbee message from '0xb4e3f9fffe47d131', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[1],"type":"Buffer"},"datatype":4,"dp":114}],"seq":5632}' from endpoint 1 with groupID 0 2022-12-23 20:51:32Received Zigbee message from '0xb4e3f9fffe47d131', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,1],"type":"Buffer"},"datatype":2,"dp":115}],"seq":6912}' from endpoint 1 with groupID 0 |
Debug 2022-12-23 21:13:13Received Zigbee message from 'Radar-Sendor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":1,"dp":103}],"seq":29952}' from endpoint 1 with groupID 0 |
|
Please check if https://gist.github.com/Koenkk/16e84ce2166611a0ba24d28490279d64 fixes your issues |
It doesn't want to start with the converter. [11:52:56] INFO: Preparing to start... |
Whoops, updated https://gist.github.com/Koenkk/16e84ce2166611a0ba24d28490279d64 |
Now it's started! Error 2022-12-24 13:11:09Exception while calling fromZigbee converter: Value '0' is not allowed, expected one of 1,2} |
if i change radar_scene to another setting, it immediately jumps back to dafault. it is the same with tumble_switch and the tumble_alarm_time too. { |
Can you provide the debug log of this?
This seems to be related to occupancy, we need to figure out what |
I've tried something else, but I haven't seen any errors. device id: 0xb4e3f9fffe47d131 | |
@salopette can you check my 2 questions from #4859 (comment) |
@salopette I've integrated and fixed that now. Can you check without the external converter and with the latest dev in 1 hour from now? Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
Can this be checked in Ext.converter? I really hate driving the dev branch. |
I have a video of how this works. With the new external converter nothing is saved either. zigbee2mqtt-home-assistant-google-chrome-2023-01-09-18-57-19_ejtFiDkA.mp4 |
can you provide the debug log when changing the values? See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging. |
I've fixed the issue with the |
Yes, the switch now saves the position.
I think that was all I could think of at first. |
can you provide the debug log of this?
limited it to 9 (I think sensor doesn't support more)
Did this work before? If yes can you provide the debug log of this
Was this also the case before? |
@Koenkk @korzenek it looks like this change has broken In Zigbee2MQTT I can see the sensors updating, however in Home Assistant they are being marked as Unknown: On the other hand the attribute on the sensor shows as a correct boolean: |
Same issue here trigger:
|
Issue persists with the radar_scene setting |
another point: This sensor publishes one message every 5sec no matter what setting it has. Woudn't this be an issue with several sensors in the same network? |
I own _TZE200_vrfecyku
In current implementation I get lots of
NOT RECOGNIZED DP 117
see: Koenkk/zigbee2mqtt#12733
After this fix, its properly recognised as fall related packets