Michel Kohanim

@Mike M, Please submit a ticket: https://www.universal-devices.com/my-tickets With kind regards, Michel

Hi Paul, thank you. I'll help as much as I can. With kind regards, Michel

I am very interested. If we can use SSDP to find it and the python library to communicate with it, it would be great. My use cases: Turn on/off Change channels/volume Connect/disconnect bluetooth Chromecast (albums and pictures) With kind regards, Michel

@sjenkins, https://pypi.org/project/samsungtvws/ ? With kind regards, Michel

Do all Samsung devices need to go through SmartThing? I want to do the same for other reasons. With kind regards, Michel

@sjenkins, perfect! I will contact you on discord. With kind regards, Michel

@rkhauto, I am not familiar with how Sonos works. Can you connect a Bluetooth source to it? If so, we should be able to since supporting Bluetooth audio is next on the list. With kind regards, Michel

@wrj0, thank you very much. It's very very odd though With kind regards, Michel

@wrj0, did you Reboot after the last update? With kind regards, Michel

@wrj0, No, you don't have to do it every time. Please do it now, reboot, and let me know whether or not it survives. With kind regards, Michel

@wrj0 Did you do: sudo zpool export storage sudo zpool import storage Without these, your file system is removed after power outage. With kind regards, Michel

Hello all, To configure your Drop system, please follow these instructions: Configuration: Go into the Drop App and go to the System option on the sidebar. Then go to the Advanced Tab. In the Advanced tab click Configure MQTT Click Connect and for the IP enter the IP of your ISY, Port 1884, and anything for name and password (can't be empty) Click Connect. Nodes should begin appearing in your IoX admin console. If they do not, first restart the plugin. If that fails, click on the Discover button on the same screen in the Drop app that you just added it to and then restart the plugin again. With kind regards, Michel

@sjenkins, In couple of weeks. With kind regards, Michel

Hello all, A minor enhancement: - We now keep an internal mapping so that, if you add/remove files, those that have not been impacted remain at the same index WARNING: Although thoroughly tested but with a minimal set. So, please make sure everything is where it should be after the upgrade + restart With kind regards, Michel

@leonpc, what exactly is the error and what exactly is not working? Please submit a ticket. With kind regards, Michel

@sjenkins, When ready, please let me know and we'll include it in our email blash (Plugin Spotlight). With kind regards, Michel

@dakall, Yes, please submit a ticket and include the output of: https://eisy.local:8443/WEB/sysconfig.txt With kind regards, Michel

@vspete, Thank you for the feedback. We started with HomeBridge but it was way too resource intensive. I am hoping we can get something out quickly. With kind regards, Michel

@sjenkins, I totally agree with you. To be frank, when I started plugin dev about a month ago, I was flabbergasted by the level of difficulty and the learning curve. I think we went too far with flexibility and made things more complicated. In essence, the platform is as flexible as being able to define anything but makes it very difficult to make a simple thing especially going back and forth between nodedef, editor, and nls. I hate that. The, you will have to use these definitions and work on your python code (going back and forth between files) because udi_interface does not know anything about those files except for uploading them to IoX. It's just way too complicated. This being said, it's now our top priority to add a layer in between so that everything (including udi_interface) are all tied together with one file. And, yes, will definitely include more documentation on the interface. Thank you so very much for the feedback. With kind regards, Michel

@sjenkins, Are you referring to udi_interface? With kind regards, Michel

@Chioti, still working on it. So sorry for the delay. With kind regards, Michel

@leonpc, Python is already installed on eisy. About a year ago, phyton had a major release. That may have been the cause. For now, we are sticking with python3 regardless of any updates. That is till we make sure nothing is going to break. That would be me! Since I started developing plugins myself, I can see that it still needs a lot of work. Many things are confusing and not well explained. It's on my list to make it better. With kind regards, Michel

@kzboray, If you don't see those events reflected in the IoX log, then it's definitely an All On/Off event. This happens for one reason and one reason only: IoX receives an event (usually from RF/dual band devices that send duplicates), a program runs in IoX and sends a group command (scene) at/around the same time. The result is that the group command is corrupted by the PLM (All devices) or something in between (Some devices). From experience, the majority of the time the issue happens when you try to control KPL backlights based on status of some other devices and/or sensors. Some remedies are outlined here: https://wiki.universal-devices.com/INSTEON_Random_All_On_Events

@larryllix, the coupon is not available to Canada. The $30 comes directly from UD but only for those who already have Polisy purchased from UD (not ebay). In short, if you were to purchase directly from UD, you would be paying more for shipping and customs than the discount. With kind regards, Michel

@dbuss, I think the issue is the size. Let me do some research and get back. In the meantime, you can always try the simple version for testing. With kind regards, Michel