ZIF5028/LHC5028 fejl i HS3 implementering
ZIF5028/LHC5028 fejl i HS3 implementering
Jeg er i fuld gang med at installer 7xZIF5028 fra Logic Group i forbindelse med en komplet renovering af en bolig. Som zwave gateway benyttes ZMEEUZB1 og controlleren er HS3.
Til min forundring præsenteres alle indgange og udgange ens, dvs. De er benævnt fra Switch 1 til Switch 12, Hvor Switch 1 til 6 er de 6 udgange og Switch 7 til 12 repræsenteres som indgang 1 til 6
Hvis jeg aktivere indgang 1 elektrisk, trækker relæ i udgang 1 osv, alt som forventet.
Men når jeg aktivere indgangene i Homeseer aktiverer indgang 1 ingenting, indgang 2 aktiverer udgang 1, indgang 3 aktivere også udgang 1, indgang 4 aktivere udgang 2, indgang 5 aktivere udgang 3 og indgang 6 aktivere udgang 4. Udgang 5 og 6 kan ikke aktiveres fra Homeseer.
Jeg har også prøvet den gamle udgave af ZIF5028 som hedder LHC5028, den reagere på samme måde. De kører begge firmware 0,8.
Derudover får en information i loggen når en indgang aktivers som jeg aldrig har set tidligere
”Payload1 zd is not nothing”
Jeg har iøvrigt testet secure og unsecure, jeg har ikke ændret på nogen parametre i ZIF’en.
Er der andre som har ZIF5028 på Homeseer 3 med har samme problem?
Nedenstående er et link til en fyr som oplever samme type problem på en ZIF5020.
https://forums.homeseer.com/forum/homes ... er-outouts
Til min forundring præsenteres alle indgange og udgange ens, dvs. De er benævnt fra Switch 1 til Switch 12, Hvor Switch 1 til 6 er de 6 udgange og Switch 7 til 12 repræsenteres som indgang 1 til 6
Hvis jeg aktivere indgang 1 elektrisk, trækker relæ i udgang 1 osv, alt som forventet.
Men når jeg aktivere indgangene i Homeseer aktiverer indgang 1 ingenting, indgang 2 aktiverer udgang 1, indgang 3 aktivere også udgang 1, indgang 4 aktivere udgang 2, indgang 5 aktivere udgang 3 og indgang 6 aktivere udgang 4. Udgang 5 og 6 kan ikke aktiveres fra Homeseer.
Jeg har også prøvet den gamle udgave af ZIF5028 som hedder LHC5028, den reagere på samme måde. De kører begge firmware 0,8.
Derudover får en information i loggen når en indgang aktivers som jeg aldrig har set tidligere
”Payload1 zd is not nothing”
Jeg har iøvrigt testet secure og unsecure, jeg har ikke ændret på nogen parametre i ZIF’en.
Er der andre som har ZIF5028 på Homeseer 3 med har samme problem?
Nedenstående er et link til en fyr som oplever samme type problem på en ZIF5020.
https://forums.homeseer.com/forum/homes ... er-outouts
-
- Indlæg: 6507
- Tilmeldt: 20 mar 2008, 23:02
- Geografisk sted: Danmark
Re: ZIF5028/LHC5028 fejl i HS3 implementering
Hej.
Jeg bad Logic Group kigge på indlæget her. Her er svaret.
"Ja, det ser da vist ikke for godt ud – jeg vil anbefale vedkommende at skrive direkte til vores support: support@logic-group.com, så får vi kigget på problemet og, hvis der er et problem i ZIF5028, så får vi løst det."
Jeg bad Logic Group kigge på indlæget her. Her er svaret.
"Ja, det ser da vist ikke for godt ud – jeg vil anbefale vedkommende at skrive direkte til vores support: support@logic-group.com, så får vi kigget på problemet og, hvis der er et problem i ZIF5028, så får vi løst det."
Mvh
Morten
Morten
Re: ZIF5028/LHC5028 fejl i HS3 implementering
Hej Morten.
Tak for det, jeg skriver til dem. Det kunne godt se ud som om der ikke er mange der benytter ZIF5028 eller Heatit Z-DIN 616 versionen sammen med Homeseer.
Mvh.
Søren
Tak for det, jeg skriver til dem. Det kunne godt se ud som om der ikke er mange der benytter ZIF5028 eller Heatit Z-DIN 616 versionen sammen med Homeseer.
Mvh.
Søren
Re: ZIF5028/LHC5028 fejl i HS3 implementering
Logic-Group har allerede svaret, at de er i gang med at finde en løsning, de er godt nok hurtige.
-
- Indlæg: 6507
- Tilmeldt: 20 mar 2008, 23:02
- Geografisk sted: Danmark
Re: ZIF5028/LHC5028 fejl i HS3 implementering
Jeps dem kan jeg godt lide. 
HS3 delen kan jeg måske hjælpe lidt med, men ZIF5028 kender jeg desværre ikke.

HS3 delen kan jeg måske hjælpe lidt med, men ZIF5028 kender jeg desværre ikke.
Mvh
Morten
Morten
Re: ZIF5028/LHC5028 fejl i HS3 implementering
Den fejl har jeg haft siden december 2018. Måtte købe et modul mere for at styre alle mine gulvvarme telestater.
Re: ZIF5028/LHC5028 fejl i HS3 implementering
Så kom svaret.
Hello Søren,
Your scenario was recreated and tested.
The behavior is exactly as you have described.
The situation is that when switch7(input1) is toggled in HomeSeer web interface, Multichannel encapsulated command is sent to endpoint 7 of the root device. And as a result, no relay switching , as this is expected behavior of our device*.
Now the strange part:
Toggling switch7(input1) => endpoint 7 (This is logical) this will change input 1 state Even though it does not do what you want, this is the expected behavior. Under Switch 7 settings t is possible to setup "Linked device" option and select Switch 1 in HomeSeer to achieve desired behavior.
Toggling switch8(input2) => endpoint 0 (root device, mapped to endpoint 1) this will trigger output
Toggling switch9(input3) => endpoint 1 (mapped to root device) this will trigger output 1
Toggling switch10(input4) => endpoint 2 this will trigger output 2
Toggling switch11(input5) => endpoint 3 this will trigger output 3
Toggling switch12(input6) => endpoint 4 this will trigger output 4
So the fact that something is switching when inputs are toggled is more of coincidence and unexplained behavior/decisions of HomeSeer.
I have no idea how HomeSeer decided to map them in such way. Nor it was possible to find where this data is located in local files in order to be manually edited and fixed.
I will contact HomeSeer support to try to find out why it is as it is and if something could be done.
*To elaborate more on this behavior:
Lets imagine a simple setup. We have random Z-Wave controller, 5028 module with Lightbulb connected to output1 and 2 switches connected to input1 and input2.
By default input1 and 2 switch the state of relay of outputs 1 and 2 correspondingly.
A person can walk to switch1 press it which will toggle the state of output 1 and the Lightbulb.
A person can toggle the state of output 1 directly from his Z-Wave controller. (Based on the controller brand/type it can be done from PC/TABLET/MOBILE via app an app, web interface etc.)
A person can toggle the state of output 1 directly from any other Z-Wave device in the network if Associations are set up properly in that device.
As there is nothing connected to output2 person can disable input2 controlling the status of output2 by changing related configuration parameter(nr20 in this case).After changing the parameter, Input2 does not control output2 anymore , while output 2 is still possible to toggle externally/remotely.
As a result input2 can be used to directly control other Z-Wave devices through association groups, events/automations/flows supported by controller as well as serve its role in Central Scene Notifications.
The question: Why would a person want to toggle inputX remotely to toggle ouputX, why not toggle outputX in the first place?
Conclusion:
The described/desired behavior is not supported by the device without a workaround in HomeSeer which involves setting up "linked device" option for endpoints 7-12.
In fact the desired behavior might not be the best way to go, and maybe the you should consider a "direct" approach of controlling outputs, or provide a detailed description/scenario why exactly it should be done as described, so we can help to achieve desired behavior.
The HomeSeer treats endpoints 8-12 incorrectly and instead communicates with endpoints 1-4. This will be adressed to HomeSeer support.
Please do not hesitate to contact us if you have any additional questions.
Hello Søren,
Your scenario was recreated and tested.
The behavior is exactly as you have described.
The situation is that when switch7(input1) is toggled in HomeSeer web interface, Multichannel encapsulated command is sent to endpoint 7 of the root device. And as a result, no relay switching , as this is expected behavior of our device*.
Now the strange part:
Toggling switch7(input1) => endpoint 7 (This is logical) this will change input 1 state Even though it does not do what you want, this is the expected behavior. Under Switch 7 settings t is possible to setup "Linked device" option and select Switch 1 in HomeSeer to achieve desired behavior.
Toggling switch8(input2) => endpoint 0 (root device, mapped to endpoint 1) this will trigger output
Toggling switch9(input3) => endpoint 1 (mapped to root device) this will trigger output 1
Toggling switch10(input4) => endpoint 2 this will trigger output 2
Toggling switch11(input5) => endpoint 3 this will trigger output 3
Toggling switch12(input6) => endpoint 4 this will trigger output 4
So the fact that something is switching when inputs are toggled is more of coincidence and unexplained behavior/decisions of HomeSeer.
I have no idea how HomeSeer decided to map them in such way. Nor it was possible to find where this data is located in local files in order to be manually edited and fixed.
I will contact HomeSeer support to try to find out why it is as it is and if something could be done.
*To elaborate more on this behavior:
Lets imagine a simple setup. We have random Z-Wave controller, 5028 module with Lightbulb connected to output1 and 2 switches connected to input1 and input2.
By default input1 and 2 switch the state of relay of outputs 1 and 2 correspondingly.
A person can walk to switch1 press it which will toggle the state of output 1 and the Lightbulb.
A person can toggle the state of output 1 directly from his Z-Wave controller. (Based on the controller brand/type it can be done from PC/TABLET/MOBILE via app an app, web interface etc.)
A person can toggle the state of output 1 directly from any other Z-Wave device in the network if Associations are set up properly in that device.
As there is nothing connected to output2 person can disable input2 controlling the status of output2 by changing related configuration parameter(nr20 in this case).After changing the parameter, Input2 does not control output2 anymore , while output 2 is still possible to toggle externally/remotely.
As a result input2 can be used to directly control other Z-Wave devices through association groups, events/automations/flows supported by controller as well as serve its role in Central Scene Notifications.
The question: Why would a person want to toggle inputX remotely to toggle ouputX, why not toggle outputX in the first place?
Conclusion:
The described/desired behavior is not supported by the device without a workaround in HomeSeer which involves setting up "linked device" option for endpoints 7-12.
In fact the desired behavior might not be the best way to go, and maybe the you should consider a "direct" approach of controlling outputs, or provide a detailed description/scenario why exactly it should be done as described, so we can help to achieve desired behavior.
The HomeSeer treats endpoints 8-12 incorrectly and instead communicates with endpoints 1-4. This will be adressed to HomeSeer support.
Please do not hesitate to contact us if you have any additional questions.
-
- Indlæg: 1
- Tilmeldt: 19 mar 2023, 14:58
Re: ZIF5028/LHC5028 fejl i HS3 implementering
Hej Søren
Fik du ZIF modulet til at opføre sig som det skal?
Sidder nemlig og døjer lidt med samme modul
Vil benytte indgangene til at måle strøm med, men når man kortslutter en af indgangene så tænder/slukker den relæerne = ikke det jeg vil
Håber du er kommet længere og hører gerne
Mvh
Lars
Fik du ZIF modulet til at opføre sig som det skal?
Sidder nemlig og døjer lidt med samme modul
Vil benytte indgangene til at måle strøm med, men når man kortslutter en af indgangene så tænder/slukker den relæerne = ikke det jeg vil

Håber du er kommet længere og hører gerne

Mvh
Lars