-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Comelit 6741W #79
Comments
Hi, unfortunately, I'm not in touch with this device. Thank you |
Sure, if I can help in any way. I use it with google assistant at the moment |
I'm interested too. I have the device and I can do any test you like. I'm using it with the alexa skill and it works but I look forward to use it in HA. I have downloaded the settings backup from the device and I can attach it if you think it useful. and some configurations related to mqtt in mqttslk.cfg and comelit cloud services on registerd.cfg the device is reachable at |
Unfortunately, it's not just a matter of configuration. The intercom has a life of its own away from the Comelit hub, so I cannot work on the development side without it. I can help with the process, but it is really hard to add support without the device. You need to start sniffing for the HTTP traffic. I really don't know which protocol it uses. |
Thanks for the quick reply
The device in my case is working standalone without a comelit hub. I can interact with it by the web interface or the app. The app relies on comelit cloud services to work when out of local network
in which direction ? source / target? the http on 8080 and https 8443 are for the interactions with the web panel ui where you can setup all the configurations If you point me in the right direction I can do any kind of tests. Thanks a lot |
Can you do things from the web panel? Or is it just something you use to configure/manage the system? |
mmm, so you need to sniff the app's traffic |
ok, the app talks to the device on the 64100 port, on that port a web server is listening so probably this is one way. I'll sniff around and I'll get back to you. |
Thanks all for try to add!! |
Hi all,
UDP
The device has two operating modes a modern one using comelit cloud services and a legacy local one using a dismissed app. The Cloud mode-The hosts involved are: I was able to sniff and decode a couple of interactions: ________DEVICE talks to cloud POST /servicerest/p2p/start HTTP/1.1 {"deviceUuid":"be4bdc9e-a822-47a0-8d1d-REDACTED-00001","data":{"authMode":"user_viper_token","secret":"REDACTED","timeout":10,"sdp":"BASE64 payload"},"protocol":{"name":"viper_p2p_v2","version":1}}HTTP/1.1 200 OK --Decoded sdp=base64 payload v=0 Server: nginx/1.23.3 {"result":"SUCCESS","data":{"sdp":"BASE64payload"}} --Decoded sdp base 64 payload v=0 ________Modern app talks to cloud POST /servicerest/appbundlecheck/verify HTTP/1.1 {"ccapi":{"version":"1.1.0","endpoint":{"requuid":"1469265513","service":"appbundlecheck/verify","version":"1.1.0"},"login":{},"body":{"bundle":"com.comelit.bigapp","appId":"058dbeff-d5ee-4f26-a0a7-22e18e09fcc6"}}}HTTP/1.1 200 {"ccapi":{"version":"1.1.0","endpoint":{"service":"appbundlecheck/verify","version":"1.1.0","requuid":"1469265513"},"login":{},"body":{"allowed":true},"error":{"code":0,"action":0,"message":""}}} **The legacy mode **-It requires a dismissed APP "ComelitViP Remote” or older "App Intercall Remote ViP". I was able to download the first one from a legacy store and looking at. |
Hi, any news about gate open integration? |
Nothing new, I think no one is working on this feature. |
Hi all, my building just decided to replace the broken interphone system with this one. Something I applauded because I hoped the Comelit Integration would allow me to add the video camera to my dashboard. But now I see things are not so simple. I really hope someone can continue this work and am most willing to test whatever is developed... |
Hi, is it possible to add wifi video intercom 6741W support?
Even just the ability to open the gate and door.
Thank you
https://pro.comelitgroup.com/en-gb/product/6741w
The text was updated successfully, but these errors were encountered: