I have just connected a zigbee LIDL 3 outlet power strip to CC.
Here is the device info.
When I try to select the device in NR I can see the strip but none of the 3 endpoints for the O/L’s.
Is there something that needs to be done or am I missing something totally obvious. (Most probably).
Thanks.
You might need to address this a bit differently. zigbee 2mqtt says it’s fully supported, so it might be an issue with the node. There were some differences in the z2m nodes that were a bit … off. can you post screenshots of the node, one of the list inside the node (the available options). I don’t have one of these, but I’ve been using things long enough that a visual will do.
also try changing the input node to complete state and put a debug with complete message and see what you get out of it.
When I pick the
node I get these options.
I suppose the 3 state options could be the 3 endpoints.
what is the node name? Are you in NR3?
Not using NR3
Herdsman is your z2m protocol. click the list and show me what’s in the herdsman list as well.
target is one of the states
Show the command list after choosing one of the state in the list.
As above
Actually, I’m kind’ve looking for the the version of the z2m node. You can find that info easiest in manage pallete . It’ll give you the contrib name and the version you’re using. It would help me.
And if i could have a peek at the command list when target field shows state
Sorry to be asking all of these questions, I’m not at home, so anything visual you can offer me woudl be helpful.
Getting this error.
24/08/2022, 16:42:57node: zigbee herdsmanmsg : error
“Error: PanID must have a value of 0x0001 (1) - 0xFFFE (65534), got 65535.”
This?
Not sure where this is on the nodes I’m using.
OH no … no . I don’t think you want to use that one. stand by. I’ll remote into my home.
Don’t put yourself out on this. I’m happy to leave it and re-visit when you are free. Work comes first.
Thanks for responding so quickly.
I feel like this is a contrib that wants to connect directly to your controller. I’m not using the updated version of this i’m still on 0.6.3 due to the bugs with the nodes.
I’ll tag @RRodman, but did you upgrade the baked in node that was at 0.6.3? Or did you add this yourself? NBD if you did, but I’ve not moved since there too many issues with the new version of nodes.
The 5 nodes I have shown above are what came with CC. I don’t believe I updated any nodes, but hey, I’ve been clicking around so much with NR, as this is the first time I have seen NR, who knows? 
I did update the Z2M-node yesterday and the with assistance I was able to revert to 2.3.2, please have a look here: https://community.oh-lalabs.com/t/need-my-help-or-advice-my-new-automation-will-help-speed-that-up/1748/4?u=carl
Dump that command node. That’s really confusing. I’m still baffled as to where you found that. You already have z2m set up.
You need to use a trigger that goes into an out node that runs the command
As you see in my flow above:
zigbee motion happens with an in node
it’s filtered from active and inactive which then turns the lights on, but when inactive turns the lights off after 20 seconds. If movement happens, then the timer is stopped until inactive again.
The light off is into an out node for the other zigbee device. All of the commands happen within that node. No extra nodes need to be added to control the device.
You can import this flow and take a look
[{"id":"f6a48bf2cf19d842","type":"switch","z":"437f14e945a3983d","name":"","property":"payload","propertyType":"msg","rules":[{"t":"false"},{"t":"true"}],"checkall":"true","repair":false,"outputs":2,"x":430,"y":1480,"wires":[["28cf2ffe3fa3223c"],["47c86147ba15ec70"]]},{"id":"28cf2ffe3fa3223c","type":"stoptimer","z":"437f14e945a3983d","duration":"20","units":"Second","payloadtype":"num","payloadval":"0","name":"","x":750,"y":1460,"wires":[["681b77f5f2052ccd","602f790fcdcb9f03"],[]]},{"id":"8ad14bdb693b8f6a","type":"change","z":"437f14e945a3983d","name":"stoptimer","rules":[{"t":"set","p":"payload","pt":"msg","to":"stop","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":760,"y":1500,"wires":[["28cf2ffe3fa3223c","1648bbbbb1f64b8a","79c36da4c6cf5e84"]]},{"id":"1648bbbbb1f64b8a","type":"zigbee2mqtt-out","z":"437f14e945a3983d","name":"","server":"c292ab1e.8d2318","friendly_name":"SPAREBedroomLampL","device_id":"0xb0ce18140362d0a6","command":"state","commandType":"z2m_cmd","payload":"on","payloadType":"z2m_payload","x":990,"y":1500,"wires":[]},{"id":"681b77f5f2052ccd","type":"zigbee2mqtt-out","z":"437f14e945a3983d","name":"","server":"c292ab1e.8d2318","friendly_name":"SPAREBedroomLampL","device_id":"0xb0ce18140362d0a6","command":"state","commandType":"z2m_cmd","payload":"off","payloadType":"z2m_payload","x":990,"y":1460,"wires":[]},{"id":"47c86147ba15ec70","type":"switch","z":"437f14e945a3983d","name":"","property":"spare_button_single","propertyType":"global","rules":[{"t":"eq","v":"0","vt":"str"}],"checkall":"true","repair":false,"outputs":1,"x":550,"y":1500,"wires":[["8ad14bdb693b8f6a"]]},{"id":"41f5672677dc1054","type":"zigbee2mqtt-in","z":"437f14e945a3983d","name":"","server":"c292ab1e.8d2318","friendly_name":"SpareBedroomMotion","device_id":"0x000d6f00057c1d88","state":"occupancy","outputAtStartup":true,"x":260,"y":1480,"wires":[["f6a48bf2cf19d842"]]},{"id":"602f790fcdcb9f03","type":"zigbee2mqtt-out","z":"437f14e945a3983d","name":"","server":"c292ab1e.8d2318","friendly_name":"SPARELampRight","device_id":"0xb0ce18140362cbc4","command":"state","commandType":"z2m_cmd","payload":"off","payloadType":"z2m_payload","x":1250,"y":1460,"wires":[]},{"id":"79c36da4c6cf5e84","type":"zigbee2mqtt-out","z":"437f14e945a3983d","name":"","server":"c292ab1e.8d2318","friendly_name":"SPARELampRight","device_id":"0xb0ce18140362cbc4","command":"state","commandType":"z2m_cmd","payload":"on","payloadType":"z2m_payload","x":1250,"y":1500,"wires":[]},{"id":"c292ab1e.8d2318","type":"zigbee2mqtt-server","name":"COREZ2M","host":"10.10.2.1","mqtt_port":"1883","mqtt_username":"johnnysilverhand","mqtt_password":"9^P+Y)[7yy}]","mqtt_qos":"0","tls":"","usetls":false,"base_topic":"zigbee2mqtt"}]
Thanks for the response and info @april.brandt. I will give it a go later.
What I didn’t make clear before, sorry about that, but I was still expecting to 3 ‘child’ devices (the 3 o/l’s) under the main parent device when the strip was joined.
Should they show up as ‘child’ devices? Personally I think they should. They do in HE.
If so, I think the problem is solved as each child device can then be treated as its own individual entity.
Don’t forget that the drivers had to be reinvented there.
I think they all show up. Check the device in zigbee and see in there what assets you have to control.
I was a bit worried about that node you showed in the Screenshot. Wherever that is. Don’t mess with it.
Looks like he updated the z2m node from the CORE shipped version. I did the same and haven’t broken anything yet, I was confused when I moved things from my old NR server to core and was missing the ability to set the device via msg.topic
Looks like I’m going to have to give up with this. Tried re-pairing again. Found it but kept saying offline.
I decided to delete device and start again.
Now when it pairs it says it is an unsupported device.
Yesterday it correctly identified it as a LIDL 3 outlet strip.
Tried 3 times and results are the same.
I will try dragging the strip closer to CC as it is around 15 metres away. Did the trick. Now to play again.