Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request Device Support ] Legrand Netatmo device #883

Closed
Smanar opened this issue Oct 18, 2018 · 203 comments

Comments

@Smanar
Copy link
Contributor

@Smanar Smanar commented Oct 18, 2018

Hi, I have a new device who works strangely, All seems good, but the led on the device stay red (go off on normal full commissioning) and on deconz it go to yellow then red.
It's a device from the netatmo gamme from Legrand https://www.netatmo.com/partners/legrand. Called Mosaic, Celiane, Dooxie or Valena.
I m making my test with the switch without neutral (legrand 600081) , see as light and not switch (I think it's normal because it control light on/off+ dimmer)

basicattribute
cluster
nodeinfo

IDK if there is a special protection or not, I can send a complete sniff make with ubiqua from the power on to the final led change make with the offciel centrale. Here a sample
snif

I take all propositions and ideas.
BTW I have some others questions:

  • The firmware is closed or open source ?
  • How I can send custom command like for read a special attribute on an unknow cluster ?
@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 20, 2018

I have make a second try with sniffing with conbee key, and there is a lot of missing request.

zigbeeprotocol

Missing:
Request key B
Transport key B
Verify key B
Confirm key

Mgmt permit join request is not send by the device too after the key echange.

snif2

Do I need to enable master key in option, but how (not supported in the release ?)?

@manup

This comment has been minimized.

Copy link
Member

@manup manup commented Oct 20, 2018

Looks like the communication and security is alright since there is some exchange of messages on ZDP level.

But the switch leaves the network for some reason, so I guess it waited for specific commands or configuration (binding?). Question is which :)

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 20, 2018

Yep, but on the first "sniff" (this one with the official central) there is only classic request, so I think the specific expected command isn't an exotic command like a manufactured one.
But not using the 2 keys echange can be the problem, and it seems it s not implemented in this version yet. ATM Deconz only use a light key echange protocol.

For information, if you use this device out of the box, it works without problems, but with less functionnalities, you need to update it (with the central), but after the update it stops working.

On the application options, I m seeing a "master key" option, not implemeted yet, you know what is it ?

Here a screenshoot for the first sniff with filter on the good device with the official central. Easier to compare.
snifclean

@manup

This comment has been minimized.

Copy link
Member

@manup manup commented Oct 20, 2018

They key and security setup is really finished here with the transport key command, a tunnel command would only be used if there was a router in between. deCONZ firmware has only enabled NWK layer security, APS layer security isn't used in ZLL/HA applications, albeit possible I wouldn't expect the switch to require APS layer security.

The two nodes wouldn't be able to exchange the further messages like node descriptor and the like if security wasn't established.

Therefore it would be interesting which messages the original central and the switch exchange after the key exchange, any bindings or read write attributes?

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 21, 2018

I m comparing the 2 captures and I can say

  • the device leave 15 s after the association request on ConBee

  • On the both capture we have
    -- device announce
    -- Node descriptor request+Response

  • Only on the working
    -- Basic read attribute request+response
    -- Match descriptor request+response
    -- IEE address + response
    -- OTA upgrade request+response
    -- A message permit join request ( ? but it s from device to central so useless I think)
    -- Add group/scene
    -- Bind request+response (20s after the association request so I have stoped here)

  • Only on the no working
    -- Active Endpoint request+response
    -- Management lqi request+response
    -- Simple descriptor request+response

On the layer NWK, on the working mode We have
link status centrale > broadcast
Route request 0x270F centrale > broadcast
Route request 0x270F all devices> broadcast

I will make some tries with more request with conbee and forcing some commands like ota or attribute read.

@manup

This comment has been minimized.

Copy link
Member

@manup manup commented Oct 21, 2018

-- Add group/scene
-- Bind request+response (20s after the association request so I have stoped here)

These are the ones I meant :) the switch might wait for this configuration to be done.
Can you please provide the sniffed details of these requests?

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 21, 2018

[17:35:55.389280]	Groups: Add Group	61-88-84-AD-DA-86-BD-00-00-48-02-86-BD-00-00-14-62-28-2B-00-11-00-58-32-18-00-00-74-04-00-00-B3-03-43-A9-EA-9E-54-BA-25-28-02-9E-19-E6-9D-07-8F-1E-D4-36
Frame Information: (51 bytes)
	Packet ID: 219
	Protocol: ZigBee
	Date: 2018/09/26
	Timestamp: 17:35:55.389280
	Time Delta: 0.178480
	Channel: 11
	Length: 51
	RSSI: -60 dBm
	Source: COM8: NXP JN51xx / Rainforest Toucan@1000000
	Layer: ZCL
	Status: Decrypted
MAC Header: (9 bytes)
	Frame Control: 0x8861
		···· ···· ···· ·001 = Frame Type: [0x1] Data
		···· ···· ···· 0··· = Security Enabled: [0x0] No
		···· ···· ···0 ···· = Frame Pending: [0x0] No
		···· ···· ··1· ···· = Acknowledgement Request: [0x1] Yes
		···· ···· ·1·· ···· = Intra-PAN: [0x1] Yes
		···· ··00 0··· ···· = Reserved: 0x0
		···· 10·· ···· ···· = Destination Addr Mode: [0x2] 16-bit Short Address
		··00 ···· ···· ···· = Reserved: 0x0
		10·· ···· ···· ···· = Source Addr Mode: [0x2] 16-bit Short Address
	Sequence Number: 132
	Destination PAN ID: 0xDAAD
	Destination Address: 0xBD86
	Source Address: 0x0000
MAC Payload: (40 bytes)
	NWK Header: 0x62140000BD860248
		Frame Control: 0x0248
			···· ···· ···· ··00 = Frame Type: [0x0] Data
			···· ···· ··00 10·· = Protocol Version: [0x2] ZigBee Pro
			···· ···· 01·· ···· = Route Discovery: [0x1] Enabled
			···· ···0 ···· ···· = Multicast Flag: [0x0] Unicast or Broadcast
			···· ··1· ···· ···· = Security Enabled: [0x1] Yes
			···· ·0·· ···· ···· = Source Route Included: [0x0] No
			···· 0··· ···· ···· = Destination IEEE Address Included: [0x0] No
			···0 ···· ···· ···· = Source IEEE Address Included: [0x0] No
			··0· ···· ···· ···· = End Device Initiator: [0x0] No
			00·· ···· ···· ···· = Reserved: 0x0
		Destination Address: 0xBD86
		Source Address: 0x0000
		Radius: 0x14
		Sequence Number: 98
	NWK Aux Header: (14 bytes)
		Network Security Control: 0x28
			···· ·000 = Network Security Level: [0x0] None
			···0 1··· = Key NWK ID: [0x1] Network Key
			··1· ···· = Extended Nonce: [0x1] Yes
			00·· ···· = Reserved: 0x0
		NWK Frame Counter: 1114155
		Source Address: 00:04:74:00:00:18:32:58
		NWK Key Sequence Number: 0
	NWK Payload: (14 bytes)
		APS Header: 0x9401010400040140
			Frame Control: 0x40
				···· ··00 = Frame Type: [0x0] Data
				···· 00·· = Delivery Mode: [0x0] Normal Unicast Delivery
				···0 ···· = Acknowledgement Format: 0x0
					Format: [0x0] Data Frame
				··0· ···· = Security Enabled: [0x0] No
				·1·· ···· = Acknowledgement Request: 0x1
					Request: [0x1] Yes
				0··· ···· = Extended Header Present: [0x0] No
			Destination Endpoint: 0x01
			Cluster ID: [0x0004] General: Groups
			Profile ID: [0x0104] ZigBee Home Automation
			Source Endpoint: 0x01
			APS Counter: 148
		APS Payload: 0x00FFF6000711
			ZCL Header: 0x000711
				Frame Control: 0x11
					···· ··01 = Frame Type: [0x1] Command is Specific to a Cluster
					···· ·0·· = Manufacturer Specific: [0x0] Manufacturer Code Not Included in the ZCL Frame
					···· 0··· = Direction: [0x0] From Client to Server
					···1 ···· = Disable Default Response: [0x1] Yes
					000· ···· = Reserved: 0x0
				Transaction Sequence Number: 7
				Command ID: [0x00] Add Group
			ZCL Payload: 0x00FFF6
				Group ID: 0xFFF6
				Group Name: 0x00
					Length: [0] Empty String
	NWK MIC: 0x88A3970D
MAC Footer: 0x36D4
	Frame Check Sequence: 0x36D4
[17:35:58.683792]	Bind Request	61-88-90-AD-DA-86-BD-00-00-48-02-86-BD-00-00-14-6D-28-37-00-11-00-58-32-18-00-00-74-04-00-00-5F-76-21-97-9E-63-8E-72-D7-C7-9F-1E-F1-5C-02-2A-9D-B2-E5-64-3A-4A-6B-C8-5C-E3-CA-E3-EA-37-58-C9-36-B8-83-41
Frame Information: (67 bytes)
	Packet ID: 272
	Protocol: ZigBee
	Date: 2018/09/26
	Timestamp: 17:35:58.683792
	Time Delta: 0.690560
	Channel: 11
	Length: 67
	RSSI: -60 dBm
	Source: COM8: NXP JN51xx / Rainforest Toucan@1000000
	Layer: ZDP
	Status: Decrypted
MAC Header: (9 bytes)
	Frame Control: 0x8861
		···· ···· ···· ·001 = Frame Type: [0x1] Data
		···· ···· ···· 0··· = Security Enabled: [0x0] No
		···· ···· ···0 ···· = Frame Pending: [0x0] No
		···· ···· ··1· ···· = Acknowledgement Request: [0x1] Yes
		···· ···· ·1·· ···· = Intra-PAN: [0x1] Yes
		···· ··00 0··· ···· = Reserved: 0x0
		···· 10·· ···· ···· = Destination Addr Mode: [0x2] 16-bit Short Address
		··00 ···· ···· ···· = Reserved: 0x0
		10·· ···· ···· ···· = Source Addr Mode: [0x2] 16-bit Short Address
	Sequence Number: 144
	Destination PAN ID: 0xDAAD
	Destination Address: 0xBD86
	Source Address: 0x0000
MAC Payload: (56 bytes)
	NWK Header: 0x6D140000BD860248
		Frame Control: 0x0248
			···· ···· ···· ··00 = Frame Type: [0x0] Data
			···· ···· ··00 10·· = Protocol Version: [0x2] ZigBee Pro
			···· ···· 01·· ···· = Route Discovery: [0x1] Enabled
			···· ···0 ···· ···· = Multicast Flag: [0x0] Unicast or Broadcast
			···· ··1· ···· ···· = Security Enabled: [0x1] Yes
			···· ·0·· ···· ···· = Source Route Included: [0x0] No
			···· 0··· ···· ···· = Destination IEEE Address Included: [0x0] No
			···0 ···· ···· ···· = Source IEEE Address Included: [0x0] No
			··0· ···· ···· ···· = End Device Initiator: [0x0] No
			00·· ···· ···· ···· = Reserved: 0x0
		Destination Address: 0xBD86
		Source Address: 0x0000
		Radius: 0x14
		Sequence Number: 109
	NWK Aux Header: (14 bytes)
		Network Security Control: 0x28
			···· ·000 = Network Security Level: [0x0] None
			···0 1··· = Key NWK ID: [0x1] Network Key
			··1· ···· = Extended Nonce: [0x1] Yes
			00·· ···· = Reserved: 0x0
		NWK Frame Counter: 1114167
		Source Address: 00:04:74:00:00:18:32:58
		NWK Key Sequence Number: 0
	NWK Payload: (30 bytes)
		APS Header: 0x9800000000210000
			Frame Control: 0x00
				···· ··00 = Frame Type: [0x0] Data
				···· 00·· = Delivery Mode: [0x0] Normal Unicast Delivery
				···0 ···· = Acknowledgement Format: 0x0
					Format: [0x0] Data Frame
				··0· ···· = Security Enabled: [0x0] No
				·0·· ···· = Acknowledgement Request: 0x0
					Request: [0x0] No
				0··· ···· = Extended Header Present: [0x0] No
			Destination Endpoint: 0x00
			Cluster ID: [0x0021] Bind Request
			Profile ID: [0x0000] ZigBee Device Profile
			Source Endpoint: 0x00
			APS Counter: 152
		APS Payload: (22 bytes)
			ZDP Transaction Sequence Number: 3
			Bind Request: (21 bytes)
				Source Address: 00:04:74:00:00:7A:26:66
				Source Endpoint: 0x01
				Cluster ID: 0x0006
				Destination Address Mode: [0x03] Direct 64-bit Addr Mode and EP
				Destination Address: 00:04:74:00:00:18:32:58
				Destination Endpoint: 0x01
	NWK MIC: 0xCC37210B
MAC Footer: 0x4183
	Frame Check Sequence: 0x4183

[17:35:58.703167]	Bind Response	61-88-91-AD-DA-00-00-86-BD-48-02-00-00-86-BD-14-FE-28-21-00-1C-00-66-26-7A-00-00-74-04-00-00-61-C7-2E-27-6B-4C-73-5C-9E-88-A7-5B-4D-18-66-B7
Frame Information: (47 bytes)
	Packet ID: 274
	Protocol: ZigBee
	Date: 2018/09/26
	Timestamp: 17:35:58.703167
	Time Delta: 0.016848
	Channel: 11
	Length: 47
	RSSI: -60 dBm
	Source: COM8: NXP JN51xx / Rainforest Toucan@1000000
	Layer: ZDP
	Status: Decrypted
MAC Header: (9 bytes)
	Frame Control: 0x8861
		···· ···· ···· ·001 = Frame Type: [0x1] Data
		···· ···· ···· 0··· = Security Enabled: [0x0] No
		···· ···· ···0 ···· = Frame Pending: [0x0] No
		···· ···· ··1· ···· = Acknowledgement Request: [0x1] Yes
		···· ···· ·1·· ···· = Intra-PAN: [0x1] Yes
		···· ··00 0··· ···· = Reserved: 0x0
		···· 10·· ···· ···· = Destination Addr Mode: [0x2] 16-bit Short Address
		··00 ···· ···· ···· = Reserved: 0x0
		10·· ···· ···· ···· = Source Addr Mode: [0x2] 16-bit Short Address
	Sequence Number: 145
	Destination PAN ID: 0xDAAD
	Destination Address: 0x0000
	Source Address: 0xBD86
MAC Payload: (36 bytes)
	NWK Header: 0xFE14BD8600000248
		Frame Control: 0x0248
			···· ···· ···· ··00 = Frame Type: [0x0] Data
			···· ···· ··00 10·· = Protocol Version: [0x2] ZigBee Pro
			···· ···· 01·· ···· = Route Discovery: [0x1] Enabled
			···· ···0 ···· ···· = Multicast Flag: [0x0] Unicast or Broadcast
			···· ··1· ···· ···· = Security Enabled: [0x1] Yes
			···· ·0·· ···· ···· = Source Route Included: [0x0] No
			···· 0··· ···· ···· = Destination IEEE Address Included: [0x0] No
			···0 ···· ···· ···· = Source IEEE Address Included: [0x0] No
			··0· ···· ···· ···· = End Device Initiator: [0x0] No
			00·· ···· ···· ···· = Reserved: 0x0
		Destination Address: 0x0000
		Source Address: 0xBD86
		Radius: 0x14
		Sequence Number: 254
	NWK Aux Header: (14 bytes)
		Network Security Control: 0x28
			···· ·000 = Network Security Level: [0x0] None
			···0 1··· = Key NWK ID: [0x1] Network Key
			··1· ···· = Extended Nonce: [0x1] Yes
			00·· ···· = Reserved: 0x0
		NWK Frame Counter: 1835041
		Source Address: 00:04:74:00:00:7A:26:66
		NWK Key Sequence Number: 0
	NWK Payload: (10 bytes)
		APS Header: 0xD900000080210000
			Frame Control: 0x00
				···· ··00 = Frame Type: [0x0] Data
				···· 00·· = Delivery Mode: [0x0] Normal Unicast Delivery
				···0 ···· = Acknowledgement Format: 0x0
					Format: [0x0] Data Frame
				··0· ···· = Security Enabled: [0x0] No
				·0·· ···· = Acknowledgement Request: 0x0
					Request: [0x0] No
				0··· ···· = Extended Header Present: [0x0] No
			Destination Endpoint: 0x00
			Cluster ID: [0x8021] Bind Response
			Profile ID: [0x0000] ZigBee Device Profile
			Source Endpoint: 0x00
			APS Counter: 217
		APS Payload: 0x0003
			ZDP Transaction Sequence Number: 3
			Bind Response: 0x00
				Status: [0x00] Success
	NWK MIC: 0x29D5EE27
MAC Footer: 0xB766
	Frame Check Sequence: 0xB766

Hu !
I m seing something, (the device have the adress BD86) so it's the device itself who ask for "basic read attribute" (Request n 159) to the device router, not the coordinator. And this request is make in the first trame, so perhpas the blocking request is just between the commissioning frame (Request n 96 ) and this one.
In fact in normal mode the device is more active.

I have others devices ikea bulb, usb device, there is a way to force the installation to work like the original one ? In fact the central have a buildin device inside, it s 'not possible to use the original central without the router, the prb is perhaps from here.

I can send you the captured packet in ubiqua format if you have a public email ? But there is too much differences betwen the working mode with and without router.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 21, 2018

Yeah ^^.
I have make a try with an ikea bulb as router, and It works ^^, at least the on/off, not the dimmer but on normal usage you need to enable this option with application.

I will post a sniff soon.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 21, 2018

workingsniff

The sniff during a working process with Deconz. I can 't explain what happen, the device try 1 time, leave , retry and it works.
But on the same sniff, I have a working try and a not working. I can send the file if you have an email to send it.

Now New try with the centrale to get all the special command to enable led and dimmer.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 21, 2018

Now I need help, this is the missing cluster/attribute I need to control it, can you say me witch one files I can edit to make it working ? Do I need to make a full integration with the new manufacture too, or just add cluster ? It seem all is hard coded ?

Frame Information: (53 bytes)
	Packet ID: 13
	Protocol: ZigBee
	Date: 2018/10/21
	Timestamp: 15:31:03.061918
	Time Delta: 2.172160
	Channel: 11
	Length: 53
	RSSI: -90 dBm
	Source: COM9: NXP JN51xx / Rainforest Toucan@1000000
	Layer: ZCL
	Status: Decrypted
MAC Header: (9 bytes)
	Frame Control: 0x8861
		···· ···· ···· ·001 = Frame Type: [0x1] Data
		···· ···· ···· 0··· = Security Enabled: [0x0] No
		···· ···· ···0 ···· = Frame Pending: [0x0] No
		···· ···· ··1· ···· = Acknowledgement Request: [0x1] Yes
		···· ···· ·1·· ···· = Intra-PAN: [0x1] Yes
		···· ··00 0··· ···· = Reserved: 0x0
		···· 10·· ···· ···· = Destination Addr Mode: [0x2] 16-bit Short Address
		··00 ···· ···· ···· = Reserved: 0x0
		10·· ···· ···· ···· = Source Addr Mode: [0x2] 16-bit Short Address
	Sequence Number: 14
	Destination PAN ID: 0xDAAD
	Destination Address: 0x2EBE
	Source Address: 0x0000
MAC Payload: (42 bytes)
	NWK Header: 0x081400002EBE0248
		Frame Control: 0x0248
			···· ···· ···· ··00 = Frame Type: [0x0] Data
			···· ···· ··00 10·· = Protocol Version: [0x2] ZigBee Pro
			···· ···· 01·· ···· = Route Discovery: [0x1] Enabled
			···· ···0 ···· ···· = Multicast Flag: [0x0] Unicast or Broadcast
			···· ··1· ···· ···· = Security Enabled: [0x1] Yes
			···· ·0·· ···· ···· = Source Route Included: [0x0] No
			···· 0··· ···· ···· = Destination IEEE Address Included: [0x0] No
			···0 ···· ···· ···· = Source IEEE Address Included: [0x0] No
			··0· ···· ···· ···· = End Device Initiator: [0x0] No
			00·· ···· ···· ···· = Reserved: 0x0
		Destination Address: 0x2EBE
		Source Address: 0x0000
		Radius: 0x14
		Sequence Number: 8
	NWK Aux Header: (14 bytes)
		Network Security Control: 0x28
			···· ·000 = Network Security Level: [0x0] None
			···0 1··· = Key NWK ID: [0x1] Network Key
			··1· ···· = Extended Nonce: [0x1] Yes
			00·· ···· = Reserved: 0x0
		NWK Frame Counter: 1572954
		Source Address: 00:04:74:00:00:18:32:58
		NWK Key Sequence Number: 0
	NWK Payload: (16 bytes)
		APS Header: 0x03010104FC010100
			Frame Control: 0x00
				···· ··00 = Frame Type: [0x0] Data
				···· 00·· = Delivery Mode: [0x0] Normal Unicast Delivery
				···0 ···· = Acknowledgement Format: 0x0
					Format: [0x0] Data Frame
				··0· ···· = Security Enabled: [0x0] No
				·0·· ···· = Acknowledgement Request: 0x0
					Request: [0x0] No
				0··· ···· = Extended Header Present: [0x0] No
			Destination Endpoint: 0x01
			Cluster ID: [0xFC01] Private Cluster
			Profile ID: [0x0104] ZigBee Home Automation
			Source Endpoint: 0x01
			APS Counter: 3
		APS Payload: 0x0101090000021910
			ZCL Header: 0x021910
				Frame Control: 0x10
					···· ··00 = Frame Type: [0x0] Command Acts Across the Entire Profile
					···· ·0·· = Manufacturer Specific: [0x0] Manufacturer Code Not Included in the ZCL Frame
					···· 0··· = Direction: [0x0] From Client to Server
					···1 ···· = Disable Default Response: [0x1] Yes
					000· ···· = Reserved: 0x0
				Transaction Sequence Number: 25
				General Command Frame: [0x02] Write Attributes
			ZCL Payload: 0x0101090000
				Attribute 0: 0x0101090000
					Attribute ID: [0x0000] Reserved
					Data Type: [0x09] 16-bit Data
					Unknown Data Type: 0x0101
	NWK MIC: 0x09834125
MAC Footer: 0x5B3A
	Frame Check Sequence: 0x5B3A

Data 0101 > Enable dimmer
Data 0100 > Disable dimmer

Frame Information: (52 bytes)
	Packet ID: 97
	Protocol: ZigBee
	Date: 2018/10/21
	Timestamp: 15:37:11.730350
	Time Delta: 0.522464
	Channel: 11
	Length: 52
	RSSI: -83 dBm
	Source: COM9: NXP JN51xx / Rainforest Toucan@1000000
	Layer: ZCL
	Status: Decrypted
MAC Header: (9 bytes)
	Frame Control: 0x8861
		···· ···· ···· ·001 = Frame Type: [0x1] Data
		···· ···· ···· 0··· = Security Enabled: [0x0] No
		···· ···· ···0 ···· = Frame Pending: [0x0] No
		···· ···· ··1· ···· = Acknowledgement Request: [0x1] Yes
		···· ···· ·1·· ···· = Intra-PAN: [0x1] Yes
		···· ··00 0··· ···· = Reserved: 0x0
		···· 10·· ···· ···· = Destination Addr Mode: [0x2] 16-bit Short Address
		··00 ···· ···· ···· = Reserved: 0x0
		10·· ···· ···· ···· = Source Addr Mode: [0x2] 16-bit Short Address
	Sequence Number: 70
	Destination PAN ID: 0xDAAD
	Destination Address: 0x2EBE
	Source Address: 0x0000
MAC Payload: (41 bytes)
	NWK Header: 0x401400002EBE0248
		Frame Control: 0x0248
			···· ···· ···· ··00 = Frame Type: [0x0] Data
			···· ···· ··00 10·· = Protocol Version: [0x2] ZigBee Pro
			···· ···· 01·· ···· = Route Discovery: [0x1] Enabled
			···· ···0 ···· ···· = Multicast Flag: [0x0] Unicast or Broadcast
			···· ··1· ···· ···· = Security Enabled: [0x1] Yes
			···· ·0·· ···· ···· = Source Route Included: [0x0] No
			···· 0··· ···· ···· = Destination IEEE Address Included: [0x0] No
			···0 ···· ···· ···· = Source IEEE Address Included: [0x0] No
			··0· ···· ···· ···· = End Device Initiator: [0x0] No
			00·· ···· ···· ···· = Reserved: 0x0
		Destination Address: 0x2EBE
		Source Address: 0x0000
		Radius: 0x14
		Sequence Number: 64
	NWK Aux Header: (14 bytes)
		Network Security Control: 0x28
			···· ·000 = Network Security Level: [0x0] None
			···0 1··· = Key NWK ID: [0x1] Network Key
			··1· ···· = Extended Nonce: [0x1] Yes
			00·· ···· = Reserved: 0x0
		NWK Frame Counter: 1573010
		Source Address: 00:04:74:00:00:18:32:58
		NWK Key Sequence Number: 0
	NWK Payload: (15 bytes)
		APS Header: 0x17010104FC010100
			Frame Control: 0x00
				···· ··00 = Frame Type: [0x0] Data
				···· 00·· = Delivery Mode: [0x0] Normal Unicast Delivery
				···0 ···· = Acknowledgement Format: 0x0
					Format: [0x0] Data Frame
				··0· ···· = Security Enabled: [0x0] No
				·0·· ···· = Acknowledgement Request: 0x0
					Request: [0x0] No
				0··· ···· = Extended Header Present: [0x0] No
			Destination Endpoint: 0x01
			Cluster ID: [0xFC01] Private Cluster
			Profile ID: [0x0104] ZigBee Home Automation
			Source Endpoint: 0x01
			APS Counter: 23
		APS Payload: 0x01100001022F10
			ZCL Header: 0x022F10
				Frame Control: 0x10
					···· ··00 = Frame Type: [0x0] Command Acts Across the Entire Profile
					···· ·0·· = Manufacturer Specific: [0x0] Manufacturer Code Not Included in the ZCL Frame
					···· 0··· = Direction: [0x0] From Client to Server
					···1 ···· = Disable Default Response: [0x1] Yes
					000· ···· = Reserved: 0x0
				Transaction Sequence Number: 47
				General Command Frame: [0x02] Write Attributes
			ZCL Payload: 0x01100001
				Attribute 0: 0x01100001
					Attribute ID: [0x0001] Reserved
					Data Type: [0x10] Boolean
					Unknown Data Type: 0x01
	NWK MIC: 0xEBD68619
MAC Footer: 0xB231
	Frame Check Sequence: 0xB231

Data 01 > enable led in dark
Data 00 > disable led in dark

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 23, 2018

Ok so It seem it's not hardcoded.
I have make this part in general.xml

	<cluster id="fc01" name="Legrand - Specific clusters">
		<description>Legrand Specific clusters.
		</description>
		<server>
			<attribute id="0x0000" name="Dimmer" type="dat16" default="0" access="rw" required="m">
				<value name="Disable dimmer" value="0x0100"></value>
				<value name="Enable Dimmer" value="0x0101"></value>
            </attribute>
			<attribute id="0x0001" type="bool" name="LED" required="m" access="rw" default="0"></attribute>
		</server>
		<client>
		</client>
	<!-- TODO -->
	</cluster>

It seem working, at least for LED, but I can't display the 2 options for dimmer with dat16 type, I can display values with other type (for exemple u16), but I have an error when I try to read/write, no error with dat16, but I can only read the value and I can see it nowhere.

I have tried with enum16, I can set the value, not possible to read it, but after close/open the dialog sa issue, read come possible but nothing to see, except the message "reading done"

setting1
Invisible value ???? And how to set it.

Edit1:
<attribute id="0x0000" name="Dimmer Enable/Disable" type="dat16" default="0x0100" access="rw" required="m" showas="hex"></attribute>
Display "0x" ^^. I rly need explaination how it work !

@manup

This comment has been minimized.

Copy link
Member

@manup manup commented Oct 23, 2018

I've checked the code, this datatype is not yet supported in the deCONZ GUI, I'll add it in the next version.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 23, 2018

Lol, I have spend 1 hour trying all datatypes.
I think this device can work "out of the box" with somes littles hacks (and all other from this gamme). I will wait for next version to continue my tests.

BTW thx a lot for answers :)

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 26, 2018

Just for information I m seing on "about deCONZ" option, I m using this one from the website, it s the V2_05_20
And from https://www.dresden-elektronik.de/deconz/win/ I m seing there is more in date version. Do you want I make tries with this version or better to wait for version > V2_05_42

Edit:
Ok, found the new version, making tries.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 29, 2018

Hi, I m making tries with the version 2.05.44, it's better but when I try to write some data (datatype = dat16, other are working), it's always "0x0000" on sniff (or 0x0100, the last read value).
Do I need to wait for a future version, or it's another problem ?

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Oct 30, 2018

So, waiting for the correction in the GUI, I have used the deconz-cli-plugin with the command
zclattr 0x0eF4 1 0xFC01 020000090101

And now all is perfect, on/off/dimmer/group/led, integration in phoscon is perfect, no bug yet.

The code I have changed in the xml file in
<domain name="Manufacturer Specific" useZcl="true"
part

		<!-- Legrand -->
		<cluster id="0xfc01" name="Legrand - Specific clusters" mfcode="1021">
			<description>Legrand Specific clusters.</description>
			<server>
				<attribute id="0x0000" name="Dimmer" type="dat16" default="0x0101" access="rw" required="m" showas="hex">
					<description>0100 = Dimmer Off, 0101 = Dimmer On</description>
				</attribute>
				<attribute id="0x0001" type="bool" name="LED" required="m" access="rw" default="0">
					<description>Enable LED in dark</description>
				</attribute>
			</server>
			<client>
			</client>
		</cluster>

Tell me if you want more information for integration.

@manup

This comment has been minimized.

Copy link
Member

@manup manup commented Nov 3, 2018

Cool, can you please submit a PR for the general.xml addition?

Hi, I m making tries with the version 2.05.44, it's better but when I try to write some data (datatype = dat16, other are working), it's always "0x0000" on sniff (or 0x0100, the last read value).

Do you mean the write attribute isn't filled with the data provided in Cluster Info Panel?

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 3, 2018

Exactly, I can put any values in the editbox, if I press write, I have the message "sucessfull", but the ConBee always send the same value at the device, and if I press the "read button" it come back to the old value again.
The problem is not from the device, because I have "snif" the request and it rly send the same value whatever is the value in the editbox.

Sure I will make the PR, but I m waiting for the GUI is working again, because without this correction, impossible to enable dimmer without deconz-cli-plugin, so my addition can't work.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 14, 2018

Just tested 2.05.47, bug still here, GUI don't support DAT16.
And I haven't checked but it seem there is exactly the same prb for int24 cf #812

@manup

This comment has been minimized.

Copy link
Member

@manup manup commented Nov 14, 2018

Yes sorry hasn't made it yet, looking forward to fix it in the next release around Friday.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 15, 2018

No problems, I will make tries on futures versions.
But this github is for only the rest plugin or all the deCONZ application ? Because it's a bug in the GUI, nothing to see with the plugin.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 19, 2018

It works, thx again for your app and support :).

So to resume, It s a switch with wire, but without neutral (zero line) with on/off AND dimmer.

  • if you use it "out of the box" it works without problem but I don't think dimmer will work.
  • if you update its firmware with the gateway, it will be harder to pair, you need to use another device as router to make it possible, I have used an ikea bulb.
  • You need to use the attribute in special cluster to enable dimmer

After that, the device is see as bulb (not a switch) so easier for integration, it works without problem in phoscon too.
The return state works too, use the bind fonction for that.

manup added a commit that referenced this issue Nov 21, 2018
More information here #883
@Smanar Smanar closed this Nov 21, 2018
@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Jun 2, 2019

Ok so just for information the values I m using for attribute report, after somes tests.

For on/off : I have set 1 - 300
For level control : I have set 1 - 600 - 0

@WhistleMaster

This comment has been minimized.

Copy link

@WhistleMaster WhistleMaster commented Aug 31, 2019

So are all the Legrand connected switch series are now supported with this change ?

Why is it seen as a light instead of a switch ?

EDIT: is this product supported: https://www.legrand.fr/catalogue/interrupteur/interrupteur-micromodule-declairage-onoff-pour-rendre-votre-eclairage-connecte-installation-with-netatmo

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 24, 2019

Lol. I m still on the code ATM, I have found the part that create the group, but I have so much question ATM.

  • Why the group don't appear in phoscon ?
  • Why it have an uniqueid

BTW to access group in api, you can use an url like this one http://192.168.1.1/api/36E138295E/groups/ here you can delete them with cul request for exemple (something like curl -X DELETE http://192.168.1.1/api/36E138295E/groups/ID
You are forced to use this way because nothing is visible on phoscon ATM, no group, no device. It s perhpas possible trought jeedom if it can manage group.

And I have found to origin of the 2 th request when you press a button, the device make a device announce every time you press the button, so you have 2 websockets return.

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 24, 2019

Lol. I m still on the code ATM, I have found the part that create the group, but I have so much question ATM.

* Why the group don't appear in phoscon ?

* Why it have an uniqueid

BTW to access group in api, you can use an url like this one http://192.168.1.1/api/36E138295E/groups/ here you can delete them with cul request for exemple (something like curl -X DELETE http://192.168.1.1/api/36E138295E/groups/ID

Shit ^^ lot of questions so ! But in fact, it's working I mean, I have associate my switch to my wall plug.

Thanks for API call :) that would be usefull. Also, a good stuff would to be able to change the name of the group.

You are forced to use this way because nothing is visible on phoscon ATM, no group, no device. It s perhpas possible trought jeedom if it can manage group.

Yeah, nothing on Phoscon, IDK why but I'm preaty sure that a combinaison of something would enable it because I've see it before. You mean that I'm able to manage them in Jeedom ? Where 0.0

And I have found to origin of the 2 th request when you press a button, the device make a device announce every time you press the button, so you have 2 websockets return.

Dont get it ... sorry 😕

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 24, 2019

I have just push a test version , that make group without the uniqueid, but not sure the group will be created ... Perhaps it's the field that block phosocn, other field are normal.

I don't know jeedom, but you haven't something to act on group made on deconz ? It s possible too using the API > https://dresden-elektronik.github.io/deconz-rest-doc/groups/ with curl command.

For the last point, if you look at jeedom log, you will see 2 websockets return when you press the button.

2019-11-23 22:55:29.028 (DeCONZ) ### WebSocket Data : {'config': {'group': '4', 'on': True, 'reachable': True}, 'e': 'changed', 'id': '6', 'r': 'sensors', 't': 'event', 'uniqueid': '00:04:74:00:00:a9:0c:6f-01-0006'}
2019-11-23 22:55:29.079 (DeCONZ) ### WebSocket Data : {'e': 'changed', 'id': '6', 'r': 'sensors', 'state': {'buttonevent': 1002, 'lastupdated': '2019-11-23T21:55:29'}, 't': 'event', 'uniqueid': '00:04:74:00:00:a9:0c:6f-01-0006'}

The first one is totally useless, but pipiche38 see it too, so surely something normal.

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 24, 2019

Sorry but I didn't get it. You are expecting me to test your new version again so ?

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 25, 2019

The one you are speaking haven't worked ^^, group is still hidden. I have make an other issue to ask if it's something normal.
So for the moment the group is working like before, hidden + with an uniqueid useless.

But after that I have cleaned the code (to pull modifications on official branch) and implemented the battery info, "gaz" is making test ATM, I m waiting to see if it is working.

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 25, 2019

</switch fr>
Hmhm je suis un peu perdu là, désolé 🤣
Les "clusters natifs zigbee" qui sont matérialisé en "groupe" dans Phoscon ne seront pas ajouté ?

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 25, 2019

Heu, j'ai pas compris la question non plus ^^.
Mais si tu parles de l"association directe, juste en rajoutant un appareil dans le groupe de l'inter, la, pas de changement, ca marchera comme avant.
Mais faut le faire a la main ou passer par la vielle app (groupe invisible), donc plutot chiant ...

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 25, 2019

BTW, we have some problem with the battery reading.
Impossible to read attributes on cluster 0x0001 "power configuration", nothing happen when pressing the "read" button, or we are using bad way to wake up the device (this one fall asleep so don't answer to request)

It's same for you ?

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 25, 2019

Heu, j'ai pas compris la question non plus ^^.
Mais si tu parles de l"association directe, juste en rajoutant un appareil dans le groupe de l'inter, la, pas de changement, ca marchera comme avant.
Mais faut le faire a la main ou passer par la vielle app (groupe invisible), donc plutot chiant ...

D'accord. Oui je parle de l'association direct. Le fait que l'interrupteur sans fil interagisse directement avec le plug / interrupteur filaire. Pour éviter le "spof" lié a la gateway et aux scénarii type jeedom & cie.
Passer par l'ancienne app / l'API ne me dérange pas dans un premier temps.
Après, est-ce que ce sera accepté comme tel pour une release ? (pas de visu du groupe / device dans Phoscon)

A terme, ces groupes pourront-être renommé ? Le device serait visible dans l'onglet "switchs" ?
ou ce n'est pas possible ?

BTW, we have some problem with the battery reading.
Impossible to read attributes on cluster 0x0001 "power configuration", nothing happen when pressing the "read" button, or we are using bad way to wake up the device (this one fall asleep so don't answer to request)

It's same for you ?

That's strange. Because I have the same issue BUT if you look my previews screenshot #883 (comment) Deconz App get the battery information. For that, I'm have enable all that stuff :

image

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 25, 2019

I haven't this icon too ^^.
But I think it just mean your device is with battery, not the battery level.
To see battery level, you have it at cluster 0x0001, attribute 0x0020 and 0x0021, perhaps other but we can't succed to read them, we press the "read" button but impossible to wake the sensor to make the "read" button working.

But "gaz" have an idea, perhaps the battery level need the update to work, its device is "out of the box", yours is updated.

BTW can you give us the device version you have on deconz or can you try the last version on my fork ?

Oui, oui, pas de soucis pour le pull, le probleme ne vient pas de moi, mais de eux ^^, c'est phoscon qui bloque, pas l'API. Il y en a plein qui sont dans ce cas.

Avec l'API tu peux tout faire, avec Jeedom aussi (faut juste que les devs le mettent en place), Phoscon n'est qu'une appli qui utilise l'api aussi. Pour que l'inter soit visible dans Phoscon c'est a eux de decider par contre.

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 25, 2019

I haven't this icon too ^^.
But I think it just mean your device is with battery, not the battery level.
To see battery level, you have it at cluster 0x0001, attribute 0x0020 and 0x0021, perhaps other but we can't succed to read them, we press the "read" button but impossible to wake the sensor to make the "read" button working.

But "gaz" have an idea, perhaps the battery level need the update to work, its device is "out of the box", yours is updated.

Well that an idea. Where are you discussion with "Gaz" ? Other forum ? To merge our discuss.

BTW can you give us the device version you have on deconz or can you try the last version on my fork ?

Here my deconz version.
image

Here my device software version regarding deconz : 001e

And I'm pulling your last fork 😄

Oui, oui, pas de soucis pour le pull, le probleme ne vient pas de moi, mais de eux ^^, c'est phoscon qui bloque, pas l'API. Il y en a plein qui sont dans ce cas.

Avec l'API tu peux tout faire, avec Jeedom aussi (faut juste que les devs le mettent en place), Phoscon n'est qu'une appli qui utilise l'api aussi. Pour que l'inter soit visible dans Phoscon c'est a eux de decider par contre.

D'accord, je comprends mieux :-)

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 26, 2019

"Gaz" is from domoticz forum, he have some problem with english so he don't have github account, but he can read here. And we are speaking with email ATM.

He have the version > "swversion":"019" = 25
And you "swversion":"01e" = 30

5 version above.

Edit:
So I have some other news, it seem when this device is slepping, it can sleep long, long time. and attribute reporting don't work with it.
The only moment when we can ask for battery level is when you trigger it.
When you press the button, it make a (re)join and it's the only moment where you can ask for information.
It's not working yet on version 25, but if you can make a try on version 30.
Easy, on deconz, go to cluster 0001 attribute 0x0020, select it to have the popup.
Use the switch and press the "read" button (on the popup), I can't give more info for timing.

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 27, 2019

Sleeping reading :
image

Awake reading :
image

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 27, 2019

Whaou, I have 2 questions.
How have you done that ? You are using a special procedure ? a special timing ? (Still not working on version 25)
Can you confirm me the battery level is still "null" on the version you are using ? visible on websocket or on API, or on jeedom log.

BTW if 28 mean 2.8V, your battery is dead, because all tests I think.

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 27, 2019

Whaou, I have 2 questions.
How have you done that ? You are using a special procedure ? a special timing ? (Still not working on version 25)
Can you confirm me the battery level is still "null" on the version you are using ? visible on websocket or on API, or on jeedom log.

BTW if 28 mean 2.8V, your battery is dead, because all tests I think.

Level still nul. I was pressing any switch button while flooding read button by click.

I've try a new battery. Same level
Edit : i've tried an other one totally new also : 29

@pipiche38

This comment has been minimized.

Copy link

@pipiche38 pipiche38 commented Nov 27, 2019

The values are not necessary wrong. I'm getting the same. What I found is if I make the switch very active during 1 minute and then trigger the query , the battery level looks much better.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 27, 2019

"gaz" have 32 on his device ^^.
So I have finally make the battery working with him. I m using same method than @pipiche38, when the device rejoin the network, I ask battery.

I have push the last version, but this one can be worse, it's realy for test.

  • The battery is asked only 1 time every 24h, but untested code.
  • I have disabled all attributes reportings (and this modification can be realy bad)

As it will be the last version, you need to delete the device + the group, to make a full inclusion to realy test all features.

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 27, 2019

Okay, I can test 😄

I have disabled all attributes reportings (and this modification can be realy bad)

why ?

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 27, 2019

Because this device don't support them, it's sutpid to spam it with useless command (and every time, it rejoin the network = every time you press it)
But the code can influence the binding part (we need it for the group code, and I don't understand all the code ^^)
If all is ok, I will make the official pull in somes days.

EDIT:
I have just reactivate report attribute, else all is broken no more buttonevent. Battery is null, need to check in 24h.

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 27, 2019

Shit, I was compilling ... ^^'

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Nov 27, 2019

Because this device don't support them, it's sutpid to spam it with useless command (and every time, it rejoin the network = every time you press it)
But the code can influence the binding part (we need it for the group code, and I don't understand all the code ^^)
If all is ok, I will make the official pull in somes days.

EDIT:
I have just reactivate report attribute, else all is broken no more buttonevent. Battery is null, need to check in 24h.

Okay so Battery still null. I'm waiting now. See ya 24H later ;-)

PS : I'm have also dual wireless switchs. We can start integration also ?

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 27, 2019

For battery I have add https://github.com/Smanar/deconz-rest-plugin/blob/master/de_web_plugin.cpp#L5169

So if I m right, you need at least 24h to have the first report.
The device take so much request every time it come back on the network, so I m searching a way to minimize them.

Sure, will be faster, now we know how to do. Like the last time, I need.

  • the basic cluster attribute panel.
  • the clusters lists.
@Xylomid

This comment has been minimized.

Copy link

@Xylomid Xylomid commented Nov 29, 2019

I followed the thread carefully but i'm not sure what's the status of the integration...
@Smanar your last merge to deconz master was on 21/10 ?

Plug (for exemple 0 677 25) Full working, on/off / power consumption.
Switch with dimmer without neutral (for exemple 0 677 71) Full working, on/off/dimmer.
Micro Module (0 648 88) Full working, on/off.
Shutter switch (For exemple 0 677 26) Working up/down/stop but problem with API (don't use bri)
Cable outlet (0 648 79) : WIP

It means that i can include a Switch with dimmer without neutral in deconz and then see it in home assistant (hassio) ? I will only have on/off (no dimmer) if i don't use the legrand gateway ?
What about the cable outlet ? Can i see the different modes in home assistant ?

I'm not sure to understand how is the wireless switch integration going haha ? good ?
Will you merge your code to the deconz master ?

Again, thanks for your work !

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Nov 29, 2019

Yep, the wireless switch is working, fully (and without update with legrand gateway, at least for on/off, haven't asked for dimmer), but we are trying to reduce the request it make, for exemple with only 1 battery report in a day, and theses ameliorations aren't finished.

For the wired switch without neutral, yep, "gaz" is using it with legand gateway, and it's working (but like you said without dimmer feature). He is using domoticz, but I don't see why you can have problem with hass.

For the cable outlet, the code is still on my fork, not on the official. But we haven't tested this device without legrand gateway (we have all the legrand gateway), I think the on/off will work, but not the "fil pilote" mode.

I will pull the modifications this Week end, If there isn't problem. Or perhpas I will try to include too the double wireless switch with @smesguich

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Dec 1, 2019

For battery I have add https://github.com/Smanar/deconz-rest-plugin/blob/master/de_web_plugin.cpp#L5169

So if I m right, you need at least 24h to have the first report.
The device take so much request every time it come back on the network, so I m searching a way to minimize them.

Sure, will be faster, now we know how to do. Like the last time, I need.

* the basic cluster attribute panel.

* the clusters lists.

Okay nice !
I'm still "in the boxes". i've freshly moove :-) so I didn't take the time for dual wireless switch but probably next week. I will also gave you stuff for scene button (Comming/leaving home and night/day).

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Dec 1, 2019

I have cancelled this battery working mode ^^. Not working. So I have make a pull without theses modifications.

NP for dual switches, but for the others Comming/leaving home and night/day, I think it's not possible to include them on deconz, special working mode.

@smesguich

This comment has been minimized.

Copy link

@smesguich smesguich commented Dec 2, 2019

I have cancelled this battery working mode ^^. Not working. So I have make a pull without theses modifications.

Okay, NP.

NP for dual switches, but for the others Comming/leaving home and night/day, I think it's not possible to include them on deconz, special working mode.

Oh, really ? But there look like integreated : https://github.com/pipiche38/Domoticz-Zigate-Wiki/blob/master/en-eng/Legrand-corner.md#scenes

@pipiche38

This comment has been minimized.

Copy link

@pipiche38 pipiche38 commented Dec 2, 2019

@Smanar and @smesguich , let me comment

NP for dual switches, but for the others Comming/leaving home and night/day, I think it's not possible to include them on deconz, special working mode.

Oh, really ? But there look like integreated : https://github.com/pipiche38/Domoticz-Zigate-Wiki/blob/master/en-eng/Legrand-corner.md#scenes

Here is my understanding of the Coming/Leaving home scenes. They are part of Legrand firmware. So what needs to be done is to create the groups as documented in the Legrand-corner. And then associated to the group you can play with the scene.

@Smanar

This comment has been minimized.

Copy link
Contributor Author

@Smanar Smanar commented Dec 2, 2019

If you already have it, we can make a try, IDK how deconz manage scene cluster. It will be a surprise ^^.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.