I’ve built a Homey app for a vast ammount of internet radios. The app connects your radio directly to Homey over your local network — no cloud required. Any internet radio based on the Frontier Silicon chipset that is compatible with the UNDOK or OKTIV app is supported. This includes radios from brands such as Kenwood, Hama, Medion, Revo, Roberts, Ruark, and many others.
Features
Automatic discovery of radios on your local network
Control multiple radios independently
Turn on/off, select source, select preset
Volume control (set, up, down, mute, unmute)
Playback control (play, pause, next, previous track)
Now playing information: source, station name, song and artist
Full Flow integration
Setup
Install the app, go to Add Device and select UNDOK / OKTIV radio. Your radio will be discovered automatically. If your radio uses a non-default PIN, change it in the device settings after pairing (default PIN: 1234).
Feel free to ask questions, report issues or share feedback in this topic!
Kind Regards,
Tim
edits: typos and removed dutch language as requested
I don’t own an Android device and/or an OKTIV operated radio. But I did a small investigation just now: OKTIV is also developed by Frontier Smart Technologies and supports newer Frontier Silicon / Venice X based radios running firmware 4.2.4 or newer. Older devices typically use UNDOK instead.
My app is built around the Frontier Silicon local network API, so there’s a good chance that OKTIV-compatible radios will work as well. However, I haven’t been able to test this since I don’t own an OKTIV-based device.
If your radio is discoverable on the local network and exposes the same API, it should work. I’d definitely be interested in feedback if you try it.
I would appreciate if you would test the functionalities of the app with your radio. If proven OK, I will definitely change the name of the app as you suggested.
Note: there’s one THEN-flowcard that doesn’t work as expected. It’s the “set relative volume to x” card. This card is automatically added by Homey when it detects a ‘volume’ as capablility. I’m investigating why it doesn’t work as expected and/or if I can fix/disable/remove that card.
Note2: the normal “set volume to”-card works just fine.
Better keep the wife happy. WAF should be as high as possible.
I believe (partially an assumption) the “set relative flow card to x” should set the volume relative to the volume that is currently set.
Example: If the current set volume is now 40% and you trigger “set relative flow to 50%”, the outcome should be 20% volume (50% of 40%).
The behavior with my Kenwood M-7000-S is that it just sets the volume to 50%. Which is the same behaviour as the ‘normal’ flow card"set volume to x%"
Indeed the WAF is so important.
It now took me 10 minutes to explain that using the device has been simplified (got rid of IR device, Virtual device, Power Meter and 2 logical states).
Now for my tests, the relative volume card does not work like that.
I had set the volume to 14%, then created a simple flow, when started, set relative volume to 25%.
When this simple flow ran, the volume went up to 25%. So that is the same behavior you see.
I also saw a completely weird behavior when using the combined TurnOn, Source, Preset, Volume card turns the radio into a state, that it is turned on, but keeps switching on volume and source. Or so it appears, I have to do some more investigation probably.
I have now solved it like this, which works flawlessly.
Just thought of something, would you be able to change settings of the radio?
Or are you completely limited to the capabilities of the Undok/Oktiv app?
Would be nice to have a flow that changes the DST setting twice per year automatically,
DST setting is not available in the FSAPI used by Frontier Silicon. So it’s something in the firmware of the radio itself. I too find it frustrating that Kenwood does not switch to DST automatically.
The combined flowcart (on+source+preset+volume) works fine for my Kenwood M-7000-S devices. However, I will spend some time on making this function more robust today. Probably this evening (CET).
I think there are two possible outcomes:
If it works, great!
If I don’t get it to work, I might remove the card alltogether if that means the app will become OKTIV compatible. As you have shown in your flow example, it works just fine using seperate cards in succession.
Thanks to @Twan_Veugelers I discovered that radios controllable with the OKTIV app (iOS and Android) might also be compatible with the UNDOK Homey app. Together with Twan tests were done and this proved to be true!
As of v1.2.0 the app is now rebranded to “UNDOK / OKTIV Radio”
I’ve just tested the app (v1.2.0 from the app store) and it’s functions with two radios: Manual controls and the THEN-flowcards.
Result: it works as intended.
Does your radio have a fixed IP address? Either reserved in DHCP-server of fixed in the radio itself.
Worth to mention:
An undok/oktiv radio can only have one communication session at any given time. If you use the android oktiv app on your phone, it will take over (or intervene with) the session from Homey. At the set poll intervall of the Homey app, Homey will take over comms with the radio from your phone app. The Homey app is designed in a way that it sets up a new comms session with every poll, IF-card or THEN-card. This is done for robustness.
First app that works with the Technisat Digitradio 143.