These can be found at most electrical wholesalers but for reference the ones I suggest you use are these. Our primary recommendation is to fit circular European style backboxes as detailed on the product documentation pages. This is typically 5mm on a standard UK metal backbox. When having this problem a good solution is a spacer or washer equal to the depth of the threaded hole in backbox to the front face of the backbox. The mounting frame that is on the Touch is identical to that of the Touch Pure and if you're having problems with the frame fulling back into a backbox then you'll also get this with the Pure.
The Touch range (Touch and Touch Pure) are designed for mounting on either metal in-wall or ideally for better fitment circular backboxes not the UK type dry lining boxes with flanges. I’m quite happy to have a credit for the returned items. The touch tree pure switch plates are the correct size for uk back boxes, I propose using these for the project and I’m awaiting the release of the black pure switches to be announced. I wish to therefore return them as not fit for purpose. I have made contact today with respect to the black pure fronts and I have now been told I cannot return the original touch tree fronts for refund or credit as they have been with me for more than 14 days. I raised both these issues with Omid last year and discussed the touch tree pure fronts, and agreed I would wait for the black pure fronts. I have tried the fronts on 3 different manufacturers back boxes with the same results. The touch tree fronts are smaller than a standard uk dry lining back box and as such leave the back box exposed when fitted, which is visually unacceptable to my client.Īlso the back mounting plates are also very too small and keep pulling inside the back boxes. When running on rpi, consider using an usb ssd instead of sdcards.I have a number of touch tree switch fronts purchased for a project which I have found to be non usable for the project. It will not save your ass from sdcard failure (because it willįail and it is only matter of time), but will reduce disk writes a lot. Set DEBUG=0 in all config files and also set LOGGING_DRIVER=none in. When running on rpi or another embedded, you should consider to disable logging at all when setup is done.
You also should check zigbee2mqtt/bridge/logs for more info about zigbee bridge. lox_out (if using loxone mapping, there must be 1:1 picture in mqtt messages of what you see in loxone web interface).lox_in (if using loxone mapping, you will see messages going from ).In fully working enviroment, there must be some messages in topics: Traffic such as "Zigbee logs" section of zigbee2mqtt manager. For example MQTT Explorer, which shows all You should use any mqtt client to monitor mqtt traffic and see if everything is going ok. It also sends mqtt messages received from topic 'lox_in' to loxone as udp text messages. (using node-lox-mqtt-gateway) and sends them to mqtt topic "lox_out". Bridge then receive value changes from loxone web interface Stop and backup following directories and files:Įverything is based on mqtt so you need to configure and run bridge first. You should list devices, show network map etc. It doesn't know anything about loxone bridge, but knows much more about zigbee than zigbee2mqtt manager.
This is more generic app to manage/view zigbee network. To understand mqtt messages produced by zigbee bridge. Hint - when you are debugging something or you are lost, zigbee logs should give more detailed info what is going on. When done with mapping, click on 'Save' button. Now loxone will receive "1" instead of "open" for this type of device and this value. Click on that record, write "1" into "Map to:" field and click "Create mapping" button. You will see for example "LUMI : lumi.magnet | contact | open" or something like this. Now wait until required zigbee message appear in the list (click on refresh). To translate these values before sent to loxone, click on Edit button. But what to do when your zigbee device uses words instead of numbers (such as yes,no,true,on,off.)? Then you should click on device's rename button and rename the device to some human understandable form. When done, click on 'Refresh' button to see if device was sucessfully paired. Click on "Enable" to start pairing new devices. Main window is used to list, pair and rename zigbee devices on network. Zigbee2mqtt will send that brightness command to zigbee device named "led1". All virtual inputs with that category will be read by the bridge and send to zigbee devices using following naming rules:Īnalog virtual output named "led1_set_brightness" with category "zigbee_out" will be sent to mqtt topic "zigbee/led1/set" with payload. To create oposite way of communication (from loxone to zigbee), you only have to create new "zigbee_out" category
and you will receive temperature as analog value.