Peter Feerick
Peter Feerick
Well, they do say bigger is better, don't they? 🤠Personally, for us mere mortals... I would prefer leaving the display as is... as I'm not sure having say -32000...
Literally that - some form of Companion support needed. i.e. I guess Companion needs to know virtual sources/inputs exist so when you read/write it doesn't delete them all! ;) On...
There are plenty of instances already where people look away from the model while it is in operation, i.e. even changing settings in flight... We have zero control over that...
Possible, perhaps, but there has not been of any work towards that of late. And that is not pertinent to this PR... which is adding two new types of inputs.
Perhaps you forgot they accept source and integer inputs as part of their configuration? ;) 
This is the same for all radios btw, not specific to the RM Pocket or Windows. It is a hard-coded value that with stock settings shouldn't trigger the battery alarm....
Check the layout of your SD card. In the top level, you should have MODELS, RADIO, SOUNDS, etc. Inside SOUNDS, you should have a two letter directory , eg "EN"....
Any progress / updates on this? Will close issue next week if no new information.
Sounds reasonable. Any further rate limiting can be considered when overhauling Lua APIs... i.e. if it makes sense to put rate limits/other safeguards on Lua functions on top of any...
@JimB40 This would be a perfect time for you to comment re: API documentation ;)