The End of Groovy Has Arrived

Don’t forget halo

1 Like

Any official word on this? It seems like something people should be told upfront. :thinking:

I know because most drivers have multiple fingerprints it may seem like 50 is plenty when the device max is 200, but obviously someone can hit it, and if there is more creative use of LAN communications such as @TAustin has done, that uses up more slots. It just seems like something that should be communicated more clearly. Unless
I just missed it…

4 Likes

Always a gotcha with Samsung these days

I have since deleted some drivers i knew were not used JD

Others no doubt have hit the limit as well or will as time goes by

1 Like

Hang on. Did I just read above that these community drivers, if the developer decides to stop letting users use it, they can and make our devices effectively useless?
Edit ; or even the Samsung official drivers as well?

2 Likes

Wouldn’t the developer just have to remove all details in the driver and then push an update… boom, job done, system hosed

2 Likes

I’ve no idea, even less of an idea on how these drivers are made and created but if a developer ( or even a Samsung for that matter ) can just push an update to a driver and make our devices useless then that’s not good at all.
I thought the whole point of this move was to have things being run on the hub itself locally and not rely on anyone or anything?

3 Likes

A way around auto pulling updates is a driver lock mechanism but im sure Smartthings have considered all that

Perhaps remove auto update driver and add an update button next to a driver or chanel in hub driver option setting if an update is available they can put a coloured dot next to a driver to indicate update available

I mean, why take an update if a driver has had more fingerprints added which are not relevant to the user

The user can at least then refer to the community thread that is relevant to see if indeed the update is required

5 Likes

This is going to be a hot discussion, no doubt.

But this is definitely the time to have it!

5 Likes

Good news… you can’t remove an Edge Driver that is currently assigned to a device

1 Like

For sure, cant forgot about those!

2 Likes

Yup, known and tested jkp, unfortunately for me i had delusions of IDE, a list of items to pick if and when needed, turns out that method not great

Well, a lot of us are definitely depending on those kind enough to create the custom edge drivers. I think it’s not only in the users interests to disable updates, but in the devs interest, as well…

Fear and/or uncertainty is not a good way to move forward… and at the moment, that box has been opened it seems.

Agreed but some drivers are being charged for, whats the fallback if a driver is paid for and then the developer removes access/driver details ?

Would you install software on your home computer by clicking a link that some rando posted on the web? That’s what you’re doing when you install a driver.

ST has sandboxed the drivers, and has said in other threads that they’ll respond if they identify bad actors. But you shouldn’t be installing in the first place if you don’t trust the source to continue to act in good faith.

3 Likes

I’m all about open source code, and wouldn’t mind to pay for that. That ultimately may be the only thing that completely alleviates those fears.

Self-hosting the code would, open source or not, solve the problem, maybe?

I agree with your comments Phil but users will be using a trusted Samsung app, i have absolutely no doubt the same users will blame Samsung if something goes wrong, for not safe guarding there instaled driver/paid for driver

That’s where we really are. Trust, is easy for me, here, at the moment, actually. The future, who knows?

4 Likes

One benefit of the ide was all code was readable by default

This is unfortunately gone, but I hope people will still post their code to GitHub

5 Likes

Same. It builds trust. It helps others learn. It allows others to suggest improvements. It lets users choose to package a static version for themselves if they want to. I’m so thankful for those that are sharing their code.

There have been a couple threads over the past year discussing this whole trust/risk issue. One of them mentioned the possibility of a community GitHub repo with real checks in place. I’m hoping that happens. Especially since the 50 driver limit (and even if they were to remove it, the very real possibility of overloading your hub with too many drivers) will make it difficult to use the “best” community driver for each of your devices.

6 Likes