Meiku seems to close connection

[sirmeili]

Think I am having the same problem. Log snippet below:

Feb-24 7:51:22 PM MeiKu There was a problem trying to get the active app at location http://192.168.1.61:8060/. Error: The operation has timed out
Feb-24 7:51:17 PM MeiKu There was a problem trying to get the device info. The operation has timed out
Feb-24 7:51:12 PM MeiKu There was a problem trying to get the active app at location http://192.168.1.61:8060/. Error: The operation has timed out
Feb-24 7:51:08 PM MeiKu There was a problem trying to get the device info. The operation has timed out
Feb-24 7:51:02 PM MeiKu There was a problem trying to get the active app at location http://192.168.1.61:8060/. Error: The operation has timed out
Feb-24 7:50:48 PM MeiKu There was a problem trying to get the device info. The operation has timed out
Feb-24 7:50:43 PM MeiKu There was a problem trying to get the active app at location http://192.168.1.61:8060/. Error: The operation has timed out


This was going on for about 20 minutes until I stopped the Meiku plugin and restarted it. The Roku was fine. The regular remote control had no problem with it.

I've turned on debug logging to try to capture more detail the next time this happens. This happens about 1 out of 3 times that I attempt to use this plugin.

As soon as you can get it I'll check it out. Thanks!

sirmeili were you working on a rewrite of this plugin?

I am and it's all but done. I'm just running some tests as I touched about every piece of code. This was my first plugin so I did have some newbie mistakes.

Sent from my Pixel 2 XL using Tapatalk

sirmeili were you working on a rewrite of this plugin?

[jayph]

Think I am having the same problem. Log snippet below:

Feb-24 7:51:22 PM MeiKu There was a problem trying to get the active app at location http://192.168.1.61:8060/. Error: The operation has timed out
Feb-24 7:51:17 PM MeiKu There was a problem trying to get the device info. The operation has timed out
Feb-24 7:51:12 PM MeiKu There was a problem trying to get the active app at location http://192.168.1.61:8060/. Error: The operation has timed out
Feb-24 7:51:08 PM MeiKu There was a problem trying to get the device info. The operation has timed out
Feb-24 7:51:02 PM MeiKu There was a problem trying to get the active app at location http://192.168.1.61:8060/. Error: The operation has timed out
Feb-24 7:50:48 PM MeiKu There was a problem trying to get the device info. The operation has timed out
Feb-24 7:50:43 PM MeiKu There was a problem trying to get the active app at location http://192.168.1.61:8060/. Error: The operation has timed out


This was going on for about 20 minutes until I stopped the Meiku plugin and restarted it. The Roku was fine. The regular remote control had no problem with it.

I've turned on debug logging to try to capture more detail the next time this happens. This happens about 1 out of 3 times that I attempt to use this plugin.

[goldriver]

It could be something in the PowerOn. Are you sending it as a command string manually or sending it as a normal command? I added PowerOn and PowerToggle to the control device a couple of weeks ago.

If you are sending it as a command string, can you try using the command devices' command?

I don't have my RokuTV yet (I'm waiting for the 2018 TCL models to be released in May). I am sending a WOL command before the PowerOn, but that is the only difference I could think of. I wonder if the WOL command is somehow messing with your Roku TV (I assume at this point it's a roku TV, right? Normal roku's don't power On).

If you could: turn on debugging in the settings (checking the box) and then wait for the issue to happen. Once you know it's happening, you can stop the plugin and send me the MeiKu.log log file from the /Logs directory in your Homeseer install directory. If it spans over 1 day, there will be multiple files., just send me the ones for the days where the issue occurred.

you are right, I have a Insignia RokuTv and i am sending from a string, I turn on the debugging and you can find the debug file attached.

I will try to figure out how to send using command devices and see if the problem persist

edit: I set the event to send command, I will see how it behaves
edit 2: so far so good, it looks like when I power on from the command instead of strings the plugin does not start looping

[sirmeili]

It looks like when i send a PowerOn string from an event to the roku tv, after that the plugin seem to lose the ability to contact the device after XXX seconds.

It could be something in the PowerOn. Are you sending it as a command string manually or sending it as a normal command? I added PowerOn and PowerToggle to the control device a couple of weeks ago.

If you are sending it as a command string, can you try using the command devices' command?

I don't have my RokuTV yet (I'm waiting for the 2018 TCL models to be released in May). I am sending a WOL command before the PowerOn, but that is the only difference I could think of. I wonder if the WOL command is somehow messing with your Roku TV (I assume at this point it's a roku TV, right? Normal roku's don't power On).

If you could: turn on debugging in the settings (checking the box) and then wait for the issue to happen. Once you know it's happening, you can stop the plugin and send me the MeiKu.log log file from the /Logs directory in your Homeseer install directory. If it spans over 1 day, there will be multiple files., just send me the ones for the days where the issue occurred.

[goldriver]

The plugin doesn't maintain a connection to the roku. It polls it at a regular interval. Mine is set to every 10 seconds.

Those messages are telling you that the roku is not responding in time. I will look into making the timeout configurable so you can try and account for network congestion.

If you get in a loop like that and it's killing the CPU, I'll have to look into it. The plugin only has a timer to run the check for the current app, if it fails it doesn't attempt to do it again. I would check for any events that might be calling the plugin in rapid succession.

Edit: also note that 4 of the 6 log entries above are for sending a keypress or command to the roku, not it's normal polling. This is what makes me think it could be an event causing it.

You are right this is called from an event but the issue is not coming from a recursive call, it looks like the plugin for some reason I can’t understand fails to contact the Roku tv and get the active app and from then it starts looping and the only way to stop it is tondisable the plugin.

It looks like when i send a PowerOn string from an event to the roku tv, after that the plugin seem to lose the ability to contact the device after XXX seconds.

[sirmeili]

Hi I am trying to use the meiku plugin to turn on - off a Roku tv on alarm events to see my cameras.

It seem to work reaticaaly, sometime it is working and sometimes it start to loop with the following messages over and over almost killing the CPU, the only way to stop it is to restart HS3

http://192.168.1.9:8060/

Any way someone have a clu on the issue ?

The plugin doesn't maintain a connection to the roku. It polls it at a regular interval. Mine is set to every 10 seconds.

Those messages are telling you that the roku is not responding in time. I will look into making the timeout configurable so you can try and account for network congestion.

If you get in a loop like that and it's killing the CPU, I'll have to look into it. The plugin only has a timer to run the check for the current app, if it fails it doesn't attempt to do it again. I would check for any events that might be calling the plugin in rapid succession.

Edit: also note that 4 of the 6 log entries above are for sending a keypress or command to the roku, not it's normal polling. This is what makes me think it could be an event causing it.

[goldriver]

Hi I am trying to use the meiku plugin to turn on - off a Roku tv on alarm events to see my cameras.

It seem to work reaticaaly, sometime it is working and sometimes it start to loop with the following messages over and over almost killing the CPU, the only way to stop it is to restart HS3

http://192.168.1.9:8060/

Any way someone have a clu on the issue ?