garybixler

@koln1011 At the moment I am using the audio player as the paging source in my whole house russound audio system. However if I move later this year I will no longer have that option. As an alternative I have been experimenting with using wifi streaming to various wifi audio receivers. I could be wrong but I have not found anyway to use Alexa speakers for this purpose. You could use bluetooth to pair with one Alexa speaker but that my be the limit. What I am experimenting with is the wiim pro that will accept either audio input jacks or bluetooth pairing from the audio player. Also there is a wiim clock that receives the stream and also acts as an Alexa device. I am hoping that they will have more products available soon. The best thing in my opinion about using wifi streaming is that there would be no Alex cloud to deal with.

@bmercier I upgraded to version 5.8.3 and now my routines are working. Thanks so much.

I just noticed the routines that controls my vertical blinds has stopped working today. The trigger device, created in the portal from a variable functions properly by closing and opening in the Alexa app. It does not however trigger the routine to run. The routine functions properly when played from the Alexa app. Another call to Amazon. This keeps repeating about every 8 months. Maybe it's the Amazon servers that serve my area. Fortunately I'm using the audio player that replaced all the voice routines.

I have had the Alexa routines fail 3 time over the last two years. It always required a call to Alexa Amazon to fix the problem. If you can see the trigger to the routine change states in the Alexa app and the routine doesn't run then it is most likely an Alexa problem. Also there is a 30 second wait time when triggers change states to prevent flip flopping. Thankfully with the addition of the Audio player plugin I have been able to drop all the Alexa routines that provide a speech response to an event. Much better solution.

I guess I will be the first to ask. Any chance that there will be a spotify plugin? Thanks

@wrj0 I am experiencing the same issue with mp3 files playing on BT.

Just reloaded the deleted _t file and now both can play it. So I guess i just need to delete and reload the files. Finding that if I play a file on the AP that will play it now allows the other to also play the file.

Just found out that is a file is deleted from one player it still shows in the other player until it is deleted from there also.

I did make sure they had the same path if that is the same thing. The one file that is not an _t can be played on either AP. However it isn't important that I can play the _t files on both. Not sure what will happen if I add another TTS file from an outside source. Will give that a try later, Thanks

@Michel KohanimThanks, the invalid output device is no longer an issue.

Hi, I have two APs running and on the second installed AP i am still not able to play the _t files on BT or speaker jacks. The first installed AP works with no issue. The log shows trying to play an _t file and playing a non _t file. Other than that they seem to be working without any issues. Thanks Temp Log File.txt

I have the same setup but haven't needed to reboot after a power outage. I am using a usb to serial adapter that is powered by the eisy's usb port. I think I purchased it on the UD store awhile ago.

I have been experiencing a problem with AP after switching back from BT to output jacks. The audio_t.mps wont play because of an invalid output device. The non _t files and streams play OK. It may have something to do with BT not working after being idle for a period of time. The BT device appears to be paired but wont work without repairing. Thee BT devices share the same issue. The only solution I have found to fix the problem is to reboot the eisy. Log of trying to play an _t file on speaker jack included. Thanks Gary Temp Log File.txt

Just thought I would pass on this info if more that one audio player is running. At this point they don't seem to be able to run independently. My goal would be to run one as a pager using speaker jacks that is connected to a paging system and the other for streaming via BT. I included the log of one that shows repeating commands when both are running. Both show the same repeating. Also if two APs could be run simultaneously I would like to thankfully request that the output type be saved. Thoughts apricated. Thanks Gary Temp Log File.txt

Thanks Michel. You were right about not actually being paired. After several tries I finally go it to pair correctly. All works great now.

I upgraded to version 1.3.1 after doing a package update but am still having a problem with using BT. BT device is paired and when I select BT and try to stream an mp3 file it shows playing but just hangs. A restart is needed to restore functionally. No problem using speaker jacks. Also update BT plugin. I think BT had initially worked under version 1.1.0. Log included. Thanks Temp Log File.txt

@TUhl01 Try this. https://192.168.xx.xx:8443/web/sysconfig.txt

@TUhl01 The audioplayer custom configurations will be found in the Pg3 plugin. I also am having BT problems but the speaker jack output works fine.

@chris.com Glad to help.

Go to pg3 then click on audioplayer. Then click on Configuration. Scroll down until you come to custom configuration. At that point you will click on add custom parameter then fill in key and value. Save. The play list will be shown on the audioplayer admin console page. There are sample files on the play list.

You can have it make speech announcements by configuring it on the audio player config page. Example: Key Entry: tts_en_en_anyname Value: Text you would like it to say like Hi there,how are you? Will need to restart the audio player and restart Admin console after configuration. It should then show up on the play list. I am having a little difficulty using Bluetooth but it may be related to my BT device

I just found this station today. Enter in station value Radio===http://stream.radioparadise.com/global-128 Radio it the name I gave it.

Log for 1.0.5. 2024-03-15 20:31:24,121 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-03-15 20:31:24,121 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-03-15 20:31:24,122 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '2'}} from Polyglot 2024-03-15 20:31:24,122 Command udi_interface INFO audio-player:processCommand: Got command: {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '2'}} 2024-03-15 20:31:24,122 Command udi_interface INFO audio-player:processCommand: Playing #2:/storage/sounds//Medication.mp3 2024-03-15 20:31:24,122 Thread-4 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 1 to Polyglot 2024-03-15 20:31:24,122 Thread-4 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2024-03-15 20:31:24,123 Thread-4 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 2 to Polyglot 2024-03-15 20:31:24,123 Thread-4 udi_interface.node DEBUG node:reportDriver: Updating value to 2 2024-03-15 20:31:24,123 Thread-4 udi_interface ERROR udi_interface:write: Exception in thread 2024-03-15 20:31:24,123 Thread-4 udi_interface ERROR udi_interface:write: Thread-4 2024-03-15 20:31:24,123 Thread-4 udi_interface ERROR udi_interface:write: : 2024-03-15 20:31:24,123 Thread-4 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2024-03-15 20:31:24,124 Thread-4 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2024-03-15 20:31:24,124 Thread-4 udi_interface ERROR udi_interface:write: self.run() 2024-03-15 20:31:24,124 Thread-4 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2024-03-15 20:31:24,125 Thread-4 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2024-03-15 20:31:24,125 Thread-4 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_18/audio-player.py", line 43, in audio_player_thread 2024-03-15 20:31:24,125 Thread-4 udi_interface ERROR udi_interface:write: pd = AudioSegment.from_file(AudioPlayerParams.mediaPath) 2024-03-15 20:31:24,125 Thread-4 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_18/.local/lib/python3.9/site-packages/pydub/audio_segment.py", line 651, in from_file 2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: file, close_file = _fd_or_path_or_tempfile(file, 'rb', tempfile=False) 2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_18/.local/lib/python3.9/site-packages/pydub/utils.py", line 60, in _fd_or_path_or_tempfile 2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: fd = open(fd, mode=mode) 2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: PermissionError 2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: : 2024-03-15 20:31:24,127 Thread-4 udi_interface ERROR udi_interface:write: [Errno 13] Permission denied: '/storage/sounds//Medication.mp3' 2024-03-15 20:31:24,131 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '1', 'uom': 25, 'text': None}]} 2024-03-15 20:31:24,131 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '2', 'uom': 25, 'text': None}]} 2024-03-15 20:31:24,162 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 1 UOM 25 2024-03-15 20:31:24,252 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 2 UOM 25

Log for version 1.3.0 2024-03-15 20:28:37,253 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-03-15 20:28:37,253 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-03-15 20:28:37,253 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '2'}} from Polyglot 2024-03-15 20:28:37,254 Command udi_interface INFO audio-player:processCommand: Got command: {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '2'}} 2024-03-15 20:28:37,254 Command udi_interface INFO audio-player:processCommand: Playing #2:/storage/sounds/Medication.mp3 2024-03-15 20:28:37,254 Command udi_interface.node DEBUG node:getDriver: 0:AudioPlayer ST - 0 :: getting dv ST 2024-03-15 20:28:37,255 Thread-21 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV3 to 100 to Polyglot 2024-03-15 20:28:37,255 Thread-21 udi_interface.node DEBUG node:reportDriver: Updating value to 100 2024-03-15 20:28:37,255 Thread-21 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 1 to Polyglot 2024-03-15 20:28:37,255 Thread-21 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2024-03-15 20:28:37,256 Thread-21 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 2 to Polyglot 2024-03-15 20:28:37,256 Thread-21 udi_interface.node DEBUG node:reportDriver: Updating value to 2 2024-03-15 20:28:37,256 Dummy-22 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 0 to Polyglot 2024-03-15 20:28:37,256 Dummy-22 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-03-15 20:28:37,257 Dummy-22 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 0 to Polyglot 2024-03-15 20:28:37,257 Dummy-22 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-03-15 20:28:37,259 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV3', 'value': '100', 'uom': 51, 'text': None}]} 2024-03-15 20:28:37,259 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '1', 'uom': 25, 'text': None}]} 2024-03-15 20:28:37,260 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '2', 'uom': 25, 'text': None}]} 2024-03-15 20:28:37,260 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '0', 'uom': 25, 'text': None}]} 2024-03-15 20:28:37,260 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '0', 'uom': 25, 'text': None}]} 2024-03-15 20:28:37,291 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV3 to 100 UOM 51 2024-03-15 20:28:37,378 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 1 UOM 25 2024-03-15 20:28:37,421 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 2 UOM 25 2024-03-15 20:28:37,478 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 0 UOM 25 2024-03-15 20:28:37,520 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 0 UOM 25

Unfortunately what ever I did I can no longer play the files on either player.