Jilas671
Members-
Posts
98 -
Joined
-
Last visited
-
Days Won
10
Jilas671 last won the day on January 15
Jilas671 had the most liked content!
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
Jilas671's Achievements
-
Manhattan T4-R remote codes?
Jilas671 replied to Reiterate1430's topic in Supported Devices / Databases
@teoformartel no worries I had recently just found those files after tidying up my nas, hence the quick reply. The assumption earlier was the the T3 and T4 may use similar codes hence the op original questions. So my raw files codes should be convertible. Quick Google I found this GitHub post. https://github.com/crankyoldgit/IRremoteESP8266/discussions/1845 Not tried it, but if this works, I'd compare one known code and hopefully you'll get the result you need. That said I did a bit of searching and also found this. https://manhattan-tv.com/support/manhattan-t4r/your-t4r-remote/pair-your-t4r-and-remote-to-prevent-interference-with-other-manhattan-devices So the plus is the codes are good if using the universal channel 0 or channel 1.. on the Manhattan but if that got changed then I guess that's when the 'fun' starts. I wish you luck, if anything from the t3 is useful happy to look further. -
Manhattan T4-R remote codes?
Jilas671 replied to Reiterate1430's topic in Supported Devices / Databases
The only other file I have, is the conversion of the first file by Jason. Uploaded in case that is of use as well. Looking back, those two files actually form this file. The missing codes I posted above, I don't have any updated/converted versions. I hope between the 3 files and the codes posted you get what you need. Manhattan T3-R v1.json -
Manhattan T4-R remote codes?
Jilas671 replied to Reiterate1430's topic in Supported Devices / Databases
@teoformartel I'm assuming you want the raw files I initially sent over for the T3 remote. Somehow when I did it initially I missed a couple hence its spread over two files. Hope they help. Manhattan T3-R Remote IR Codes.txt Manhattan T3-R Remote IR Codes pt2.txt -
Manhattan T4-R remote codes?
Jilas671 replied to Reiterate1430's topic in Supported Devices / Databases
@jason This might be why I got confused. But looks like the sorting of the forum by "most recent" seems to be ignoring the year. Hence I picked up this post a year later, checking other posts, it's a mix of 2023, 2024 and no date (2025?) dated posts. So maybe a bug in Sort by code as seems to be present across the forum. Sharing in case you were not aware. -
Manhattan T4-R remote codes?
Jilas671 replied to Reiterate1430's topic in Supported Devices / Databases
And now just seen it was a year ago. Doh! -
Manhattan T4-R remote codes?
Jilas671 replied to Reiterate1430's topic in Supported Devices / Databases
Using Flirc app, and its IR debugging. Below are the resulting codes. I hope once processed these work with th T4 (Happy to test it with the T3). Programme Up -875000 +9008 -4435 +596 -493 +540 -1662 +540 -1663 +592 -496 +592 -1610 +596 -492 +595 -494 +596 -497 +540 -555 +588 -494 +594 -495 +594 -493 +598 -491 +540 -1663 +594 -494 +540 -553 +596 -492 +595 -1607 +597 -1606 +597 -492 +596 -492 +595 -1607 +597 -491 +596 -1611 +597 -1605 +597 -491 +597 -1605 +597 -1605 +597 -492 +597 -1605 +597 -1606 +597 -496 +598 -43000 +9003 -2195 +598 Programme Down -5001000 +8998 -4445 +596 -493 +595 -1607 +596 -1606 +595 -504 +585 -1606 +595 -494 +595 -493 +539 -554 +596 -492 +595 -493 +596 -492 +596 -492 +596 -492 +597 -1605 +597 -492 +596 -497 +597 -491 +597 -1605 +597 -1605 +597 -491 +597 -1606 +597 -491 +597 -1605 +597 -1610 +598 -490 +598 -1606 +597 -491 +598 -1605 +598 -491 +598 -1604 +598 -1605 +599 -495 +598 -43000 +9000 -2195 +599 -
Manhattan T4-R remote codes?
Jilas671 replied to Reiterate1430's topic in Supported Devices / Databases
@jason @Reiterate1430 Only just saw this, but I can check and scan the programme up/down from my T3 if it helps. Surprised it wasn't in the file I did the last time, no idea how it got missed it. I'll try and remember how and do this over the weekend if it helps and upload what I get. Let me know if there is any other key that is missing. -
So to follow up the app issues. Somehow I had two version of Skip installed.. Cleared both as the older one was causing the usb issues (but did do the extra update needed I found in another post). Finally found the post about how to force a firmware update Center button + return with no battery (as couldn't find a download etc). So I now have 4.13.11-0-gd3238fe firmware and rc/0.9.993.9063 installed and no toggle features in play/pause or mute. And I would assume as this version is greater than 0.9.984 it should work? for info the later release of 993 (27th Nov), just crashes. It might be useful to break down what the differences are between the channels, and how we can force them to change. And on old bugbear... when doing a fresh install, can we have a button to let use import a remote vs having to create one, add a device, then do the import. Beyond the why is this not working. Perhaps we need a central single post, that has the link to the current app, how to firmware update and how to fix usb connection issues for windows. EDIT: Not sure what I did but now the extra options for Play/Pause/Mute have appeared. Confused. Not sure if it was an issue with importing information, and the app needed a restart. So for now thats ok. Will test it.
-
Firstly thanks for coming back and confirming the situation with new products and support of the 1s, I totally get the need to work on the next products, but equally I'm sure you understand the concern, of what does this mean for the orginal devices and their support. Given your team size, and how little time you do have, you can understand the concern if you are now looking at the future and what this means. Glad the macros on activity vs power is still in the pipeline, as said before this is a show stopper for my household. The Play/Pause thing, I missed that post, but I had checked the app before posting, and it wasn't present, it was updated to 0.9.993 so assumed as its later it should have it. Now checked tried all the channels, and not seeing it (I so wish when you switch from Beta to Regular it would force download/install vs waiting until the new channel changes). So unless the app is aware of the firmware version of the remote, something isn't working in these later versions (the links to 0.9.984 are not working and get a XML report saying AccessDenied, so I can't try that). Not been able to update the remote (if I could find the firmware link), as app in windows 11 won't connect to the remote again. I'll check on that in a bit from the previous posts about not connecting. Indeed I did mean the colour button as a shift, so less used commands could be assigned to more keys (say 0-9). This is a desirable if you have say have special controls for amp settings, lights or environmental controls.
-
Just saw a post from Sunday, that there is a Skip2s in development?? So what does this mean for the Skip1s requests and issues, and various promises made to improve that still on the to-do list, to name the top 3 I had. - Macro controls on the activity buttons instead of the Power button. - Play/pause - how to deal with remotes with two codes (e.g. long press idea). - Expanding the colour wheel, to include more keys. Given the post linked below, I think some details as to the focus on development, especially given how long we have waited on these improvements. With any new product they bring issues (they always do), so it is a natural concern that Skip1s will at best just get minimal support now and it could get worse. For someone with their units still in boxes from kickstarter, and these first 2 show stopping issues, I feel let down and not sure how I feel about hearing about this in a random one liner not even in the Skip forums. So some simple yes/no answers would be useful at this point considering how long some of us have waited, and we need to understand the impact of a new product - do you now have new staff dedicated to this job, or is it eating into the development/update time on the Skip1s.
-
Good question, currently (unless things have changed), you basically need to assign another key to make this happen. It's been stated they have an idea where, you can long press a button to run a second command or I think toggling between codes e.g first press - sends on, next press sends off... but this could get weird if you are playing and power off.. personally not sure about this, the press hold would work better and should be easier to code. I only have one device with this issue, but agree would nice to get an idea if/when this will get added.
-
This one feature is all I need to make these units useful. As it stands, the two I have, have been unused (beyond occasional testing) since I backed this. While I know the windows app stability has been a royal pain, this is a firmware change, and hopefully a smaller adjustment to the app than dealing with all the usb/windows issues I know Jason and the team have faced. It would be useful to get an idea when this feature will get added if at all.. As if not, then I may as well try to get some money back and sell my near mint units on ebay and hope someone that didn't come from a harmony world and are ok about the switching setup where switching modes does nothing, and you still needing to press another button to run a macro to activate the modes it should be controlling. It's a shame as the hardware feels nice.
-
@jason thanks for coming back with a response on this and sharing a detailed response it's much appreciated. I'll drop a Pm over in a bit on just some thoughts in case they help. Again thanks for everything you and the team are doing, it's not easy when there are so many moving parts.
-
I note the test version we had lost the update channel, so had to go back to a earlier release and update and have 0.9.966 beta now installed. With the service re-enabled. Fire it up first time, it didn't work was a bit odd (may have been me). Did create the remote, skipped passed the add device stuff so I could just do a restore (an option for this at the start might be good, especially as it seems you can detect if the remote is new or has been updated). So tried a second time, this time it did bring up the pop up after the remote was detected and sync was tried. Get the previous windows permissions error then your new pop up with the download link, used that installed the "fix". Checked the services it does disable it correctly - some of the messages are kinda worrying, (I think deleting usb devices .. was a fun one to see). When complete return to the app. Remote is picked up, and could sync. Swapped remotes, picked up the second one ok, (as a fresh install) tried to skip past the setup which locked the app up, needed a restart to clear that. Came back to the blank second remote, imported the config ok. Remote connects (doesn't offer a sync this time). Swap them over again the app swaps to the other remote correctly. So looks like this is all working to fix the usb/logitech/steam issue. Thanks for getting it included and working. Can I dare ask if there will be an update or a roadmap for the remote and things we can expect (no dates, or order) just so we can see what's hopefully coming at some point. Just my remotes are still in their boxes waiting for some key changes and would be at least nice to know these are still planned and will appear at some point (time etc permitting). Happy to post or message you a list of what I'm hoping for and you can confirm yes/maybe/no if easier.
-
No problem, just good timing on when you posted. I guess you expected the new app, to block the skip software from connecting, in a similar way that the logitech service does. And I guess that proves you can grab sole control over the remote when they are plugged in without asking for extra permissions. Very happy to test any versions as you need (timezones permitting of course will depend on the speed of the answer). PS those commands I mentioned are one of the worst case options, next to doing it manually in the service panel, they just need sticking in a batch file (or run from a command prompt) as long as it has admin privileges - it will just stop and then block the service.