arevinje
November 28, 2021, 10:52pm
21
Info from the DeCONZ Community Forum:
opened 08:58PM - 01 Aug 21 UTC
Confirmed Bug
Bug report
<!--
- Use this issue template to report a bug in the deCONZ REST-API.
- I… f you want to report a bug for the Phoscon App, please head over to: https://github.com/dresden-elektronik/phoscon-app-beta
- Make sure not to remove any headers and fill the template completely. If you remove the headers, the issue will be auto-closed.
- If you're unsure if the bug fits into this issue tracker, please ask for advise in our Discord chat: https://discord.gg/QFhTxqN
- Please make sure sure you're running the latest version of deCONZ: https://github.com/dresden-elektronik/deconz-rest-plugin/releases
-->
## Describe the bug
<!--
Describe the issue you are experiencing here to communicate to the
maintainers. Tell us what you were trying to do and what happened.
Help us understand the issue by providing valuable context.
-->
Pick up the channel change issue for higher channels from here https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4005#issuecomment-750582124
Tested in my test environment. Previous channel was 15. Going down to 11 was ok, going up to 20 resulted in a failed channel change (25 untested, but same expected).
This guidance does **NOT** succeed: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4005#issuecomment-750399933
## Steps to reproduce the behavior
<!--
If the problem is reproducable, list the steps here:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. Observed error
If the problem can't be reproduced and is sporadic, please provide some details
on how often and when the issue happens.
-->
Change channel from 11 to 20 (regardless if Phoscon or deconz GUI).
## Expected behavior
<!--
If applicable, describe what you expected to happen.
-->
Channel change to be successful and also applied to the coordinator.
## Screenshots
<!--
If applicable, add screenshots to help explain the problem.
-->
## Environment
<!--
The deCONZ and firmware versions are found in the Phoscon App: Menu -> Settings -> Gateway,
as well as in the deCONZ GUI: Menu > Help > About deCONZ.
-->
- Host system: Raspberry Pi
- Running method: Raspbian
- Firmware version: 26390500
- deCONZ version: 2.12.03-beta
- Device: RaspBee I
- Do you use an USB extension cable: No
- Is there any other USB or serial devices connected to the host system: No
## deCONZ Logs
<!--
Debug logs can help to investigate certain problems like device pairing and communication issues.
Logging can be enabled on the command line as described in:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags
Secondly, for versions above 2.05.87: In the deCONZ GUI: click Help > debug view. Output of APS,ZDP, ZCL and INFO can be handy.
-->
## Additional context
<!--
If relevant, add any other context about the problem here, like network size, number of routers and end-devices
and what kind of devices/brands are in the network.
-->
My observations:
- Routers seem to get the channel change
- Coordinator does NOT get the channgel change
- End devices do NOT get the channel change
- Downgrade to FW 26350500, manually apply channel change to 20 in deconz GUI and then upgrade again to 26390500 apparently works.
- Eventually, Phoscon reports a successful channel change although it failed.
MarVin
November 29, 2021, 1:42pm
22
I was definitely on an earlier firmware when I changed mine but am on the newest one now. I just verified that the channel stayed after upgrading. I was on 262F0500 (Nov 2018) when I made the change but am now on 26400500. It does not look like 264X has been tested to see if the bug was fixed and I don’t see anything in the changelog. It’s pretty easy to flash it in a DOS window if it were me I would downgrade set the channel then upgrade to 264X.
1 Like