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

Add hardware support - Nordic NRF905 Transceiver #139

Open
wants to merge 19 commits into
base: OrangePi
Choose a base branch
from
Open

Conversation

JacekKac
Copy link

Maybe sombody will be interested in adding support for NRF905 Transeiver? it should help to set it quicker without soldering

Hardware & setup details :
https://www.instructables.com/How-to-Use-the-Nordic-NRF905-Transceiver-With-a-Ra/

example library:
https://github.com/ZakKemble/nRF905.git

MarkGodwin and others added 12 commits October 23, 2021 15:34
add seperate down and up durations
separate up and down durations and remove pointless wait
Use down duration time for principal direction. Up direction could be added to UI later as seperate field
add comments for durations
Separate duration for up and down directions
Adding special set-up keypresses and a simple guided UI
Thanks @MarkGodwin
The pigpio.pi may return without an established connection. Therefore, the connected variable must be verified after the call
Check if pigpio is connected during initialization
@Nickduino
Copy link
Owner

What's the link between that merge request and the NRF905?

@JacekKac
Copy link
Author

my assumption was to give you an idea to use other hardware (NRF905 in Pi-somfy -dont know i a pull request is good for such idea :) but still, this is a good idea. What u think ? it has software adjustable frequence and is also cheap

@Nickduino
Copy link
Owner

But that specific pull request isn't linked to the NRF905, is it?

@JacekKac
Copy link
Author

oh now i see i made a mess sorry for that :( don't know what went wrong ;( i juts want to submit a idea using

@Nickduino
Copy link
Owner

No issue, I just wanted to clarify things. You're suggesting to make the project compatible with the NRF905, you're not doing a pull out merge request.

Have you had a look at the forks? I'm almost certain someone used the project with a variable emitter. I think that's also what the guy from Pushstack (see the readme) did.

huanvu and others added 7 commits June 24, 2022 21:31
Fix config issues with duration for adding and removing shutter
`requests` missing from requirements.txt
compatibility with Home Assistant 2023.08
As known, Alexa is unable to discover the blinds when running operateShutters.py -e. At the moment, I created a temporary fix to overcome this by using n8henrie/fauxmo simultaneously with Pi-Somfy. This works by calling the HTTP API from the webserver to open and shut the blinds. You will need to find your shutter id with the networking tools in your web browser when manually operating the blinds via the web UI. The payload will contain the shutters id which you can update in fauxmo_config.json. You will need to reinstall the daemon service to use the new start-up script. To use multiple blinds within the alexa integration, add more devices to the fauxmo_config.json. Hopefully OP implements the up-to-date fauxmo repo by n8henrie and can properly integrate it within the program so the process is much more streamlined and works as it should. Unfortunately, I don't have to time to research further into the project to make this work seamlessly but from what I can gather, Alexa now requires some sort of byte response as mandatory and in it's current configuration, Alexa does not receive a discovery response from the program, it could be because of this? I also saw somewhere that Alexa needs the state of the device - with the current implementation it uses a fake state but when you call Alexa and tell her to open the blinds it will set the device on and off accordingly anyway, it's only really annoying if you use the Alexa app for example and see that the device is 'on' (blinds open) when they are shut; still - turn the device off and on with the app and it works as usual. I did look over and see if there was a state handler within the program but I myself am not very familiarised with OOP and so didn't spend much time investigating. But, for now, this works and is a suitable enough fix for me. Additionally, you will need to alter the n8henrie/fauxmo files. Please see: n8henrie/fauxmo#122 where this seperate issue is documented. That said, I am grateful for this project as I can now control my blinds hands-free.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants