Update!

Hey folks, hope all is well out there!

My end of week time crunch is getting even crunchier so I wanted to quickly confirm that the Operator middleware has been pushed to the Mugsy Org page on Github. Some notes:

  • Repo Link: https://github.com/MugsyOS/Operator

  • I have not had a chance to merge in a lot of work so a bunch is missing. No auth, no docs, platform weight service is being converted to a socket service, etc.

  • If you run the install on a non-pi device it will likely fail. There are a few GPIO libs that just won’t work without linux or specific hardware. Setup will eventually be updated to conditionally configure the system depending on the local hardware and OS. Additional mocking will be added to simplify dev on non-pi hardware.

  • Given that a bunch of stuff needs to be merged in, your best bet for testing it out is using the relay or pump routes. That should give a good foundation on how the middleware works.

  • The RFID and Watchtower services will eventually be installed as system services when running the setup script. Until then, you can run them by entering:

    • python src/operator_services/rfid_service.py

    • python src/operator_services/watchtower_service.py

  • Make sure you start your local pigpiod service before starting Operator:

    • sudo pigpiod

  • Any pin mappings currently missing from the config file will be in the relevant api routes or services.

  • The non-specific pin service has not been merged in yet. There are two on and off endpoints in the status routes that will allow you set any pin high or low. This is only there to simplify some dev checks while working and control is limited. Please be sure you understand how this functionality works if you decide to check it out as it is not monitored by Watchtower.

  • I expect to start merging in the remaining work late Sunday or Monday. My hope is that everything will be in there by the end of next week. Docs will likely be last, although I will add basic usage updates as new functionality is introduced.

  • Repo contributions are limited to prior contributurs for the next 7 days. Big issues that you may run into over the next few days will likely be resolved with the upcoming merges. Once that code is in, you will be able to submit issues and PRs as normal.

  • Reminder that this middleware is focused very tightly on GPIO control. User, recipe, brew commands, etc is handled in the DECAF API. DECAF connects to Operator when some hardware action must occur. DECAF should go live on the Org page sometime around the 15th.

As noted in Wednesday’s update, this middleware is going out undercooked since I have an event this weekend that I spaced on when scheduling this weeks workload. I hope to complete the work I would have done this weekend quickly once I am back at my desk.

I will have a short status update out on Tuesday night to go over whats left to merge in.

Thanks!

MComment