The Zigbee “Monitored Attributes” functionality and corresponding checks are being deprecated.
2025-12-30T16:05:45.787535333Z WARN button-battery-v1.4.4 The Zigbee "Monitored Attributes" functionality and corresponding checks are being deprecated. Please set `health_check = false` on your driver template and replace any behavior depending on this if needed.
Edit:
@erickv
I’m using your driver from this channel:
These drivers are available at the @erickv Shared Drivers channel.
Dear @TapioX
I really appreciate that you brought this into the thread.
I’ve been reviewing the code over and over again and fortunately (at least to my eye) I wrote the driver without relying on the deprecated features.
This is because, as far as I can remember, I wrote the whole driver using the st_libcode as documentation itself rather than relying on the actual SmartThings Edge Device Drivers Reference Documentation… so I used a few low-level functionalities to “simplify” the code.
By the way, @nayelyz I didn’t find any documentation related to the st.zigbee.device_management API… is it something super “low-level no worth documenting” perhaps?
Hi, @erickv
It’s great hearing from you. I asked the engineering team about this. Once they reply, I’ll let you know their feedback.
Awesome, @nayelyz
I really appreciate it 
and its also great that you’re still around 
Hi @erickv ,
I tried to use your driver for a meos 4 button scene switch. However, only one switch is displayed, but there should be four. In your list it is also displayed as “button-battery” and not as “4-button-battery” like all other TS0044 models. Could you adjust this so that the correct four switches are displayed? Thank you in advance.
You can also try @zambobmaz driver that also support :
“manufacturer”: “_TZ3000_kfu8zapd”,
“model”: “TS0044”,
https://api.smartthings.com/invitation-web/accept?id=2d6da83b-ae22-4fda-8af5-bbb8890872d4
@erickv, following up. The team mentioned that the documentation for this feature should be included, but it seems it wasn’t referenced correctly for the docs generation process.
So they’ll add the corresponding link to include it in the next firmware release docs.
Awesome, @nayelyz!
Thanks a lot for the follow up and the great news.
Hi @dotan_shai
Thanks for the tip about the driver. I had already tried it and it worked so far, but I had significant problems with battery drain (the 3V button cell was empty within a day).I have no idea whether it’s the switch itself or the driver had something to do with it, but it looks like it doesn’t switch to sleep mode. I thought that the battery problem could be solved with a different driver from @erickv (which makes maybe better use of sleep mode). Thank you for adjusting the driver so far.
@zambobmaz , can you comment on @Tischlor battery drain issue ?
@Tischlor I’ve seen this issue with two of my switches that are apparently the same model, but with big differences in their behavior.
One of them is slower to transition from one click to another in SCENE mode, but in REMOTE it supports the Group cluster to broadcast commands and operate the whole living room without configuring app automations (further than configuring the group, of course)… this one has an amazing power consumption capability… lasts years.
But the other has a better response from one click to the next one enhancing user experience, but doesn’t support REMOTE anymore and drains battery faster even with the maximum refresh rate configured.
So, it is most likely to be a firmware limitation aiming to enhance user experience over durability.
@erickv I have a similar issue with some new remotes we just got (retail link: Robot or human? ) They show as TS004F, but slightly different manufacturer code _TZ3000_g9g2xnch
I added your button-battery-v1.4.5 and it works but only recognizes one button. I’m wondering if it just needs a fingerprint to set the profile as 4 button?
Hello @pgbunce
Welcome to the SmartThings Community. I’m glad you took the opportunity to leave a comment and collaborate with this project.
Related to your issue, the fingerprint of your device has been added to the list of supported devices, so try re-adding the device.
Hi @erickv Thanks for the quick response!
I’ve removed the device, uninstalled the driver, reinstalled the driver and added the device and still seeing one button. The driver timestamp I see still shows 24 Jan though, so do I need to clear a cache or something like that? It shows ID 3cde7eee-3ad9-44bd-a7d3-6ba50025bee2
@pgbunce Thanks for the message
I reviewed the package deployment and noticed an issue that blocked that latest deployment, but it has been addressed.
Here’s the info about the latest version
Basic Information
───────────────────────────────────────────────────
Driver Id 3cde7eee-3ad9-44bd-a7d3-6ba50025bee2
Name button-battery-v1.4.5
Version 2026-02-10T01:59:04.787121719
Package Key button-battery-v1.4.5
Description
Permissions zigbee
───────────────────────────────────────────────────
Can you please retry integrating the driver?
Thanks. We removed the device and driver, rebooted the hub, and added things back. The driver shows the correct timestamp, but the remote is still showing only 1 button.
Any ideas on what I should try next?
Thanks 
Oh! you’re using the web interface, Nice!… but I have no idea regarding the metadata refresh time frame, but normally I would suggest to wait for the app (in the case of mobile) to refresh the device profile metadata instead of getting rid of the app’s cache and cookies which in your case would be more chaotic considering the opened session, etc, etc.
Let’s give it some time and let’s bounce back tomorrow (at its worst 
)
We’ll give it overnight, and see what the app and web say. Was looking at the code, (I’m a developer in my day job ) and the only thing that stood out to me is the init.lua references 1.4.4 (although it looks like that’s just a label, and not relevant). Smartthings recognizes that the driver matches the device, or we couldn’t have assigned it in the first place.
Code line 58 in init.lua: local driver = ZigbeeDriver(“button-battery-v1.4.4”, driver_config)
Well, it’s been over a day, and we have added a 2nd remote fresh, and neither is being recognized as a 4-button-battery. It’s like the fingerprint is matching one of the earlier TS004F that has a profile of button-battery, rather than the new fingerprint with the manufacturer match that is a 4-button-battery profile.
The only thing I can think of to try is to create my own fork/clone and strip out everything but the one fingerprint, and try it as a test mode, but that will involve some set up, and installing the CLI, etc. so will have to wait for the weekend, at the earliest.
