Evolution of the Z-Wave JS UI service

Hello,

Promises made, promises kept.
New PR available on GitHub : [Zwavejs] Support Air Temperature \u0026 Power properties from Multilevel Sensor Command Class by sescandell · Pull Request #2027 · GladysAssistant/Gladys (github.com)

Support for temperature and power reporting:
![image|690x359](upload://

1 Like

@Sescandell
chat-gpt :wink: : so here the device (which must be a switch) when it receives a command « change from 0 to 1 » sets the device to 1 then sends back « command executed, set to 1 » or a similar message

In the context of Z-Wave devices, has_feedback probably refers to a feature that allows determining whether a device has received feedback after sending a command.

The Z-Wave protocol is designed to be bidirectional, which means devices can not only receive commands but also send feedback to indicate whether a command was successfully executed or whether an action was performed. This feature is often used to ensure the reliability of commands and to obtain information about the state of devices.

Thus, when has_feedback is used in the context of a Z-Wave device, it generally indicates whether that device is capable of providing feedback after executing a command. This can be useful for home automation or monitoring systems, where it is important to know whether commands sent to devices were actually executed.

Hello,

My question may have lacked context: this is a property on the Gladys side and not specific to Z-Wave (zWave).

I quickly went through the code. I see a usage on a saveState, but I didn’t trace further. Pierre Gilles should be able to answer. Otherwise I’ll follow up on it.

Thanks for the attempt :+1:

1 Like

@Sescandell le has_feedback means that the device at the end sends a status feedback after Gladys has sent it a command.

This allows Gladys to know whether it should record the value locally when controlling, or whether it should wait for the device to send an event saying « I’ve been controlled ».

Example of has_feedback = true:

I control a smart plug from Gladys → Gladys sends a command to the plug → the plug sends a « state changed » event to Gladys → Gladys

1 Like

[quote="Sescand

Understood, thanks,

Yes I saw the coverage… but these are cases the linter forces me to add for « nothing »… I’ll see what I do to handle them. I think in this scenario I’ll return a value undefined, and if undefined that will imply « unknown request » and therefore « cancellation of the request ». That’s what seems most logical to me.

OK, keep me posted! If you can’t manage, I can help you.

Small bug to report on the Z-Wave integration, I have one Z-Wave device per room to manage each radiator. In zwavejs-ui I therefore declared the name as Radiator and the location as the room.

Except that in Gladys I only have radiators displayed (normal), but it’s hard to know which is which. Maybe add the location somewhere so we can differentiate each device? But I’m afraid that will cause a duplicate with the Gladys room. What do you think @pierre-gilles ?

Back to the bug, I get a message when I try to add my radiators to Gladys

There is a conflict with the selector which is not unique.

Looking at the code I didn’t see a selector in the zwavejs-ui integration so I think the selector is formed from the name thanks to this function.
image

I’m trying to propose something to fix the selector.

EDIT: By adding the selector I can save all my devices

1 Like

@pierre-gilles, the PR

Well spotted @_Will_71! I left a comment on the PR :slight_smile:

I think we need to do the same work on the feature selector, otherwise it’ll get stuck at that point too, I think

Ok, I’ll take care of it as soon as possible.

@pierre-gilles, I’ve made the changes to the PR.

2 Likes

Thanks @_Will_71! It’s fine with me, it’s merged into master and it will be included in the next Gladys release :slight_smile:

2 Likes

Ok👍.
I’ll then wait for @Sescandell’s next PR because what he did will allow me to add a new device.

I’m also preparing a PR to integrate the « location » of each device

2 Likes

Hello,

I’ve updated the PR: rebased onto master to pull in the latest changes from @_Will_71 and address code coverage issues.

PR for the documentation available here: Update Zwavejs UI doc by sescandell · Pull Request #255 · GladysAssistant/v4-website (github.com)

Your turn @pierre-gilles :wink:

1 Like

@pierre-gilles , the PR for adding the « location »

@Sescandell Thanks for the PR on temperature + power, it looks great to me :slight_smile: I merged it and it will be included in the next Gladys release! I’ll merge the website when the release is live

@_Will_71 Your PR is good for me too, but there’s a small conflict with @Sescandell’s PR that I merged just before — can you take a look?

1 Like

I’m trying to watch at noon during my lunch break.

1 Like

@pierre-gilles It’s fine, I’ve resolved the conflict

2 Likes