Sharptools privacy concern

🛎️ Get Help Apps
1

I turned on logging of the Sharptools app, and what a surprise, it's logging e.v.e.r.y.t.h.i.n.g. from my Hubitat location without my permission.
I gave Sharptools access to 25 devices and that it's. But all my WebCoRE global variables are being sent to their servers, sunset/sunrise times, location modes, HSM Status, even stuff from my multi room speakers, everything. I don't want Sharptools to know when the house is armed, what mode it's in. I consider this a privacy breach. All my WebCoRE global variables going to their servers? And apart from the privacy issues, it's a resource hog on the hub. There are multiple entries a minute.
We use Hubitat because it's the best at respecting privacy. We can decide which devices to expose to Alexa/Google for example.
I emailed Josh from Sharptools, he gave me an overly technical explanation, said it wasn't resource heavy, it was lightweight, and as the holidays are coming, he'll look at it later. He crucially didn't appear to grasp the seriousness of what I was saying, nor apologize. This has clearly been going on for 5 years I've had the logging button disabled on the Sharptools app inside Hubitat.
To Hubitat, can you look into this, and see if the Sharptools smartapp meets your guidelines. And help Josh fix this, because he's clearly got the scope for the WHOLE Location, when this should be user controlled, unless I'm wrong.
To Josh, please can you update your smartapp, to include checkmarks for LOCATION, a checkmark for MODES, a checkmark for SECURITY STATUS, for anything else. At the moment, a user assumes, they're giving access only to certain DEVICES from a list that they choose from.

app:432025-12-17 09:07:51.775 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 09:07:51.754 AMdebug
Sending event for LOCATION: :xxxxxx275d6bxxxxxxx:.@Fully_Kitchen_Screen -> @Fully_Kitchen_Screen
app:432025-12-17 09:07:51.417 AMdebug
Sending event for LOCATION: :xxxxxxx0146xxxxxxx: -> [192.168xxxx]
app:432025-12-17 09:07:16.360 AMdebug
Current location status for hsmStatus is null
app:432025-12-17 09:07:15.425 AMdebug
Available modes: [Home, xxxxxx, Night, Away, xxxxx, xxxxxx, xxxxxxx Away]
app:432025-12-17 09:07:15.424 AMdebug
Current mode is Home
app:432025-12-17 09:06:10.101 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 09:06:09.823 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 09:06:09.739 AMdebug
Sending event for LOCATION: :xxxxx75d6bxxxxxxxx:.@Fully_Kitchen_Screen -> @Fully_Kitchen_Screen
app:432025-12-17 09:06:09.424 AMdebug
Sending event for LOCATION: :xxxxxxec01xxxxxxxxxx: -> [192.168.xxxx]
app:432025-12-17 09:03:42.591 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 09:03:42.388 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 09:03:42.381 AMdebug
Sending event for LOCATION: :xxxxxx275d6xxxxxxx:.@Fully_Kitchen_Screen -> @Fully_Kitchen_Screen
app:432025-12-17 09:03:42.000 AMdebug
Sending event for LOCATION: :xxxxxxx1466a4xxxxxx: -> [192.168.xxxx]
app:432025-12-17 09:01:05.427 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 09:01:05.088 AMdebug
Sending event for LOCATION: :xxxxd6bdxxxxxxxx:.@Fully_Kitchen_Screen -> @Fully_Kitchen_Screen
app:432025-12-17 09:01:05.037 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 09:01:04.830 AMdebug
Sending event for LOCATION: :xxxxxdec01466axxxxxxxx: -> [192.168xxxx]
app:432025-12-17 09:00:23.645 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 09:00:23.268 AMdebug
Sending event for LOCATION: :xxxxxx5275xxx:.@House_Temp -> @House_Temp
app:432025-12-17 08:57:06.167 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 08:57:05.069 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 08:57:04.879 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 08:57:04.652 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 08:57:04.527 AMdebug
Sending event for LOCATION: :xxxxx5275dxxx:.@A_Radio_Stations -> @A_Radio_Stations

app:432025-12-17 06:03:41.345 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 06:03:41.210 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 06:03:41.009 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 06:03:40.234 AMdebug
Sending event for LOCATION: :xxxxxxxxxxxc219axxxx:.@Previous_Mode -> @Previous_Mode
app:432025-12-17 06:03:40.128 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 06:03:40.016 AMdebug
Sending event for LOCATION: mode -> Home
app:432025-12-17 06:03:40.016 AMdebug
Sending event for LOCATION: mode -> Home

app:432025-12-17 07:40:00.728 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 07:40:00.500 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 07:40:00.401 AMdebug
Sending event for LOCATION: sunriseTime -> 2025-12-18T06:41:00.000Z
app:432025-12-17 07:40:00.090 AMdebug
Sending event for LOCATION: sunrise -> true

app:432025-12-17 07:55:55.963 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 07:55:55.768 AMdebug
Sending event for LOCATION: :xxxxxxx5275d6xxxxxx:.@TV_Watching -> @TV_Watching
app:432025-12-17 07:55:55.739 AMdebug
Event data successfully posted to SharpTools.io

and logging info from my speakers...

app:432025-12-17 07:01:56.040 AMdebug
Sending event for HUB: ssdpTerm -> urn:schemas-upnp-org:device:MediaRenderer:1
app:1032025-12-17 07:01:56.040 AMinfo
Samsung Speakers Integration 4.0: ssdpHandler: parsedEvent = [mac:xxxxx, networkAddress:xxxx3267, deviceAddress:7d6, ssdpPath:/, ssdpUSN:uuid:xxxxxxxxxxxx184-f49d-af190xxx077f::urn:schemas-upnp-org:device:MediaRenderer:1, ssdpTerm:urn:schemas-upnp-org:device:MediaRenderer:1, ssdpNTS:null]
app:xxxx025-12-17 07:01:54.819 AMdebug
Event data successfully posted to SharpTools.io
app:xxx025-12-17 07:01:54.710 AMdebug
Event data successfully posted to SharpTools.io
app:xxx025-12-17 07:01:54.509 AMdebug
Event data successfully posted to SharpTools.io
app:xxx025-12-17 07:01:54.405 AMdebug
Sending event for HUB: ssdpTerm -> urn:dial-multiscreen-org:device:dialreceiver:1
app:xxx025-12-17 07:01:54.405 AMdebug
Sending event for HUB: ssdpTerm -> urn:dial-multiscreen-org:device:dialreceiver:1
app:xxx2025-12-17 07:01:54.154 AMinfo
Samsung Speakers Integration 4.0: ssdpHandler: parsedEvent = [mac:xxxxxxxB1xx5, networkAddress:xxxx3219, deviceAddress:1dfc, ssdpPath:/smp_7_, ssdpUSN:uuid:xxxxxx00-00a0-1000-b47c-8xxxx2d90ee::urn:dial-multiscreen-org:device:dialreceiver:1, ssdpTerm:urn:dial-multiscreen-org:device:dialreceiver:1, ssdpNTS:null]
app:xxx25-12-17 07:01:54.154 AMdebug
Sending event for HUB: ssdpTerm -> urn:dial-multiscreen-org:device:dialreceiver:1
app:1032025-12-17 07:01:54.143 AMinfo
Samsung Speakers Integration 4.0: ssdpHandler: parsedEvent = [mac:xxxxxxADxxx5F, networkAddress:xx8xxF, deviceAddress:1dfc, ssdpPath:/smp_7_, ssdpUSN:uuid:xxxxx0-00a0-1000-b47c-90f1aaa9df02::urn:dial-multiscreen-org:device:dialreceiver:1, ssdpTerm:urn:dial-multiscreen-org:device:dialreceiver:1, ssdpNTS:null]
app:xxx2025-12-17 07:01:54.143 AMinfo
Samsung Speakers Integration 4.0: ssdpHandler: parsedEvent = [mac:xxxxxDxxx6, networkAddress:Cxxx323B, deviceAddress:1dfc, ssdpPath:/smp_7_, ssdpUSN:uuid:xxxxxx-00a0-1000-xxxxc-9xxxxaaa8177::urn:dial-multiscreen-org:device:dialreceiver:1, ssdpTerm:urn:dial-multiscreen-org:device:dialreceiver:1, ssdpNTS:null]

app:432025-12-17 05:38:20.975 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 05:38:20.813 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 05:38:20.651 AMdebug
Sending event for LOCATION: xxxxxxxxxxxxd6bd5a5xxxxx:.@Wind_Speed -> @Wind_Speed
app:432025-12-17 05:38:20.409 AMdebug
Sending event for LOCATION: :xxxxxxx5d6xxxxxxx:.@Wind_Gusts -> @Wind_Gusts
2

@Greenwave if you want to ensure that Josh from SharpTools sees your message on this user forum, please ensure you tag him @josh (no further need to do so now, as I just have!)

2 Likes
3

and maybe @bobbyD

app:432025-12-17 11:30:30.232 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-17 11:30:29.862 AMdebug
Sending event for LOCATION: webCoRE -> pistonList
4

Fair enough that privacy is a concern, it is becoming one for many people, not just in the home automation space.... and sure, the logs you have raised could be seen as concerning.... and definitely worth raising, no doubt...

But is it necessarily something to be classified as a data breach like it would be for a legal entity governed by local authorities? From my POV there is a level of trust and acceptance of responsibility when taking on Community developed integrations... not that I am entirely attempting to absolve myself of all responsibility... but most if I can get away with it :wink:

EDIT - Seems I was incorrect...

All I'm saying is... yes, call it out... ideally privately to begin with.... but let's not lump @josh amongst the technical offenders that quickly.... give him time to respond and correct the issue before putting him in front of the firing squad...

EDIT - Even with edit above... let's give him some time to respond...

5

Sharptools is not a community integration, its a business, a legal entity, that I pay a yearly subscription to.

6

Fair enough then, show's my ignorance... I'll update my earlier post...

7

Here is a link to their privacy policy... For other people here, obviously...

https://cdn.sharptools.io/policies/privacy.html

8

Actually, now that I read your OP, you have a fair point in that the assurance has always been that apps only have access to the devices users provide authority for them to access, but system-level events do appear to slip past this.... So I can see your concern.

1 Like
9

No.

Not trying to minimize anyone’s privacy concerns.

But a data or privacy “breach” implies that some kind of safeguard/barrier that was in place was bypassed or defeated so that data could be accessed by someone that isn’t supposed to have access to it.

So I have made a minor edit to the thread title, accordingly.

4 Likes
10

I'm not going to quibble over terminology... was mostly interested in the more "black and white" element of is this a concern.... which it feels like it still is, even under your definition...

11

Words, and their meanings, are important :slightly_smiling_face:.

4 Likes
12

True, particularly in this case... It is hopefully only my mastering of them at this hour that is lacking... :slight_smile:

13

Thanks for your feedback. @josh reached out to us and our developers will work with his team to see what can be done to improve their app. Nothing has changed in their code in a long time, so there may be ways to enhance how individual hub events are managed by the SharpTools app.

7 Likes
14

Thanks for tagging me, @johnwill1 and @sburke781, and sorry to hear that I didn't properly address your concerns @Greenwave

As Bobby alluded to, SharpTools has used the current approach to listen to hub events for keeping the Mode and HSM Status in sync since the initial app release with the very first version of Hubitat.

Over time, Hubitat has introduced lots of awesome new features and it seems like many of those features now emit events at the hub level. On the SharpTools event receiving side, we filter out all the hub events that aren't Mode or HSM Status events, but I certainly understand the concern with the app seeing those events in the first place.

I'm working with the Hubitat team to see if there's a better way to listen to just the individual hub events that the app needs -- similar to how the app listens to just specific device attribute events as needed.

Edit: a new version that listens just for the Mode and HSM changes should be included in an upcoming Hubitat (beta) release. Maybe 2.4.3.174

13 Likes
15

I'm a huge fan of sharptools, have been for years.

I'm sure "issues" will be dealt with accordingly by Josh and the team.

For me - No concerns here at all.

5 Likes
16

@marktheknife If someones personal information has breached the confines of their home without their permission, its a privacy breach. If you speak to a lawyer, they will tell you even a secretary emailing employees' salaries to a third party is a privacy breach, words and their meanings are important.

@josh A thoroughly tone deaf response, as if you haven't read my concerns at all. Customer care clearly isn't your forte. Still no apology, it's as if I have to thank you for not collecting children's names stored in WebCoRE variables! All you had write was "I'm very sorry greenwave this was happening, we had no idea, honestly we haven't looked at the Sharptools Hubitat app for a few years, we at Sharptools certainly don't want to collate any information that doesn't concern your using our service. Originally we got the whole of the users Location data, this no longer is pertinent and we will update the app accordingly."

And your response mentioned just filtering Location data? But users don't want to arbitrarily give you full location acces, users want to be in control if it, do you understand? Users want a TOGGLE for location as well as devices, like they do on SmartThings. Surely Hubitat users aren't going to get less control of their location than ST users?

Screenshot 2025-12-25 115441
Screenshot 2025-12-25 1154411539×678 32.9 KB

@bobbyD Please note latest firmware has made no fix for this issue.

Screenshot 2025-12-25 115847
Screenshot 2025-12-25 1158471393×359 17.7 KB

Currently running version: 2.4.3.173

No updates available.

app:432025-12-25 11:50:18.601 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-25 11:50:18.289 AMdebug
Sending event for LOCATION: :xxxxxb785275xxxxxxx:.@Fully_Kitchen_Screen -> @Fully_Kitchen_Screen
app:1082025-12-25 11:50:18.283 AMinfo
║ Kitchen Screen turned on at 11:50 on 25 of December
app:432025-12-25 11:38:24.948 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-25 11:38:24.759 AMdebug
Event data successfully posted to SharpTools.io
app:432025-12-25 11:38:24.759 AMdebug
Event data successfully posted to SharpTools.io
app:322025-12-25 11:38:23.481 AMinfo
║ 10
app:322025-12-25 11:38:23.479 AMinfo
║ 11
app:322025-12-25 11:38:23.477 AMinfo
║ Broken clouds
app:322025-12-25 11:38:23.475 AMinfo
║ Wind speed is 11 and Gusts are 11
app:432025-12-25 11:38:20.692 AMdebug
Sending event for LOCATION: :xxxxxx5d6bd5a5bxxxxxx:.@Wind_Gusts -> @Wind_Gusts
app:432025-12-25 11:38:20.692 AMdebug
Sending event for LOCATION: :xxxx6b785275dxxxxx:.@Wind_Speed -> @Wind_Speed
app:432025-12-25 11:38:19.387 AMdebug
Sending event for LOCATION: :dxxxxd6bd5a5bxxxx:.@Rain_today -> @Rain_today
17

That sounds completely irrelevant to me.

Glad to see we agree on that much.

Happy Holidays!

3 Likes
18

You’ll need to save your SharpTools Hubitat app settings after the update for the changes to take effect.

Open the SharpTools ‘app’ configuration from the Hubitat UI and tap Next through to save the existing settings.

5 Likes
19

This was the first thing I tried, also a reboot. No point in sending more logs now as I see it's Christmas so I'll wait until you are back in the Sharptools office to verify on your own Hubitat hub. I'll also wait for your answer to my second question, that so far you've subtly ignored (which is a bad omen), twice.

20

This is very rude and not the way we talk to developers in this community.

8 Likes