Daniel

Ah, unbelievable! That really works! I wonder if that button wasn't there when I fiddled around with this or if I simply missed, I remember going through all buttons that could be remotely related. Thanks a lot, finally this paperweight is usable! Next problem is the lack of a dedicated pause button, really need that one. But that's material for another thread :-) /Daniel

Just checking back a few months later... Is this something that will ever be fixed or would I be better off just putting this piece of hardware in the trash right away? Or am I asking in the wrong place?

Absolutely, that would solve the problem for me too. I did some digging in the forum into how to do it but I never solved the problem myself, so my remote has now half a year later never been used at all.

Hi again. I never succeeded in solving this myself and never got any answers, so my remote has been a paper weight now for three months. Is there any way of adding own buttons coming?

Anyone got any input here? Without the back button the remote is kinda useless...

This is weird, I responded to this just minutes after you wrote it, but my respons is nowhere to find now... Anyway, this solved it for me! Now my remote connects just fine! Well done! Have you got any use for my logs? flirc_devicebroker-7_6_2023.log flirc20230706.log

Hi. I'm setting up my new remote with my Philips 50PUS7906. Everything seems to be working quite well out of the box (after finally being able to start the app, thanks!), but I can't seem to get the back button working. I'm kinda guessing which model is the correct. "Code Group 1" doesn't work at all, "Code Group 3" and "Code Group 4" both entirely seem to lack any back button, so the best shot seems to be "Code Group 2" which has one, but it has no effect on my TV. All other keys I've tried are working fine. Any ideas what to try next?

This is a laptop that I turn off every evening, so it seldom runs longer than over the day.

Ok... Something changed, now it's actually saying "Successfully lifted device restriction". However my plugged in remote still doesn't turn up in the app :-/ flirc_devicebroker-7_1_2023.log flirc20230701.log

I'm sorry guys... No luck... New logs attached... flirc20230630.log flirc_devicebroker-6_30_2023.log

Attaching log. flirc20230629.log

Yep, new logfiles attached. (just a parenthesis: The forum software doesn't seem to like links with URL parameters in them, only the part up to the question mark is clickable. Works fine when copying and pasting the url though.) flirc20230629.log flirc_devicebroker-6_29_2023.log

Yep, the computer is running FortiClient antivirus. Unfortunately it's an enterprise solution that I have no control over so I can't try without it. I might be able to get a specific exe file whitelisted if that might help?

Yep. I'm glad I mostly live in Linux land, that really seems like a nightmare :-D With this version I got two log files and no errors in the console. Attaching the files and pasting console output below: LoggerShouldSendAppServiceMessages = True LoggerShouldWriteToFile = True GUID_DEVINTERFACE_HID = 4d1e55b2-f16f-11cf-88cb-001111000030 flirc20230628.log flirc_devicebroker-6_28_2023.log

Ok. The console window didn't say much, it's just complaining about a non existing directory (I don't know if the problem is that the folder is in reality named SkipApp_sddpyax1dmvqm, not SkipApp_vg5akken3mtem?). Pasting the output below and attaching logfile! r-6_28_2023.log, Reason: Could not find a part of the path 'C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log'. Logger::Print failed for file C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log, Reason: Could not find a part of the path 'C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log'. Logger::Print failed for file C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log, Reason: Could not find a part of the path 'C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log'. Logger::Print failed for file C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log, Reason: Could not find a part of the path 'C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log'. Logger::Print failed for file C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log, Reason: Could not find a part of the path 'C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log'. Logger::Print failed for file C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log, Reason: Could not find a part of the path 'C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log'. LoggerShouldSendAppServiceMessages = True Logger::WriteLine failed for file C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log, Reason: Could not find a part of the path 'C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log'. LoggerShouldWriteToFile = True Logger::WriteLine failed for file C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log, Reason: Could not find a part of the path 'C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log'. GUID_DEVINTERFACE_HID = 4d1e55b2-f16f-11cf-88cb-001111000030 Logger::WriteLine failed for file C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log, Reason: Could not find a part of the path 'C:\Users\damal08\AppData\Local\Packages\SkipApp_vg5akken3mtem\LocalState\flirc_devicebroker-6_28_2023.log'. flirc20230628.log

Ok. Well, tell me if there's anything more I could test. I'm in no hurry to get it working and being a systems developer I know how infuriating this kind of problems is :-D

My Steam isn't started. It's not in any autostart and in fact I haven't started it in months. I guess I could simply uninstall it completely if it would help in the investigation? And about the privileges requester, yes I grant it again and again. Also tried not granting, which made no difference.

Well, no matter how I try I can't seem to run it as administrator, there's no such choice in the right click menu. There are for normal programs, but not for "apps" (never really understood that strange difference). Anyways, I got a log out, hope it tells you something! flirc20230627.log

Exact the same behaviour here, only I'm on Windows 10. The SkipDeviceRestrictionBroker alert pops up once every ten seconds or so but no detection of the remote. I also have Steam software installed.