BeNext / iHome tag reader

Discussions about existing Z-Wave device and their usage with Z-Way/Z-Cloud/Z-Box
Post Reply
gertjuhh
Posts: 10
Joined: 25 Sep 2013 15:07

BeNext / iHome tag reader

Post by gertjuhh » 14 Nov 2013 15:47

Has anyone tried the BeNext tag reader?
http://www.ihome.eu/static/manual/tagreader.pdf

Does it play nice with Z-Way?
How is your experience with this device and in what scenario have you used it?

droll
Posts: 47
Joined: 20 Dec 2013 01:37

Re: BeNext / iHome tag reader

Post by droll » 25 Feb 2014 23:45

The Z-Way server revision 1.5.0 RC1 solves a problem with the user code (0x63 - COMMAND_CLASS_USER_CODE) that is needed to report to the z-way server the incorrectly entered codes, or the code of your badges you are using together with the tag reader.

If you want to have your tag reader sending an audible acknowledge after having entered a valid code (or having presented a known badge), you need to bind the alarm command (0x71 - COMMAND_CLASS_ALARM_V2) to a function that sends a binary switch command to the tag reader (for both the "home" and "away" events). Example:

zway.devices[<TagReaderId>].Alarm.data[6][5].status.bind(function() { zway.devices[22].SwitchBinary.Set(true); });
zway.devices[<TagReaderId>].Alarm.data[6][6].status.bind(function() { zway.devices[22].SwitchBinary.Set(true); });

Add these commands into a custom JS script. Starting with revision 1.5.0 RC1 the custom scripts cannot be declared anymore inside the config.json file. You need to modify the main JS script (main.js) to execute your custom script:

executeFile(<YourCustomScript>);

The Z-Wave.me team promised a UI to configure custom code in the future.

alibab
Posts: 11
Joined: 26 Mar 2014 15:01

Re: BeNext / iHome tag reader

Post by alibab » 10 Apr 2014 19:08

Hi,
We have the same benext tag reader, and have some pb to configure it.
The device is correctly include in zwave network.
We have set some code with no pb, but we can't add rfid tag, when I send the rfid Iobtain this error :

zwave error
[2014-04-05 17:49:07.134] SETDATA devices.11.data.lastReceived = 0 (0x00000000)
[2014-04-05 17:49:07.135] SETDATA devices.11.instances.0.commandClasses.99.data.0.status = 0 (0x00000000)
[2014-04-05 17:49:07.135] SETDATA devices.11.instances.0.commandClasses.99.data.0.code = "ϑ+м"
[2014-04-05 17:49:07.135] SETDATA devices.11.instances.0.commandClasses.99.data.0.hasCode = True
[2014-04-05 17:49:07.136] SETDATA devices.11.instances.0.commandClasses.99.data.0 = Empty
[2014-04-05 17:49:07.143] Custom: bind usercode2 clavier.js : ��+�|
[2014-04-05 17:49:07.154] Node 11:0 CC UserCode: user code should be 4...10 characters, "��+�|" rejected!

The commandClass UserCode seem to reject the code greater than 10 characters. what must we do? where i'm wrong ? must we convert the tag code?

Another question for this module management :
I use openremote to manage it, but how can I memorise the current status of the alarm?, open remote can only make a http request and if I understand, the alarm report is only a bind, not a status.

Thk in advance for your response.

pofs
Posts: 688
Joined: 25 Mar 2011 19:03

Re: BeNext / iHome tag reader

Post by pofs » 14 Apr 2014 07:38

The restriction on code length is declared in UserCode CC specification. More than that, it must contain only ASCII characters.

droll
Posts: 47
Joined: 20 Dec 2013 01:37

Re: BeNext / iHome tag reader

Post by droll » 08 Dec 2019 19:17

Hello,
The BeNEXT/iHome Tag Reader does not work anymore well since I have migrated to Z-Way version 3 (v3.0.1). Or more precisely, the optional notification does not work anymore reliably. The reason is that the Z-Way controller has to issue the notification to the Tag Reader very quickly after receiving an alarm report. If this notification is not issued sufficiently quickly, the Tag Reader falls back to sleep and will not receive the notification from the controller.
The quick reaction to the alarm event has been ensured by binding the notification (binary switch) command to the alarm event. This was working well with the different version 2 releases:

Code: Select all

zway.devices[TagReaderIndex].Alarm.data[6].event.bind(function() {
   zway.devices[TagReaderIndex].SwitchBinary.Set(true);
});
It seems that Z-Way version 3 does not react sufficiently quickly anymore. The Tag Reader falls back to sleep and plays the notification sound only the next time it wakes up.
The protocol between the Tag Reader and Controller will be attached as reference.
I hope the Z-Way controller reaction speed can be increased to make this Tag Reader working again in the expected manner.
BeNEXT Tag Reader Protocol.PNG
BeNEXT Tag Reader Protocol.PNG (31.05 KiB) Viewed 623 times

User avatar
PoltoS
Posts: 5286
Joined: 26 Jan 2011 19:36

Re: BeNext / iHome tag reader

Post by PoltoS » 13 Dec 2019 19:51

You should check logs to see what is happening in between. Z-Way has not became slower since v2.3.8

wbmsmart
Posts: 2
Joined: 11 Feb 2020 23:06

Re: BeNext / iHome tag reader

Post by wbmsmart » 12 Feb 2020 01:45

Find helpful customer reviews and review ratings for iHOME IBT230SSC iBT230 Bluetooth Bedside Dual Alarm ... Update: So I was considering getting NFC tags so bluetooth turned on when I got in my car and I realized I only ... Avid Reader.
WBMSmartShop & learn about the perfect smart home devices products for your home in 2020. 30-Day No Hassle Returns & 20% Off Your First Order.

Post Reply