Differences

This shows you the differences between two versions of the page.

--- supported_hardware:serverevents [2020/03/14 15:06] – created James Sentman
+++ supported_hardware:serverevents [2023/02/13 14:52] (current) – external edit 127.0.0.1
@@ Line 13: / Line 13: @@
 {{:supported_hardware:server_events_settings.png?600 |}}
 **Outgoing Network Connection:**
-Enter the address and port that the server is running on. If possible assign a static IP address to the remove device or server so that it won’t change and we are no longer able to connect to it. You can also use an mDNS/Bonjour name or standard DNS name here if necessary.\\
+Enter the address and port that the server is running on. If possible assign a static IP address to the remote device or server so that it won’t change and break the connection. You can also use an mDNS/Bonjour name or standard DNS name here if necessary.\\
 \\
 **HTTP Path:**
-This is the request path to make to receive the server events stream. Any GET parameters can be included after the path as in the example picture. As of version 1.0 it is not possible to send a PUT or POST request to start the stream. If you need to do this please drop me a note and I’ll move adding this up the priorities list.\\
+This is the request path to start the server events stream. Any GET parameters can be included after the path as in the example picture. As of version 1.0 it is not possible to send a PUT or POST request to start the stream. If you need to do this please drop me a note and I’ll move adding this up the priorities list.\\
 \\
 Note that this is not the full URL. This field should not contain the “http://192.167.54.3:80/“ portion of the URL. Only the path portion beginning with a forward slash as in the example.
@@ Line 23: / Line 23: @@
 ====Events With No Data:====
-If an event is received with no Data section after it 2 things are done. First the event name is written to the XTension log in case that is something that you wish to see. In addition an ON is sent for a unit with the same address as the event name. In the case of something like the data stream from a networked video camera it may just send “event: Motion” type events without any extra data. If you create a Unit on this interface and set it’s address to “Motion” then it will receive an On command whenever that is received and you can now process the motion hit in the On script of that Unit.
+If an event is received with no Data section after it two things are done. First the event name is written to the XTension log in case that is something that you wish to see. In addition an ON is sent for a unit with the same address as the event name. In the case of something like the data stream from a networked video camera it may just send “event: Motion” type events without any extra data. If you create a Unit on this interface and set it’s address to “Motion” then it will receive an On command whenever that is received and you can now process the motion hit in the On script of that Unit.
 For example, if we receive:
@@ Line 71: / Line 71: @@
 The Server Events plugin first appeared in XTension 9.4.28 in March of 2020. It is part of the standard XTension plugin pack and included with the download of the app. No extra install is required.
+The Server events plugin was updated to run under the embedded version of python in 9.4.45 in march of 2022. As of the initial embedding the python version was 3.10. No longer requires a system version of python2.7