Deconz-rest-plugin: Skip automatic channel change, TODO warn user
Describe the bug
Log says Skip automatic channel change ever 10 seconds after changing channel from 11 to 15.
Seems like im running channel 15, getting counterwise messages in the logs.
20:38:06:141 Current channel 15
20:38:16:081 channel is 15 but should be 11, start channel change
20:38:16:081 Skip automatic channel change, TODO warn user
20:38:26:082 channel is 15 but should be 11, start channel change
20:38:26:082 Skip automatic channel change, TODO warn user
20:38:36:081 channel is 15 but should be 11, start channel change
20:38:36:081 Skip automatic channel change, TODO warn user
20:38:46:082 channel is 15 but should be 11, start channel change
20:38:46:082 Skip automatic channel change, TODO warn user
20:38:56:081 channel is 15 but should be 11, start channel change
20:38:56:081 Skip automatic channel change, TODO warn user
20:39:06:082 channel is 15 but should be 11, start channel change
Steps to reproduce the behavior
Unsure if its reproducable when i dont want to change channel more than necessary.
- Go to 'Phoscon'
- Click on 'Gateway, Advanced'
- Scroll down to 'Change zigbee channel', switch to 15.
- Observed error
Expected behavior
Unsure if this is a problem or not, but output should mean something
Environment
(Please make this copy/pastable by web interface)
- Host system: PC
- Running method: Marthoc docker
- Firmware version: (2635050000)
- deCONZ version: (2.05.79)
- Device: (ConBee I )
- Do you use an USB extension cable: yes
deCONZ Logs
20:42:51:145 don't close database yet, keep open for 900 seconds
20:42:56:081 channel is 15 but should be 11, start channel change
20:42:56:081 Skip automatic channel change, TODO warn user
20:42:57:525 0x7CB2 seems to be a zombie recv errors 6
20:42:57:525 Node zombie state changed 0x00178801035617db
20:42:58:090 don't close database yet, keep open for 900 seconds
20:42:58:703 ZCL attribute report 0x00158D0001D555FF for cluster: 0x0406, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:00:159 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:00:191 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:00:223 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:05:137 don't close database yet, keep open for 900 seconds
20:43:06:082 channel is 15 but should be 11, start channel change
20:43:06:082 Skip automatic channel change, TODO warn user
20:43:06:110 GW firmware version: 0x26350500
20:43:06:110 GW firmware version is up to date: 0x26350500
20:43:06:161 Current channel 15
20:43:06:193 Device TTL 5380 s flags: 0x7
20:43:10:628 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0000, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:10:628 0x00158D0001F55A51 extract Xiaomi special attribute 0xFF01
20:43:10:628 01 battery 2965 (0x0B95)
20:43:10:628 04 unknown 5032 (0x13A8)
20:43:10:628 05 RSSI dB (?) 10486 (0x28F6)
20:43:10:628 06 LQI (?) 4294967296 (0x0100000000)
20:43:10:628 64 temperature 2293
20:43:10:628 65 humidity 4164
20:43:10:628 66 pressure 98783 (988)
20:43:10:628 0a unknown 0 (0x0000)
20:43:11:444 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:11:476 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:11:508 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:12:091 don't close database yet, keep open for 900 seconds
20:43:16:081 channel is 15 but should be 11, start channel change
20:43:16:081 Skip automatic channel change, TODO warn user
20:43:19:057 don't close database yet, keep open for 900 seconds
20:43:21:913 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:21:945 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:21:977 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:25:242 don't close database yet, keep open for 900 seconds
20:43:26:082 channel is 15 but should be 11, start channel change
20:43:26:082 Skip automatic channel change, TODO warn user
20:43:32:090 don't close database yet, keep open for 900 seconds
20:43:32:412 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:32:444 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:32:476 ZCL attribute report 0x00158D0001F55A51 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
20:43:36:081 channel is 15 but should be 11, start channel change
20:43:36:081 Skip automatic channel change, TODO warn user
Additional context
IKEA Tr氓fri/Xiaomi sensors, about 15-20 devices total
roflmao
All 9 comments
What does Phoscon say under _Gateway -> Advanced_ for the current channel? I understand channel 15 was not working for you?
SwoopX
on 4 Aug 2020
A couple of weeks ago i changed from channel 11(iirc) to channel 15.
Since then i have had these messages. Phoscon, Gateway, Advanced says Zigbee channel 15, but the logs keeps telling me something is up.
I have strange behaviour of old sensors coming back after a while after deleting as well (thought adding this in another bug report, but may be relevant?)
roflmao
on 5 Aug 2020
Thanks, that's interesting. I'll see if I can reproduce this somehow. If it's currently just an annoyance, then we're good for the moment.
Devices coming back when previously deleted in deconz GUI is normal. The mechanism behind that is a bit delicate but I also got some tests in this regard on my list. No need for a seperate issue.
SwoopX
on 5 Aug 2020
I also have an issue currently where added devices suddenly disappear as well. I will try to reproduce, what kind of logs do you want?
I use docker marthoc image with the following envs:
DEBUG_INFO=1
DEBUG_APS=0
DEBUG_ZDP=0
DEBUG_OTAU=1
DEBUG_ZCL=0
@roflmao To keep issues on subject, I'd like you to open a seperate issue for that. 馃槃
Mimiix
on 5 Aug 2020
@Mimiix Sure thing, just wanted a recommandation for which debug data to enable before reproducing
roflmao
on 5 Aug 2020
DEBUG_INFO=2
SwoopX
on 5 Aug 2020
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.
![stale[bot] picture](https://avatars3.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 27 Aug 2020
As there hasn't been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it isn't solved, request to get this opened again.
stale[bot]
on 3 Sep 2020
Related issues
jan666
路
4Comments
qm3ster
路
3Comments
salopette
路
4Comments
felixstorm
路
4Comments
ReeChip
路
5Comments