Yeah, some of these frient devices have a firmware bug where it doesn’t report its manufacturer and model when queried by the hub, it’s been reported to them. I will need your debug logs to see the model and mfr details. Feel free to send us an email and we can guide you through the process to get that information and see what’s going on. Mostly likely it’s a manufacturing variant which needs a minor driver update.
Thanks for the logs, it appears to be an issue with you smartthings hub and not the driver. Either a corrupted firmware or it’s missing some libraries. Basically it’s not able to load some of the standard z-wave libraries. What hub version are you using?
2025-05-04T13:23:03.176126972-07:00 FATAL Enhanced Zigbee Keypad runtime error: [string “init.lua”]:19: [string “SecurityControl.lua”]:9: Module ‘st.zwave.CommandClass.Notification’ not found
stack traceback:
[C]: in function ‘error’
[string “env builder”]:97: in global ‘require’
[string “init.lua”]:19: in main chunk
This has happened to another user last year and eventually SmartThings was able to fix the issue from the backend.
Tagging @nayelyz
Firmware Version: 000.056.00010
Hardware Type: SAMSUNG_VD_TV_HUB
matterSoftwareComponentVersion: 1.4-0
My hub does not have any z-wave capability, so I assume the hub doesn’t have any z-wave libraries installed. Now I don’t know SmartThings libraries, but a driver for zigbee devices shouldn’t rely on libraries from different communication method. Thus wouldn’t it be better to replace the st.zwave.CommandClass.Notification with a st.zigbee.CommandClass.Notification or something else along those lines?
Samsung seems to be pushing the hub everywhere approach with fridges, TVs, soundbars, and monitors all now capable to be hubs with zigbee/thread built in, so I can assume that my situation is bound to happen again. Perhaps not with this driver but other drivers as well.
1 Like
Hi, @RBoy
I’m confused about why the library with the error is Z-Wave when the driver is for a Zigbee device. Can you provide more info about that, please?
4 Likes
It’s using features from the standard zwave library for interacting with hub core for notification events related to user codes (these aren’t available on the Zigbee library). Will have to refactor the code to make them as an independent library. Assumed that all libraries shipped with all hub devices.
Was probably true before there were hubs that don’t support Z-Wave such as the appliances, TV’s, and the Station.
1 Like
Enhanced ZigBee Keypad Driver - v250507
- (Fix) Support for wider range of hubs which only support ZigBee protocol
NOTES
- This version of the enhanced driver is only available via the new platform Drivers license (refer to website for details). If you have an active subscription, the new driver will be automatically pushed to your hub within 24 hours
- See the first post for a full list of available features
- The latest SmartThings mobile app now cuts off the text after the second line so not all user codes are visible. See the FAQ page for details on how to view the programmed codes
@TVman the driver update should be pushed out within 24 hours after which it should start working for you
1 Like