+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10)
+--- Thread: Zigbee gateway integration (/showthread.php?tid=3320)
RE: Zigbee gateway integration - Daniel - 05.03.2025
Did you try opening network and setting device in to pairing mode?
RE: Zigbee gateway integration - Erwin van der Zwart - 10.03.2025
Hi,
Can we add this profile? It's for Wireless Emergency Lightning, or will the GreenPower clusters be an issue like with the Powertags?
Code:
Manufacturer: Schneider Electric
Model: OVA47211
Firmware version: 001.001.001
Device type: Router
Power source: Mains
Receive when idle: Yes
Endpoint 1
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- OnOff (6)
- HaDiagnostic (2821)
- 65301
- 65316
Output clusters
- Ota (25)
Endpoint 242
Profile: 41440
Output clusters
- GreenPower (33)
Reported attributes
- calclevel: 0
- onoff: false
- prevlevel: 254RE: Zigbee gateway integration - admin - 10.03.2025
Profile is not needed for On/Off control.
There are two custom clusters which cannot be implemented without documentation.
RE: Zigbee gateway integration - Erwin van der Zwart - 10.03.2025
Thanks, I will ask our team to see if we can implement it somehow, tbc..
RE: Zigbee gateway integration - hocine - 10.03.2025
Hello,
I have installed the VIMAR ‘wheelthermostat’ thermostat on some installations and recently VIMAR updated its firmware to version 1.06, it is no longer recognised the Zigbee module.
I've put the two profiles below and there's nothing that changes except the version.
Is there anything we can do?
The old Firmware
Model: WheelThermostat_v1.0
Firmware version: 1.0.0_z
Device type: Router
Power source: Mains
Receive when idle: Yes
Endpoint 10
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- HvacThermostat (513)
Endpoint 242
Profile: 41440
Output clusters
- GreenPower (33)
Reported attributes
- coolingstatus: false
- heatingstatus: true
- localtemperature: 18.60
- occupiedcoolingsetpoint: 40.00
- occupiedheatingsetpoint: 18.00
- systemmode: 4
The new one
Fabricant: Vimar
Modèle : WheelThermostat_v1.0
Version du micrologiciel : 1.0.6_z
Type d'appareil : routeur
Source d'alimentation : secteur
Recevoir en mode inactif : Oui
Point final 10
Profil : 260
Groupes d'entrée
- Basique (0)
- Identifier (3)
- Identifier (3)
Groupes de sortie
- Thermostat CVC (513)
Point final 242
Profil : 41440
Groupes de sortie
- Énergie verte (33)
Attributs signalés
- état de refroidissement : faux
- statut de chauffage : faux
- température locale : 21,70
- point de consigne de refroidissement occupé : 40,00
- point de consigne de chauffage occupé : 20,00
- mode système : 0
RE: Zigbee gateway integration - admin - 10.03.2025
Contact the thermostat manufacturer. They've moved HvacThermostat cluster from Input clusters to Output clusters so commands cannot be sent to it anymore.
Most likely they wanted to put HvacThermostat cluster into both Input and Output but instead they have Identify Input cluster listed twice.
RE: Zigbee gateway integration - hocine - 10.03.2025
(10.03.2025, 14:11)admin Wrote: Contact the thermostat manufacturer. They've moved HvacThermostat cluster from Input clusters to Output clusters so commands cannot be sent to it anymore.
Most likely they wanted to put HvacThermostat cluster into both Input and Output but instead they have Identify Input cluster listed twice.
and it's not possible to do something manually via script?
I've been looking for a long time for a wired Zigbee thermostat that works and now I'm back to zero.
The Schneider electric S520619 thermostat is still not compatible.
Manufacturer: Schneider Electric
Model: S520619
Firmware version: 001.000.053
Device type: Router
Power source: Mains
Receive when idle: Yes
Endpoint 1
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- Groups (4)
- HvacThermostat (513)
- HvacUserInterfaceCfg (516)
- HaDiagnostic (2821)
- ManuSpecificWiserEvent (65027)
- ManuSpecificCycleTime (65302)
- ManuSpecificHeatingCooling (65315)
Output clusters
- Identify (3)
- Time (10)
- Ota (25)
- MsTemperatureMeasurement (1026)
- MsOccupancySensing (1030)
Endpoint 2
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- MsTemperatureMeasurement (1026)
Output clusters
- Identify (3)
Endpoint 4
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- MsOccupancySensing (1030)
Output clusters
- Identify (3)
Endpoint 5
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- Groups (4)
- SeMetering (1794)
Endpoint 242
Profile: 41440
Output clusters
- GreenPower (33)
Reported attributes
- occupancy: true
- temperature: 19.22
RE: Zigbee gateway integration - admin - 10.03.2025
Some other Schneider Electric thermostats are already supported. S520619 looks quite similar so it will be added to the app. I'll send you a test version when it's ready.
RE: Zigbee gateway integration - Erwin van der Zwart - 14.03.2025
Is it possible to read the Zigbee version of a device from applibs.zigbee? If yes how, i need to determine if Zigbee 2 or 3 is used before sending the HW to a 3th party..
RE: Zigbee gateway integration - admin - 14.03.2025
You can try reading the Stack version attribute. But it's optional so you might not get a reply from the device.
Code:
zb = require('applibs.zigbee')
-- Basic / StackVersion
res, err = zb.cmdsync('getrawattribute', '0123456789abcdef', 0, 2)
log(res, err)RE: Zigbee gateway integration - Erwin van der Zwart - 14.03.2025
Thnks but to bad.. Any other ideas?
Code:
Test 14.03.2025 12:15:26
* arg: 1
* nil
* arg: 2
* nilRE: Zigbee gateway integration - admin - 14.03.2025
I don't see any other options in the standard.
RE: Zigbee gateway integration - Erwin van der Zwart - 14.03.2025
When i do this:
Code:
zb = require('applibs.zigbee.zigbee')
addr = '04cd15fffe7ccf75'
cluster = 0x0000 -- Basic
attrs = { 'ZCLVersion' }
res, err = zb.cmdsync('getnamedattributes', addr, cluster, attrs)
log(res, err)Code:
* arg: 1
* table:
["ZCLVersion"]
* number: 3RE: Zigbee gateway integration - admin - 14.03.2025
It's ZigBee Cluster Library version. Newer devices will report a larger number, for example 8.