AQL-PS-8 Remote Emulator App

Jump to latest Follow Reply
This is the code for the filter button. See if you can send it:

100200028000800001141003

Also, with the app, see if you can try pressing one of the buttons multiple times in a row and see if it works at all. Sometimes when the timing is off, you can sneak in a command at that right time. It just might confirm it is a timing issue.

Should add the above may only work without the script loaded.
 
mas985 said:
It should be sending the same codes as what the local controller does. The only thing I can think of is the timing is different with that controller.
Click to expand...
I do appreciate the help so far. Is there something I can try through the monitoring app on sending, or other ways to adjust timing and see if I can get something to stick? Probably time for me to make some attempts on my own, or validate that the EW11 is receiving the signal and it is getting discarded prior to sending to the board
 
I replaced the script with a modified one.. changed these variables.
TIME _GAP = 6
KA_NEXT_TIME = SYSTIME + 60 - TIME_GAP
DT= DT+60

and IT WORKED! Have seen a few times where I had to click again on the windows app, but haven't had a total failure again!


EDIT - removing script - note to future readers this was all in error as response to my missing a field to be updated on the EW11 configuration!
 
Last edited:
  • Like
Reactions: mas985
The script uses the keep alive for timing purposes and I did some timing measurements from my unit and they come in at 100 ms intervals which is why I used 100.

I would keep gap time the same at 10ms as that is for margin. For the other try 50 and 200.
 
mas985 said:
The script uses the keep alive for timing purposes and I did some timing measurements from my unit and they come in at 100 ms intervals which is why I used 100.

I would keep gap time the same at 10ms as that is for margin. For the other try 50 and 200.
Click to expand...
strangely, I think I got purely lucky with the 6/60. going to 5/50/100/200 or 10/50/200, and even other small changes around the 6/60 seem to make it worse.

I can deal with a bit of repeated sending if necessary.
 

Enjoying this content?

Support TFP with a donation.

Give Support
One more thought.

Is the clock on your P4 constantly running fast or slow? How many minutes per day/week? There have been reports of the clocks going bad on some models and this could explain why the original script does not work. If the internal P4 clock is shifted, the keep alive internal could be shifted as well.

Anyway, I will update the other app platforms. Should be ready by tomorrow.
 
I do think it drifts fast on clock, but not super bad (ie.. I adjust seasonally to correct). My device is the EW-11A, which I understood was just acceptance of 5-36V vs 5-18V.

Here's a snip of my setup screen. Confirmed iOS app works!
 

Attachments

  • ew11 config1.JPG
    ew11 config1.JPG
    82.3 KB · Views: 2
  • ew11_home screen.JPG
    ew11_home screen.JPG
    39.2 KB · Views: 2
That all looks good. I still can't explain why the timing is different on your unit.

But I did some sensitivity testing on both the gap time and interval time and if I change by 1 in any direction, things get worse so you might want to change those parms by 1 in each direction to see if things improve. It is very sensitive to timing.
 
Also, on the setup detail page, what do you have for Gap Time?

595_luT8FfkaHgI0yeL4wDle51kx1EwAnQav8YNKSdcgOPJpnSpfuhIo-SlCrXb0sH_xLnw2tM4dJ-sTJ6NpERvBBZEIMimWjQvn7Ky-k_18bDQ10G7kxd_r0eDepcZ-OetFaai1zeo2-2a8PH91ULk
 
  • Love
Reactions: elizb
Shoot! I had Gap Time at 50. I apologize.. Guess I missed that while focusing on loading the script.
Changed to 10 - original script works now (and better than my modified one).

Where do I send the thank you?
 
  • Like
Reactions: mas985
Hey Mark,

Thanks for creating this app. I have the Android version install and it's works well. I also implemented the Home Assistant version from the thread you referenced. It's working good for reading data, but the switches are not reliable (if they work at all). A lot of people in that thread said wireless didn't work well and most switched to wired. It would be difficult for me to do that, so I want to get wireless working. That's what brought me here.

Your app is working over wireless so I'm curious what you're doing different than the Home Assistant Python code. I see that you use a script on the ew11 and I'm wondering how you're using that or what you're doing. I'm not a Python developer, but I'd like to try whatever you're doing. Any help would be appreciated.

John
 
The script in the EW11 handles all the key presses to manage timing. It also handles the device reset and unlocking the configuration menu. All require special handling.

Are you using the EW11 for the HA? If so, it should work. You may just need to remove any timing handling in the HA software to prevent any interference.

What controller do you have?
 
mas985 said:
The script in the EW11 handles all the key presses to manage timing. It also handles the device reset and unlocking the configuration menu. All require special handling.

Are you using the EW11 for the HA? If so, it should work. You may just need to remove any timing handling in the HA software to prevent any interference.

What controller do you have?
Click to expand...
I have a P4.

So your script is managing all the key presses and timing? Interesting. I wonder if you script is overriding what HA is trying to do? Might need to test without your script and see what happens. I'm not a Python developer, but it looks like a good bit of the code is build around the timing. not sure how easy it would be to strip out.

I attached the core.py code that is using. There's other code, but that's where the most things happen.
 

Attachments

  • core.py.txt
    25.1 KB · Views: 1

Enjoying this content?

Support TFP with a donation.

Give Support
You must log in or register to reply here.
Top Bottom
Back
Jump to latest Follow Reply