Client should have a "headless mode" for Freedomotic headless

[amenak77]

As the idea to have a single page application for freedomotic hedless mode seems to be not so smart, we should have a client headless mode. No synoptic, no many other things without having tons of error messages. To be honest in my opinion there should be something freedomotic side too (in headless mode)

[mcicolella]

I don't get it. Please can you explain better?

[amenak77]

I mean that the client is quite smart and detects differences between mobile mode and browser mode; but freedomotic headless is a singularity about browser mode. There is no jfrontend and I don' know if it is to be considered just like another client of freedomotic core, or contains some fundamental info. In this case we could have errors if the situation isn't managed properly.

[amenak77]

The other question is freedomotic side about headless; as you know, if the framework doesn't run from CLI, in headless mode the user could not have any signal that freedomotic is running in background. This could be a problem

[amenak77]

I've made a test with an headless freedomotic instance and client on browser; no particular problem and I command my home lights in this way from things panel; it's the same using a smartphone and webapp clent. Maybe no headless mode is needed