Kemper
My feedback
4 results found
-
57 votes
We are planning to provide trigger support within 2020.
We are now in the process of restructuring our rendering engine in order to allow several features to be implemented. One of these features is triggers. We are planning to initially support UDP, TCP/HTTP, GPIO events, and then support keyboard/mouse events.
[Draft Specs follow:] Triggers will be available as a different menu item, in order to manage, set them up, test them, and so on. After setting them up, Users will be able to use them in Playlists, e.g. to skip a Media (or Subplaylist) entry, jump to specific Media (or Subplaylist) entry, and so on.
Kemper supported this idea ·An error occurred while saving the comment -
23 votes
This makes sense. We will add support for a second WiFi soon.
We are also provide support for WPA Enterprise.
An error occurred while saving the comment Kemper commentedThis is becoming a major pain point for our project teams. We want to roll more devices out to the field but knowing that each one of them, at some point, need to be carried back to an old ssid or wired connection, makes it far less attractive. The wpa_supplicant.conf has provisions for multiple ssids. Can this be added to the web ui?
Kemper supported this idea ·An error occurred while saving the comment Kemper commentedAny update on this?
-
0 votes
-
62 votes
Our whole backend (server) provides an RESTful HTTP API. This is currently used only by our UI, the User Interface that our users see on their screen.
This API needs to be documented and polished up, but it is (more or less) already usable for special purposes. We will just provide you with a access token.
We are planning to release a fully documented API spec within Q2-2017.
An error occurred while saving the comment Kemper commentedAny updates?
Voting for this as well. We have teams trying to use a smattering of smart TV's native slideshow apps and laptops jammed behind TVs. Some level of HID support would be amazing and definitely increase our usage.