garybixler

Just update to udx version 3.5.6_6 and installed audio player 1.1.0. The problem that I am having is that my speech files are being cut off before completion. Some in 1 second and others in about 3 seconds. Same files that i used in version 1.0.5 with no issue. I am using the speaker jack output. This is the log of one mp3 file played. Thanks Gary 2024-03-12 17:17:53,225 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-03-12 17:17:53,226 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-03-12 17:17:53,226 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '1'}} from Polyglot 2024-03-12 17:17:53,226 Command udi_interface INFO audio-player:processCommand: Got command: {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '1'}} 2024-03-12 17:17:53,226 Command udi_interface INFO audio-player:processCommand: Playing #1:/storage/sounds/Medication.mp3 2024-03-12 17:17:53,226 Command udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 0 to Polyglot 2024-03-12 17:17:53,226 Command udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-03-12 17:17:53,226 Command udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 0 to Polyglot 2024-03-12 17:17:53,226 Command udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-03-12 17:17:53,227 Command udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV3 to 100 to Polyglot 2024-03-12 17:17:53,227 Command udi_interface.node DEBUG node:reportDriver: Updating value to 100 2024-03-12 17:17:53,228 Thread-33 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 1 to Polyglot 2024-03-12 17:17:53,228 Thread-33 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2024-03-12 17:17:53,228 Thread-33 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 1 to Polyglot 2024-03-12 17:17:53,228 Thread-33 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2024-03-12 17:17:53,230 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '0', 'uom': 25, 'text': None}]} 2024-03-12 17:17:53,230 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '0', 'uom': 25, 'text': None}]} 2024-03-12 17:17:53,230 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV3', 'value': '100', 'uom': 51, 'text': None}]} 2024-03-12 17:17:53,231 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '1', 'uom': 25, 'text': None}]} 2024-03-12 17:17:53,231 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '1', 'uom': 25, 'text': None}]} 2024-03-12 17:17:53,263 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 0 UOM 25 2024-03-12 17:17:53,350 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 0 UOM 25 2024-03-12 17:17:53,393 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV3 to 100 UOM 51 2024-03-12 17:17:53,449 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 1 UOM 25 2024-03-12 17:17:53,490 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 1 UOM 25 2024-03-12 17:17:53,967 Dummy-34 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 0 to Polyglot 2024-03-12 17:17:53,968 Dummy-34 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-03-12 17:17:53,968 Dummy-34 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 0 to Polyglot 2024-03-12 17:17:53,968 Dummy-34 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-03-12 17:17:53,970 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '0', 'uom': 25, 'text': None}]} 2024-03-12 17:17:53,970 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '0', 'uom': 25, 'text': None}]} 2024-03-12 17:17:54,002 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 0 UOM 25 2024-03-12 17:17:54,090 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 0 UOM 25 2024-03-12 17:18:07,928 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-03-12 17:18:07,928 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-03-12 17:18:07,928 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-03-12 17:18:07,929 Thread-35 udi_interface INFO audio-player:poll: short poll

Was just wondering if keypad presses (+, -, forward, reverse) should be seen by the NS? Example, pressing the forward key on the keypad can be used to forward the source to the next song. Thanks Gary

I updated to ver. 3.6.12 and am unable to get past the following errors. Reinstalled but no change. Added the portal api key but the NS will not connect. Also it doesn't show the additional config info like pushover service nodes. Thanks I'm on PG3x 3.2.18 024-02-10 23:04:01,095 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026038_4/notification-poly.py", line 17, in <module> polyglot = Interface([Controller]) File "/var/polyglot/pg3/ns/0021b9026038_4/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 253, in __init__ self._mqttc = mqtt.Client(self.id, True) File "/var/polyglot/pg3/ns/0021b9026038_4/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__ raise ValueError( ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details 2024-02-10 23:04:02,327 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2024-02-10 23:04:02,327 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2024-02-10 23:04:02,327 MainThread udi_interface INFO __init__:<module>: User=0021b9026038_4 2024-02-10 23:04:02,327 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026038_4 2024-02-10 23:04:02,328 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026038_4 2024-02-10 23:04:02,328 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6NjA6MzgiLCJwcm9maWxlTnVtIjo0LCJsb2dMZXZlbCI6IldBUk5JTkciLCJ0b2tlbiI6InVFMyg5OCY4RDhSaEwtSXQiLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xOCIsImlzeVZlcnNpb24iOiI1LjguMCIsImVkaXRpb24iOiJTdGFuZGFyZCJ9 2024-02-10 23:04:02,328 MainThread udi_interface INFO __init__:<module>: Loading interface module 2024-02-10 23:04:02,370 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2024-02-10 23:04:02,911 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2024-02-10 23:04:03,148 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2024-02-10 23:04:03,149 MainThread udi_interface INFO __init__:<module>: Loading node module 2024-02-10 23:04:03,149 MainThread udi_interface INFO __init__:<module>: Loading custom module 2024-02-10 23:04:03,149 MainThread udi_interface INFO __init__:<module>: Loading isy module 2024-02-10 23:04:03,149 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2024-02-10 23:04:03,149 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.6 Starting... 2024-02-10 23:04:03,214 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026038_4/notification-poly.py", line 17, in <module> polyglot = Interface([Controller]) File "/var/polyglot/pg3/ns/0021b9026038_4/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 253, in __init__ self._mqttc = mqtt.Client(self.id, True) File "/var/polyglot/pg3/ns/0021b9026038_4/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__ raise ValueError( ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details

@wrj0 Great News. Setting up the NVMe SSD was a success thanks to Michel's instructions on installing and configuring the SSD and your detailed instructions on permissions and mp3 file uploads. Just a little snag figuring out different paths but all went very well. Thanks again.

At the moment I don't see any setting capability to adjust the audio like balance, tone, volume, mono etc. At this time I will be using it just for voice announcements. Right now I will be connecting it to an audio mixer along with an ELK, Echo and phone system for paging into a russound system. Allows great flexibility. I do think that an audio combiner would work. Y-cable. I made my own that includes resistors that isolate the channels to prevent interference with one another. However my mp3 announcing files are mono anyway so either channel alone should work.

@wrj0 Looks like I wont get the SSD drive until Friday but I will let you know how I make out. In the mean time I will be creating mp3 files. Thanks

@wrj0Thanks, excellent information. Defiantly looks like a project I will be able to accomplish. Looking forward for the eisy to make announcements. Ordering the NVMe today. Again thanks for all the great detailed info.

@wrj0Thanks so much for all the info. i would have a problem with setting up the directory and permissions. Pretty clueless when it comes to linux commands. The file transfer looks pretty straight forward after the NVMe SSD storage is installed and permissions configured. Maybe I will need to wait until an integrated system is available for uploading mp3 files. Per Michel's info on the plugin, "For custom sounds, for now, you are in charge of creating a directory, uploading your music files, and giving read permission either to the plugin user or everyone." I am hoping "for now" means that there will be a system for loading the files forthcoming. Could you recommend the type of NVMe SSD that the eisy requires. I was looking at a 1tb 2280. I don't know if there are specific requirements for the eisy or not. Again thanks for your time and information.

@wrjo hi. I am lost as what I need to do in order to load mp3 files for the audio player. Could you provide some instructions on how this is done or are there instructions posted elsewhere. I would greatly apricate any info. Thanks Gary

All working now thanks Michel.

There seems to be something missing according to the log. Do I need to do a package upgrade? Thanks. 2024-01-19 17:39:58,567 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2024-01-19 17:39:58,567 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2024-01-19 17:39:58,568 MainThread udi_interface INFO __init__:<module>: User=0021b9026038_18 2024-01-19 17:39:58,568 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026038_18 2024-01-19 17:39:58,568 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026038_18 2024-01-19 17:39:58,568 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6NjA6MzgiLCJwcm9maWxlTnVtIjoxOCwibG9nTGV2ZWwiOiJJTkZPIiwidG9rZW4iOiJNJnYycmNlM3RXOXJjJShyIiwibXF0dEhvc3QiOiJsb2NhbGhvc3QiLCJtcXR0UG9ydCI6ODg4Mywic2VjdXJlIjoxLCJpc1BHM3giOnRydWUsInBnM1ZlcnNpb24iOiIzLjIuMTciLCJpc3lWZXJzaW9uIjoiNS44LjAiLCJlZGl0aW9uIjoiRnJlZSJ9 2024-01-19 17:39:58,568 MainThread udi_interface INFO __init__:<module>: Loading interface module 2024-01-19 17:39:58,620 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2024-01-19 17:39:59,140 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2024-01-19 17:39:59,379 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2024-01-19 17:39:59,380 MainThread udi_interface INFO __init__:<module>: Loading node module 2024-01-19 17:39:59,380 MainThread udi_interface INFO __init__:<module>: Loading custom module 2024-01-19 17:39:59,380 MainThread udi_interface INFO __init__:<module>: Loading isy module 2024-01-19 17:39:59,380 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2024-01-19 17:39:59,381 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.6 Starting... 2024-01-19 17:39:59,382 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026038_18/audio-player.py", line 18, in <module> import pyaudio ModuleNotFoundError: No module named 'pyaudio'

Thanks Michel. Just need to know how to set it up on the eisy. Thanks So much. Gary

Found sites where TTV can be created. Should they be in mp3 or wav format or does it matter? Thanks

Can an example of how to set this up be provided. Also is there any collection of audio files available. Really would like to replace ELK and Alexa as the voice source. Any such capability of text to voice? Thanks. Great addition to the eisy. Gary

@thruster999Alexa will fix the problem after they realize that it is their problem. Been down this road with Alexa 3 times now. The first time was like pulling teeth. The second time they used their screen share to the phone app so I could show them exactly what wasn't working. The last time however I basically told them they had a problem and corrected it within a day. I think they looked back on my previous tickets. They also had me recreate a non working routine just to satisfy their requirements.

@thruster999Did you check you Alexa app and verify that the variable device does actually turn on and off? If it does it is an Alexa account issue.

In my case only devices created from variables were the problem. On/Off contact type. Those devices were used to trigger routines. I could see that the devices were working correctly on the Alexa app but they were not triggering the routine. Something was broken between the triggers and routines at Alexa.

I have had my Alexa routines just stop working but not disabled sever times in the past two years for no reason. Always had to call and try to explain the problem. When finely seen that the problem was with Alexa a service ticket was opened and all my routines were working the next day. Never given an explanation.

I had IoX Launcher issues after up dating my PC to Win 11 from Win 10. My solution was to delete Java and download a new copy. Not sure if you had started from a new Win 11 pc or not.

@oberkcJust tried your config but still I am not getting the zwave device to control an insteon on/off module. If i look at the insteon device it does show that it is a responder to the zwave device but does not respond to the swave device. If I look at the zwave device I do not see that the membership includes being a controller. It was added as a controller and shows that by being printed in red. Does your zwave device show it being a controller in the membership? This is what shows on my zwave device. Just tried adding the zwave first but no difference. All I see is that the zwave does not get added as a controller just a responder to the scene. Event viewer response. Zwave event ignored doesn't look good I am using the eisy with IoX 5.7.1. But this setup of a zwave device being a controller has never worked in the past.

I have found that if a secondary button is part of a scene it will respond to the scene status of on or off by being lit or not. I did try an Insteon on/off module and had the same results. The z-wave device does not become a controller for any device in the scene even if added as such. No idea if that is by design or an oversite.

It appears that a z-wave device can't be added as a controller even though the option is there and appears to be added that way.

I have a scene set up with a Z-wave nano on/off switch and a button on an Insteon 8 button wall switch. Both are defined as controllers. If the scene is executed both device respond as expected. When the button on the switch is turned on the z-wave device also comes on as expected. However if the z-wave device is turned on the scene doesn't get turned on so the button never gets lit. The z-wave device does show on in the scene. I am using a program to have the scene turn on/off from the state of the z-wave device. Was wondering if this normal for mixed intsteon z-wave devices or am I missing something? Tried many settings with no results. Thanks for any info.

My issue has been solved by reinstalling Java. Upgrading from Win 10 to Win 11 seemed to cause problems for Java. Also i think the original Win 10 version of Java was 32 bit. But after installing a new Java App all is working great.

I think my issue has to do with my desk top PC upgraded to W-11 or the latest Java update. When using my lap top PC everything works fine. Lap top is also W-11 so no clue why the difference. Thanks