lobo/wemo
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
21 Commits 1 Branch 0 Tags 650 KiB
Python 45.1%
Go 42.2%
Shell 11.6%
Dockerfile 1.1%
683a3774c3
Go to file
Emil Lerch 683a3774c3
fully operable system - wemo's duration arg doesn't seem to do anything useful
2019-07-27 15:04:08 -07:00
fauxmo change search function to honor ssdp:all and the proper urn 2019-07-24 17:44:47 -07:00
logger fully operable system - wemo's duration arg doesn't seem to do anything useful 2019-07-27 15:04:08 -07:00
wemodiscovery fully operable system - wemo's duration arg doesn't seem to do anything useful 2019-07-27 15:04:08 -07:00
.gitignore move scanning features into wemo golang package 2019-07-24 17:42:52 -07:00
build move scanning features into wemo golang package 2019-07-24 17:42:52 -07:00
go.mod fully operable system - wemo's duration arg doesn't seem to do anything useful 2019-07-27 15:04:08 -07:00
go.sum move scanning features into wemo golang package 2019-07-24 17:42:52 -07:00
LICENSE add license 2019-07-19 18:44:12 -07:00
movieMode.json fully operable system - wemo's duration arg doesn't seem to do anything useful 2019-07-27 15:04:08 -07:00
README.md switch to port 20000/update readme 2019-07-24 08:48:46 -07:00
wemo_control.sh add shell script to control wemos (this will later be built into wemo.go 2019-07-24 17:45:39 -07:00
wemo.go fully operable system - wemo's duration arg doesn't seem to do anything useful 2019-07-27 15:04:08 -07:00

README.md

WeMo control

The plan:

  1. Use Fauxmo to create a virtual switch 'Movie Lights' recognized on the NAS at port 20000 on a MacVLAN IP address in the IP range 224-240
  2. Fauxmo will run in a docker file and be able to talk to another container, which runs our golang executable. Other container host will be movielights (added via add-host option)
  3. Our golang executable will then talk to the actual wemo switches

TODO:

Figure out how to discover the IP addresses. Options are:

  • Do a discovery at startup
  • Do a discovery before an event I don't like this one due to latency
  • Do a discovery after an event
  • Do a discovery on a time basis

Discovery is currently via a node module. Would prefer to use go here