Volumio plugins source code for Volumio 3
Volumio plugins source code for Volumio 3
You want to write a plugin to extend Volumio, or before sending a Pull Request, please have a look here
When usIng the Spotify app I get an issue where it stops playing after a few seconds fairly often, I press play and it stops again over and over. Sometimes was able to get it to start and play but keep running into this issue.
Seems like the issue could be steamed from another song being in the queue from another device. My roommate uses it as well.
Sometimes restarting the device gets it rolling sometimes not. It seems like its only an issue when using spotify app as I can tell. Sometimes running a song in a different app and running in Spotify corrects it as well.
Could you please add to spotify plugin's package.json (after)
"architectures": [
"armhf",
the following 2 lines
"amd64",
"i386"
Thanks
Volumio v3.233
Volumio Spotify Connect2 plugin v.3.0.7
Settings > General Playback Options > Volume Options > Max Volume Level > set to N > Save
Playback via Spotify Connect, and raise volume on connected device > Possible to raise volume above N (observable via Volumio web UI)
Potential mild heart-attacks when you connect a device that was set at a high volume appropriate for it, but not for your Volumio speaker set up ;)
After first connect from spotify the volume is always low and after every song it changes back down. But I need the spotify volume to be as high as possible, because the hifibirry amp is regulating the volume.
Can I somehow tell the spotify plugin to have and keep an initial volume?
hello. i have modify a script fot apple a1156 alternative to modifice up and down to set a volume.
all works perfectly but i want edit a menu button function to play a playlist called Rock
i read a api documentation but not work
in a documentation the command to play a playlist are:
volumio.local/api/v1/commands/?cmd=playplaylist&name=Rock
i edit a file lirirc:
`
begin
prog = irexec
button = KEY_MENU
config = /usr/local/bin/volumio playplaylist&name=Rock
end
`
but not work
i try to edit:
begin
prog = irexec
button = KEY_MENU
config = /usr/local/bin/volumio play playlist name=Rock
end
i unlucky
@volumio The repository does not appear to be searchable via the GitHub search function ("Search or jump to..."). The search result is always 0, no matter which search term you enter. Is this by intent?
When you disconnect Spotify Connect, the sound is played elsewhere, but in volumio it still looks as if it is still connected. Player controls in this state still work, so you can play/pause, skip etc. inside volumio and it affects the playing on the other device.
There is no way to continue playing in volumio, except using the spotify app to establish a new connection
It seems like the current LMS plugin does not properly download the .deb file from slimdevices.com. Arch is armv7l. String appending seems to go wrong.
Sometimes when you select a track, sometime another track is played. Sometimes there's a weird jumping where some other track plays for a second, then another track again a second and so on
So UI displays it like it is playing still, and time is ticking over total duration.
Volumio installed in a raspberry pi with a hifiberry DAC.
Spotify plugin version 3.0.9.
When connecting from desktop Spotify client, connection fails and the Volumio log shows the following:
[Vollibrespot] : Connecting to AP "ap-gew4.spotify.com:443"
[Vollibrespot] : Authenticated as "csaavedra" !
[Vollibrespot] : Using alsa sink
[Vollibrespot] : Metadata pipe established
[Vollibrespot] : Event: Volume { volume_to_mixer: 65535 }
[Vollibrespot] : Country: "FI"
[SpotifyConnect] Volume Spotify: 100 Volumio: 100
[Vollibrespot] : Fetching autoplay context uri
[Vollibrespot] : Event: SessionActive { became_active_at: 1688583959054 }
[Vollibrespot] : SessionActive!
[Vollibrespot] : Event: PlaybackStarted { track_id: SpotifyId { id: 277999119335806011727077590465924168756, audio_type: Track } }
[Vollibrespot] : Event: PlaybackLoading { track_id: SpotifyId { id: 277999119335806011727077590465924168756, audio_type: Track } }
[SpotifyConnect] A connect session has begun
[SpotifyConnect] Device palyback is active!
[SpotifyConnect] Device palyback is loading
[Vollibrespot] : Autoplay uri resolved to <"spotify:station:playlist:1H0ha8lbgTDJbvDbHbdbJp">
[Vollibrespot] : Resolving uri "spotify:station:playlist:1H0ha8lbgTDJbvDbHbdbJp"
[Vollibrespot] : error 403 for uri hm://keymaster/token/authenticated?client_id=4ced2e7c73484127be5d36015752eb43&scope=streaming,user-read-playback-state,user-modify-playback-state,user-read-currently-playing,user-read-private
[Vollibrespot] : Error: MercuryError
thread 'main' panicked at 'cannot poll Map twice', /build/cache/registry/src/github.com-1ecc6299db9ec823/futures-0.1.31/src/future/map.rs:35:29
stack backtrace:
0: 0x9d8444 - std::backtrace_rs::backtrace::libunwind::trace::h40a4eff66330a36d
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
1: 0x9d8444 - std::backtrace_rs::backtrace::trace_unsynchronized::hbce01963451b0cd5
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
2: 0x9d8444 - std::sys_common::backtrace::_print_fmt::h95da650d09c7e00b
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:66:5
3: 0x9d8444 - ::fmt::h33b23b1d14f668ff
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:45:22
4: 0xa010dc - core::fmt::write::h6320fb0e6ac90e58
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/fmt/mod.rs:1190:17
5: 0x9d04c4 - std::io::Write::write_fmt::h33b25d4810ca481f
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/io/mod.rs:1657:15
6: 0x9daef4 - std::sys_common::backtrace::_print::h7e61c5be69c715ef
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:48:5
7: 0x9daef4 - std::sys_common::backtrace::print::h3cee176d7c8dab8b
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:35:9
8: 0x9daef4 - std::panicking::default_hook::{{closure}}::h2d0211dd2e97dc43
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:295:22
9: 0x9dab14 - std::panicking::default_hook::hcbdb3b7c40dca30c
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:314:9
10: 0x9db694 - std::panicking::rust_panic_with_hook::h4ce49e7a343dc12b
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:698:17
11: 0x9db304 - std::panicking::begin_panic_handler::{{closure}}::h4961100fae529fe9
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:588:13
12: 0x9d89c4 - std::sys_common::backtrace::__rust_end_short_backtrace::hf2e68e62c7a80f1f
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:138:18
13: 0x9db098 - rust_begin_unwind
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:584:5
14: 0x4be6f4 - core::panicking::panic_fmt::h84c42730e4a50809
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:143:14
15: 0x9fdf88 - core::panicking::panic_display::he50fbe261a13d083
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:73:5
16: 0x9fdf38 - core::panicking::panic_str::h6e4cfb6a94cf14e8
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:56:5
17: 0x4be57c - core::option::expect_failed::h5f2b901fbc810215
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/option.rs:1852:5
18: 0x720e18 - as futures::future::Future>::poll::h794cc547cc6bc145
19: 0x5a9d78 - ::poll::h2a7bff75029d3b82
20: 0x4e62ec - ::poll::h5fd9e3bcdeb25ad9
21: 0x5033dc - futures::task_impl::std::set::h8f754e80bd562d0a
22: 0x51a42c - std::thread::local::LocalKey::with::h71cfa1e374fcc0a0
23: 0x4ff99c - tokio_current_thread::Entered
::block_on::hde55cdf28eabe6d5
24: 0x51a6f0 - std::thread::local::LocalKey::with::hedba3cfe41326627
25: 0x502880 - tokio::runtime::current_thread::runtime::Runtime::block_on::h60d5b89560100ed8
26: 0x4e8eb0 - vollibrespot::main::h35555355ed947dd1
27: 0x508c50 - std::sys_common::backtrace::__rust_begin_short_backtrace::hef626a10d324c12a
28: 0x52e52c - std::rt::lang_start::{{closure}}::hd80188e4bcac5072
29: 0x9d7b28 - core::ops::function::impls:: for &F>::call_once::h0567da839a080232
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/ops/function.rs:259:13
30: 0x9d7b28 - std::panicking::try::do_call::hdf194554a41aa3cc
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:492:40
31: 0x9d7b28 - std::panicking::try::hbf4b7be9f9ffa5f8
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:456:19
32: 0x9d7b28 - std::panic::catch_unwind::h45f392a39f2fe48c
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panic.rs:137:14
33: 0x9d7b28 - std::rt::lang_start_internal::{{closure}}::hd772cb03c2060671
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/rt.rs:128:48
34: 0x9d7b28 - std::panicking::try::do_call::hd126f715b519ff2a
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:492:40
35: 0x9d7b28 - std::panicking::try::h80b7148ce71893dc
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:456:19
36: 0x9d7b28 - std::panic::catch_unwind::h1562f0b2e8a9cb0d
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panic.rs:137:14
37: 0x9d7b28 - std::rt::lang_start_internal::h3daa586a0b835507
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/rt.rs:128:20
38: 0x4eae80 - main
39: 0x76c52718 - __libc_start_main
[Vollibrespot] : EventSender disconnected
[SpotifyConnect] PlaybackInactive
have tried adding my own links in my web radios. seems to happen for all stations when using "Web Radio" Does not happen when playing music from other sources such as Radio Paradise.
It looks like the visibility of the delay units for the "StopMustic" event is incorrectly bound to the "ShutDown" event.
Hi,
Thank you for your amazing project.
I tryed quick fix install.sh.
install.sh.patch
Hello,
using the gpio-buttons plugin without a hardware debouncing of the input pins, at least in my case, often leads to bouncing effects (e.g. pressing play/stop one time leads to a stop and direct restart). While this is no problem for a shutdown button or maybe even a volume +/- button, it can be quite annoying on a play/stop button.
As far as I found out, the used onoff library for the Gpio reading already provides a software debounce, which works flawlessly for me.
Wouldn't it be meaningful to generally activate this debouncing in gpio-buttons or maybe make it configurable?
I just had to change this line of code in index.js of gpio-buttons:
currently:
var j = new Gpio(pin,'in','both');
modified:
var j = new Gpio(pin,'in','both', {debounceTimeout: 50});
I chose 50ms as debounce value, since I don't think a quicker reaction is necessary, but probably this value could also be reduced to 10-20ms, if desired.
Hi! When playing a playlist which contains unavailable tracks, upon trying to reproduce one of such tracks, the playback gets stuck and everything goes back to normal if the track is skipped.
@patrickkfkan
Hi Patrick,
I've noticed (after merging the bandcamp discover plugin) issues with the manifest UI when using the search function.
Can you look into this?
In the spotify app, the connection is still active and you can start playback, but playback of other source does not end, spotify sound is not played on volumio
When you are playing spotifiy tracks selected in volumio and you hit pause in the spotify app, volumio instantly continues playing with another track as if you had hit next
Raspberry PI 3B+
Volumio: 3.396
Plugin: FusionDSP
Full volumio log: http://logs.volumio.org/volumio/QBBdVzQ.html
After playing several tracks music stoped and I get error:
Jan 11 10:08:58 volumiopi3 systemd[1]: fusiondsp.service: Main process exited, code=exited, status=1/FAILURE Jan 11 10:08:58 volumiopi3 systemd[1]: fusiondsp.service: Failed with result 'exit-code'. Jan 11 10:09:00 volumiopi3 systemd[1]: fusiondsp.service: Service RestartSec=2s expired, scheduling restart. Jan 11 10:09:00 volumiopi3 systemd[1]: fusiondsp.service: Scheduled restart job, restart counter is at 1. Jan 11 10:09:00 volumiopi3 systemd[1]: Stopped FusionDsp Daemon. Jan 11 10:09:00 volumiopi3 systemd[1]: Started FusionDsp Daemon. Jan 11 10:09:01 volumiopi3 volumio[10347]: Traceback (most recent call last): Jan 11 10:09:01 volumiopi3 volumio[10347]: File "/data/plugins/audio_interface/fusiondsp/cgui/main.py", line 5, in Jan 11 10:09:01 volumiopi3 volumio[10347]: from camilladsp_plot.validate_config import CamillaValidator Jan 11 10:09:01 volumiopi3 volumio[10347]: File "/usr/local/lib/python3.7/dist-packages/camilladsp_plot/validate_config.py", line 4, in Jan 11 10:09:01 volumiopi3 volumio[10347]: from jsonschema import Draft7Validator, validators Jan 11 10:09:01 volumiopi3 volumio[10347]: File "/usr/local/lib/python3.7/dist-packages/jsonschema/__init__.py", line 13, in Jan 11 10:09:01 volumiopi3 volumio[10347]: from jsonschema._format import FormatChecker Jan 11 10:09:01 volumiopi3 volumio[10347]: File "/usr/local/lib/python3.7/dist-packages/jsonschema/_format.py", line 11, in Jan 11 10:09:01 volumiopi3 volumio[10347]: from jsonschema.exceptions import FormatError Jan 11 10:09:01 volumiopi3 volumio[10347]: File "/usr/local/lib/python3.7/dist-packages/jsonschema/exceptions.py", line 14, in Jan 11 10:09:01 volumiopi3 volumio[10347]: from jsonschema import _utils Jan 11 10:09:01 volumiopi3 volumio[10347]: File "/usr/local/lib/python3.7/dist-packages/jsonschema/_utils.py", line 12, in Jan 11 10:09:01 volumiopi3 volumio[10347]: import importlib_resources as resources # type: ignore Jan 11 10:09:01 volumiopi3 volumio[10347]: ValueError: source code string cannot contain null bytes Jan 11 10:09:01 volumiopi3 volumio[4422]: error: updateQueue error: null
For quite some time (years) I have had random instances of my various Volumio systems failing to boot.
These instances are unpredictable and can not be caused on demand.
In all instances, it involves a Raspberry PI 3B with official 7Inch display (I have two such setups, both have same problem randomly).
It has occured for multiple versions of Volumio and the TouchScreen plugin.
Generally what I have been able to find over the years, is that the Chromium Browser (displayed on the 7Inch display) is writing Cache data to the SD card, which ultimately results in the card being corrupted at some point, which only shows up folllowing a shutdown or reboot request (manually invoked from either Web link or touch screen).
I also have a PI ZeroW with no display, only remote web control, this never has a problem.
When a PI 3B board starts up, the corruption can cause various failures, again unpredictable, but could be any of the following:
1: Total failure to boot and board is unreachable, LCD screen displays a boot failure, or nothing.
2: Board boots, and can be accessed via web link, but touch screen is blank, though touch screen and backlight still react, just no browser display, appears to be caused by corruption of the SD card browser cache data preventing Chromium from completing startup. But media can still be played via the web link.
3: Board boots and can control from the touch screen, but can not access via web link, as target does not respond to a ping, unclear if this is the board failing to respond, or something blocking ping request and response via network router.
I am certain that there has been no power failure at any time, as I use the target by placing media tracks in the play queue, then play.
I do not empty the queue until I want to play something else, at which time I delete the queue and add the new items.
I have the queue to be NON persistent, this causes the queue to be empty following power up, so if there were a power fail between the last time I used the device, and trying to use it again after a period of days, the queue will still contain what was last played, it would be empty if a reboot had occured at any time, I have never seen the queue empty other than when I have requested a shutdown or reboot.
As a result of my observations on multiple devices, I must assume that there is a problem with Chromium corrupting the SD card while running in Kiosk mode for an extended period of time.
Not sure what fixes may be possible, as Chromium probably does not have any configurable options to prevent page cache being written to SD card, or be placed in the limited RAM, so that it can be purged on startup.
It gives me an alert that the song was added successfully, but the song doesn't get added to the playlist.
If I need to give more info or something, just tell me. I have never written a bug report before in my life.
plugin works
would like to have output sent to fifo file for snapcast like this below instead of also
thks
audio_output {
type "fifo"
enabled "yes"
name "multiroom"
path "/tmp/snapfifo"
format "44100:16:2"
}
Hi,
I have a volumio with a I2C display which shows the title and artist information. Unfortunately after switching from web radio to Spotify as music source the display still shows the last web radio information.
For the display I use lcdproc, LCDd and mpdlcd.
Because the playback of a web radio displays all the necessary information and the playback via the Spotify plugin does not, my guess is that the problem lies in the plugin. Does anyone maybe have an idea or suggestion what I can try?
For plugins that utilize compiled native node modules, the Node version should be correspondingly indicated.
The current notation will fail during Volumio/Node major version upgrades.
volumio-plugins-sources/gpio-buttons/package.json
Lines 31 to 34 in 1d59fa8
i.e
"node": "^14"Device: Integro
System-Version: 3.6.29
Plugin: Spotify 4.04
Hi,
When I add a title to the queue, this title does not appear in the queue.
I think, that's a generally problem, because there are several reports in the volumio community forum, e. g. https://community.volumio.com/t/new-2023-spotify-plugin/63381/14?u=supric
Kind regards,
Martin
Artist/Title/Albumart are not shown in the UI. When the next song plays, everything is ok.
When configuring this plugin, the title is, "Spotify Account". Since the settings really have nothing to do with the user's account, the title should probably be something like, "General Settings".
Currently the SSL certificate for repo.volumio.org is expired. Since the install.sh of the Spotify plugin runs without set -e the UI returns a successful installation, while in fact the wget and subsequent unpacking fails.
See volumio/volumio-plugins#639
Just looked at the code, which seems to be nearly the same...
there is a config file problem where normalisation pregain and external volume the yaml config file for the go-librespot daemon don’t get properly replaced and their placeholders stay there, causing the librespot daemon to be unable to start due the messed up config.yml, i fixed this by removing the placeholders in the yml tmp file in the plugins folder and replacing them with static values but that’s not really something i should need to do
Newest Volumio, newest iOS app.
When I select volumio as device, it seems to connect, but it just keeps cycling through the playlist.
No problems playing on the phone.
I have tried a complete re-install, including downloading the latest version of the Volumio image.
Hi,
CamillaDSP has new version.
It gives some functionalities than can be used like SetFaderExternalVolume command.
We should upgrade FusionDSP to use this version.
It adds it to Favourites, not Favourite Radios, which is correct, it's just the text in the popup menu.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.