New Device: Immax NEO 07505L

1rfsNet commented 3 years ago

Is it possible to support the Immax NEO 07505L?

https://www.beleuchtung.de/immax-neo-07505l-smart-tastatur-smart-zigbee-3-0-3xaaa-4-5v/

I was able to pair it but it is recognized as TS0601. The little brother is already supported (Immax NEO 07046L): https://zigbee.blakadder.com/Immax_07046L.html

Please let me know if there is anything I can do :)

modelZigbee:TS0601 type:EndDevice nwk:55613 manuf id:4098 manufacturer:_TZE200_n9clpsht power:Battery app version:68 hard version:1 zcl version:3 stack version:0 date code: interviewed:true configured:false endpoint:1 profile:260 input clusters:genBasic (0) genGroups (4) genScenes (5) manuSpecificTuya (61184) output clusters:genOta (25) genTime (10)

Found this, not sure if it helps: https://github.com/zigpy/zha-device-handlers/issues/997

asgothian commented 3 years ago

Please follow this document.

Note that the device you are referencing is a TuYa device, which may or may not handle many (if not all) messages using the 'manuSpecificTuya' Cluster.

Once this device is properly supported by the zigbee-herdsman-converters, it should also work in the iobroker.zigbee adapter.

A.

1rfsNet commented 3 years ago

I have now tried to add the fingerprint (no idea if I did this correctly, but the device was at least displayed as NEO 07046L and the data points were created). Unfortunately it did not work, no input was recognized.

I then tried the instructions for new devices, but unfortunately was also unsuccessful. I could not find the option "zigbee herdsman debug info" in the settings. "manuSpecificTuya" unfortunately has no attributes, is that right?

asgothian commented 3 years ago

I have now tried to add the fingerprint (no idea if I did this correctly, but the device was at least displayed as NEO 07046L and the data points were created). Unfortunately it did not work, no input was recognized.

I then tried the instructions for new devices, but unfortunately was also unsuccessful. I could not find the option "zigbee herdsman debug info" in the settings. "manuSpecificTuya" unfortunately has no attributes, is that right?

The zigbee herdsman debug info setting should be available from the adapter configuration page - where you set port, channel, etc.
The "manuSpecificTuya" has few documented attributes, and the ones which exist are not standardised and documentation is not good enough to easily add them to the developer interface.
what you can try: add the ieee (without the 0x) to the state zigbee.0.info.debugmessages, then activate various buttons and see if you get messages with the keyword "ELEVATED".
In order to see which messages the device is sending from the tuya cluster you might want to look at https://www.zigbee2mqtt.io/how_tos/how_to_support_new_tuya_devices.html

1rfsNet commented 3 years ago

what you can try: add the ieee (without the 0x) to the state zigbee.0.info.debugmessages, then activate various buttons and see if you get messages with the keyword "ELEVATED".

What do you mean with activate various buttons? Just press buttons on the keypad? And where should I get these debugmessages? In the log? Unfortunately it remains empty.

1rfsNet commented 3 years ago

In the meantime, something showed up in the log, but I hadn't actually done anything at that time:

2021-09-27 13:55:42.950 - warn: zigbee.0 (696450) ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"commandSetTimeRequest\",\"data\":{\"payloadSize\":18688},\"linkquality\":117,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":110,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 847127fffe0571fe type 'TS0601'

2021-09-27 13:55:42.950 - warn: zigbee.0 (696450) ELEVATED publishToState: value generated '"{\"type\":\"commandSetTimeRequest\",\"data\":{\"payloadSize\":18688},\"linkquality\":117,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":110,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 847127fffe0571fe for 'Message from Zigbee' 2021-09-27 13:55:42.951 - warn: zigbee.0 (696450) ELEVATED publishToState: value generated '"{\"type\":\"commandSetTimeRequest\",\"data\":{\"payloadSize\":18688},\"linkquality\":117,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":110,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 847127fffe0571fe for 'Message from Zigbee'

asgothian commented 3 years ago

These messages come from the device implementation. It seems that a large amount of unparsed binary data is passed from the remote to the coordinator what i suspect is a response to a command to set the internal timestamp of the system.

Which device did you "clone" for the remote implementation ?

A.

1rfsNet commented 3 years ago

It's this one: https://zigbee.blakadder.com/Immax_07046L.html (also available on the supported device list of this adapter) I edited the config in /opt/iobroker/node_modules/zigbee-herdsman-converters/devices/immax.js and added the fingerprint:

zigbeeModel: ['Keyfob-ZB3.0'], fingerprint: [{modelID: 'TS0601', manufacturerName: '_TZE200_n9clpsht'}], model: '07046L', vendor: 'Immax', description: '4-Touch single click buttons', fromZigbee: [fz.legacy.immax_07046L_arm, fz.command_panic], exposes: [e.action(['disarm', 'arm_stay', 'arm_away', 'panic'])], toZigbee: [],

just tried it again (removed and readded the device): https://pastebin.com/GwfnZNtt But nothing happens if I use any key on the keypad.

asgothian commented 3 years ago

Das Problem ist das der 07046L eine explizite Implementierung seiner Buttons unter fz.legacy.immax_07046L_arm und fz.command_panic nutzt.

Was du versuchen kannst:

fromZigbee um fz.tuya_on_off_action, fz.battery erweitern, testen ob es Nachrichten im Log gibt (Es wird keine neuen States geben, und die bestehenden werden nicht reagieren)
fromZigbee um fz.command_on, fz.command_off, fz.command_step, fz.command_move, fz.command_stop erweitern, testen ob es Nachrichten im Log gibt (auch hier keine neuen States, die bestehenden werden nicht arbeiten.

Wenn da was kommt schauen wir weiter.

A.

1rfsNet commented 3 years ago

Hat leider beides nicht geklappt. Gibts sonst noch ne Möglichkeit?

asgothian commented 3 years ago

Weitere fz Methoden zum Testen:

command_recall (sollte Nachrichten generieren)
tuya_data_point_dump (sollte eine Datei data/tuya.dump.txt erzeugen, wahrscheinlich in /opt/iobroker/iobroker-data/zigbee_0) A.

1rfsNet commented 3 years ago

Weitere fz Methoden zum Testen:

command_recall (sollte Nachrichten generieren)

das hier sind die Nachrichten, die nach dem Pairing angezeigt werden: https://pastebin.com/kS9w3rkp

tuya_data_point_dump (sollte eine Datei data/tuya.dump.txt erzeugen, wahrscheinlich in /opt/iobroker/iobroker-data/zigbee_0)

2021-09-28T22:15:43 0x847127fffe0571fe (tid: 217, s: 0) [thermostat ] => 0 True 2021-09-28T22:15:44 0x847127fffe0571fe (tid: 218, s: 0) [set temp ] => 0 0.0°C 2021-09-28T22:15:44 0x847127fffe0571fe (tid: 219, s: 0) [time sync] => 0 True 2021-09-28T22:15:44 0x847127fffe0571fe (tid: 220, s: 0) [valve pos ] => 0 False 2021-09-28T22:15:44 0x847127fffe0571fe (tid: 221, s: 0) [battery low ] => 0 False 2021-09-28T22:15:44 0x847127fffe0571fe (tid: 222, s: 0) [away mode ] => 0 False 2021-09-28T22:15:44 0x847127fffe0571fe (tid: 223, s: 0) [sched mode ] => 0 False 2021-09-28T22:15:44 0x847127fffe0571fe (tid: 224, s: 0) [sched enable] => 0 123456 2021-09-28T22:15:48 0x847127fffe0571fe (tid: 229, s: 0) [unknown ] => 0 100

asgothian commented 3 years ago

I am afraid i am all out of ideas. None of the data sent seems linked to any buttons. I will not be able to help further without additional information on the workings of the device and/or physical access to the device.

Since it is TuYa, some strong drink may be required too.

A.

1rfsNet commented 3 years ago

How bad, but thank you for your help. Will return the device :( Or would it be helpful to order the original gateway or send you the device?

asgothian commented 3 years ago

I am afraid that i do not have the patience to deal with a tuya remote at this time. As you see from the suggestions above, this is by far not trivial. I would feel bad to ask you to send the device and then have it lying on my desk for 2 months before i can get results.

A.

penge1510 commented 2 years ago

Hi All, I am currently working on this. I bought the same device and I want it to make it work. This is the first time that I have to put a new device into support phase, but after I got familiar with the basics and managed to get one data point to interpret, translate and display in openHAB, I just need to interpret the rest of the datapoints. Some data points already recognized easily because of the debug log and the correct button on the device, but some dp I have no information about yet. I will try to find out somehow, maybe contact the manufacturer. So, I just wanted to let you know that you are not alone. Let you know when I'm done, unless someone else is make a supporting before me. :)

Fardenco commented 2 years ago

@penge1510 any news about getting the keypad working ? Thanks

Fardenco commented 2 years ago

I managed to get the keypad working It has many commands but I found only 2 are needed to use it The first is just a counter, it increments at each action (arm, disarm, etc.), and the second is a value that changes depending on the action.

1rfsNet commented 2 years ago

@Fardenco Could you help to get this device into the zigbee adapter? I've returned the item but would buy it again if it would work with the iobroker.zigbee adapter. Couldn't find any good alternative to this device.

penge1510 commented 2 years ago

@penge1510 any news about getting the keypad working ? Thanks

Hi, Sorry for my late reply. I still did not get any answer from the factory besides they contact with me. Maybe I'll submit a refund and take back the device to the store.

Fardenco commented 2 years ago

I don't know if I'll be helping you much because I'm not using ioBroker. I'm using a home automation software that is not compatible either with the keypad, maybe you'll be able to use the same process, maybe not. Forst I included the keypad in the network, instructions for that are in the manual. Then, I used a feature provided by the software I use to auto detect commands, basically you enter the learning mode, and you do all the actions you can on the device, for example press every buttons, long press, double press, etc. Everything that could be sending a message via zigbee. This gave me a number of commands, and I figured that only 2 are useful. One is a counter that increments at each action (1::61184::cmd::1.1), and the second is some kind of id related to the action (1::61184::cmd::1.2). This id will be a certain value if you enabled the alarm, if you enable night mode, push SOS button or disable the alarm. Then I just put an event on the counter, and each time it changes I go and look at the value of the action ID, and depending on that I do what I want to do (enable alarm for example) I hope that can help

1rfsNet commented 2 years ago

I don't know if I'll be helping you much because I'm not using ioBroker. I'm using a home automation software that is not compatible either with the keypad, maybe you'll be able to use the same process, maybe not. Forst I included the keypad in the network, instructions for that are in the manual. Then, I used a feature provided by the software I use to auto detect commands, basically you enter the learning mode, and you do all the actions you can on the device, for example press every buttons, long press, double press, etc. Everything that could be sending a message via zigbee. This gave me a number of commands, and I figured that only 2 are useful. One is a counter that increments at each action (1::61184::cmd::1.1), and the second is some kind of id related to the action (1::61184::cmd::1.2). This id will be a certain value if you enabled the alarm, if you enable night mode, push SOS button or disable the alarm. Then I just put an event on the counter, and each time it changes I go and look at the value of the action ID, and depending on that I do what I want to do (enable alarm for example) I hope that can help

Thanks for that, unfortunately I already tried my best but I am not good at it. Maybe these information are helpful for @asgothian or @penge1510

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

PonyOny commented 2 years ago

Any news about support for this device? I’m planing to buy one as there is not many options for a Zigbee keypad.

1rfsNet commented 1 year ago

Anyone knows if this device is working now? I see it in my Zigbee Adapter, but unfortunately I returned the device, so I cannot check it. Device is now listed here: https://www.zigbee2mqtt.io/devices/07505L.html https://zigbee.blakadder.com/Immax_07505L.html

PonyOny commented 1 year ago

Anyone knows if this device is working now? I see it in my Zigbee Adapter, but unfortunately I returned the device, so I cannot check it. Device is now listed here: https://www.zigbee2mqtt.io/devices/07505L.html https://zigbee.blakadder.com/Immax_07505L.html

Hi, there is a custom file to be able to use it with Z2M and there is also a custom quirk to use it with ZHA it's currently in a PR but it's working, I have managed to use it with Z2M & ZHA actually i'm using it as my main keypad.

This is the PR for ZHA: --> https://github.com/zigpy/zha-device-handlers/pull/1908 And this is the Opened issue where you will find the working custom component for Z2M --> https://github.com/zigpy/zha-device-handlers/issues/1852

asgothian commented 1 year ago

You can use the file linked in that issue as an external converter in the zigbee Adapter as well - just place it in the adapters data folder and enter the filename in the configuration as external converter

Note that this feature requires at least the version1.8.9

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

1rfsNet commented 1 year ago

You can use the file linked in that issue as an external converter in the zigbee Adapter as well - just place it in the adapters data folder and enter the filename in the configuration as external converter

The device just arrived and I tried to add it but a stupid question: Which file is the correct one? https://github.com/zigpy/zha-device-handlers/issues/1852#issuecomment-1287925577 or https://github.com/zigpy/zha-device-handlers/issues/1852#issuecomment-1304904389

I used the first one (had to update the manufacturer id) and the device is detected correctly but the objects are not working. Can press any key I want but nothing happens.

luke7101 commented 1 year ago

@PonyOny what device controls should I get by using the https://github.com/zigpy/zha-device-handlers/pull/1908 quirks ? I only got the main arm(home, away, night)/disarm button. I was hoping to get the settings as well. I have the _TZE200_nyvavzbj model TS0601 keypad instead of the _TZE200_n9clpsht but the quirks file worked by editing the MODELS_INFO section.

Thanks

PonyOny commented 1 year ago

@PonyOny what device controls should I get by using the zigpy/zha-device-handlers#1908 quirks ? I only got the main arm(home, away, night)/disarm button. I was hoping to get the settings as well. I have the _TZE200_nyvavzbj model TS0601 keypad instead of the _TZE200_n9clpsht but the quirks file worked by editing the MODELS_INFO section.

Thanks

@luke7101 With that quirk you should be getting the battery & status of the keypa, if it's Armed, Dissarmed etc... you have then to make your automations considering value change of that property, in order to have all settings and values they had to do another change in the Core of HAS and the person who was doing this decided to stop the development because of different problems /difficulties he found to integrate all in the Core.

luke7101 commented 1 year ago

Thanks @PonyOny, yeah I followed MrAdam's progresses and I saw he had stopped the development. By searching the internet I found an interesting script for synchronizing a Xfinity keypad with the Alarmo integration using its built-in MQTT capabilities, I hope I'll work with some tweaks !

PonyOny commented 1 year ago

Thanks @PonyOny, yeah I followed MrAdam's progresses and I saw he had stopped the development. By searching the internet I found an interesting script for synchronizing a Xfinity keypad with the Alarmo integration using its built-in MQTT capabilities, I hope I'll work with some tweaks !

I have the keypad integrated with Alarmo with automatations :) no need of MQTT if you don't want to configure all that you can just use some automations like this one:

alias: Security Keypad
description: ""
trigger:
  - platform: state
    entity_id:
      - alarm_control_panel.keypad_alarmcontrolpanel
condition: []
action:
  - choose:
      - conditions:
          - condition: state
            entity_id: alarm_control_panel.keypad_alarmcontrolpanel
            state: disarmed
        sequence:
          - service: alarmo.disarm
            data:
              entity_id: alarm_control_panel.alarmo
              code: "XXXXX" <--- Your Alarmo code to dissarm
      - conditions:
          - condition: state
            entity_id: alarm_control_panel.keypad_alarmcontrolpanel
            state: armed_home
        sequence:
          - service: alarmo.arm
            data:
              entity_id: alarm_control_panel.alarmo
              mode: home
      - conditions:
          - condition: state
            entity_id: alarm_control_panel.keypad_alarmcontrolpanel
            state: armed_away
        sequence:
          - service: alarmo.arm
            data:
              mode: away
              entity_id: alarm_control_panel.alarmo
mode: single

luke7101 commented 1 year ago

I just tried the MQTT script because I thought I could get the benefit of using the codes stored in Alarmo (the script author says so), but it only works with the hard coded User code of the Immax keypad. The keypad doesn't send any command if you try another code, so it makes all this MQTT stuff useless... right ? There's no way to use multiple codes or codes stored in Alarmo I guess ?

PonyOny commented 1 year ago

I just tried the MQTT script because I thought I could get the benefit of using the codes stored in Alarmo (the script author says so), but it only works with the hard coded User code of the Immax keypad. The keypad doesn't send any command if you try another code, so it makes all this MQTT stuff useless... right ? There's no way to use multiple codes or codes stored in Alarmo I guess ?

Yes, the keypad only sends the change events if you enter the correct code that was set in the hardware keypad, there is no way with the existing quirk to automatically match the Alarmo code, that's why I used automations and pass to the Alarmo service the code as data to trigger the Alarmo states. The keypad can have the key you want and Alarmo can have the same one or another one it's up to you how you manage this, I know it's not the best scenario but at least I can use the device and use it instead of having it as a paperweight 😄

luke7101 commented 1 year ago

Ok, I think I'll do the same, and keep looking for a better keypad for ZHA ! Thanks 😉

PonyOny commented 1 year ago

If you find any better alternative please let me know 😉

luke7101 commented 1 year ago

I'll maybe buy one of those used Centralite 3400 or Xfinity XHK1-UE on eBay ...

luke7101 commented 1 year ago

Would you be interested in a group buy of one or few Xfinity XHK1-UE from the USA? I'll buy 2, could add more and save on shipping then forward to Spain for cheap if you're in. Keep me posted (haven't found how to PM you).

PonyOny commented 12 months ago

I had a look on those Xfinity XHK1-UE before I purchased the Neo, but they are all from USA and shipping was extremely expensive and then the taxes etc... make the product really expensive.

luke7101 commented 12 months ago

I found some reasonable prices : I'll buy 2, price should be 32€/unit for 2, 30€/u for 3 and 27,5€/u for 4. There shouldn't be extra fees (ebay:"VAT added to prices based on delivery address. No additional customs charges will apply."), worst case +20% so +5€/unit. Still good value for money in my opinion. Shipping to Spain will be around 5€ by using Vinted. Tell me what you think before the end on the week, then I'll make an order. 😉

PonyOny commented 12 months ago

Thanks for your offer but I think I will stay at the moment with the keypad I have, it's not perfect but for the use i'm giving it now it's enough at the moment, if you finally get one of those keypads let me know how they are working for you 😄

luke7101 commented 12 months ago

Ok no problem. Yeah, I'll get one I hope, I'll keep you posted! The feedback on the keypad, with a led indicating if the alarm has been armed or disarmed on HA, finally decided me. Maybe more than the codes checked on the HA side.

luke7101 commented 12 months ago

Just made the order, now is time to wait. I'll keep you posted in 2 or 3 weeks!

besiktas97 commented 10 months ago

@PonyOny what device controls should I get by using the zigpy/zha-device-handlers#1908 quirks ? I only got the main arm(home, away, night)/disarm button. I was hoping to get the settings as well. I have the _TZE200_nyvavzbj model TS0601 keypad instead of the _TZE200_n9clpsht but the quirks file worked by editing the MODELS_INFO section. Thanks

@luke7101 With that quirk you should be getting the battery & status of the keypa, if it's Armed, Dissarmed etc... you have then to make your automations considering value change of that property, in order to have all settings and values they had to do another change in the Core of HAS and the person who was doing this decided to stop the development because of different problems /difficulties he found to integrate all in the Core.

Hello PonyOny,

Which ZHA quirck is the right one to let this keypad work ? I tried 2-3 different quircks and non of them are working...

luke7101 commented 9 months ago

Thanks for your offer but I think I will stay at the moment with the keypad I have, it's not perfect but for the use i'm giving it now it's enough at the moment, if you finally get one of those keypads let me know how they are working for you 😄

@PonyOny I'm sorry, I forgot to keep you informed. I finally got the 2 keyboards I ordered (one was defective so I was lucky to order 2!). I'm super happy, it just works as I hoped.

Features: 4 digits security codes checked among Alarmo stored codes. Visual and audio feedback for alarm arming / disarming / general events. Visual thanks to the backlit keypad with red or white leds (red for the current activated mode, white for the rest of the keys). Audio are short or long beeps, long for a successful arm or disarm, short for keypress or entry/arming delay. Proximity sensor to automatically lit the keys. Bonus : temperature sensor.

Keypad sync with Alarmo works thanks to an automation I found on internet, tweaked a bit by me: https://github.com/luke7101/home-assitant/blob/main/automations/ZHA%20Xfinity%20and%20Alarmo%20Synchronization.yaml and https://github.com/luke7101/home-assitant/blob/main/scripts/xfinity_beeping.yaml is the script for beeping during arming/entry delay

😊

PonyOny commented 9 months ago

Hello PonyOny,

Which ZHA quirck is the right one to let this keypad work ? I tried 2-3 different quircks and non of them are working...

@besiktas97 Here is the quirk I am using, just rename the file without the .txt ts0601_keypad.py.txt if you have any problems let me know.

PonyOny commented 9 months ago

@luke7101 That's amazing, I'm glad it worked for you and that you were lucky to get 2 of them and one of them worked, I don't discard getting one in the future to test it 😊 thanks for the feedback 👍

PetrStol commented 8 months ago

Hello ! Pleasssse help :-) I have the ts601_keypad.py file in config/custom_zha_quirks/ folder. in configuration.yaml:

zha: enable_quirks: true custom_quirks_path: /config/custom_zha_quirks/

Keyboard uninstalled, HA restarted and Keyboard again added via Sonof Dongle. But, still all the same. No other entities except LQI and RSSI Keybaord model is sure the same _TZE200_n9clpsht Can anybody advice, where can be a problem ? Thx.

ioBroker / ioBroker.zigbee

New Device: Immax NEO 07505L #1221