├── .gitattributes
├── .github
└── FUNDING.yml
├── .gitignore
├── CHANGELOG.md
├── LICENSE
├── MANIFEST.in
├── NodeRed examples
├── README.md
└── images
│ ├── dashboard2.png
│ ├── dashboard3.png
│ ├── few_nodes.png
│ ├── playback.png
│ └── playlists.png
├── README.md
├── mopiqtt
├── __init__.py
├── ext.conf
├── frontend.py
├── mqtt.py
└── utils.py
├── setup.cfg
├── setup.py
├── tests
├── __init__.py
├── conftest.py
└── test_smoke.py
└── tox.ini
/.gitattributes:
--------------------------------------------------------------------------------
1 | # Auto detect text files and perform LF normalization
2 | * text=auto
3 |
--------------------------------------------------------------------------------
/.github/FUNDING.yml:
--------------------------------------------------------------------------------
1 | # Would you like to sponsor my work?
2 |
3 | # Developing open source projects takes a lot of time and effort. Any level of one-off or recuring sponsorship
4 | # helps focus my energies on improving the projects. If you would like to contribute, please use one of these links.
5 |
6 | custom: ['https://paypal.me/FabioMarzocca']
7 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | dist/
2 | *.egg-info
3 | build/
4 | mynotes.txt
5 |
--------------------------------------------------------------------------------
/CHANGELOG.md:
--------------------------------------------------------------------------------
1 | # Changelog
2 | ## 1.2.0
3 | * Added track uri message
4 |
5 | ## 1.1.0
6 | * New paho-mqqt requirement (v.>=2.0)
7 |
8 | ## 1.0.11
9 | * Fixes [#4](https://github.com/fmarzocca/Mopiqtt/issues/4)
10 |
11 | ## 1.0.10
12 | * Fixed default artwork image
13 |
14 | ## 1.0.9
15 | * Bugfix on mqtt username (Credit: @hirschharald) Closes [#2](https://github.com/fmarzocca/Mopiqtt/issues/2)
16 |
17 | ## 1.0.8
18 | * Local artwork is not supported
19 |
20 | ## 1.0.7
21 | * Added `mopidy/cmnd/queryschemes` to request a list of uri-schemes Mopidy can handle in searches
22 | * Added `mopidy/stat/uri_schemes` to get a list of uri-schemes Mopidy can handle in searches
23 | * Added `mopidy/cmnd/search` to search libraries for any string (artist, album, track)
24 | * Added Added `mopidy/stat/search_results` to get results of search command
25 |
26 | ## 1.0.6
27 | * Fixed bug on `mopidy/cmnd/plrefresh`
28 | * Class name renaming
29 |
30 | ## 1.0.5
31 | * Improved error catching
32 | * Added `mopidy/stat/trklist` message showing the list of tracks in the queue
33 | * Added `mopidy/cmnd/chgtrk` to change current playing track in tracklist
34 |
35 | ## 1.0.4
36 | * Fixed bug on `mopidy/cmnd/add`
37 | * Added `mopidy/cmnd/pstream` to load and play a radio stream (or any single track)
38 | * Added `mopidy/stat/refreshed` event when playlists have been refreshed
39 | * Added `mopidy/stat/plrefresh` to refresh one or all playlists
40 |
41 | ## 1.0.3
42 | * Better playlist list formatting **Breaking change:** Now the list is an array of objects
43 | * Introducing position of current playing track
44 |
45 | ## 1.0.2
46 | * Added `mopidy/cmnd/ploadshf` to load and play shuffled playlists
47 |
48 | ## 1.0.1
49 | * First release
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Apache License
2 | Version 2.0, January 2004
3 | http://www.apache.org/licenses/
4 |
5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6 |
7 | 1. Definitions.
8 |
9 | "License" shall mean the terms and conditions for use, reproduction,
10 | and distribution as defined by Sections 1 through 9 of this document.
11 |
12 | "Licensor" shall mean the copyright owner or entity authorized by
13 | the copyright owner that is granting the License.
14 |
15 | "Legal Entity" shall mean the union of the acting entity and all
16 | other entities that control, are controlled by, or are under common
17 | control with that entity. For the purposes of this definition,
18 | "control" means (i) the power, direct or indirect, to cause the
19 | direction or management of such entity, whether by contract or
20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 | outstanding shares, or (iii) beneficial ownership of such entity.
22 |
23 | "You" (or "Your") shall mean an individual or Legal Entity
24 | exercising permissions granted by this License.
25 |
26 | "Source" form shall mean the preferred form for making modifications,
27 | including but not limited to software source code, documentation
28 | source, and configuration files.
29 |
30 | "Object" form shall mean any form resulting from mechanical
31 | transformation or translation of a Source form, including but
32 | not limited to compiled object code, generated documentation,
33 | and conversions to other media types.
34 |
35 | "Work" shall mean the work of authorship, whether in Source or
36 | Object form, made available under the License, as indicated by a
37 | copyright notice that is included in or attached to the work
38 | (an example is provided in the Appendix below).
39 |
40 | "Derivative Works" shall mean any work, whether in Source or Object
41 | form, that is based on (or derived from) the Work and for which the
42 | editorial revisions, annotations, elaborations, or other modifications
43 | represent, as a whole, an original work of authorship. For the purposes
44 | of this License, Derivative Works shall not include works that remain
45 | separable from, or merely link (or bind by name) to the interfaces of,
46 | the Work and Derivative Works thereof.
47 |
48 | "Contribution" shall mean any work of authorship, including
49 | the original version of the Work and any modifications or additions
50 | to that Work or Derivative Works thereof, that is intentionally
51 | submitted to Licensor for inclusion in the Work by the copyright owner
52 | or by an individual or Legal Entity authorized to submit on behalf of
53 | the copyright owner. For the purposes of this definition, "submitted"
54 | means any form of electronic, verbal, or written communication sent
55 | to the Licensor or its representatives, including but not limited to
56 | communication on electronic mailing lists, source code control systems,
57 | and issue tracking systems that are managed by, or on behalf of, the
58 | Licensor for the purpose of discussing and improving the Work, but
59 | excluding communication that is conspicuously marked or otherwise
60 | designated in writing by the copyright owner as "Not a Contribution."
61 |
62 | "Contributor" shall mean Licensor and any individual or Legal Entity
63 | on behalf of whom a Contribution has been received by Licensor and
64 | subsequently incorporated within the Work.
65 |
66 | 2. Grant of Copyright License. Subject to the terms and conditions of
67 | this License, each Contributor hereby grants to You a perpetual,
68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 | copyright license to reproduce, prepare Derivative Works of,
70 | publicly display, publicly perform, sublicense, and distribute the
71 | Work and such Derivative Works in Source or Object form.
72 |
73 | 3. Grant of Patent License. Subject to the terms and conditions of
74 | this License, each Contributor hereby grants to You a perpetual,
75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 | (except as stated in this section) patent license to make, have made,
77 | use, offer to sell, sell, import, and otherwise transfer the Work,
78 | where such license applies only to those patent claims licensable
79 | by such Contributor that are necessarily infringed by their
80 | Contribution(s) alone or by combination of their Contribution(s)
81 | with the Work to which such Contribution(s) was submitted. If You
82 | institute patent litigation against any entity (including a
83 | cross-claim or counterclaim in a lawsuit) alleging that the Work
84 | or a Contribution incorporated within the Work constitutes direct
85 | or contributory patent infringement, then any patent licenses
86 | granted to You under this License for that Work shall terminate
87 | as of the date such litigation is filed.
88 |
89 | 4. Redistribution. You may reproduce and distribute copies of the
90 | Work or Derivative Works thereof in any medium, with or without
91 | modifications, and in Source or Object form, provided that You
92 | meet the following conditions:
93 |
94 | (a) You must give any other recipients of the Work or
95 | Derivative Works a copy of this License; and
96 |
97 | (b) You must cause any modified files to carry prominent notices
98 | stating that You changed the files; and
99 |
100 | (c) You must retain, in the Source form of any Derivative Works
101 | that You distribute, all copyright, patent, trademark, and
102 | attribution notices from the Source form of the Work,
103 | excluding those notices that do not pertain to any part of
104 | the Derivative Works; and
105 |
106 | (d) If the Work includes a "NOTICE" text file as part of its
107 | distribution, then any Derivative Works that You distribute must
108 | include a readable copy of the attribution notices contained
109 | within such NOTICE file, excluding those notices that do not
110 | pertain to any part of the Derivative Works, in at least one
111 | of the following places: within a NOTICE text file distributed
112 | as part of the Derivative Works; within the Source form or
113 | documentation, if provided along with the Derivative Works; or,
114 | within a display generated by the Derivative Works, if and
115 | wherever such third-party notices normally appear. The contents
116 | of the NOTICE file are for informational purposes only and
117 | do not modify the License. You may add Your own attribution
118 | notices within Derivative Works that You distribute, alongside
119 | or as an addendum to the NOTICE text from the Work, provided
120 | that such additional attribution notices cannot be construed
121 | as modifying the License.
122 |
123 | You may add Your own copyright statement to Your modifications and
124 | may provide additional or different license terms and conditions
125 | for use, reproduction, or distribution of Your modifications, or
126 | for any such Derivative Works as a whole, provided Your use,
127 | reproduction, and distribution of the Work otherwise complies with
128 | the conditions stated in this License.
129 |
130 | 5. Submission of Contributions. Unless You explicitly state otherwise,
131 | any Contribution intentionally submitted for inclusion in the Work
132 | by You to the Licensor shall be under the terms and conditions of
133 | this License, without any additional terms or conditions.
134 | Notwithstanding the above, nothing herein shall supersede or modify
135 | the terms of any separate license agreement you may have executed
136 | with Licensor regarding such Contributions.
137 |
138 | 6. Trademarks. This License does not grant permission to use the trade
139 | names, trademarks, service marks, or product names of the Licensor,
140 | except as required for reasonable and customary use in describing the
141 | origin of the Work and reproducing the content of the NOTICE file.
142 |
143 | 7. Disclaimer of Warranty. Unless required by applicable law or
144 | agreed to in writing, Licensor provides the Work (and each
145 | Contributor provides its Contributions) on an "AS IS" BASIS,
146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 | implied, including, without limitation, any warranties or conditions
148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 | PARTICULAR PURPOSE. You are solely responsible for determining the
150 | appropriateness of using or redistributing the Work and assume any
151 | risks associated with Your exercise of permissions under this License.
152 |
153 | 8. Limitation of Liability. In no event and under no legal theory,
154 | whether in tort (including negligence), contract, or otherwise,
155 | unless required by applicable law (such as deliberate and grossly
156 | negligent acts) or agreed to in writing, shall any Contributor be
157 | liable to You for damages, including any direct, indirect, special,
158 | incidental, or consequential damages of any character arising as a
159 | result of this License or out of the use or inability to use the
160 | Work (including but not limited to damages for loss of goodwill,
161 | work stoppage, computer failure or malfunction, or any and all
162 | other commercial damages or losses), even if such Contributor
163 | has been advised of the possibility of such damages.
164 |
165 | 9. Accepting Warranty or Additional Liability. While redistributing
166 | the Work or Derivative Works thereof, You may choose to offer,
167 | and charge a fee for, acceptance of support, warranty, indemnity,
168 | or other liability obligations and/or rights consistent with this
169 | License. However, in accepting such obligations, You may act only
170 | on Your own behalf and on Your sole responsibility, not on behalf
171 | of any other Contributor, and only if You agree to indemnify,
172 | defend, and hold each Contributor harmless for any liability
173 | incurred by, or claims asserted against, such Contributor by reason
174 | of your accepting any such warranty or additional liability.
175 |
176 | END OF TERMS AND CONDITIONS
177 |
178 | APPENDIX: How to apply the Apache License to your work.
179 |
180 | To apply the Apache License to your work, attach the following
181 | boilerplate notice, with the fields enclosed by brackets "[]"
182 | replaced with your own identifying information. (Don't include
183 | the brackets!) The text should be enclosed in the appropriate
184 | comment syntax for the file format. We also recommend that a
185 | file or class name and description of purpose be included on the
186 | same "printed page" as the copyright notice for easier
187 | identification within third-party archives.
188 |
189 | Copyright [yyyy] [name of copyright owner]
190 |
191 | Licensed under the Apache License, Version 2.0 (the "License");
192 | you may not use this file except in compliance with the License.
193 | You may obtain a copy of the License at
194 |
195 | http://www.apache.org/licenses/LICENSE-2.0
196 |
197 | Unless required by applicable law or agreed to in writing, software
198 | distributed under the License is distributed on an "AS IS" BASIS,
199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 | See the License for the specific language governing permissions and
201 | limitations under the License.
202 |
--------------------------------------------------------------------------------
/MANIFEST.in:
--------------------------------------------------------------------------------
1 | include *.txt
2 | include *.md
3 | include LICENSE
4 | include MANIFEST.in
5 | include mopiqtt/ext.conf
6 | include tox.ini
7 | recursive-include tests *.py
8 |
--------------------------------------------------------------------------------
/NodeRed examples/README.md:
--------------------------------------------------------------------------------
1 |
2 | # Examples of use Mopiqtt in Node Red
3 | This package is mainly useful to Node Red users, who can embed in their flows a full control over Mopidy by simple mqtt-in or mqtt-out nodes. Of course, it can be used by any other MQTT client too.
4 |
5 | Few example nodes in Node-Red (self explaining):
6 |
7 |
8 |
9 |
10 |
11 | 
12 |
13 | A dashboard example:
14 |
15 |
16 |
17 |
--------------------------------------------------------------------------------
/NodeRed examples/images/dashboard2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/fmarzocca/Mopiqtt/dc96fdf50e5e015ffe6d5bd38def809fec0fa517/NodeRed examples/images/dashboard2.png
--------------------------------------------------------------------------------
/NodeRed examples/images/dashboard3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/fmarzocca/Mopiqtt/dc96fdf50e5e015ffe6d5bd38def809fec0fa517/NodeRed examples/images/dashboard3.png
--------------------------------------------------------------------------------
/NodeRed examples/images/few_nodes.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/fmarzocca/Mopiqtt/dc96fdf50e5e015ffe6d5bd38def809fec0fa517/NodeRed examples/images/few_nodes.png
--------------------------------------------------------------------------------
/NodeRed examples/images/playback.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/fmarzocca/Mopiqtt/dc96fdf50e5e015ffe6d5bd38def809fec0fa517/NodeRed examples/images/playback.png
--------------------------------------------------------------------------------
/NodeRed examples/images/playlists.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/fmarzocca/Mopiqtt/dc96fdf50e5e015ffe6d5bd38def809fec0fa517/NodeRed examples/images/playlists.png
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | Based on [mopidy-mqtt](https://github.com/odiroot/mopidy-mqtt)
2 |
3 | # Mopiqtt
4 | MQTT interface for Mopidy music server. Allows easy integration with Node Red or any MQTT client.
5 | This package is mainly useful to Node Red users, who can embed in their flows a full control over Mopidy by simple mqtt-in or mqtt-out nodes. See [Node Red examples](https://github.com/fmarzocca/Mopiqtt/tree/Development/NodeRed%20examples). Of course, it can be used by any other MQTT client too.
6 |
7 |
8 | # Installation
9 |
10 | Using pip:
11 | ```
12 | [sudo] python3 -m pip install Mopiqtt
13 | ```
14 | (If you are running Mopidy as a service, use `sudo`)
15 |
16 | # Configuration
17 |
18 | Add the following section to your mopidy's configuration file: `/etc/mopidy/mopidy.conf`
19 |
20 |
21 | ```
22 | [mopiqtt]
23 | host =
24 | port = 1883
25 | topic = mopidy
26 | username =
27 | password =
28 | ```
29 |
30 | *Note*: Remember to also supply `username` and `password` options if your
31 | MQTT broker requires authentication. If not, just leave blank the two values.
32 |
33 | *Note*: Restart Mopidy with `sudo service mopidy restart`
34 |
35 | To check Mopidy log run `sudo tail -f /var/log/mopidy/mopidy.log`
36 |
37 | # Features
38 |
39 | * Sends information about Mopidy state on any change
40 | - Playback status
41 | - Volume
42 | - Track description
43 | - Playlists list
44 | - Artwork
45 | - Track index
46 | * Reacts to control commands
47 | - Playback control
48 | - Tracklist control
49 | - Volume control
50 | - Load & play a playlist (straight or shuffle)
51 | - Request playlists list
52 | - Refresh playlists
53 | - Get tracklist
54 | - Search for artist/album/track name
55 |
56 |
57 | # MQTT protocol
58 |
59 | ## Topics
60 |
61 | Default top level topic: `mopidy`.
62 |
63 | Control topic: `mopidy/cmnd`.
64 |
65 | Information topic `mopidy/stat`.
66 |
67 | ## Messages to subscribe to (mopidy/stat/``)
68 |
69 | | | Subtopic | Values |
70 | |:-------------:|:---------:|:-----------------------------------------:|
71 | | Playback State| `/plstate` | `paused` / `stop` / `playing` |
72 | | Volume | `/vol` | `` |
73 | | Current track | `/trk` | ` - - ` or ` ` |
74 | | List of playlists | `/plists` | `` |
75 | | Track Artwork (*)| `/artw` | `` |
76 | | Track uri (*)| `/trk_uri` | `