Today I upgraded pymc repeater using manage.sh, during this process it allowed me to preserve config options. Most of the config options were preserved, but somehow it reset tx_power to 30, which is really bad because my ebyte 900m33s has an upper limit of 8. Setting 8db on the sx1262 actually outputs 33db from the PA. I'm very worried that I may have permanently damaged my radio from this.
Today I upgraded pymc repeater using manage.sh, during this process it allowed me to preserve config options. Most of the config options were preserved, but somehow it reset tx_power to 30, which is really bad because my ebyte 900m33s has an upper limit of 8. Setting 8db on the sx1262 actually outputs 33db from the PA. I'm very worried that I may have permanently damaged my radio from this.
<!-- github-sync-id:4005935711 -->
I'm not sure how this has happened, as if you had existing config that is normally preserved, what branch were you using?
I'm not sure how this has happened, as if you had existing config that is normally preserved, what branch were you using?
<!-- github-comment-id:3980933775 -->
I think i migrated from main to dev, during the process it also restructured the yaml file, all the comments in the config file were gone. Maybe there should be an option to not touch the file at all and let the user hand-migrate the file. There's many hardware radios in the wild that have their own P1db limit that may not have safety bound checks
I think i migrated from main to dev, during the process it also restructured the yaml file, all the comments in the config file were gone. Maybe there should be an option to not touch the file at all and let the user hand-migrate the file. There's many hardware radios in the wild that have their own P1db limit that may not have safety bound checks
<!-- github-comment-id:3985702893 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Today I upgraded pymc repeater using manage.sh, during this process it allowed me to preserve config options. Most of the config options were preserved, but somehow it reset tx_power to 30, which is really bad because my ebyte 900m33s has an upper limit of 8. Setting 8db on the sx1262 actually outputs 33db from the PA. I'm very worried that I may have permanently damaged my radio from this.
I'm not sure how this has happened, as if you had existing config that is normally preserved, what branch were you using?
I think i migrated from main to dev, during the process it also restructured the yaml file, all the comments in the config file were gone. Maybe there should be an option to not touch the file at all and let the user hand-migrate the file. There's many hardware radios in the wild that have their own P1db limit that may not have safety bound checks