I am a newbee and need help.
As ask in the headline already, i need to know if anybody tried already this part?
If yes it is maybe possible to get a brief description how to install and use it.
Thanks to everbody in advance
It should be 'Plug and Play'.
I feel that more information is needed. If you are using MQTT then maybe it is the Zigbee2MQTT that needs looking at. If using with Home Assistant, not many people have experience of that here.
Have you seen this? That should get you up and running for the device. You then need to decide what you are trying to do.
Of course, if you are thinking of buying one, please say.
Thx for your answer. I bought already one and 2 plugs for Test.
I didnt find the page, Hope this will Help.
I use mqtt with nodered and used tasmota devices only. Installed already the addon mqtt2zigbee but it feels like Something is still Missing to connect the device.
Have to Test next week because i am out now.
It was a lot easier to implement than I expected, a bit like using MQTT the first time!
Not having the device I can't help, but suffice to say, the SLZB-60 picks up the Zigbee comms and outputs via Z2M or ZHA. I would be using Z2M, and then I use MQTT Explorer to see what is going on.
An example which may help you.
Still struggling with the SLZB-06,
installed ser2net but i fail to get the path to the adapter.
It is connected via Wlan, tried also with LAN, but how to find the adress?
%YAML 1.1
---
# This is a ser2net configuration file, tailored to be rather
# simple.
#
# Find detailed documentation in ser2net.yaml(5)
# A fully featured configuration file is in
# /usr/share/doc/ser2net/examples/ser2net.yaml.gz
#
# If you find your configuration more useful than this very simple
# one, please submit it as a bugreport
define: &banner \r\nser2net port \p device \d [\B] (Debian GNU/Linux)\r\n\r\n
connection: &con01
accepter: tcp,20108
enable: on
connector: serialdev,/dev/ttyACM0,115200n81,local
options:
banner: *banner
kickolduser: true
telnet-brk-on-sync: true
connector: serialdev,
/dev/ttyS0,
9600n81,local
connection: &con1096
accepter: tcp,2001
enable: on
options:
banner: *banner
kickolduser: true
telnet-brk-on-sync: true
connector: serialdev,
/dev/ttyS1,
9600n81,local
connection: &con0192
accepter: tcp,3000
enable: on
options:
banner: *banner
kickolduser: true
telnet-brk-on-sync: true
connector: serialdev,
/dev/ttyS0,
19200n81,local
connection: &con1192
accepter: tcp,3001
enable: on
Maybe anybody is able to show me the way
I even dont know wich part of the config to use
How about showing us what you have so far...
Ok
first of all i installed zigbee2mqtt and try to get contact with USB. But i cannot find the device in the Raspi.
After a while i get an POE Adapter and connect the device to my network, but i still cannot find the device. I found have to install another programm ser2net to connect failed again on this point:
Add the following entry, replace /dev/ttyACM0 with the correct path to your adapter.
I am complete off for now and uninstall everything and start over again.
[type or paste code here](https://www.zigbee2mqtt.io/guide/getting-started/)
Here is a complete installation guide but i fail to find the device.
I use a Raspi4 with a SSD connected to usb as server for Nodered only.
Is this on the same device as MQTT server?
For what? You said USB in the previous paragraph.
You shouldn't need to install ser2net for zigbee2mqtt as far as I am aware as it sends it payloads from this server to MQTT and the payloads should then be accessible using MQTT Explorer or something similar.
Once you have this working you can progress to Node-RED.
Your Pi4 is capable of handling MQTT and Node-RED together to make things easier. Personally, I use a RPI Zero 2 W for the Zigbee2MQTT and a Pi4 for MQTT and Node-RED.
I feel you might be making some things complicated for yourself. Take everything a step at a time and make sure you know 'where things are' on your devices before adding each server software.
HTH
1 Like
Thx for your pacience
Zigbee2mqtt, mqtt and nodered are on the same device P4. Also ser2net.
I want to Run all in one and Connect the Simlight via Network to the Pi. This will make it easy to place it anywhere in my House. This is the reason to Install ser2net.
Have you installed Zigbee2MQTT and looked at it's webpage?
It does have it's own http server, go to the web address :8080
Can you see your device in the Zigbee2MQTT server page?
Have you connected to the MQTT server correctly?
Use MQTT Explorer once Mosquitto is loaded and check what Zigbee2MQTT is sending as a message.
Once this is done...
Connect with Node-RED to collect the payload.
You really aren't helping us to help you. You need to take things a step at a time. We cannot see what you are doing or how you are doing it, and wherever the server is in the house, providing it is connected to your network (easiest option), it is possible to access Zigbee to MQTT via it's webpages.
I suggest you look at the the Official pages for each step, check that each step works before continuing to the next step. Once you have done all that, we can probably help you.
Have you seen this link?
Forget the Home Assistant side of things, Node-RED takes over at this point.
There are plenty of Videos/help pages out there, possibly even Forums. As I say, not sure anyone in this Forum is using this device, so we are not really able to help you until you get to using Node-RED to talk to Mosquitto.
Ok will go back completly and start over again,
i will reply and tell what happens
Thx
Startet completly new and get a hand, now it is working.
Now i have to find out how to connect Tasmota driven switches in combination with zigbee bulb or other epuipment
Cord
1 Like
If your Tasmota devices are Zigbee than all you do is send data from the devices using Zigbee2MQTT and then use the same MQTT server to access the data.
TLDR: Register the devices to Zigbee2MQTT and 'Voila!'
2 Likes
Ok i did this and i am able to switch on and off a bulb using a "toggle".
Now i want to use one of my switches to do the same, but it will not work.
The LOG in Z2M will be flooded with
z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartGlühlampe', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"linkquality":112,"state":"ON","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"}}'
info 2024-11-22 13:26:41z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartGlühlampe', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"linkquality":109,"state":"OFF","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"}}'
info 2024-11-22 13:26:41z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartGlühlampe', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"linkquality":109,"state":"ON","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"}}'
info 2024-11-22 13:26:41z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartGlühlampe', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"linkquality":109,"state":"OFF","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"}}'
info 2024-11-22 13:26:41z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartGlühlampe', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"linkquality":109,"state":"ON","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"}}'
info 2024-11-22 13:26:41z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartGlühlampe', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"linkquality":109,"state":"OFF","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"}}'
info 2024-11-22 13:26:41z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartGlühlampe', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"linkquality":112,"state":"ON","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"}}'
info 2024-11-22 13:26:41z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartGlühlampe', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"linkquality":112,"state":"OFF","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"}}'
info 2024-11-22 13:26:41z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/SmartGlühlampe', payload '{"brightness":120,"color_mode":"color_temp","color_temp":454,"linkquality":109,"state":"ON","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"}}'
until i switch off the lamp and reset the server.
The debug from NodRed shows
22.11.2024, 13:29:40node: debug 3
msg.payload : boolean
true
22.11.2024, 13:29:40node: Solar
msg : string[12]
"MQTT Offline"
22.11.2024, 13:29:41node: Solar
msg : string[13]
"Bridge online"
22.11.2024, 13:29:43node: debug 3
msg.payload : boolean
false
22.11.2024, 13:29:43node: Solar
msg : string[12]
"MQTT Offline"
22.11.2024, 13:29:44node: Solar
msg : string[13]
"Bridge online"
In my suggestion the payload from the switch is wrong, but i am not able to change.
There was for one time only something written from a node to transcript the message, but i cannot find it.
The other way can be to change the output message from the switch, but i dont know howto.
What is the output of the switch (SLZ01)?
Connect a debug node to the output.
You may have to use a change node to get the same input to the lamp as you get from the Toggle node
1 Like
There are so many things to learn.
THX that works for now, some new parts are on the way for testing.
body movement, smoke sensor, water sensor.
Next step in a time to implement some Somphy parts.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
