ZWave Range Extender - Initial setup

Add-ons Bindings
1

Openhab2 Version: version":“0.9.0.201703201701
Moving my setup to a new set of hardware.
The one thing that always gives me hangups that really shouldn’t” zwave range extender…it’s plugged in…should be one of the first things to be recognized.

Anyway, still waiting on it to check in for over 15 hours.

Usually when something hasn’t checked in there is just a NODE id in paper ui
As you can see there is something weird this time…a set of numbers separated with colons and periods.
Should I add this or wait some more? I’ve never seen this happen.

Thanks

2

I guess this isn’t the OH2 version :wink: It should be 2.x - this is probably the ESH version (maybe?).

That means the device isn’t in the database. The database needs a modification to support this as the device does nothing so the database doesn’t export it. It doesn’t mean the device isn’t working in your network - it should work fine.

3

Hmm i always though i go here to get the version: http://172.16.1.242:8080/rest/
It’s the nightly build from Monday.

Anyway, thanks for the response. I’m curious as to why it’s not in the database anymore?
With the last build i was using(December timeframe) it was in the database and was recognized.

Was it removed for newer builds?
Aeon Labs DSD37-ZWUS Repeater, DSD37-ZWUS, by Aeotec, Cert ID: ZC08-13010004

Thanks

Rich

4

I’ve no idea what this link is?

Possibly - every now and then I do a complete resync which removes all files, and then exports everything from the database. This probably removed the entry as the database won’t currently export entries with no channels (like a range extender) to avoid errors.

5

Thats my openhab’s IP/rest; i read somewhere at some point on here that’s where i obtain the version from; hence why i posted it. Where should i obtain the real version from?

So are “no channel” devices no longer being put into the database?

6

At the moment devices with no channels are in the database but aren’t being exported into the binding

7

Ok, that’s unfortunate…one handy thing about that was that when i rebuilt the system, i was sure a node checked in and was ready when i saw that info populate…hence why i finally asked b/c i thought something was wrong with the device for a bit there.

8

Hello,

I bought the Z-Wave Range Extender from Aeotec and it shows similar as yours indicating it’s not in the database (or not exported).

Now it’s hard for me to tell, whether this is an issue or not. Can I consider the device is working, or is it more or less useless? By just saying “is the network more stable now?” is hard to tell, as some devices (sensors) seem just at the border to be out of range (sometimes they seem to report less reliable) and thus I need some time to pass to see whether they work reliable now or not.

But since I have 2 weeks to return the device, I’d rather return it if it means it’s not working when not in the database.

So my question: does the range extender still serve its purpose also when not in the database (export)?

9

Yes - fundamentally there’s nothing that the binding can do with this device. It’s a repeater - that’s all.

Yes - it will be fully used by the ZWave network - the database will not impact it at all. The only thing is you won’t have it listed as a thing in the UI.

1 Like
10

Hello @chris,

thanks a lot for the clarification. Have a Happy Easter!

Cheers!

11

Here’s how handle the zWave repeaters to insure they are reporting back; I have four of them setup.

Capture
Capture.PNG1189×336 20.8 KB 

rule "zWave Node15 - Garage Repeater Sensor"
	when
		Item GarageRepeater_Color received update or
		Item GarageRepeater_Color_Temp received update
	then

		if (systemStarted.state != ON) {

			GarageRepeater_Update.postUpdate(new DateTimeType())
		}

		if (Node15_tAlive === null && systemStarted.state != ON) {

    		logInfo("zWave", "Checking Garage Repeater Status - 4 hour interval.")

    		Node15_tAlive = createTimer(now.plusHours(4), [ |
    		Node15_tAlive.cancel()
				Thread::sleep(2000)  // 2 second wait
			Node15_tAlive = null

    		logWarn ("N15", "Garage Repeater Sensor N15 appears to be Dead")

    		// send an email
			if (systemStarted.state != ON && InternetConnection.state == ON){ 

				val toemailzwaveN15 = "Jay gMail"
				val subjectemailzwaveN15 = "OpenHAB - zWave Garage Repeater Node15 Down"	
				val bodyemailzwaveN15 = "OpenHAB - zWave Garage Repeater Sensor Appears Dead. Please Investigate."
	
				sendMail(toemailzwaveN15, subjectemailzwaveN15, bodyemailzwaveN15)
					Thread::sleep(2000)  // 2 second wait
			}
    	])
		
		} else if (Node15_tAlive !== null && Node15_tAlive != NULL && systemStarted.state != ON){

    			Node15_tAlive.cancel()
					Thread::sleep(2000)  // 2 second wait
				Node15_tAlive = null
    	}
end

Best, Jay

12

Just a quick one to the Range extender topic:

I just bought the version 7 of the aeotec range extender and the installation was easy.
However even though the node27 is correctly recognized and shown in mainUI things, it does not show up in the network map.
Does this take more than half a day?

image
image751×681 78.2 KB

After a few days it obviously popped up:

image
image732×789 82.2 KB