I agree with you, but I notice that now we who have the May 2 beta drive, we can’t do anything to switch to the May 23 drive. Perhaps the only way would be to delete the Philips hue device, then delete the drive, and then trying to reconnect the hue hub to smartthings again would automatically mount the new drive. I don’t think I want to do that though, that would wipe out dozens and dozens of automations
Also I wouldn’t recommend it, if as you say could result in having to repair a load of automations. I found the new driver (23/5) installed 2 days ago but after 24 hours with everything Hue offline yesterday I had a whole day when it worked perfectly, with the new ‘recent colours’ palette. But now results today again offline! As the ST update 48.x is being pushed from today better to wait and see what happens.
that’s right, me and a friend of mine too (@pilone ). both of us are in beta so we got that new hue driver again. After a bit of a mess now everything works for both, but with the May 2nd driver. We will wait for next developments without doing anything.
drive or driver? hmmmmm 
sorry, I corrected. I don’t speak English well, I use google translator, and sometimes I don’t write very well
Hi, @Diegocampy
Drivers in the beta channel and the default channel have the same configuration, so, there’s not a problem if you have the beta one, the date changes based on when it was packaged, not if there were changes in the code.
Also, something important to consider about LAN drivers is that they don’t support driver switching because, during the discovery and onboarding of the device, there is some info collected and saved in the data store which isn’t transferred among drivers for security reasons. Hue is a great example of this. The driver stores the API key from the Link Button process in the driver’s datastore.
So, if you were using the driver in beta and then changed to the one in “default”, it could have caused issues.
Thanks for the reply. No, honestly I did the opposite, I had the default drive, but I wasn’t sure the hue devices worked with that, so I tried changing it . After the change it didn’t work anymore. Then I reinstalled the drive and the beta overwrote the default. If as you say it’s not a problem, I’ll keep the beta drive 
They may not support it (and it makes sense that they don’t), but the UI still allows it, at least on Android. It would be good if this ability was removed from the UIs.
I understand, I will open a report to see what the team can do about it.
Hey @Diegocampy - What issues were you experiencing before you attempted to do a driver switch with your Hue devices?
Nobody 
As I said in this message I changed to do some tests, I didn’t have problem now.
I reinstalled the drive manually and now I have beta instead of stable, but that shouldn’t change, everything works
As a belated follow up, the API does expose the routing for Zigbee and Z-Wave devices, but I’ve only encountered it for the legacy DTH devices. So that isn’t terribly helpful. Especially when you only have one.
Anyone know how to see logs when use edge drivers
Anyone know where to see the list of “st.zigbee.zcl.clusters”
Install @Mariano_Colmenarejo “ZigBee Thing Mc” driver and temporarily switch your device to that driver and it will show your clusters when you open the device tile.
You can do Edge driver logging with the ST CLI and using the command “smartthings edge:drivers:logcat”.
Did you ever find a driver for your monoprice 24259 open/close sensors?
To Search for specific drivers, check the quick browse lists in the community – created wiki. they are divided by device class, so there’s one for sensors.
https://thingsthataresmart.wiki/index.php?title=Quick_Browse_Lists_for_Edge_Drivers
In this case, I’ll save you a step: try this one
We don’t support the Hank HKZW-DWS01 (aka Monoprice 24259). It seems to be a problematic sensor anyway. Doesn’t honor the check in/wake up period.
Thanks. I had taken a look at the Wiki, and even commented in that thread you linked previously. I thought I would ask some of the other users who have these sensors as well what they have ended up doing.
Is there a better place for this question than this thread where the user has previously discussed them? I like the idea of the combined thread for zwave driver requests, but the requests there go unanswered and get buried sometimes.