ghoma - npm Package Compare versions

Comparing version 1.0.3 to 1.0.4

ghoma.js

		@@ -29,6 +29,4 @@ /**
		var gHomaRegistry = [];

		// Timeout to kick the nodes that have not send a heartbeat in some time
		var timeout = 60000*5; // 5 Minutes
		// The interval timer

		@@ -52,2 +50,3 @@ var server = net.createServer(function(socket) {
		lastheartbeat : new Date(),
		reregistered : 0,
		on : switchOn,
		@@ -94,2 +93,3 @@ off : switchOff,
		}
		ghoma.reregistered = gHomaRegistry[idx].reregistered + 1;
		gHomaRegistry[idx] = ghoma;
		@@ -293,2 +293,3 @@ } else {
		off : plug.off,
		reregistered : plug.reregistered,
		heartbeat: plug.lastheartbeat
		@@ -295,0 +296,0 @@ }

package.json

		{
		"name": "ghoma",
		"version": "1.0.3",
		"version": "1.0.4",
		"description": "A control server for g-homa wifi plugs.",
		@@ -5,0 +5,0 @@ "main": "ghoma.js",

README.md

		@@ -5,3 +5,3 @@ A control server for G-Homa wifi plugs written in [node](http://nodejs.org).

		This library is intended to be used as part of a home automatisation solution. For example, it can be used together with a framework like [express.js](https://expressjs.com/) to switch the plugs on or off by simple http calls.
		This library is intended to be used as part of a home automatization solution. For example, it can be used together with a framework like [express.js](https://expressjs.com/) to switch the plugs on or off by simple http calls.

		@@ -106,3 +106,4 @@ Installation
		"remotePort": 14283, // The remote port
		"heartbeat": "2017-01-22T21:00:20.893Z" // Time of the last heartbeat call from the plug
		"heartbeat": "2017-01-22T21:00:20.893Z", // Time of the last heartbeat call from the plug
		"reregistered" : 2 // Number of re registrations of the plug. May be a indicator for the connection stability
		}
		@@ -115,4 +116,9 @@ ```
		With firmware version <=1.0.06 you can use the embedded web server to adjust the control server address. See the fhem wiki page for instructions.
		With newer firmware version, this easy way to configure the plug is disabled. The only known way to run your own control server is to setup your own DNS and DHCP service. Then the DNS entry for 'plug.g-homa.com' must point to your own server and you are forced to use '4196' as listening port.
		With newer firmware version, this easy way to configure the plug is disabled.

		One way to run your own control server is to setup your own DNS and DHCP service. Then the DNS entry for 'plug.g-homa.com' must point to your own server and you are forced to use '4196' as listening port.

		Another way that may work for you is to use this node script to change the control server. See [config.js](https://github.com/rodney42/node-ghoma/blob/master/config.js).


		Further information
		@@ -119,0 +125,0 @@ -------------------

ghoma - npm Package Compare versions

Improved metrics