Z-wave Group 1.1 instead of 1

[hestia]

Hi,
I have several nodes with 1.1 in the Group 1.
When I remove 1.1 to put 1, the node is back in 1.

ScreenShot107.jpg (92.22 KiB) Viewed 2621 times

Could it be a cause of issues?

For one device, I have no refresh in domoticz when I use the switch (the real one!). Could it be due to this?

Version: 4.11307
Build Hash: 7439b1b9e

OpenZWave USB
Version: 1.6-808-gbb0a4bf7-dirty

[hestia]

Hi
no answer?
Am I the only one with Group 1 with 1.1 instead of 1 ?

Still the same after upgrade to
Version: 4.11337
Build Hash: c3a517bff
Compile Date: 2019-09-23 15:39:16

on a new device just added with the version.

BTW, the refresh on this device doesn't work

[ropske]

hi mate, i also have the same 1.1 but i don't have issues with it

[Gravityz]

i think the change to 1.1 happened when going from zwave 1.4 to zwave 1.6

1 represents single instance devices and 1.1 devices which are capable of communicating multi instance

so i think 1.1 is actually good since it proofs the device is capable of communicating with the new zwave 1.6 protocol

i have some devices which create problems when they are using multi instance. those devices are set to use single instance to function ok

the fgms-001 is such a device
also qubino devices are not 100% multi instance capable

maybe the explanation is not 100% correct.

you should however not be able to change the 1.1 to 1
if you delete 1.1 and add either 1 or 1.1 it should stick to 1.1

[hestia]

thanks for you explanation

So perhaps it is not an problem to have this 1.1, but I have another Qubino with this 1.1 and no refresh neither.

FIBARO System FGD212 Dimmer 2+ OK
Qubino (Goap) ZMNHBDx Flush 2 Relays+ OK
Qubino (Goap) ZMNHADx Flush 1 Relay+ KO
Qubino (Goap) ZMNHDD1 Flush Dimmer+ KO

OK : refresh OK
KO : no refresh

[Gravityz]

i also have the ZMNHADx and this module does not function well in a multi instance way.

i had to change the config file(if you know how that works
after that i deleted the ozw cache file and stopped/started domoticz again.

i believe that after the change a refresh node should also work

this is what is in my file at the end

please note that the forceinstances part is what the module make work with zwave v1.6 in a multi instance environment.
you could add this as well for the other module connfig file to see if it helps

<Compatibility>
<ForceInstances>false</ForceInstances>
</Compatibility>

<!-- Multi Channel Association Groups -->
<CommandClass id="142">
<Compatibility>
<ForceInstances>false</ForceInstances>
</Compatibility>
<Associations num_groups="9">
<Group index="1" label="Lifeline" max_associations="1"/>
<Group auto="true" index="2" label="basic on/off (Output Q)" max_associations="16"/>
<Group index="3" label="Input I2 basic report" max_associations="16"/>
<Group index="4" label="Input I2 notification report" max_associations="16"/>
<Group index="5" label="Input I2 binary sensor report" max_associations="16"/>
<Group index="6" label="Input I3 basic report" max_associations="16"/>
<Group index="7" label="Input I3 notification report" max_associations="16"/>
<Group index="8" label="Input I3 binary sensor report" max_associations="16"/>
<Group auto="true" index="9" label="Multilevel sensor report" max_associations="16"/>
</Associations>
</CommandClass>
<!-- Map endpoints to instances -->
<CommandClass id="96">
<Compatibility>
<MapRootToEndpoint>true</MapRootToEndpoint>
</Compatibility>
<Instance index="1" label="Load" />
<Instance index="2" label="i2" />
<Instance index="3" label="i3" />
<Instance index="4" label="Temp Sensor" />
</CommandClass>
<!-- COMMAND_CLASS_ALARM. This class is supported but is missing from the list reported by the ZMNHADx -->
<CommandClass action="add" id="113">
<Compatibility>
<GetSupported>false</GetSupported>
</Compatibility>
</CommandClass>

[hestia]

Thanks Gravityz for your reply
Actually I'm not familiar with those config files.
I've tried to do it but it doesn't change anything. If you could post your config file it could be more convenient.
When I go to OZW Control Panel end click Refresh on this node, I've got the device refreshed in Domoticz

[Gravityz]

here are the 2 files

Config.rar

(7.38 KiB) Downloaded 114 times

you need to ssh into your raspberry pi and replace those files on a file level
if you are not familiar with changing files in a file system do not bother

i noticed that the zmnhadx has an updated file in the latest build (v4.11349) which has this fix in place
maybe update to this version and do a refresh node on the zmnhadx node

[hestia]

Thanks Gravityz for the files
I changed the ZMNHADx config file, delete the ozw cache and restart Domoticz, and there was no change = no refresh.
I’ve deleted the devices and clicked Refresh Node Info to recreated new devices and it was the same.
After that, I’ve installed the last beta (4.11349), and it was the same (for both devices ZMNHADx and ZMNHDD1)
I’ve done the same “delete devices and recreate” for the other device ZMNHDD1 with no success .
What is strange is that I have 2 other ZMNHDD1 and they works fine regarding the refresh

[Gravityz]

ok, strange.

if you have the same modules and one works and the others not something else might be happening.(or they have different firmware)
in my situation controller 1 was gone in group 1,2 and 9(9 is for temp)
with the modified config file i was able to add 1 to group 1,2 and nine

did you check the groups? do you see 1 in group 1, 2,3 etc
if not see of you can add 1 to all the groups
if this still does not work it might be best to report it in the openzwave forum because it might not be domoticz related

https://github.com/OpenZWave/open-zwave/

[hestia]

I've added 1 in each group and it is the same result
When I go to OZW Control Panel and click Refresh on this node, I've got the device refreshed in Domoticz, so I'd say on the openzwave side the device state is known!
I'm going to go back to Qubino support and when I have to openzwave forum

[hestia]

New test
on another Qubino (Goap) ZMNHDD1 Flush Dimmer+
when the device is still "Not Used" the refresh is ok
when the device is "Used" the refresh doesn't works
So I think it is not an issue in openzwave, but more in Domoticz

[hestia]

New test
on another Qubino (Goap) ZMNHDD1 Flush Dimmer+
when the device is still "Not Used" the refresh is ok
when the device is "Used" the refresh doesn't works
So I think it is not an issue in openzwave, but more in Domoticz

Could not get this result again today. Perhaps it was too later yesterday
But the state of my device is still not refreshed in Domoticz
I bought a new one to try...

[hestia]

I've got info from Qubino support
<<Here's the data we send to the Domoticz developer about the Flush Dimmer for the beta version 4.11213 of the gateway. We send this data + extra notes for all of our devices.
[...]
The gateway configures a multi channel lifeline association, using MULTI_CHANNEL_ASSOCIATION_SET(groupId=1, multichannelnodeId=1, endpoint=1). The gateway should have configured an ordinary lifeline association, using ASSOCIATION_SET(groupId=1, nodeId=1).>>

So on their side, they consider that 1.1 is not the right value!

[Olifant1990]

I have the same problem, no refreshes from two Qubino flush shutter controllers, which have a lifline group "1.1". I also have a third flush shutter, installed before the update to the newest beta of Domoticz and is still in group "1". This device does refresh when chaning position of the shutter.
The new two do not update.

[hestia]

Resolved in this topic https://www.domoticz.com/forum/viewtopi ... 15#p225812