×
Login
Nickname
Password
Login
X Series
U Series
Holiday Announcement
Remote control
Affiliate
Tags
Login
Register
Samsung TV back command not picked up
Purchased the the U1 remote to replace the Samsung TV remote as the back button doesn't work well on it. I successfully set...
botoniiii
U Series
1 year ago
806
1
Strange Remote Issue
My hub is on top of the AV cabinet, with IR cables, controlling 3 devices that are inside the cabinet. I sit approx.6ft fro...
kougei
X Series
1 year ago
712
4
Not sure how to simulate holding number buttons down
On LG WebOS TVs application shortcuts can be created to easily switch between applications by holding down the number butto...
Krusheen
X Series
1 year ago
390
2
Nvidia Shield issues
Many times a week I want to use my shield and the remote won't controll it properly. Sometimes, hitting home a few times wa...
BiGnOsE
X Series
1 year ago
2314
5
Can't seem to control Denon AVR-S760H
The X1 seems to have found the codes ok, and I downloaded them but the power doesn't work. I tried other functions and noth...
bbeckstead
X Series
1 year ago
428
5
Software can't find hub
I got all of my devices in a few days agoand had to spend time to find a good spot for the hub so all of my devices were co...
swandruski
X Series
1 year ago
371
1
Software is a mess
So far I am finding the software for programming the remote to be a mess. Half the time it can't find the hub.
Bcard3170
X Series
1 year ago
554
3
Xfinity x1 cable box does not always work with remote.
My brand new X1 remote has some trouble controlling the xfinity cable box. It was so inconsistent that I assumed that the r...
Bcard3170
X Series
1 year ago
1484
6
EVPad and Sony XBR4
I'm considering to purchase the X1 and wanted to know if this has been trialed to work on an evpad (an android based tv box...
jrlee53
X Series
1 year ago
609
3
Arris VIP5303
Hi, This TV decoder has been found in SofaBaton X1 database, uploaded, but no response at all from dedicated buttons, nor l...
HarryO
X Series
1 year ago
785
7
1
...
116
117
118
...
181
Most Popular Articles
1.
2022.9.9, Major Update of Android APP ,HUB
2.
【Tutorial】 X1 User Guide and FAQ, Continuously Updated...
3.
X1 Hub Upgrade Already!
4.
How to program macros?
5.
What I learned about the U1 (edited)
6.
Major Advancement: X1 Hub firmware version V15 is here!
Latest Release
1.
Adding IR devices to database by support
2.
Bug in firmware version 5 of the X2 hub
3.
Need the ability to activate another activity
4.
Slow command repeat delay on X2
5.
Ziggo media box Next
6.
Searching for Phillips Hue Bridge
Latest comments
Does anybody from Sofabaton reading these posts?
P.s. I've also seen devices give up and think you've stopped your sequence because Sofabaton is taking too long
This forces a sequence that in Harmony could execute in half a second total, but Sofabaton takes about three. For another sequence, Sofabaton takes 12 seconds where harmony would do it in 3
Confirmed It's annoying especially if a device only has discrete power off command and not discrete power on. The Sofabaton will send a repeat of the power-toggle command even when it doesn't need to. Harmony remembered which devices were on and which were if and only triggered the on or off events if the device was new or not needed for the next activity or power state
Agreed Input switching is also impacted in nearly identical way. If I've configured a device to one of the two indirect methods of switching inputs using a menu and then arrow key presses, or repeated press of the same input button then Sofabaton gets confused if the same device in both current and next activity. That happens even if the "when device starts" correctly to the top of the list, and "normally press" correctly to remember last input. The issue is that when switching the activity Sofabaton forgets the last input, but because device powered for both before and after it's actually remembered. Sofabaton then starts counting again from the top and mucks things up. Also there's something wrong with the starting from 0 position logic. I can't quite put by finger on it, but when directly testing inputs using the fix command, if the targeted input is above the current input, Sofabaton tries to go off the bottom but miscounted the 0 item (which is actually first in the list). I think they need to get rid of the zero, and think carefully about the remembered last state and start from top settings
I would appreciate if somebody can test it with his system. I would like to know if it’s only related to my hub or if that is a common issue. Thank you very much, greetings from Germany.