Techman

The update process you listed would apply only to the Polisy, not the ISY994. Be sure to backup your Polisy prior to updating. If you have Zwave devices installed then you need to also do a Zwave backup. Nothing you need to be aware of unless your Polisy is a very early version in which case you may need a bios update as well. If you do the update and everything works then the bios won't be an issue.

@Javi The admin console correctly displays the file that's playing, UD Mobile either shows the incorrect file name or a number. I done a few syncs but the issue is still there.

Appartently so, I think Zigbee is still being refined.

@bmercier Prior to uploading my MP3 files I deleted all the default sounds. When I did the 5.8.3 update I had to restart the audio player as it wouldn't populate and it reinstalled all the default MP3 files which I then had to delete again. I thought there might be an easy workaround.

When playing a MP3 file on Audio Player via UD Mobile an incorrect file name is displayed in the playing field

I was thinking in the terms of both an MP3 upload and TTS generated MP3s, the latter which can't easily be saved.

@bmercier Is there a way to backup and restore the Audio Player data directory (just the MP3 files) without doing a full system restore. If not, could that be an added feature for the next firmware update?

On the bluetooth service select ENABLED, then click on the SERVICE button to the left. If that doesn't work then go into PG3 and restart the bluetooth service. Once the service is enabled click on "Scan for Bluetooth Devices"

If you're in safe mode that meas that the ISY can't communicate with the PLM. Is the green led lit on the PLM? Make sure the PLM cable is plugged into the correct port on the ISY and that the cable isn't defective.

@timekiller Did you follow the replace PLM procedure (see attached) Replace PLM.pdf

Prior to migration did you update the EISY firmware? Was your ISY Zwave dongle the 300 or 500 series? Did you do a Zwave backup on your ISY prior to thr migration? Some programs that include Zwave devices may need a tweek depending on how you named your devices. Did you exactly follow the migration instructions, as the migration should have gone smoothly.

@bmercier When I use "/var/polyglot/pg3/ns/<NS Folder>/data" I'm able to get to the directory but I get a permission denied. So I can't see the data. How do I get past that?

Thank you. I'm getting a "no such directory" response. I'm not using developer mode. Is the slot the one used for the audio player?

@alixer To verify that all the devices in a scene are properly responding, Right click on the scene, click on diagnostics, scene test.

@bmercier What would be the syntax, and directory location, for accessing and downloading the MP3 files. I'd like to save the files created by the TTS. option

@bmercier What directory are the Audio player MP3 files stored in, can they be downloaded and saved?

@alixer If the THEN clause works correctly in your fast off program then the problem is most likely the timing of your double off clicks. Try doing a faster double click.

@Chris Wacker What is your Eisy firmware nad UI versions. Are you currently using the admin console to do your programming ?

Use the link I posted, the IoX Launcher was updated a while back. You most likely had the previous version

Clear your Java cache, checking all 3 boxes, then download the IoX Launcher from here https://isy.universal-devices.com/start.jnlp

Make sure one one sensor at a time is in the linking mode. Once in the linking mode right click on the device and click on restore device.

The launcer window size parameters are stored in the windows 10 temporary folder. Some utilities such as Norton periodically delete the contents of the window temp folder which will cause the launcher window to revert to full screen.

The update from 5.014 to 5.3.4 shouldn't be problematic. You can update directly to 5.3.4. Be sure to closely follow the release notes, and be sure to backup both Zwave and ISY. If your Zwave version is 6.81.00 then you have the 500 series zwave dongle, so you're good to go.

Sorry, you're correct. It's not in a scene, I was looking at something else. Try deleting and reinstalling the module. You should also update your ISY firmware and UI to 5.3.4 which includes bug fixes and may resolve you problem.

The options you have selected are OK and wouldn't have any impact on your issue. In your previous post you posted a screenshot of your module which shows it as a member of a scene yet you mentioned that's it's not included in a scene. If it's still a member of that scene then you most likely have a program that's turning that scene on