When I look at these remotes they look exactly as the standard small two button IKEA remote and it adds to Deconz fine with the normal new Phoscon app.
You add it in Phoscon with Add New Switch and then you choose Other. There is an IKEA entry but it only supports the 5 button and the rotary. But these special entries are just about giving instruction how to pair. They all lead to Deconz turning on pairing.
To put the standard two button switch in pairing mode you have to remove the back plate (one screw) and press the small button 4 times.
After pairing it shows up in Phoscon as a new switch and it even shows the correct picture of it (which makes me wonder why the Phoscon IKEA menu does not show it yet).
You can now rename it. Often HA will already have imported it with the standard name and the only way I have found to rename it in HA is to first rename in Phoscon and then restart HA. It does not rename the event name by running a reload from HA. As long as you know that is not a problem.
I cannot say if the curtain switch is the same with just another plastic top with different symbols (the standard says 0 and 1). But I would be very surprised if it is much different.
And if it really is and you cannot pair it - but you can pair the curtain itself and control it - maybe a cheap work around is to buy the cheap little standard two button switch and use that until Phoscon/Deconz gets updated.
Kenneth the remote looks like the other one but it has another firmware inside that doesn’t work with this version of Conbee firmware. It will probably inserted in the next update (this I read in Github Dresden Elektronik thread)
But you gave me a great idea and I used a Xiaomi button as a remote and it works fine one click open two close the blind, so I can have automations and physical button and use that until Phoscon/Deconz gets updated.
Thanks
Hi Together,
I’m running a Raspbee together with HA and the standard phoscon add-on. I’m using several Osram bulbs, LEDs & motion sensors, Tradfri bulbs, Philips LED stripes, Innr plugs, some china wall switches (feibit) and integrated switches as well as Xiaomi switches (battery driven).
I connected the switches/motion sensors to the lights via the Phoscon Web UI (no HA involved here).
This setup is running quite well, nevertheless I’m not 100% happy with the Osram motion sensors and the Xiaomi/Aqara switches (WXKG02LM & WXKG03LM). Both are not working all the time. Sometimes I have to push the switch up to 3 times until something happens or although I’m moving in front of the motion sensor, nothing happens - 5 minutes later it’s working as usual.
2 questions:
I’m wondering how I can debug such situations? For example if I push the switch and nothing happens, I would assume that a) The “button pushed” command is not received by the raspbee or b) The “turn the light on” command is not received by the light. How can I find out what’s the cause?
Is the binding dropbox a solution? Shall I create a binding between the On/Off clusters of the switch and the light? Can anyone explain me a bit what the binding exactly does? The official docs did not help me that much to be honest…
And another question: is there any best practice for what’s the best way to connect end devices (so no routers, such as switches and sensors) to the network? Just connect it to the nearest router? Connect it to the device it controls (in case of switches)? Connect it to the coordinator?
From my experience, Zigbee is just total crap when it comes to routing. Devices become unreachable even if there is another device literally right next to them which has routing capabilities and perfect connection. This is the reason I would never use Zigbee for anything mission critical. All wireless solutions have the problem of not being 100% reliable, but Zigbee is the worst of all. E.g. Z-Wave is much better in this regard.
Ok, I find my zigbee network extremely reliable. Just, a bit random with pairing. It’s not caused me any issue yet, with about 30 devices, but it makes me nervous that I could go over my limit for pairing to the conbee, rather than routers.
My story is the opposite
I started with Z-wave sensors on all doors and windows but all the time windows and doors could open and close but the message was never received by HA.
After I changed to Deconz and zigbee my windows and doors are always in sync with HA
I think it is more a matter of which sensors and devices you buy and that you are ready to replace any crap that makes the network unreliable. And you need to software upgrade devices. I eliminated some Osram smart sockets that did not route very well and that made a huge difference for me.
But I never got the Aeotec window/door sensors to work well with Z-wave and now I only have 4 Z-wave devices left.
I’m testing deCONZ, and it’s looking good!
I have my ConBee at /dev/ttyUSB1.
To avoid problems with the everchanging usb port numbers after reboot, I tried to set device="/dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00K8EX-if00-port0"
This causes an error when I restart deCONZ (version 237): FATAL: No device /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00K8EX-if00-port0 found!
The device name is from the list in hassio/system/hardware.
What’s wrong?
Could it be something with the docker-compose.yaml, that I just saw further up in this thread?
My guess is that it happens when you have two USB sticks. There is a 5 second timeout in the docker start up that waits for udev to create the serial links. My guess is that if you have two sticks and the other takes more than 5 seconds to come up - you have the problem.
Unfortunately each we open a bug report on this they get closed unresolved. Please open yet another bug on github. It does not help writing on the existing closed reports.
Note this problem is in the HA Addon Docker. It is not the deconz that fails.
Hi everyone. I have been using ConBeeII succesfully for a couple of months now but recently I had to install a snapshot on a USB/SATA SSD because of SD failure but ever since Deconz has been sketchy at best and has now stopped working altogether.
I’m honestly at a loss. It used to work great but now the gateway says “Firmware” “Not connected”. I’ve tried to use ACM0 through 3 but only when I use ACM0 does the Add-on start without saying it’s not detecting any device. I’ve also tried using dev/by-id and no joy.
I thought I fixed the problem earlier this week but then I updated HASS from 0.98.5 to 0.99.3 and I was back to square one. I need help.
22:07:58:182 Websocket disconnected 192.168.1.30:54076 (state: 0)
22:08:00:092 Invalid admin password hash: $1$8282jdkm$w.o6XjJEGLzAYkVqLPAYx1
22:08:01:129 try to reconnect to network try=6
22:08:01:140 Device protocol version: 0x010B
22:08:01:200 Current channel 11
22:08:01:221 CTRL ANT_CTRL 0x03
22:08:01:252 Device protocol version: 0x010B
22:08:01:312 Current channel 11
22:08:01:329 CTRL ANT_CTRL 0x03
22:08:01:360 NET ZDO start network status 0xC4
22:08:06:129 try to reconnect to network try=7
22:08:06:137 Device protocol version: 0x010B
22:08:06:195 Current channel 11
22:08:06:213 CTRL ANT_CTRL 0x03
22:08:06:241 Device protocol version: 0x010B
22:08:06:299 Current channel 11
22:08:06:317 CTRL ANT_CTRL 0x03
22:08:06:344 NET ZDO start network status 0xC4
22:08:06:498 created username: 03CE24C40A, devicetype: Phoscon#B1177x667
22:08:11:129 try to reconnect to network try=8
22:08:11:140 Device protocol version: 0x010B
22:08:11:197 Current channel 11
22:08:11:215 CTRL ANT_CTRL 0x03
22:08:11:246 Device protocol version: 0x010B
22:08:11:301 Current channel 11
22:08:11:319 CTRL ANT_CTRL 0x03
22:08:11:346 NET ZDO start network status 0xC4
22:08:16:129 try to reconnect to network try=9
22:08:16:140 Device protocol version: 0x010B
22:08:16:198 Current channel 11
22:08:16:216 CTRL ANT_CTRL 0x03
22:08:16:244 Device protocol version: 0x010B
22:08:16:302 Current channel 11
22:08:16:320 CTRL ANT_CTRL 0x03
22:08:16:350 NET ZDO start network status 0xC4
22:08:19:668 New websocket 192.168.1.30:54106 (state: 3)
22:08:21:129 try to reconnect to network try=10
22:08:21:141 Device protocol version: 0x010B
22:08:21:199 Current channel 11
22:08:21:219 CTRL ANT_CTRL 0x03
22:08:21:249 Device protocol version: 0x010B
22:08:21:303 Current channel 11
22:08:21:321 CTRL ANT_CTRL 0x03
22:08:21:348 NET ZDO start network status 0xC4
22:08:26:129 reconnect network failed
22:08:43:752
22:08:43:785
22:08:43:787 backup: removed temporary file /data/.local/share/dresden-elektronik/deCONZ/deCONZ.conf
22:08:43:787 backup: removed temporary file /data/.local/share/dresden-elektronik/deCONZ/deCONZ.tar
22:08:43:808 don't close database yet, keep open for 900 seconds
22:08:59:229 start reconnect to network
22:08:59:329 try to reconnect to network try=1
22:08:59:342 Device protocol version: 0x010B
22:08:59:398 Current channel 11
22:08:59:417 CTRL ANT_CTRL 0x03
22:08:59:447 Device protocol version: 0x010B
22:08:59:509 Current channel 11
22:08:59:528 CTRL ANT_CTRL 0x03
22:08:59:559 NET ZDO start network status 0xC4
22:09:04:129 try to reconnect to network try=2
22:09:04:140 Device protocol version: 0x010B
22:09:04:202 Current channel 11
22:09:04:222 CTRL ANT_CTRL 0x03
22:09:04:253 Device protocol version: 0x010B
22:09:04:315 Current channel 11
22:09:04:335 CTRL ANT_CTRL 0x03
22:09:04:366 NET ZDO start network status 0xC4
22:09:09:129 try to reconnect to network try=3
22:09:09:136 Device protocol version: 0x010B
22:09:09:195 Current channel 11
22:09:09:213 CTRL ANT_CTRL 0x03
22:09:09:241 Device protocol version: 0x010B
22:09:09:299 Current channel 11
22:09:09:317 CTRL ANT_CTRL 0x03
22:09:09:347 NET ZDO start network status 0xC4
22:09:14:129 try to reconnect to network try=4
22:09:14:140 Device protocol version: 0x010B
22:09:14:196 Current channel 11
22:09:14:216 CTRL ANT_CTRL 0x03
22:09:14:247 Device protocol version: 0x010B
22:09:14:309 Current channel 11
22:09:14:328 CTRL ANT_CTRL 0x03
22:09:14:359 NET ZDO start network status 0xC4
22:09:17:426 Websocket disconnected 192.168.1.30:54106 (state: 0)
22:09:19:129 try to reconnect to network try=5
22:09:19:141 Device protocol version: 0x010B
22:09:19:196 Current channel 11
22:09:19:216 CTRL ANT_CTRL 0x03
22:09:19:246 Device protocol version: 0x010B
22:09:19:307 Current channel 11
22:09:19:326 CTRL ANT_CTRL 0x03
22:09:19:357 NET ZDO start network status 0xC4
22:09:23:536 New websocket 192.168.1.30:54127 (state: 3)
22:09:24:129 try to reconnect to network try=6
22:09:24:140 Device protocol version: 0x010B
22:09:24:194 Current channel 11
22:09:24:213 CTRL ANT_CTRL 0x03
22:09:24:243 Device protocol version: 0x010B
22:09:24:304 Current channel 11
22:09:24:325 CTRL ANT_CTRL 0x03
Thank you for your response. I already tried connecting the ConBeeII with a short extension cord but it didn’t change anything. I didn’t use an extension cord before when it was working fine either.
EDIT: I spoke too soon about it still not working. Thank you for the advice!
After I used a longer USB cord to get more distance between the ConBeeII and the SSD it worked again. Here’s hoping it stays that way.
Just to recap. In Phoscon it said “Firmware Not Connected” but after putting the ConBeeII about 55cm away from the SSD using a USB cord it worked again.
Do you have any other USB devices that present themselves as ttyACM#?
I had a similar behaviour once where my Zwave and Conbee II sticks swapped device numbers and both Zwave and the Deconz integrations tried to access same port.
The advice on extension cables are mostly about RF interference. Your problem seem to be the link between the computer and the stick itself and the extension cable has no positive influence on that. On the contrary
There is a known issue with recent Addon versions of Deconz where linking by-id does not always work but the error happens very early before Deconz is started and this is not the case here so it cannot be that problem