search

dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.9k stars 502 forks source link

Firmware not connected Conbee II #1439

Closed florianru1984 closed 5 years ago

florianru1984 commented 5 years ago

I have a new Conbee II Stick. He shows sometimes Firmware not connected. After restart it works.

manup commented 5 years ago

Hi which deCONZ and firmware version are you using?

Latest is deCONZ 2.05.63 with firmware 0x26480700

florianru1984 commented 5 years ago

I use deCONZ 2.05.63 with firmware 0x26480700

manup commented 5 years ago

Hmm interesting, and which platform?

florianru1984 commented 5 years ago

It's connected to an RPi3 with Raspian stretch

manup commented 5 years ago

Is the user also in the group dialout (restart/relogin needed)?

florianru1984 commented 5 years ago

The user is in group dialout. After restarting the Gateway it works for half an hour till 4 hours, then i have to restart the Gateway. Today i reinstalled DeCONZ. But there was no effect. Tommorow i will try it with an fresh Raspian Image.

florianru1984 commented 5 years ago

Today i Installed a new Raspian Image, but there is the same problem

manup commented 5 years ago

I'll do some tests with auto connect turned off, not sure yet what is happening here.

goermezer commented 5 years ago

It seems, that I have the same problem. Phoscon shows not connected. And in the GUI ConBee II doesn`t join the network. I switched over from Raspbee on RPI to Conbee II on Windows with a fresh installation.

After installation it worked for a day. Then suddenly after switching from LAN to WIFI (and changed IP address) no connection anymore. I got it working for a couple of hours by trying, switching networks, running as admin etc. One hour later it is not connected again ?!

Then I tried a fresh install, hoping to use the backup when it works. But no connection anymore. I can reboot the device with the flasher tool. But it simply doesnt connect . The debug parameters doesnt work on windows. Is there any way to get a log on windows?

goermezer commented 5 years ago

I got one step forward. I tried Conbee II on another Windows machine (same OS), where it runs fine. It`s strange. The only difference seems to be the USB serial driver on windows.

manup commented 5 years ago

The only difference seems to be the USB serial driver on windows.

Is this a Win 10 installation? Perhaps there are driver updates in the Windows update. If you can provide more details of your driver versions that would be helpful.

We've tested Win 10 Home and Pro only in short tests yet — long running tests only on Win 7. Long running Win 10 setup will be added in a few days.

For Win 7 we provide a driver https://phoscon.de/conbee2/install#windows7 not sure if it can be installed on Win 10.

goermezer commented 5 years ago

The issues were on Windows 10 1803. The other system is running 1809, where I made 2 successful tests yesterday. Currently Im upgrading 1803 to 1809, and will see, what happens... If it doesnt work, I will try the Win7 driver...

goermezer commented 5 years ago

Ok, no progress anymore. After the upgrade nothing has changed. Same OS, same driver version now. Even the Conbee driver for Win7, which I could install on Win10, doesn`t help. How do I debug this thing on Windows?

I am a bit confused. What is this? image I got this after first plugging in RFLink and then Conbee. After removing the adapters and detecting them again, it is ok now. But Conbee II still doesn`t join the network.

manup commented 5 years ago

But Conbee II still doesn`t join the network.

Do you mean deCONZ is connected to ConBee II but it says "Not in Network"? Which deCONZ and firmware version is installed?

deCONZ → Help → About deCONZ

Latest deCONZ version is 2.05.63 and firmware 0x26480700. If deCONZ doesn't join the network with latest version we should check the Zigbee configuration in:

deCONZ → Edit → Network Settings

goermezer commented 5 years ago

I use Deconz 2.05.63 with Firmware 0x26480700 on Windows 10 1809. Deconz ist connected to the stick. But I can not open a network: image

Here is my network setting: image

And the Endpoints in settings: image

manup commented 5 years ago

Ok that's weird, so this basically means there is no problem with the driver, otherwise deCONZ wouldn't be able to connect and show these settings.

The Zigbee configuration looks valid too.

Just a wild guess, but when the network is started the firmware will try to send some beacon request to figure out channel is ok. If that fails due MAC channel access failure the opening of the network won't succeed.

Is the ConBee II connected directly to the PC or with a usb extension cable?

goermezer commented 5 years ago

It is directly connected. I also have switched between the 4 available ports.

manup commented 5 years ago

If possible can you please try with an usb extension cable, it can strongly rule out interference issues.

ebaauw commented 5 years ago

I'm seeing something similar, but I'm not sure if it's the same issue.

I've got a ConBee II connected to a RaspBerry Pi 3B running Raspbian Stretch. It's the only USB device connected to that Pi. I tried both with and without a USB extention cable. I'm running deCONZ 2.05.63, installed from the package in the README. After a while, deCONZ GUI shows the firmware update screen, even though the ConBee runs on 0x26480700.

After exiting and restarting deCONZ, it runs normally again for a couple of hours. Currently I have no devices connected to the ConBee II's ZigBee network. This is still a test setup, that I used to upgrade the Trådfri remote firmware. This worked fine for my first remote, with the ConBee II connected directly to the Pi. Before the second upgrade, I used a small (20cm) USB extension cable (wondering whether it would speed up the firmware upgrade). After three attemps, where the upgrade was interruped by the ConBee firmware upgrade message in the GUI, I blamed the extention cable and connected the ConBee II directly again. However, the next attempt also failed. I noticed the stable stretch package v2.05.63 from the APT repository still contains v3.02 of GCFFlasher_internal, so I installed the package from the README. That does contain v3.03 of the flasher, but still no joy.

$ apt list deconz
Listing... Done
deconz/now 2.05.63-raspbian-jessie-beta armhf [installed,local]
$ GCFFlasher_internal -l
GCFFlasher V3_03 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyS0       | 0x0000 | 0x0000  |            | RaspBee 
/dev/ttyACM0     | 0x1CF1 | 0x0030  | DE1948490  | ConBee II
goermezer commented 5 years ago

@manup, instead of an extension cable I connected an old USB 1.1 hub and connected Conbee II to it. Now the network is joined and sensors are visible in GUI. But Phoscon still says Firmware not connected: image Update: The result is the same with an USB extension cable. It seems there are really some interferences between WIFI and ZIGBEE.

ebaauw commented 5 years ago

I'm seeing some worrying messages in the syslog:

Apr 20 14:52:37 pi4 kernel: [1968316.021497] usb 1-1.5: USB disconnect, device number 31
Apr 20 14:52:37 pi4 kernel: [1968316.040652] cdc_acm 1-1.5:1.0: failed to set dtr/rts 
Apr 20 14:52:37 pi4 kernel: [1968316.340555] usb 1-1.5: new full-speed USB device number 32 using dwc_otg 
Apr 20 14:52:37 pi4 kernel: [1968316.474927] usb 1-1.5: New USB device found, idVendor=1cf1, idProduct=0030
Apr 20 14:52:37 pi4 kernel: [1968316.474939] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 20 14:52:37 pi4 kernel: [1968316.474943] usb 1-1.5: Product: ConBee II
Apr 20 14:52:37 pi4 kernel: [1968316.474948] usb 1-1.5: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Apr 20 14:52:37 pi4 kernel: [1968316.474953] usb 1-1.5: SerialNumber: DE1948490
Apr 20 14:52:37 pi4 kernel: [1968316.477147] cdc_acm 1-1.5:1.0: ttyACM1: USB ACM device
Apr 20 14:52:38 pi4 mtp-probe: checking bus 1, device 32: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5"
Apr 20 14:52:38 pi4 mtp-probe: bus: 1, device: 32 was not an MTP device
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:30:888 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 241, rssi: 19
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:30:888 #011asdu: 6200000000
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:30:888 APS-DATA.indication request id: 200 -> finished
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:30:888 APS-DATA.request id: 200 erase from queue
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:30:889 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:32:159 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0 
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:33:268 APS-DATA.request id: 202, addrmode: 0x03, addr: 0x00212effff03d4a7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:33:281 APS-DATA.confirm id: 202, status: 0x00 SUCCESS 
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:33:281 APS-DATA.confirm request id: 202 -> confirmed, timeout 7558176 
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:33:290 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 241, rssi: 19
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:33:290 #011asdu: 6300000000
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:33:290 APS-DATA.indication request id: 202 -> finished
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:33:290 APS-DATA.request id: 202 erase from queue
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:33:290 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:35:159 Idle timer triggered
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:35:667 APS-DATA.request id: 204, addrmode: 0x03, addr: 0x00212effff03d4a7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:35:680 APS-DATA.confirm id: 204, status: 0x00 SUCCESS 
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:35:680 APS-DATA.confirm request id: 204 -> confirmed, timeout 7494856 
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:35:686 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 241, rssi: 19
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:35:686 #011asdu: 6400000000
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:35:687 APS-DATA.indication request id: 204 -> finished
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:35:687 APS-DATA.request id: 204 erase from queue
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:35:687 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:38:067 APS-DATA.request id: 206, addrmode: 0x03, addr: 0x00212effff03d4a7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:38:160 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:38:160 device state timeout ignored in state 3 
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:39:160 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:39:160 device state timeout ignored in state 3 
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:40:160 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:40:160 device state timeout ignored in state 3 
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:41:160 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:41:160 device state timeout ignored in state 3
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:42:160 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:42:160 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:42:160 device state timeout ignored in state 3
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:160 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:160 device state timeout (handled)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:160 MASTER kill cmd 0x0A (ERROR)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:163 CTRL read param resp id: 0x01, status: 0x05
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:163 MASTER kill cmd 0x0A (ERROR)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:165 CTRL read param resp id: 0x01, status: 0x05
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:165 MASTER kill cmd 0x0A (ERROR)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:167 CTRL read param resp id: 0x01, status: 0x05
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:167 MASTER kill cmd 0x0A (ERROR)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:169 CTRL read param resp id: 0x01, status: 0x05
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:169 MASTER kill cmd 0x0A (ERROR)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:171 CTRL read param resp id: 0x01, status: 0x05
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:171 MASTER kill cmd 0x0A (ERROR)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:173 CTRL read param resp id: 0x01, status: 0x05
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:225 Serial com disconnected, reason: 4
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:253 aps request id: 206 prf: 0x0000 cl: 0x0031 timeout (confirmed: 0) to 0x00212EFFFF03D4A7 (0x0000)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:253 aps request id: 206 prf: 0x0000 cl: 0x0031 timeout NOT confirmed to 0x00212EFFFF03D4A7 (0x0000)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:268 aps request id: 206 failed, erase from queue
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:268 emit artificial APSDE-DATA.confirm id: 206
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:348 aps request id: 206 failed, erase from queue
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:660 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:43:660 device state timeout (handled)
Apr 20 14:52:44 pi4 deCONZ[26385]: 14:52:44:223 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
Apr 20 14:52:53 pi4 kernel: [1968331.732718] cdc_acm 1-1.5:1.0: failed to set dtr/rts
Apr 20 14:52:53 pi4 kernel: [1968331.893223] usb 1-1.5: USB disconnect, device number 32
Apr 20 14:52:53 pi4 kernel: [1968332.190600] usb 1-1.5: new full-speed USB device number 33 using dwc_otg
Apr 20 14:52:53 pi4 kernel: [1968332.324920] usb 1-1.5: New USB device found, idVendor=1cf1, idProduct=0030
Apr 20 14:52:53 pi4 kernel: [1968332.324931] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 20 14:52:53 pi4 kernel: [1968332.324937] usb 1-1.5: Product: ConBee II
Apr 20 14:52:53 pi4 kernel: [1968332.324942] usb 1-1.5: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Apr 20 14:52:53 pi4 kernel: [1968332.324946] usb 1-1.5: SerialNumber: DE1948490
Apr 20 14:52:53 pi4 kernel: [1968332.325712] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
Apr 20 14:52:53 pi4 mtp-probe: checking bus 1, device 33: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5"
Apr 20 14:52:53 pi4 mtp-probe: bus: 1, device: 33 was not an MTP device
Apr 20 14:53:01 pi4 kernel: [1968339.573192] usb 1-1.5: USB disconnect, device number 33
Apr 20 14:53:01 pi4 kernel: [1968339.920605] usb 1-1.5: new full-speed USB device number 34 using dwc_otg
Apr 20 14:53:01 pi4 kernel: [1968340.054924] usb 1-1.5: New USB device found, idVendor=1cf1, idProduct=0030
Apr 20 14:53:01 pi4 kernel: [1968340.054934] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 20 14:53:01 pi4 kernel: [1968340.054939] usb 1-1.5: Product: ConBee II
Apr 20 14:53:01 pi4 kernel: [1968340.054944] usb 1-1.5: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Apr 20 14:53:01 pi4 kernel: [1968340.054948] usb 1-1.5: SerialNumber: DE1948490
Apr 20 14:53:01 pi4 kernel: [1968340.057121] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
Apr 20 14:53:01 pi4 mtp-probe: checking bus 1, device 34: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5"
Apr 20 14:53:01 pi4 mtp-probe: bus: 1, device: 34 was not an MTP device
Apr 20 14:55:01 pi4 CRON[30250]: (pi) CMD (Applications/cputemp.command)
Apr 20 14:55:43 pi4 systemd[1]: Started Session c26 of user pi.
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:44:224 COM: /dev/ttyS0 :  (0x0000/0x0000)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:44:230 dev /dev/ttyS0 (/dev/ttyS0)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:44:230 COM: /dev/ttyACM1 : ConBee II (0x1CF1/0x0030)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:44:238 auto connect com /dev/ttyS0
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:44:244 Serial com disconnected, reason: 4
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:226 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:227 COM: /dev/ttyS0 :  (0x0000/0x0000)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:227 dev /dev/ttyS0 (/dev/ttyS0)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:227 COM: /dev/ttyACM1 : ConBee II (0x1CF1/0x0030)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:278 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:278 COM: /dev/ttyS0 :  (0x0000/0x0000)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:278 dev /dev/ttyS0 (/dev/ttyS0)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:278 COM: /dev/ttyACM1 : ConBee II (0x1CF1/0x0030)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:281 auto connect com /dev/ttyACM1
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:286 Serial com connected
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:763 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:45:763 device state timeout ignored in state 2
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:46:713 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:46:713 device state timeout ignored in state 2
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:47:192 COM: /dev/ttyAMA0 :  (0x0000/0x0000)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:47:193 COM: /dev/ttyS0 :  (0x0000/0x0000)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:47:193 dev /dev/ttyS0 (/dev/ttyS0)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:47:193 COM: /dev/ttyACM1 : ConBee II (0x1CF1/0x0030)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:47:667 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:47:668 device state timeout ignored in state 2
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:48:659 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:48:659 device state timeout ignored in state 2
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:49:659 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:49:659 device state timeout ignored in state 2
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:50:660 void zmMaster::handleStateStatus(zmMaster::MasterEvent) EVENT_TIMEOUT
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:50:660 device state timeout (handled)
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:51:160 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:51:160 device state timeout ignored in state 4
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:52:160 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:52:53:242 Serial com disconnected, reason: 4
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:53:02:160 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
Apr 20 14:57:07 pi4 deCONZ[26385]: 14:53:12:160 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
manup commented 5 years ago

Hmm strange, it looks like the firmware reboots, perhaps the watchdog triggers. When the firmware reboots the USB device is also enumerated again.

I'll setup a equal test with stretch and just the ConBee II to see if the problem can be recreated.

Open questions:

On it ...

manup commented 5 years ago

Confirmed in my setup. Looks like the conditions to reset the watchdog from deCONZ core are a bit to strict and don't cover certain setups. Also reconnecting should take care of ConBee II boot time, or at least check if bootloader is still active.

Will be fixed in 2.05.64.

manup commented 5 years ago

Version 2.05.64 is available now: https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/V2_05_64

tenholde commented 5 years ago

Is there a WIN10 installation package?

manup commented 5 years ago

All windows releases can be found here:

https://www.dresden-elektronik.de/deconz/win/?C=M;O=D

tenholde commented 5 years ago

Thank you for pointing me to the windows installation file.

I successfully updated to 2.05.64 and updated firmware to 26330500 and still cannot get Phoscon to find the vent as a light.

I can control the vent using the On/Off cluster, but in order to get it to work with HomeSeer, it must be found as a light, and Phoscon is not finding it.

Ed Tenholder ed@tenholder.net

From: Manuel Pietschmann notifications@github.com Sent: Sunday, April 28, 2019 10:47 AM To: dresden-elektronik/deconz-rest-plugin deconz-rest-plugin@noreply.github.com Cc: Ed Tenholder ed@tenholder.net; Comment comment@noreply.github.com Subject: Re: [dresden-elektronik/deconz-rest-plugin] Firmware not connected Conbee II (#1439)

All windows releases can be found here:

https://www.dresden-elektronik.de/deconz/win/?C=M;O=D

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/dresden-elektronik/deconz-rest-plugin/issues/1439#issuecomment-487390904, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AESZNCGHBMK7ZKNWXM6N5H3PSXBGJANCNFSM4HGK2OZA.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

0evmc commented 5 years ago

Has a resolution been found for this issue? I have Hass.io running deCONZ, and I am trying to add my Keen Vents, but I can't even get that far because deCONZ wont connect to the Raspbee.

mikkihugo commented 4 years ago

I often get same issue with docker on openhab

marine1988 commented 4 years ago

Im using hassio in docker and having same issue what yo guys do to fix it?

ocedric commented 4 years ago

Im using hassio in docker and having same issue what yo guys do to fix it?

Same here... But it was working 2 days ago and just stopped... Install is hassio as a docker in raspbian.

Restoring snapshots from 3 days ago doesn't help.

atechnical commented 4 years ago

same problem here, but I'm running hassio on a virtual box on a windows 10 machine if it matters

ronaldtveen commented 4 years ago

I’m running marthoc deconz docker container on a fresh Raspbian Buster lite install. Getting the Firmware: not connected on the Settings > Gateway page.

Also tried ZHA integration in Home Assistant, can’t connect to it the conbee.

It is a new out of the box conbee II stick.

DiggaTS commented 4 years ago

Same problem here. I have tryed a long usb 2.0 cabel. Then i have for a few minutes a connect and i have learned a few devices. The after reboot ... no connect ... Firmware was shown, but no response ...

can i hope for a solution?

Smanar commented 4 years ago

The firmware not connected is a bug, all device loosed after restart is another problem https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2273

mikkihugo commented 4 years ago

It happpes like every 2 weeks for me that it gets disconnected. Seems the USB device is not reachable but a reboot solves it, but annoys the family.

kmplngj commented 4 years ago

It happpes like every 2 weeks for me that it gets disconnected. Seems the USB device is not reachable but a reboot solves it, but annoys the family.

@mikkihugo +1

Smanar commented 4 years ago

And you are all with Hassio and docker ? Pls add your config, it's hard to find a common point. Have you tried to reboot just the gateway ? (with unplug, wait 30s and replug it)

Ageo commented 4 years ago

Hi all, i have the same problem. Now is seams to work fine, thanks Smanar in the other topic ;)

So my new issue, the key is connected, everything work but about 4h only after I can steal reach the website into the port 8484 but the conbee key is firmware: not connected.

Into debian I doesn't see the key anymore: root@home:~# GCFFlasher_internal -l GCFFlasher V3_13 (c) dresden elektronik ingenieurtechnik gmbh Path | Vendor | Product | Serial | Type -----------------+--------+---------+------------+-------

A reboot fix that but I can't reboot the VM every 4 hours... Any fix for that ?

Many thanks for your help

Smanar commented 4 years ago

Hello, have you try to just unplug/wait sometime/replug the conbee ? It can be an indice to check if the problem is from the conbee or the software, can be USB power (try powered HUB), USB interference, have you tried the USB cable extension ? never use 3.0 port.

Edit: Ha yes I remember you, you have just updated the firmware using the SwoopX link ? This solution is realy usefull for device that disconnect every 5s, if your can work 4h, I don't think it's the same problem, but can be tested.

I know you don't want to use it on a windows machine, but It's a realy usefull test to test the device. If you can let a windows machine working for more than 4h to make test.

Ageo commented 4 years ago

Hello, the key is plugged into a USB 3.0 (no choice into this computer) and I have change the cable extension to 2.0. Same result, key disconnected and firmware not connected 4h after. Reboot still fix this issue.

Unplug/plug don't work.

I have updated the firmware into windows 10 and I have followed the official tutorial and requirements. Everything was ok when I done it, the key was well recognized into windows and was not disconnected.

Any new idea ? :)

Ageo commented 4 years ago

Tried to disable the Deconz plugin into jeedom, re enable it and restart the deamon same firmware not connected. Only the reboot seams to fix that.

Smanar commented 4 years ago

Ok so, reset the conbee alone don't work, reset the software alone don't work too ... Why only the reboot is working ?

And (if someone can correct me) USB 3 issue is malfunction but not "firmware not connected".

You havent USB powered HUB to check power ? (but in this situation I think the unplug/replug have worked)

Can you make a try on a windows machine, to be sure it's not the device that have problem ? If you already have too much device you can migrate all the database with backup/restore feature.

Ageo commented 4 years ago

I don't know but i've try something new.

Into Proxmox on the VM configuration with USB I can disable USB 3.0 so I will emulate a USB 2.0 even if the physical port is a 3.0 I think so let's wait and see :)

I will let you know if that don't work I will try with the USB powered HUB.

Thanks for your follow and help.

Ageo commented 4 years ago

Issue solved with this configuration into proxmox. Now the key seams to be stable :) ! Nice. Thanks again Smanar.

DiggaTS commented 4 years ago

Hy,

i solved the Problem .. how? I dont know ... I have tryed a long USB2.0 cable.. reinstallation ... and then ... suddenly .. a new installation and a raspberry pi 4 ... it worked. I dont know why ...

I have tryed to reinstall the os bevor .. but now it worked...

It anoying a lot ;-)

mikkihugo commented 4 years ago

I still have the issue. Running latest openhabian and using a usb 2.0 extension cable.

Smanar commented 4 years ago

hello

fusco commented 4 years ago

Same issue 

$ GCFFlasher_internal -l
GCFFlasher V3_03 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyS0       | 0x0000 | 0x0000  |            | RaspBee 
/dev/ttyACM0     | 0x1CF1 | 0x0030  | DE1948490  | ConBee II

after some seconds 

$ GCFFlasher_internal -l
GCFFlasher V3_03 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyS0       | 0x0000 | 0x0000  |            | RaspBee

I can see a loop usb disconnect with lusb

I d'ont have usb 3 (raspberry 3B) I haven't windows machine, only with virtualMachine

Same comportment on Mac OS X. (usb loop disconnect)