Error message

🎬 Get Started Novice Help
1

Any know what these mean since the ip address is not changing?

app:6422020-12-26 02:59:39.551 pm debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:59:39.544 pm debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:58:20.636 pm debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/script.js?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:58:18.778 pm debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:58:18.762 pm debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:35:59.869 am debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/script.js?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:35:57.290 am debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:35:57.282 am debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:35:51.625 am debugEndpoint: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:35:51.623 am debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:35:51.618 am traceHubitat Z-Wave Mesh Details | Now Running Updated() Method

app:6422020-12-26 02:35:47.777 am debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

app:6422020-12-26 02:35:47.762 am debugHost overrride: 192.168.86.194 new link: http://192.168.86.194/apps/api/642/meshinfo?access_token=a90a02fb-9536-4a3c-b0cb-7c1080570e66

2

What is app 642?

Also, those are debug messages, not errors.

Also, you need to reset the access token if the app is cloud accessible.

2 Likes
3

My ESP tells me these errors are coming from the community Z-Wave Mesh Tool app. You'll usually get better luck if you ask questions about a specific app in the thread that that app authors tend to create for their apps, this one included. If you're not sure how to tell what app the "app:642" in your logs (you can see the app ID in the far left of the window or in your copy/paste above), then there are a few ways to figure that out. Clicking "app:642" itself will filter entries to just that app and highlight its name at the top, or clicking the "debug" (or similar "info," "error," etc. log level) will take you to the app itself. You can also match the id, 642 here, with the number you see in the URL when editing or viewing the app itself.

Anyway, it looks like those messages will disappear if you uncheck the "Enable debug" logging option in the Mesh Tool app. Alternatively, it appears that blanking out the "Override link host" preference that you may have filled in might also get rid of the messages by not executing that code path in the first place, but it also looks like that might get filled in with a default value for you when saved anyway, so it might not work long-term and may explain why you're seeing it even if you don't remember doing that.

If that doesn't help or you're curious what the use case is (I have no idea :slight_smile: ), then I'd recommend posting in that other thread and the author will undoubtedly know more. That being said, the above is also correct--these aren't errors, just messages the author chose to log when you have that option enabled. Debug logging is generally something you'd enable for troubleshooting, either on your own or with the app (or driver) author, but can otherwise keep disabled.

Good luck!

1 Like
4

Ahhh thanks! I thought it was coming from the hub itself!