There will be of course situations that some remotes can have more or less buttons or even different button names so the Flirc app itself would need to allow customization of function to button mappings (for example by displaying available functions and providing dropdown with button selection). Flirc app would need to allow selecting a remote profile and app profile pair (or even more pairs if capacity still allows to store multiple mappings). It could also provide default remote button name (from remote definitions). Application definitions would assign a name of function in the app to a key combination (could be in the same format as for record_api). Remote definitions would assign a set of names to hex hashes of IR signals each button creates (with an ability to assign multiple hashes to a single name for MCE/RC6 remotes and other similar) - one file per remote model. There could be two types of ini files: remote definition and application definition. It would be even better if the profile definition could be in some easily editable format like ini, so the community can create new profiles by themselves.
Profile definitions could be defined in some file format loadable by the Flirc software. I think it would be better to remove built-in profiles and ship Flirc with pre-programmed one for XBMC/Harmony setup (if this is main reason for the built-in profiles to exist in the first place).
#FLIRC HARMONY ONE NOT WORKING SOFTWARE#
There are also other problems like for example differences in key shortcuts between software versions - like right now there are differences between XBMC and Kodi so it would require a new Harmony profile with at least some codes different from current one. I know that it allows a fast start if all someone wants is to control XBMC with Harmony (it only requires from the user to set up the Harmony remote with correct profile), but on the other hand it probably takes some space in the flash memory which could be used for some other functionality, given that the micro used in Flirc doesn't have it that much. My friends just roll their eyes at me and deliberately turn my light switches on manually to mess with my automations.I've been wondering if having a built-in profiles in current form is really a good idea. I'm like "why is your light not just turning on when I enter a room?", and "how come I can't turn on your TV, Xbox, AVR, shut the blinds, turn the lights on the room to a different pattern and colour, and turn off the doorbell chime just by saying "Alexa, Game time"? Going to other people's houses now is like when you had one of the first touchscreen phones for a few months and you had to use a friend's phone to do something for a minute and you spent 90 seconds prodding the screen before remembering most people didn't have touchscreens yet.
I've got one that uses geolocation and local network connection to HA to detect if I'm coming in the front door, and if I've been out for more than five minutes then it'll trigger an automation to welcome me home, turn on the lights, turn on the AVR, start the Nvidia Shield, run Plex, and then go to music and play tracks tracks randomly from my library (the Plex server actually runs off of the same server as my HA instance) Luckily I'm single so I can do what the hell I like with regards to automations. Yeah, while the voice assistants are great, and Nabu Casa makes linking then to HA easy, I'd much rather have entirely local voice control.
0 kommentar(er)
