Closed Supermagnum closed 3 years ago
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/request-jitsi-meet-binding/127125/1
What kind of integration do you expect? What features for this binding?
What kind of integration do you expect? What features for this binding?
The possibility to turn on and off lights, turn on and off alarms, open door locks, control audio, share files between users and a folder,pipe audio to and from devices. As an example, if nobody is home (away mode is on) route my doorphone calls to Jitsi meet. Also, support XEP-0384: OMEMO Encryption, a XMPP extension.
If it uses XMPP, you might already be able to interact with it using the XMPPClient Binding today. :slightly_smiling_face:
If it uses XMPP, you might already be able to interact with it using the XMPPClient Binding today. 🙂
It appears to use the Prosody XMPP server .
This information may be relevant: https://github.com/jitsi/jitsi-xmpp-extensions
https://m.youtube.com/watch?v=EhAc2CztHLw
https://desktop.jitsi.org/Documentation/DeveloperDocumentation
Reply by one of the Jitsi meet developers can be found here: https://github.com/jitsi/jitsi-meet/issues/10087
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/does-openhab-handle-ip-cameras-with-two-way-audio/127259/1
I'm pretty familiar with Jitsi meet, i used to run a very large global cluster for a commercial application (1000's of HD streams) , and did a lot of development against it and the underlying XMPP infrastructure.
I'm still not sure I understand the use case? How would you control openHAB, are there buttons on the Jitsi UI ? Why Jitsi Meet? Seems like an odd integration.
While it uses XMPP for signaling and control, its all based on the multi user chat extension (MUC) and requires a special moderator process to add additional controls to that room. Rooms are dynamically created per video conference.... this is all a very long way of saying it's a complicated beast.
If you are looking for AV integration, if anything a device is going to speak SIP, or no specific standard signaling protocol at all (so raw RTP or some custom web signaling method) . Jitsi uses XMPP and an extension to that called Jingle which was created by Google for their chat product many years ago, but later abandoned by them, and pretty much used by none except Jitsi these days.
The only use case i can think of would be some central video intercom.
I'd suggest to use the forum for discussing ideas and only create issues here for new bindings if any developer is willing to look into it and it is clear what the integration should look like.
Jitsi meet is a collection of free and open-source multiplatform voice (VoIP), video conferencing and instant messaging applications for the web platform, Windows, Linux, macOS, iOS and Android. It uses WebRTC compatible software Video bridge for high-quality video conferences. In addition, WebRTC enabled server is used to route video streams amongst members. Jitsi Meet uses XMPP for signaling. https://jitsi.org/
Self-hosting instructions: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-start
There is a API: https://jitsi.github.io/handbook/docs/dev-guide/dev-guide-iframe
OpenHab forum discussion: https://community.openhab.org/t/request-jitsi-meet-binding/127125