Good stuff! Well done Jamie

Messages like that make my day! So thank YOU!

Hi Lars, Sorry for the delay! have you managed to figure this out? Is Zigbee2MQTT setup correctly and passing anything into MQTT? You should be able to test this with Node Red using a MQTT-IN node. You should be able to see a message when you do the permit/disable join. Failing that... I would say possibly a re-boot might sort it?

I wonder that too! I have just installed ZigBee2MQTT on a Sonoff dongle E and added the IKEA plugtop and DimSwitch and I can read status with a current state node directly from what is installed via MQTT integration/add-on

I figured out that the firmware version of the coordinator was to old

Sure, you can map them into anything you like. Use node red and you can use them for anything. Pretty sure it’s in this video: kzfaq.info/get/bejne/kMVhermIzdPSlWg.html

Do you have the one with the external antenna? that’s the one I have and it works pretty well. You could always just get a few plug tops as they normally act as signal repeaters - one of the great things about zigbee over WiFi.

@@HomeSight I own the one with the internal antenna unfortunately. The range is around 6 meters only

Ah, you might want to get the external antenna version

@@HomeSight Thank you! . I don't really need plugs atm, but probably it's a way better solution as a repeater

Yeah, I don’t really need them either, but I do have one in a strategic spot which gets the signal to a zigbee bulb in a feature lamp.

Hi again! Ok so I was able to connect (i was only mossing the login and password of the server. However i still cant see anything when i click on the ikea remote. I was able to see the there is a link by using the #.

If you click on “developer tools” (hammer icon), can you see the device in there? If you can, when you click the button does it appear with an action (it might flash up fast and disappear).

@@HomeSight thanks for the help. No it doesn't I look also at the commentary and I think I need to update the cc2531 firmware. I lookup with mqtt explorer and I think its the 2018mmdd. I'll try that and let you know! Thanks!

Ok so yeah it was the firmware update that was causing the problem!

I’m glad you have it sorted!

Hi, no I don’t find that. What is your setup? Zigbee2mqtt? ZHA?

@@HomeSight I'm using Tasmota on the Sonoff Zigbee Bridge so not using Zigbee2MQTT but it does work with MQTT so connecting it to the Mosquito broker. I like it because the bridge doesn't need to be plugged in to the Raspberry PI. On another note, I popped in to IKEA yesterday which was surprisingly quiet for NYD. I coudn't see the SYMFONISK dimmer. Maybe its not available anymore. Shame because it looks really good

Can you see the input into the console of your bridge - I guess the tasmota console will display the received signal? Is that working consistently? The symfonisk is great, probably my favourite remote. Last time I was there, they didn’t have it out on the shelf, you have to get it from the warehouse bit. Remember Ikea consider it to be a “sound remote”, so it’s with their speakers rather than lights.

@@HomeSight I don't see it in Tasmota console on a few occasions. Just seems very intermittent. I bought a couple more dimmers yesterday just to eliminate the issue with the device. Also going to play around with the position of the bridge and put it in a different room

I had an issue with a zigbee bulb, which meant I needed better placement of receiver (or next repeater)

For me the address of the server was mqtt://core-mosquitto. The username and password could be obtained by going to Configuration main tab in home assistant, then Integrations, then clicking on the Configure option of the Mosquitto Broker and finding the into there

Only took me 6 hours

Glad you got it working (even after 6 hours)

Have you changed the broker in the MQTT in/out node

@@HomeSight No I found the problem, my cc2531 stick broke. I ordered a Conbee 2 stick instead in the hope it'll be easier to use.

Good luck!

Sorry if I’ve not been clear. When you setup a MQTT In node you’ll need to make sure you have a MQTT broker and all of that setup … have you got that already

Hi thanks for watching, it’s a good question. If you’re planning on using them in node Red alone, it’s fine just to use the MQTT alone. I use them on a Lovelace interface too, so need them to appear as entities.

Is there something more to achieve adding devices like this compared to normal entity, like zigbee devices are showing up?

Ah, I see your question, I don’t slow zigbee devices to be added automatically, I find I want greater control! Maybe that’s just me, but I have found that the automatically added devices don’t always do exactly what I want, and sometimes I want to add additional templates, for example brightness as s separate entity.

@@HomeSight Ok. Thanks for taking time to answer.

@@HomeSight I installed ZigBee2MQTT on a Sonoff Dongel E (thanks for that detailed guide!) and paired an IKEA plugtop and a DimSwitch as first devices. I can for example monitor battery level on the DimSwitch in a lovelace card without defining the sensor in configuration.yaml. For what thins do you need those manually defined sensors?

Thanks, although I don’t quite understand your comment. People without what? The remotes?

@@HomeSight hm sorry, for some reason KZfaq cut my comment. I meant to write: "Good video, but what about people without CC2531. what about just with the Tradfri gateway and official Tradfri remote?

​@@HomeSight I only find KZfaq videos on how to do it if you don't have the ikea gateway. but unsure how to integrate the Tradfri remote + gateway , without having to use MQ/mosquito etc. All it shows are the battery level entity for the remote.

Hi Eric, it is possible to use the Ikea integration with the tradfri hub, but personally would rather use native Zigbee into zigbee2mqtt. Are you wanting to use the Ikea Tradfri hub?

Hmm, that’s odd. Have you changed the name of the device in zigbee2mqtt, and ensured it’s the same in your config? I normally ensure the names of the device names in zigbee2mqtt don’t have any spaces to make life easy...

@@HomeSight yes, i just copied it directly from the zigbee2mqtt page, but when I copied the code from your webpage, i could see you have a capital letter in the first name on all 4 places, but of course the second was exactly as the name of the device. So i did the same thing. I don't think this could be the problem? But one thing I suspect, it would be nice to hear your opinion. When I check the log for mosquitto broker, the ip address used is another weird ip address (172.x.x.x) which my home assistant is not connected on (192.168.x.x). Nevertheless, mosquitto connects successfully, and if I check the mqtt with mqtt explorer it looks like everything works. I even receive some kind of messages whenever i push the button. Could this be the problem? In node red, when i use a state event i can see something's happens when i push the button, but it doesn't send me a debug code.. :S I am really not sure what this is..

Hi, the 172.16.x.x address is probably the internal network for your HA, it uses IPs in that range for the docker images. I don’t quite understand your last point. What messages are sent in? If you add a “MQTT in” node and wire that straight to a debug node, what happens when you press the button then?

@@HomeSight and is that okay, that the ip range is different because of docker? This doesn't result in missing communication between zigbee and HA? If I put a mqtt in node in, i don't receive anything in my debug node. The only thing I have received in my debug node is if I put an inject node and push it manually. If I go to developer tools in HA should i be able to see the different actions pop up for my switch there also? As of now I don't see any messages there.

Seems like zigbee2mqtt is not getting or certainly passing the info in to MQTT. It’s fine for then to have the 172.16.0.0 address as it is how the talk in the background. It’s a bit of a “clutching at straws” method, but try rebooting?!