Hi everybody. Well this was fast, from idea to app in a matter of what a couple of days?
Can I just ask a couple of questions, so in this stage you have two homeys pro, whichever if I understood 2018, 2019, 2023, and on one you install satellite on the second controller app. Those two pair.
However devices added to satellite do not automagically appear in the controller rather you manipulate with devices on the satellite over flows in controller, right?
with the “official” Homey 2023 controller it will be like that, and a bridge can be a satellite, as stated in the keynote. In this case it’s a community app that will run on any Homey Pro as a controller (not the bridge) and can connect to any Homey Pro as a satellite. so it’s a bit different, might work in a different way than the “official satellite with the bridge”, but the end results for both will be awesome and create so many new opportunities.
I am not making any restriction myself, so no, the Homesh Controller App can be installed on any Homey Pro devices.
However, Homesh Satellite will have abilities that will only work on the "old White Balls"and not the Early 2023.
I don’t know yet if apps can be made in a way that you can install it on 2023 and use it without the non-existing features. If so, the Satellite could be installed on a 2023. If not, then not
Well there are a couple of things to keep in mind:
I hope to be able to use Soundboard on the NEW pro 2023, as it will ditribute the files to the satellite itself to keep control in just the Controller.
But currently it says it cannot be installed on 2023. I have no idea why when i look at the sourcecode! I think Athom has it manually tagged.
I have no idea what ahappends when you try to reference an App that does not work on 2023. Can it be filtered out?
So, i guess, it’s mostly about the permissions and what that means for app availability.
I have created a flowcard to play files on the Satellite, directly from the Micro Web Server app.
It lets you select a file and play it on Homeys (Satellites).
This way you can control the files on the Controller while playing it on the Satellite(s).
Also, it allows for files larger then 900Kb to be played.
This currently works already, but i get the file lists through the FTP client, which means the Ftp Server from the Micro Web Server needs to be active while editing flows (autostart is available in MWS).
(The url that is used in the background is to the HTTP source, so the flows will work when ftp is down, just not the editing).
You can set the Ftp Port in the App Settings. Default is 5081 as is default by the Micro Web Server.