No. These are not what you seem to think they are, and would not be of help in what you are trying to track down. As @csteele points out, every error that IS relevant gets posted to Logs -- and if/when we find an error that doesn't routinely get reported to Logs, that gets fixed. There are some errors that can happen in communication protocols that don't show up in any log, and aren't directly identifiable, just an unfortunate artifact of the code in use. For these, even we use embedded log.debug in the code to track them down.
I know I was a little surprised when support told me about echo speaks throwing an error about once per second. Those errors didn't show up in my log at all. I had disabled Echo Speaks, but not the echo devices. Once I got rid of the devices my hub speed has been fine ever since. But I never saw the errors.
Iām already doing this; I wouldnāt have said anything if I hadnāt already been doing this. There are logs that they have access to that Iām not getting through logsocket.
I'm kinda glad to know that I'm not the only one who experiencing this hub "slow down effect" also.
After I reboot my hub I notice for each room that has a light bulb or light switch associated to a motion sensor or a contact sensor (via RM or SL), the light turns on less than a second every time you walk into that room or open the door, which is great!
But come 5 to 7 days later, each room will have a 4 to 6 second delay (very rarely not come on at all) before turning on. Which means I have to reboot the hub again.
I have tried numerous times to do a Z-Wave Network Repair, as well as powering down the hub for 30 minutes for Zigbee mesh heal. Hoping that would fix my delay issue, but really never has.
I switched my GE switches back to Generic drivers, deleted everything Alexa Speaks and also dropped L360.... and
Prior to this, Z-Wave repair took 2.5 hours (~30 devices), today 9 mins
The GE outlet that generally takes 2-5 seconds and took 28 seconds to turn on last week, has been taking less than a second everytime. Even my wife mentioned how much faster it is
Now to get an updated Echo Speaks app and see if we are still in business
No, a ticket just got opened 6 days ago to get this error message added to the user logs. As Bruce pointed out, if we find a log that is not being logged to the user log then it gets added.
The new Echo Speaks v3.0 beta is available here: GitHub - tonesto7/echo-speaks at beta .
I've tracked down a ton of bugs and I'm working on one for cookie refreshes failing and silently clearing the authentication. There are still items remaining but it's pretty stable
Can we just replace the v2 app code with v3? Or does it need to be reinstalled? Thanks
EDIT: I was too impatient and went ahead and updated the code, it does seem to work but when I click on the button for login status, I get this error: Error: Cannot cast object 'null' with class 'java.lang.String' to class 'java.lang.Integer'
EDIT: after installing, Iāve noticed my hub is very slow to respond to actions/events... looks like Iāll be rolling back for now ..
I've installed the most recent release and as soon as I created a couple of actions my HUB started to slow down and many of my unrelated RM4 rules became unresponsive. I disabled all eco speaks apps and devices and the hub is back to working order.