Wireless tag drivers stopped working on all my hubs with this error

Get Help Apps
1

already tried removing reinstalling same error ... any ideas. looking up message was not helpfull. lookes like some java key in the hub may need updating.

@bobbyD

Screenshot 2025-07-08 191422
Screenshot 2025-07-08 1914222418Ă—404 46.3 KB

2

it appears the code breaks down at this point the swaptoken api call to the hub is just hanging

http://192.168.1.109/apps/api/96//swapToken?access_token=xxxxxxx-8772-47ee-a3b0-7c9aea4f8810&?code=96aa4c7a-f09d-4a90-80b1-xxxxxx&state=47e92ea7-e615-4b90-8f48-xxxxxxxx

3

Looks like self-signed or expired certificate somewhere in the HTTPS request.
What is the app source code link?

1 Like
4

is this like a FindMy tag?

5
6

Any update on what is meeded to fix this rhe swap on return is hanging

7

I believe the sensors have a “beep” feature so you can find them if you lose track of them.

But that’s not their primary purpose.

They’re a range of sensors for monitoring environmental conditions. Temp, humidity etc.

2 Likes
8

Yup - and very reliable. I used these years ago to monitor freezers and incubators. Their range was very impressive as well.

1 Like
9

Not like.that. not for.location . Goto wirlesstag.net there are for.envirmental.monitoring.

1 Like
10

@gopher.ny

Still waiting for more info.on what needs to be done to get this working again

11

My wirelesstag integration recently stopped working. I tried reinstalling the code. That works well. Adding the app fails when attempting to "Grant access to Hubitat." That generates the error "Problem connecting your Wireless Tags account. Close this window and try again in the app." Have others reported the same issue? Suggestions?

"not secure" prevents Wireless Tag Integration
12

Details follow:

Hub: C8 Pro
Platform: 2.4.2.129
WirelessTag Integration installed by Hubitat Package Manager had been working flawlessly for years. It failed recently. The WirelessTag developer and community claim the API has remained the same for years. The Package Manager no longer supports the WT integration, so I installed the code from Github. Both the driver and the app code installed successfully. App OAuth succeeded, and the WT site shows access granted. Subsequent attempts to install the program failed at the authorization step with the "Not secure" error message.

WirelessTagApp
WirelessTagApp1280Ă—1356 133 KB

InstallationErrorMessage
InstallationErrorMessage802Ă—1336 22.1 KB

"not secure" prevents Wireless Tag Integration
13

any more info on fixing this accord to the java instructions here i need to add the cert to the jvm but that is built into the hub.. any way you can do that..

@gopher.ny

14

How is http call made?

For regular httpGet/httpPost/asynchttpGet/asynchttpPost calls, there is ignoreSSLIssues: true flag in the request parameters. It will turn certificate validation off entirely.

15

here is the call. i added your ignore ssl issues to the params i assume that is the correct way but it still hangs aon the swapaccess tokens call with the same error. am i doing it wrong?

Screenshot 2025-08-11 131826
Screenshot 2025-08-11 1318262005Ă—994 111 KB

in addition, i also added it directly to the swaptoken redircect url..

Screenshot 2025-08-11 131516
Screenshot 2025-08-11 1315161978Ă—222 39.3 KB

16

Make it just plain boolean true, no quotes.

1 Like
17

the quotes have noting to do that url is going external.. the return does have the ignore=true and has no effect

18

The ignoreSSLIssues: true parameter is something specific to the hub, and the quotes, or really the parameter value, matter there. It wouldn't make it to the external system (I'm not clear with what you mean about seeing it there), and adding it as a query string to the URL is not a valid approach (I guess you would if you did that?).

2 Likes
19

Thanks for the help.. got it working eventually

For anyone that wants the changed code it is here:

You may have to remove and reinstall.. i did.

Remember to enable oauth in the app source code before adding the app instance.