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

Feature home assistant #85

Open
wants to merge 50 commits into
base: develop
Choose a base branch
from

Conversation

micolspitale93
Copy link
Collaborator

Adding the package harmoni home assistant to control the smart home devices. This package is a wrapper for the request to Home Assistant open source service: https://www.home-assistant.io/getting-started/

micolspitale93 and others added 30 commits April 21, 2021 14:51
Copy link
Collaborator

@RMichaelSwan RMichaelSwan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall good. There are a few minor issues to fix. Also recommend merging in current develop branch changes into this branch before we do the final merge.

doc/tutorials/Create-New-Package.md Outdated Show resolved Hide resolved
doc/tutorials/Create-New-Package.md Outdated Show resolved Hide resolved
doc/tutorials/Create-New-Package.md Outdated Show resolved Hide resolved
doc/tutorials/Create-New-Package.md Outdated Show resolved Hide resolved
doc/tutorials/Create-New-Package.md Show resolved Hide resolved
@@ -0,0 +1,326 @@
#!/usr/bin/env python3
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this file here? Should be in nodes or src (seems like this is a copy?)

Copy link

@etoscano etoscano Jul 19, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no clue about why this is here. I think this is a mistake. This file can be removed.

harmoni_actuators/harmoni_tts/setup.py Outdated Show resolved Hide resolved
harmoni_core/harmoni_pattern/nodes/sequential_pattern.py Outdated Show resolved Hide resolved
harmoni_core/harmoni_pattern/setup.py Outdated Show resolved Hide resolved
while not rospy.is_shutdown() and not self.result:
self.rate.sleep()
assert self.result == True

Copy link
Collaborator

@RMichaelSwan RMichaelSwan Jul 7, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add another test to verify the text received is the same as what is expected. All you need is another function with the test_ prefix. Note that the context will be reset between tests and setup will run again.

Copy link

@etoscano etoscano Jul 19, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your suggestion! I was a bit stuck.
However, I have just found out that the code the code here for the stt service is not the same as the one in feature/edison-smarthome. I changed it a while ago because it was giving me "ERROR: Broken Pipe" when using the method transcribe_stream_request. So I followed the instruction on the google stt page to create a different method for a continuous stream from the mic.

TLDR: I cannot add another test since this stt service is not working (for me at least).
I can add a test if I change the stt service file to the one in feature/edison-smarthome, where there is a different method for handling a stream.
https://github.com/micolspitale93/HARMONI/blob/feature/edison-smarthome/harmoni_detectors/harmoni_stt/nodes/google_service.py

etoscano and others added 6 commits July 9, 2021 10:24
Co-authored-by: Michael Swan <10856729+RMichaelSwan@users.noreply.github.com>
Co-authored-by: Michael Swan <10856729+RMichaelSwan@users.noreply.github.com>
Co-authored-by: Michael Swan <10856729+RMichaelSwan@users.noreply.github.com>
@RMichaelSwan
Copy link
Collaborator

RMichaelSwan commented Jul 16, 2021

The fixes are good. Unresolved comments still need to be handled or addressed (feel free to disagree with me) and merge conflicts fixed (can be done by merging in develop from the main repo-- @micolspitale93 you might want to do this to your fork's develop first and then have changes from that develop merged to the current branch; up to you, feel free to ping me if you need assistance). Feel free to start discussion or message affected parties (can use git blame to see who last made changes to affected files/lines) if there's something difficult to handle in the conflicts.

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.

4 participants