Jump to content
Flirc Forums

Skip 1s Firmware v4.12.11-beta


jason

Recommended Posts

On 3/3/2023 at 12:41 AM, infrb said:

Seems to happen when I'm switching from activity B to A. 

Attached is my latest config (made some slight changes since the last one I uploaded).

Steps:

- Hit B

- Hit Power to turn activity on and let macro complete

- Wait about 5-10 seconds or so

- Hit Power to turn off activity B

- Wait about 5-10 seconds or so

- Hit A

- Hit Power to turn on activity A

TV does not turn on.

 

Living Room.skip 542.49 kB · 1 download

I added a bit more logging, when this happens, can you plug in, dump the log, and pass that my way?

Thank you.

skip.1s.a06.release-4.12.11-7-g0113c.bin

Link to comment
Share on other sites

I had to enable the admin tab, which I didn't know how to do. Luckily I found the config.json file in another thread.

Here's the log, though in looking at it, I don't know how useful it is. Activity button presses aren't being captured in the logging. I would expect that if I hit A, B, or C, that it would show in the log. I also don't see what commands are being sent to the TV, only button presses.

In order to get the button presses to show in the log, I had to have the remote connected to my laptop and hit refresh after. If I repro'd the issue without it being connected, then connected afterwards, I never got any logs. 

Luckily this is a pretty easy repro and happens consistently. What's interesting is that when looking at the IR blaster via my phone, the A activity is sending a signal. The TV just isn't receiving it. I wonder if the remote is somehow sending a different command or something. 

Also, if I start with activity B, power off, Hit C, then Power on, that works fine. It's only when going from B to A where I see this problem. So strange.

flirc-remote-control20230305.log

 

Link to comment
Share on other sites

53 minutes ago, infrb said:

I had to enable the admin tab, which I didn't know how to do. Luckily I found the config.json file in another thread.

Here's the log, though in looking at it, I don't know how useful it is. Activity button presses aren't being captured in the logging. I would expect that if I hit A, B, or C, that it would show in the log. I also don't see what commands are being sent to the TV, only button presses.

In order to get the button presses to show in the log, I had to have the remote connected to my laptop and hit refresh after. If I repro'd the issue without it being connected, then connected afterwards, I never got any logs. 

Luckily this is a pretty easy repro and happens consistently. What's interesting is that when looking at the IR blaster via my phone, the A activity is sending a signal. The TV just isn't receiving it. I wonder if the remote is somehow sending a different command or something. 

Also, if I start with activity B, power off, Hit C, then Power on, that works fine. It's only when going from B to A where I see this problem. So strange.

flirc-remote-control20230305.log 1.33 kB · 1 download

 

This was helpful. I’ll add more soon. 

  • Like 1
Link to comment
Share on other sites

Just wanted to give a very positive update and thank Jason and the team for their work on this.  Running the 4.2.11 firmware and latest app 0.9.66.5722 both my remotes are highly functional now.  The Power Up and Power Down macros are working and my set of devices are all able to be controlled.  I can see lots of cool features being added in the future and making it more like the Harmony remotes possible in the future with more updates.  Right now, I think the important base pieces are getting there.  The only issue I still have is both the remotes going unresponsive.  I know I posted in another thread a while back about it and there are other threads where this is mentioned.  I can't figure out a pattern to it but you will just go to use it and hit any button, no LEDs light up but around 10 seconds or so it is back to normal.  This may be happening a lot but you don't notice it because sometimes you don't need the remote.  I am not sure if it is triggered by a button push or it is just happening on a timed basis.  I have had it happen back to back in pretty shortly timed basis but this is not common.  Any ideas to help isolate it and then maybe give you logs or is this already being worked on?

Edited by virtualshock
typo
Link to comment
Share on other sites

23 minutes ago, virtualshock said:

Just wanted to give a very positive update and thank Jason and the team for their work on this.  Running the 4.2.11 firmware and latest app 0.9.66.5722 both my remotes are highly functional now.  The Power Up and Power Down macros are working and my set of devices are all able to be controlled.  I can see lots of cool features being added in the future and making it more like the Harmony remotes possible in the future with more updates.  Right now, I think the important base pieces are getting there.  The only issue I still have is both the remotes going unresponsive.  I know I posted in another thread a while back about it and there are other threads where this is mentioned.  I can't figure out a pattern to it but you will just go to use it and hit any button, no LEDs light up but around 10 seconds or so it is back to normal.  This may be happening a lot but you don't notice it because sometimes you don't need the remote.  I am not sure if it is triggered by a button push or it is just happening on a timed basis.  I have had it happen back to back in pretty shortly timed basis but this is not common.  Any ideas to help isolate it and then maybe give you logs or is this already being worked on?

I’m going to fix this. I’ve reproduced it twice but I am working out a log that will diagnose it. 

  • Like 3
Link to comment
Share on other sites

  • 2 weeks later...
On 3/8/2023 at 7:14 AM, jason said:

I’m going to fix this. I’ve reproduced it twice but I am working out a log that will diagnose it. 

I just wanted to say that I've been working incredibly hard on a way to log the event. I have something working that I'll post soon. Hopefully we can narrow down the cause for the hang.

Link to comment
Share on other sites

3 hours ago, infrb said:

Thanks, Jason. We're still seeing this, not a huge deal as it resolves itself, but definitely annoying. 

Try the attached, when it happens, post the log. I still need to add more, but this might help. A second crash and a second log will be helpful too. Thank you so much.

skip.1s.a06.release-4.12.11-13-g042dc+.bin

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...