bigDvette

I was able to set this to my custom topic prefix by changing the value in ratgoapi.py. I have a lot of sensor going to a custom topic prefix I use in Home Assistant so would really like ability to use my open topic prefix via a config key:value. After changing it, I am able to get the status and issue commands. Thanks for your work

all good, happy holidays.

Yes I refreshed the store. Both the store and the purchased page when click in to Harmony show 3.0.8 and no upgrade message on dashboard and no upgrade button on purchased tab.

I haven't seen it hit the store. Still shows 3.0.8 version.

It looks like the changes are applied in git and version 3.0.9 assigned. Curious if it will be pushed to store soon?

What would you do with it in a scene?

@Flex the updated node server is in the store. If you go to purchases then click reinstall you will see there is an update. I also added a mute status (thought might be handy for what you were doing). I’m not 100% that status will get added to existing speakers. The speakers should get the same names if they get re-added so if you have any problems try deleting the Sonos speakers and then restart the nodeserver. I usually remove them using the nodes tab on the polyglot web page. if you change play, pause, volume or mute from say the Sonos app, it will take up to as many seconds as you have configured the shortpoll on the config tab of the nodeserver.

@bpwwer I found it odd there was no discover button and no controller node but didn’t mess with that too much. I actually had it adding a controller node in 1 version but commented it out later because I didn’t understand why it didn’t exist. ill re-pull and tinker again. I had the hardest time even getting the custom params to read initially as the nodeserver didn’t use any and there was no load being called anywhere.

@bpwwerI think I was able to push changes to Git. Let me know if that looks like it worked and I can test.

Thanks @bpwwer I worked on it a lot last night. I have added a manual method to assign IP addresses and sonos speakers and I have also figured out in the soco library that there is a method to call discovery and specify subnets to scan. I have added and left both methods in the file. I then went and extended the editor.xml, and nodesdefs.xml to add a status for mute to the config. based on what @Flex was wanting to do to map button status, I though a mute status was a good idea. I'm not sure how to submit a pull request, but have used git. If I can't figure out, I will send you sonos-poly.py, editors.xml, nodedefs.xml and an updated README.md with syntax to use the other methods. Thank you very much! I did learn a lot between figuring out how to add back the manual method to harmony nodeserver as well.

I’ll see if I can get changes committed. Not sure who is maintaining the nodeserver.

@Flex I am digging in to this nodeserver. There is a typo for shortPoll in the plugin that is not causing it to get any updated states. I have it workiing. I also have it working to scan networks beyond the base network and the ability to manually add nodes. If you are interested I can send you the custom python file for you to test.

@Jimbo.Automates I have made changes to the harmony Controller.py to add back the functionality to add hubs from config parameters. Any way to get this put in to the production nodeserver? Really helps when using vlan seperation of IOT devices. Once nodes learned they can talk no problem with rules, but discovery isn't so easy. I've marked all my changes with DD - comments. I think there are like line changes after uncommenting previous code. Thanks in advance. Controller.py

I'm using a vlan and while speakers can be controlled, discovery is really flakey. No set of rules help. I can open up the ports completely and still doesn't get discovered. I "borrowed" from the harmonyhub nodeserver and made minimal modifications to the sonos-poly.py file to allow a similar method to add speakers from a config file. Any way to get these changes incorporated? File attached. I assume @bpwwer is still the developer? Thanks in advance. sonos-poly-mod.py

I implemented a vlan and lost discover. I modified the sonos-poly.py to have functionality similar to the harmony controller. I'm going to ask if it can be put in to the production instance. Essentially you add custom config values using format of: key = sonos_(some_name_you_want_to_use) value = {"name": "(name you want to use)", "host": "xxx.xxx.xxx.xxx"} I've attached the file in case you want to use it. YOu have to copy to your node server directory /var/polyglot/pg3/ns/{nodeserver directory} as sonos-poly.py sonos-poly-mod.py

do you have fixed IP addresses for your Harmony hubs?

Not sure who owns this nodeserver. In the end to get it to work I only had to I added a comment before each change starting with DD Uncomment the code that had been commented out when moved to PG3 Change 3 lines of the code. 2 were to change the old way Params were used to self.Params and 1 was to ensure the address was all lower case like it does when it adds the node. Attached is the Controller.py file for whoever owns this. If we can get this put in the plugin production store everyone can take advantage. Controller.py

I think I figured it out. I uncommented the manual code and got it to add the hub. all the definition was in the yaml file for activities and devices, but no devices were created under the hub and no node definitions. when it creates the node, it sets the address to all lower. if you for instance use your key as hub_ShopHarmony vs hub_shopharmony, when it goes to build profile it tries to match the node address to the part after hub_ and if not all lower it doesn't match. Changed the manual code to make address.lower() and it adds the nodes. I'm going to start from scratch and put comments in and add back the missing code and changes I made and then figure out where to submit so maybe the node server can be updated in store.

I spent hours trying to fix the code last night. Manual is commented out I. controller.py. there seem to be general discovery issues as well . I was able to get it to add a node and could control activities from the node (power off, change activity) but it would never add the devices to the node. May take another run at it tomorrow.

I'd like the post to stay on point. There is a manual method for adding Harmony Hubs. It isn't working, doesn't even try to add the manual nodes. Either I am not putting in the keys right or it is broken. I don't have problems talking to the harmony from the eisy. It is working fine once the entries have the correct ip address in hubs.json. So, putting aside trying to do discovery across vlans. I understand how firewall rules work and they are setup correctly. So again, thanks for the network conversation, but this is not about that. It is about being able to manually add harmony hubs using the documented method Here is the paragraph from the README.md. Items 7 states it can't do discovery across subnets and then there is a section on manually adding. === 7. This should find your Harmony Hubs and add them to the ISY with all devices and activities if your Harmony Hub and Polyglot are on the same subnet. If they are not, then you can manually add the hub address as described in the next section, ==== Manual Hub Entries If the discover does not work, or you prefer to not use it, you can add customParms in the Polyglot Web UI to tell it about your hubs. Create a param with the name 'hub_uniqueid' where uniqueid is the address that will be used for the ISY node, and with a value like: { "name": "HarmonyHub FamilyRoom", "host": "192.168.1.86" } Anytime these params are added or modified you need to run the 'Discover' on the HarmonyController node.

Thanks, I'm not talking about how to get networking to work. As indicated, I can access the harmony hubs in their subnet (I consider the EISY a trusted Server and harmony hubs an untrusted IOT so seperate vlans). The issue is discovery. Discovery only broadcasts in the same subnet as far as I can tell. So the obvious workaround is the manual method which is documented on the git site for the nodeserver, however I can't get THAT to work. I worked around the issue by temporarily putting the eisy in the same vlan as the harmony hubs, doing discover, disconnecting it from that vlan and putting it back in it's trusted vlan. Once the IPs are stored for the hubs, you don't need to do discovery again. However, that isn't a great option. Would be nice if the documented way to manually add hubs worked which either I am doing something wrong or it is broken. For clarity, after I seperated them in their own vlans again, I can control the harmony from ISY so I got it working.

I've been using the Harmony plugin for years and love it. I've been re-working my network to add some isolation to IOT devices. I've had some issues, but it has gone pretty well. Sure would be nice if there was a way to edit IP addresses in plugins in pg3 vs have to go through discovery, but can't figure that out. Anyway, I did what I normally do and just tried removing the devices and adding them back to harmony node server. After reading the docs, it is obvious that discover only works on the same /24 subnet. So I created custom params and followed instructions (I think). Essentially, it doesn't even seem to try and read those configuration items. I've created an entry with: key = hub_mancaveharmony value = { 'name': 'Mancave Harmony' , 'host' : '192.168.30.190' } I have SSH'd in to the Easy and I can ping that address no problem. When I click discover from either Admin Console or Polyglot screen, it just comes back with an error but log looks like it is does normal discover and then just craps out. I have it working at the moment. Essentially I moved the Eisy to my untrusted IOT vlan, let it run discover, shut it all down and moved it back and now it "re-learned" the IP addresses and stored them somewhere (this is why would be nice to be able to edit them) and those IPs are all fixed IPs. I can't seem to get the manual mode above to work and didn't know if anyone else has used it. I have same issue with Sonos but it is worse because it does rediscovery every time it starts and doesn't seem to save the IPs. If it can't find them on startup, it just doesn't load anything. I needed up hacking the Sonos-poly.py on my Eisy to manually add them. It would be nice for all plugins to allow a manual file method to load devices vs using discovery as setting up the rules form them to talk is fairly easy but getting everything discovered requires mdns repeaters temporarily ... and the Sonos node server just won't work because it has no memory other than node names. Sent a PM to Jimbo with the log. Thought I'd see if anyone else runs in to these problems.

I’m using the meross and it has local Mqtt control (no cloud) once setups. Using with home assistant for now but it also has native HomeKit built in.

Did you get an answer to this question? i was wondering the same.

I'm using the Meross msg100hk. It also has local control (I'm using HA with it this way at the moment). It also uses MQTT and can be configured to use a local MQTT broker. There is a HA integration called Meross Lan available via HACS. IT is a sealed unit, I'm running it off a solar controller at my gate (USB). The think I like is it has Native HomeKit if you are using HomeKit (no publishing from HA) and if UDI supported it I probably wouldn't even add it to HA.