Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for Sonoff RF bridge needs to be updated #670

Closed
oldgeezy opened this issue Mar 12, 2021 · 2 comments
Closed

Documentation for Sonoff RF bridge needs to be updated #670

oldgeezy opened this issue Mar 12, 2021 · 2 comments
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@oldgeezy
Copy link

@
re PR: arendst/tasmota#

Following the instructions here:

https://github.com/tasmota/docs/blob/master/docs/devices/Sonoff-RF-Bridge-433.md

I was not able to flash the RF chip. I got an invalid file signature error trying to upload the hex files given by Tasmota.

When I downloaded the Portisch firmware directly from here:

https://github.com/Portisch/RF-Bridge-EFM8BB1/releases/tag/0x04

It worked just fine.

I would update it myself, but I don't know how, or perhaps have permission.

Regards

@oldgeezy oldgeezy added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Mar 12, 2021
@barbudor
Copy link
Collaborator

barbudor commented Mar 12, 2021

@oldgeezy You probably didn't performed the download correctly
Steps are :

Check by opening the file you previously downloaded in a text editor if it is an HEX file or if you misdownloaded an HTML file

If you want to add more details to the doc, please feel free by using the pencil icon on the top right of the doc page.

@oldgeezy
Copy link
Author

You are correct sir! That's frustrating - can't remember exactly which technique I used to download it. Thought it was wget. But opening the HEX file in a text editor clearly shows that it's an HTML file.

Also wonder which way I did it differently from the Portisch repo that I was actually able to get the HEX file...?

I'd add a precautionary note there if 'Edit the file in your fork of this project' (which is what shows when I hover over that edit button is the correct way.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants