Device state timeout ignored in state 3

deCONZ General Support
1

In log I have full of warning device state timeout ignored in state 3. I have not found any information about this.

16:41:05:641 DEV Tick.Init: booted after 8000 seconds
16:41:07:188 Device firmware version 0x26660700 ConBee II
16:41:07:191 unlocked max nodes: 512
16:41:07:246 Device protocol version: 0x010C
16:41:07:300 Current channel 15
16:41:07:314 CTRL ANT_CTRL 0x03
16:41:07:337 Device protocol version: 0x010C
16:41:07:389 CTRL ANT_CTRL 0x03
[16:41:07] INFO: Successfully send discovery information to Home Assistant.
16:41:12:649 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26720700.bin.GCF
16:41:12:649 GW firmware version is up to date: 0x26720700
16:41:17:324 device state timeout ignored in state 3
16:41:31:740 Bind response success for 0x000d6ffffe9e108f ep: 0x01 cluster: 0x0000
16:41:31:839 ZCL configure reporting rsp seq: 1 0x000D6FFFFE9E108F for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
16:41:35:156 device state timeout ignored in state 3
16:41:35:316 device state timeout ignored in state 3
16:41:35:476 device state timeout ignored in state 3
16:41:35:636 device state timeout ignored in state 3
16:41:35:797 device state timeout ignored in state 3
16:41:35:956 device state timeout ignored in state 3
6:41:52:149 ZCL attribute report 0x00158D0001643EB2 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
16:41:52:157 ZCL attribute report 0x00158D0001643EB2 for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
16:41:52:648 Set sensor check interval to 100 milliseconds
16:41:52:741 Bind response success for 0x000d6ffffe9e108f ep: 0x01 cluster: 0x0000
16:41:55:733 device state timeout ignored in state 3
16:41:56:665 Device TTL 1358 s flags: 0x7
...
16:49:43:508 ZCL attribute report 0x00158D00027D8E39 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F 
16:49:43:508 0x00158D00027D8E39 extract Xiaomi special attribute 0xFF01
16:49:43:509 	01 battery 3045 (0x0BE5)
16:49:43:509 	03 Device temperature 27 °C
16:49:43:509 	04 unknown 17320 (0x43A8)
16:49:43:509 	05 RSSI dB (?) 1194 (0x04AA)
16:49:43:509 	06 LQI (?) 4294967296 (0x0100000000)
16:49:43:509 	0a Parent NWK 0 (0x0000)
16:49:43:510 	97 unknown 0 (0x0000)
16:49:43:510 	98 unknown 0 (0x0000)
16:49:43:510 	99 unknown 0 (0x0000)
16:49:43:510 	9a unknown 4 (0x0004)
16:49:47:228 device state timeout ignored in state 3
16:49:47:388 device state timeout ignored in state 3
16:49:47:549 device state timeout ignored in state 3
16:49:47:709 device state timeout ignored in state 3
16:49:47:868 device state timeout ignored in state 3
16:49:48:028 device state timeout ignored in state 3
16:49:56:663 Device TTL 877 s flags: 0x7
16:49:57:282 ZCL attribute report 0x00158D0001643EB2 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
16:49:57:290 ZCL attribute report 0x00158D0001643EB2 for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
16:49:57:661 Set sensor check interval to 100 milliseconds
16:50:08:228 device state timeout ignored in state 3
16:50:56:228 device state timeout ignored in state 3
16:50:56:669 Device TTL 817 s flags: 0x7
...
17:41:04:420 device state timeout ignored in state 3
17:41:04:580 device state timeout ignored in state 3
17:41:06:161 ZCL attribute report 0x00158D0001643EB2 for cluster: 0x0400, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
17:41:06:176 ZCL attribute report 0x00158D0001643EB2 for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
17:41:12:685 Device TTL 2780 s flags: 0x7
17:41:17:272 device state timeout ignored in state 3
17:41:20:317 device state timeout ignored in state 3
17:41:36:732 device state timeout ignored in state 3
17:41:39:732 device state timeout ignored in state 3

Anyone knows what is this and if it is needs to be resolved?

2

Can you share some larger logs with appropriate flags? There’s an post in #deconz

3

@Mimiix

Here it is (1 minute log, there a lot of data):

https://pastebin.com/raw/wQNGnW8B

If you need longer log, let me know.

4

There’s not a lot I see. Just randomly losing serial connection. I’ve seen a bit more cases like this on the home assistant addon lately. No clue why.

@manup remember the odd case were the user had it on the addon and not on an native install? Probably has to do with home assistant os having some changes.

5

That’s not good. I do not see any disconnection in dmesg, also I am using extension cable to avoid interference. Maybe it is worth to open a ticket for this on HA?

I do not want to open another topic with the same question, but maybe can you take a look at this question at HA forum?

6

Id like to stay on topic. Either keep it with that post or open another one here :sweat_smile:

1 Like
7

The message means that the ConBee/RaspBee firmware is polled for it’s state but a response wasn’t received, note this is just the wired connection via USB or UART.

The usual suspects to check here are: no USB extension cable, serial port not correctly configured on Raspberry Pi, too weak power adapter for Raspberry Pi, or SSD drives nearby. Could it be one of these?

8

I have a extension cable, normal PC. Today I replaced the cable and even tried directly plug into PC. Not helped. There is no other way to check what’s wrong?

9

We only see this with the ha addon

10

Is there a possability to disable the check if firmware up to date for the ha addon?

Every Time after the check the Stick changes the state —> device state timeout ignored in state 3

00:52:05:861 	65 humidity 5320
00:52:05:861 	66 pressure 98069 (981)
00:52:05:862 	0a Parent NWK 0 (0x0000)
00:52:09:665 GW firmware version is up to date: 0x26700700
00:52:22:166 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)
00:52:26:005 device state timeout ignored in state 3
00:52:26:165 device state timeout ignored in state 3
00:52:26:325 device state timeout ignored in state 3
00:52:26:484 device state timeout ignored in state 3
11

Hi,

We don’t develop the HA addon so we can’t help with that.

I’m not sure what the message means tho.

12

Hello, thanks for the reply and ok.
In general is there the possibility to disable the firmware update check?

Regards Rob

13

I don’t think the message is related to the firmware check, in recent deCONZ / FW versions the check doesn’t send anything to the firmware as it operates on a cached value.

Anyway I lower the debug message output level for this message (it’s mainly for internal debugging purpose).