Logic Machine Forum
Doorbell 2N IP (Intercom) - Printable Version

+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Scripting (https://forum.logicmachine.net/forumdisplay.php?fid=8)
+--- Thread: Doorbell 2N IP (Intercom) (/showthread.php?tid=3834)



Doorbell 2N IP (Intercom) - KNXSeb - 29.01.2022

Hello,
I am a novice in scripting. 
Is there Anyone that can help me in reading out my doorbell status to link to object in KNX?

My Dorrbell is the 2N IP Verso and it has its own HTTP API (Testtool).
I need the status of the relay switch or the validation of the rfid card. Both would work. 

My goal is following problem:
If the relay switch status of the doorbell turns to 'true' then the knx group adresss (boolean) should write to 'true'.

I can start with "https://<ip-adress>/api/switch/status?switch=1"  an request from the doorbell. The doorbell uses TLS and the type "digest" for https.
The response is:

Code:
{
  "success" : true,
  "result" : {
    "switches" : [
      {
        "switch" : 1,
        "active" : false,
        "locked" : false,
        "held" : false
      }
    ]
  }
}


With the automation manual for the http request it is possible to send an request from the doorbell.
https://wiki.2n.com/hip/auto/latest/en/4-akce-action

Is there already a solution for my question/problem?
Thanks!!


RE: Doorbell 2N IP (Intercom) - KNXSeb - 30.01.2022

I've got my solution:

I activate the remote service and use the remote http code:

"https://remote:remote@192.XXX.XX.XX/cgi-bin/scada-remote/request.cgi?m=json&r=grp&fn=write&alias=1/1/2&value=true"

I just used it in the automation of the 2N IP Doorbell. Just stupid i am.
How simple...

Works fine for me!


RE: Doorbell 2N IP (Intercom) - j.martinez@t-ingeniamos.com - 28.06.2025

(30.01.2022, 13:23)KNXSeb Wrote: I've got my solution:

I activate the remote service and use the remote http code:

"https://remote:remote@192.XXX.XX.XX/cgi-bin/scada-remote/request.cgi?m=json&r=grp&fn=write&alias=1/1/2&value=true"

I just used it in the automation of the 2N IP Doorbell. Just stupid i am.
How simple...

Works fine for me!

Hello there! I am trying the same but without success

What i am missing?


RE: Doorbell 2N IP (Intercom) - Daniel - 30.06.2025

Did you enable remote services and did you export the object you are trying to write too?
Also enable Send Basic auth header in Remote services.


RE: Doorbell 2N IP (Intercom) - j.martinez@t-ingeniamos.com - 30.06.2025

(30.06.2025, 07:46)Daniel Wrote: Did you enable remote services and did you export the object you are trying to write too?
Also enable Send Basic auth header in Remote services.

Yes, the point is the url works in a browser, then the LM works.

But i cannot make it works from 2n sending the http requests....


RE: Doorbell 2N IP (Intercom) - Daniel - 30.06.2025

Then you should contact 2N for support.


RE: Doorbell 2N IP (Intercom) - Erwin van der Zwart - 30.06.2025

I would make it a GET request and put the text part after the URL


RE: Doorbell 2N IP (Intercom) - j.martinez@t-ingeniamos.com - 30.06.2025

(30.06.2025, 11:05)Erwin van der Zwart Wrote: I would make it a GET request and put the text part after the URL

I Would try! Thankyou all!


RE: Doorbell 2N IP (Intercom) - DGrandes - 11.09.2025

Good afternoon,
I am trying to set up this integration to know from the Logic Machine when there is an access attempt or an authorized access, and I’ve been communicating with 2N for several days. However, the conclusion they reach is that the Logic Machine redirects with a 302 and requests authentication. I’ve been running several tests and sending them the logs from the 2N device, but there’s no way to make it work.
I’m attaching a screenshot so you can see the configuration that I also sent to j.martinez. Did you manage to get it working?
2N is asking me to modify the Logic Machine API, but I know there must be something in the 2N access controller, because it should work with the same parameters as a normal POST.
The URL you see in the image is:
http://192.168.2.205/login?ref=scada-remote
The text/plain is:
m=json&r=grp&fn=write&alias=35/1/12&value=Prueba2N
I have tried several approaches — putting username, password and body in the URL; only body with username and password separately… but nothing works.

   


RE: Doorbell 2N IP (Intercom) - j.martinez@t-ingeniamos.com - 11.09.2025

(11.09.2025, 13:37)DGrandes Wrote: Good afternoon,
I am trying to set up this integration to know from the Logic Machine when there is an access attempt or an authorized access, and I’ve been communicating with 2N for several days. However, the conclusion they reach is that the Logic Machine redirects with a 302 and requests authentication. I’ve been running several tests and sending them the logs from the 2N device, but there’s no way to make it work.
I’m attaching a screenshot so you can see the configuration that I also sent to j.martinez. Did you manage to get it working?
2N is asking me to modify the Logic Machine API, but I know there must be something in the 2N access controller, because it should work with the same parameters as a normal POST.
The URL you see in the image is:
http://192.168.2.205/login?ref=scada-remote
The text/plain is:
m=json&r=grp&fn=write&alias=35/1/12&value=Prueba2N
I have tried several approaches — putting username, password and body in the URL; only body with username and password separately… but nothing works.

Hello DGrandes!!

The point is 2N devices didn't works with http request with headers where the user and password is sended...... 2N says they will includes headers to work with ASAP..... for that reason i used other way script they don't use passwords until we could do it in a safest way....

   


The http request 2n module point to a url like: http://LM_IP/public/write.lp?addr=9/1/1&value=0 

Check this--> https://forum.logicmachine.net/printthread.php?tid=3141


RE: Doorbell 2N IP (Intercom) - admin - 11.09.2025

Try this: install 2025 RC firmware and enable "Send Basic auth header" in System config > Services > Remove services.