Help with Integrating zwave ring v2 alarm keypad via z-wave js/mqtt

[edipseamm]

Hey all

I'm trying to integrate a Ring V2 keypad as there seems to be limited options on the market to have a dedicated keypad for the alarm.

I have the pad connected and configured via Z-Wave JS (The only way to support S2 devices). I am then sending all the info via mqtt.

The problem comes where my skills are lacking. The default message type is via json. Which is ok when reading values as they are expanded and easy to read. Where I stuggle is able to send messages via json from loxone to be able to trigger features on the keypad.

I am able to have a small workaround for this by using 'value only' option in Z-Wave JS which solves my writing issue but commands from the keypad now show with no value and just the time stamp gets updated so then there is nothing to read and use as a trigger,

See here:



If someone can help with:
1. Being able to send json from loxone
2. Being able to get a trigger from the inputs with no value

Ty
S

[Christian Fenzl]

Sending json from Loxone to MQTT is easy. The publish syntax always follows:
publish <topic> <value>

E.g.
publish to/my/topic { "this": "is", "my": "json", "easy?": true }

The second question is not clear to me, as a topic always should have a value. Possibly you simply do not see the first value (the push action) as it is immediately overwritten by the delete value (the release of the button).

[edipseamm]

Thanks for the JSON clarification.

As for the topic with no value see below. I can see the trigger in the incoming overview. But then as there is no data or it's happening too quick then nothing is being populated in the gateway and I can't use it as a trigger in loxone

See below:



;;

[Christian Fenzl]

Check the MQTT Gateway Log, what data have arrived and have been forwarded.
You won't see pulses that immediately are overwritten in these views.

[edipseamm]

19:55:16.140 OK: MQTT IN: zwave/2/111/0/5/0:
19:55:16.141 zwave/2/111/0/5/0 is cached
19:55:16.141 zwave/# matches zwave/2/111/0/5/0, send to MS 1
19:55:16.142 HTTP: Preparing input zwave_2_111_0_5_0 (using cache):

..


This is what is received

[edipseamm]

Ok. Changed the config a little but using json

I'm able to write what I need via this. Pretty simply



The only thing is the button presses just come in as epoc time stamps.

I'm just using this as a DI input and using the 'reset after send' function in the incoming. Is there a better way to do this?

[Christian Fenzl]

When it is working that way, then it's fine?

[edipseamm]

Yes and no

yes it sends the trigger

no- when you update or restart the pi then you get them all pulsed in a random order which can do weird things and potentially turn off the alarm

i cant get the epoc time into Loxone as it’s too long to try and do a compare but even that seems over complex.

any other ideas on how to get a clean trigger from the time value being updated?

[Christian Fenzl]

Try this one with Google Translate:

https://loxwiki.atlassian.net/wiki/spaces/LOX/pages/1525056058/nderung+eines+Wertes+erkennen

[edipseamm]

Thanks for your support this.

Yes this should work and I did try this before but the max value allowed in loxone via a VI is 2147483647 and my epoc value 1681718477549 for example so the value is to large.

Arghhhhh

Any other ideas?

[Christian Fenzl]

Possibly this works with a Virtual Text Input, but presumably not…

[edipseamm]

Unless I could use the http VI. Is that possible like I send data to the MQTT broker

Would this work:
/dev/udp/loxberry/1883 or 9001
Then
zwave/2/111/0/2/2/value as the input

Not sure this works as generally the mqqt > miniserver is not this way

[edipseamm]

Possibly this works with a Virtual Text Input, but presumably not…

No it just shows like this, even with text in the value