I was adding to another topic above Echo Speak but it said it was closed...so here goes...
The echo speak driver is complaining that a device is offline.
I added a little more details to that error and get
The speech request is coming from webcore piston and when it fails a different webcore piston (press samsung button) speaks just fine.
The question is whether "null" makes sense and whether the information regarding the request makes sense when it fails...or what would be my next steps to finding the culprit
With a webcore piston, I send a speech cmd speechCmd SpeakCommand, msg=The mailbox was filled at 11:10:28 PM CST and the health status is INACTIVE and its ignored for OFFLINE
With another webcore piston, I create another speech cmd speechCmd SpeakCommand msg=testing echo speak and the health status is ACTIVE and it works
Again this is to the SAME echo dot.
I dumped the online status, devtype,serial, account,dni and they are IDENTICAL in both cases ….HOW can the same device be INACTIVE for 1 piston and ACTIVE for another? What else can I dump to better understand??
HELP !! Is there ANY chance of getting expert help on this? I don't know how to solve this but this issue is pervasive.... my smart home is so dependent on echo speak but this behavior has me confounded....I've added debug code to help understand but i'm at the point where i don't know what to do next... FOR SOME REASON, many of my standard webcore pistons (telling me door is open, mailbox full,etc) are not spoken and in the logs its says the device is INACTIVE, but I can cause speech from them consistently from a simple webcore piston (pressing a samsung button). What I'm looking for is what can I log about the request that I can compare a good with a bad.....I've dumps several things and they are all the same...there has to be something else in the request that is wrong ......
One last thing...if I pause the webcore piston and restart it, it starts working.....but since echo speak is logging error...i really need to understand the request to echo speak ...below is the same piston working after doing a pause and resume
I suggest you consider posting this issue in either the main Echo Speaks and/or WebCoRE threads, where it is most likely to be seen by users/developers of those applications.