So looking at api maker in the logs has alot of “debug” also seeing debug with other apps. But maker api was the worst by far. I’m using maker api for home assistant and home remote. I turned off debugging for maker api as everything seems fine cpu and memory are fine as well as the performance of my hub. However I’m a little curious as to why it’s doing the debug thing . Anyone have any ideas??
Sounds like you had this setting enabled? Are you saying it's still happening with the setting disabled? Make sure you hit "Done" in the Maker API app to save your settings.
That's a device, not an app. Did you just add the device to your hub? Debug logging is enabled for 30 minutes by default after adding a device (or after manually enabling). You can manually disable it at any time.
Hello thanks for the reply, yes I did add a new zigbee switch last night and another today . So in the last 2 days I added two new zigbee plug on/off switches. So it’s saying it’s device 25 and device 18 ? Is that correct
Sort of; it's app 25 and devices 18, 17, and 107. You can click the link like "dev:18" and filter the logs list to just that device (or app), which will also highlight its name at the top so you can see what it actually is; or you can click the "info," "debug," etc. box to open the device detail page (or the app) and see what it really is. These numbers are the sort of internal ID for the device or app that don't have much use in regular hub operation, you aren't likely to just know what they are or see them many other places (except the URL bar in your browser -- another handy way to match things up).
You can disable debug (or info/descriptionText) logging on any device where you don't wait it. By default, debug logging will auto-disable but is on for a bit after adding, as I mentioned above; and info logging is on indefinitely but can be disabled. Apps vary but generally offer similar options you can enable or disable. These entries are not indicative of a problem, just reflective of your settings. Some can be helpful for troubleshooting. It sounds like you aren't having problems and are just curious where they're coming from, though? If so, it's just that -- your settings for that particular app or device.
1 Like
Thanks for the quick response . So just because I’m seeing “debug” within the logs doesn’t mean there is a problem, correct?
If I disable this on the settings will it save on memory and cpu usage?
Correct. It just reflects the logging options you've chosen on that device or app.
There should be no noticeable effect from enabling or not (it seems likely that more logs would have slightly more overhead, but writing a line of text isn't exactly intensive enough to matter),
1 Like
This is the settings to turn it off correct?
Also when looking in the logs is there anything I should look for if a serious problem occurred? Like “error” does that indicate an issue ?
Those are the settings for that particular, device, yes. (Each device or app has its own settings.)
A log entry with "error" typically indicates some problem, though how much you need to care depends on the particular app or device in question. If you aren't sure, sharing a specific log entry here and more information about the app, device/driver, and your actual problems, if any, would be a good place to start.
This doc would also be good to read:
As might the Logs page docs themselves.
1 Like
So one that has been giving issues for a long time is dev43 it’s from a ring virtual. Logging is turned off. However it all works fine
It’s logging is off but still getting stuff in logs
That looks like third-party code, so you'd need to troubleshoot the issue with the developer, someone familiar with the integration, or any documentation they may have provided.
That being said, following the steps in the error message text is the first place I'd start: did you install it with HPM (Hubitat Package Manager, another third-party piece of code), and assuming so, have you tried doing an "Update" on the package and selecting the driver it's complaining about? 
This can still happen, particularly when there is a problem that warrants logging regardless of your settings (or if there is an error thrown by the platform the app or driver doesn't handle), as there appears to be in your case.
2 Likes
