Slim::Schema::Storage::throw_exception (121) Backtrace:įrame 0: Slim::Utils::Log::logBacktrace (/usr/share/perl5/Slim/Schema/Storage.pm line 121)įrame 1: Slim::Schema::Storage::throw_exception (/usr/share/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 1007)įrame 2: DBIx::Class::Storage::DBI::_ANON_ (/usr/share/squeezeboxserver/lib/DBIx/Migration.pm line 113)įrame 3: DBIx::Migration::migrate (/usr/share/perl5/Slim/Schema.pm line 480)įrame 4: Slim::Schema::migrateDB (/usr/share/perl5/Slim/Schema.pm line 167)įrame 5: Slim::Schema::init (/usr/sbin/squeezeboxserver line 555)įrame 6: main::init (/usr/sbin/squeezeboxserver line 678)įrame 7: main::main (/usr/sbin/squeezeboxserver line 1224) Slim::Schema::Storage::throw_exception (121) Error: DBI Exception: DBD::SQLite::db do failed: duplicate column name: extid Slim::Schema::forceCommit (2177) Warning: Trying to commit transactions before DB is initialized! In this case you add the child switch to Google Home instead of the player itself.Code: main::init (390) Starting Logitech Media Server (v8.2.0, 1627922070, Tue Aug 3 11:39:20 CEST 2021) perl 5.028001 - arm-linux-gnueabihf-thread-multi-64int The only reason you might need this is if you want to add the player to Google Home and you want it just to be a switch instead of how Google Home normally sees a music player which is as a light (I guess because the music player properties include 'level' so Google thinks it's a dimmable light). The other switch a player can create is basically a copy of the player's on/off function. switch off your morning alarm clock when you're on holiday) then it can create an All Alarms switch to allow you to do that. If you want to be able to control the player alarms with automations (e.g. Squeezebox Player Child Switch Device - Each player can create up to two of these (you configure this when setting the players up in the app). There is only network traffic if something changes (e.g. You don't need to disable or switch off these devices to reduce polling any more. You can fully control the player (including switching it on/off) using this device. Squeezebox Player Device - The app creates one of these for each player. Then after starting LMS again you can switch the Squeezebox Server device back on so that it reconnects. But, if you are shutting down LMS deliberately, then you can switch this device off to stop it trying to reconnect whilst LMS is shutdown. If you're just using LMS normally then you should be able to pretty much ignore this device. you update the plugins on LMS and it restarts) then the Squeezebox Server device will automatically try to reconnect, if that fails it will carry on trying to reconnect every minute until it succeeds. There is no longer any polling in the integration. It maintains a single lightweight connection which is used to send player commands and subscribe to status change updates from LMS. It is responsible for connecting to the LMS server. Squeezebox Server Device - The app creates exactly one of these. The integration has an app and three device types: I have tested it but please let me know if there are any bugs and I'll stomp them as quick as I can. For documentation on the things you can do via the CLI interface check out the help on your Squeezebox Server web app (help -> Technical Information -> The Logitech Media Server Command Line Interface) However, you can always re- Initialize if that happens. Be wary of sending messages that can change the subscription, it will probably stop the integration from getting the updates it needs. It's an advanced use case but, if you want to, you can use these to force a reconnect or to send your own CLI commands to the service via this device. I have exposed the Initialize and Send Msg commands on the device. The Squeezebox Server device should automatically reconnect if there are issues with communication to the service. This should mean that dashboard support for things like album art works properly (I've confirmed this works with SharpTools.io) The players now report the track information using the correct trackData JSON attribute. This should have a far lower requirement on hub resources whilst at the same time giving immediate updates on player status changes. There is a new device (Squeezebox Server) which is managed by the app and maintains a Telnet connection to the server over which it can send commands but also receive updates on changes. The main advantage of this is no more polling. I have rewritten the player communication to use the the CLI interface (over Telnet). I am happy to announce version 2.0 of Squeezebox Connect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |