bigDvette

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.

I have local control. Just not through ISY. i flip a switch in in ISY as a variable, home assistant picks it up and publishes it to HomeKit as a sensor and I close all the doors. All on the network. i use HomeKit for my ui and have everything there for manual control and use ISY for automation and obviously most of the devices.

I think I'm giving up on this. I bought the 819LM homekit enabled gateway (discontinued product) and linked it to homekit (I was also running homebridge to get MyQ in Apple Home). Of course that bridge doesn't enable gates as homekit accessories (why is beyond me). I then bought a Meross smart garage opener that is homekit enabled to add the gate ( I may just dump the myq gateway altogether in get a meross device for the 2 garage doors) they are super simple to wire in, but I did have to put an additional solar panel and batter on the gate to run the meross device. I then just use homeassistant to make an ISY variable as a binary switch to homekit and trigger an automation in homekit which runs on the hubs. Given all the issues, maybe there is an opportunity to support Meross. Homebridge and Homeassistant have plug-ins for Meross devices and on homeassistant there is a meross-lan that is smart enough to use local or cloud access depending on what is available so I assume there is an API. Not sure how the other MyQ users are feeling but being hostage to not restarting polyglot or updating ISY or on the rare occasion my eisy just reboots is a bridge too far in terms of reliability. I do appreciate all the work here to keep trying to support and if they did just enable a pay service (reasonable) I would consider but I'm kind of thinking only 1 of my fingers has something to say to MyQ right now ... lol.

mine is 20/60

I got mine working but only after I changed my external wan IP address by moving from to my backup wan from primary. After authenticated, I moved it back. They must be loggin the 429: too many requests against an IP address. If that's the case you should be able to do a VPN trick to get it authenticated and then disconnect it. I know this won't work for everyone but I did get it working this morning. If you are getting 429 errors, I suggest you stop the nodeserver completely for 2 hours and let it reset whatever counter it has going. You can also setup another email address and invite that person to your myq account and that also seems to give some relief. I have homebridge and pg3 going against myQ and I have them on separate logins

Homebridge also went down. Then get 429 errors for too many logins (not sure how long that takes to reset). Moved my devices to use my backup wan connection and it started working (homebridge). still can't get pg3 nodeserver to login

So I just took a shot at fixing myself. ssh in to device sudo find . -name myq*.* find location of myqapi.py in list ( sudo cp {location of myqapi.py}/myqapi.py {location of myqapi.py}/myqapi.py.bk (make backup in case) sudo vi {location of myqapi.py}/myqapi.py There are 2 instance of the below line "User-Agent": "null"^M Find then and change them toi "User-Agent": str("{sometexthere}")^M (I used /Agent to find it, went over before "null" and typed i, then typed str("{sometexthere}") and hit esc key, then d {right arrow key} x 6, :qw, restarted nodeserver obviously {sometexthere} is whatever random text you want to use Essentially same as I did for my homeassitant plugin. Should be able to work around. Maybe we need a new config variable with ability to define a unique user_agent and it get put in instead of "null". No idea. But I'm working again.

I'm in Texas and have the problem with homeassistant. Not sure which servers for MyQ connected to, but HA isn't working. I haven't seen a bunch of people on the HA boards saying it is working.

started having same issue on Home Assistant. They found a fix by modifying one of the python files. https://github.com/home-assistant/core/issues/99947#issuecomment-1712369141 specifically this was the fix. docker exec -it homeassistant bash cd /usr/local/lib/python3.11/site-packages/pymyq/ cp request.py request_bup.py vi request.py i to enter insert mode Modify line 34 Was self._useragent = None Is self._useragent = str("anytexthere") Esc key to exit insert mode :w + enter to write the changes + enter to exit VI I see in the old v2 node server User_Agent was set to "null" Not sure if this will help

Ok I have pmd. Not sure how to get the geofence log. The geofence log has an error. my radius is 800.

I also am having really poor geofence results. Exit seems to fire more than entry for me and my wife. we are on 16.4.1.

this shows up as an elk notice under the node server. ERROR: 04/02/2023 18:09:26 See log for: ISY None is not initialized, see log I can't see any log entries under the ELK node server when I click on LOG. Log file when I download has this for that start. 2023-04-02 18:06:51,418 Thread-140 udi_interface WARNING Controller:elk_stop: Stopping ELK thread... 2023-04-02 18:08:14,034 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-04-02 18:08:14,410 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.56 Starting... 2023-04-02 18:08:14,493 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.24 [ISY: 5.5.9, Slot: 11] 2023-04-02 18:08:14,494 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: DELETED} 2023-04-02 18:08:14,494 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-04-02 18:08:14,495 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-04-02 18:08:14,495 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-04-02 18:08:14,495 MainThread udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-04-02 18:08:14,495 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'set': [{'key': 'notices', 'value': {}}]} 2023-04-02 18:08:14,496 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: xxxxxxx.key 2023-04-02 18:08:14,503 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-04-02 18:08:14,504 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/IDIDIDIDIDIDI - MID: 2 Result: 0 2023-04-02 18:08:14,546 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-04-02 18:08:17,578 MainThread udi_interface.interface INFO interface:addNode: Adding node ELK Controller(controller) [None] 2023-04-02 18:08:17,578 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2023-04-02 18:08:17,596 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-04-02 18:08:36,129 ELK-4065 udi_interface WARNING Controller:add_node: Existing node name 'Output 001' for output_1 does not match requested name 'Output-001', NOT changing to match, set change_node_names=true to enable 2023-04-02 18:08:44,004 Thread-27 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2023-04-02 18:09:13,005 Thread-52 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2023-04-02 18:09:26,497 ELK-4065 udi_interface WARNING Controller:sync_complete: ELK Controller: All nodes added, ready to go... 2023-04-02 18:09:26,498 ELK-4065 udi_interface ERROR Controller:update_config_docs: ISY None is not initialized, see log

well I was on 5.5.5 and had updated to 5.5.6. Guess it didn't take, pushed upgrade and thought I had gone down the rabbit hole of upgrade not working. Took about 4 reboots manually and it came up with 5.5.7 so I guess we will see if this fixes it.

So still happening: happened today. When it happens it disappears from pg3x. If I go to portal it doesn’t even show it is installed. I click install and it installs back in the same slot 6 out of 14. The it reboots my ISY and it is back/ I do think it happens when I reboot or lose connectivity. It happened sometime last night and of course then my house thinks I’m not home and I wake up and it is like 60 in house: I haven’t turned off that stuff because I wouldn’t know it isn’t working. oh and the node is missing in ISY console. If I restart pg3 it does not come back. Only way to get back is to go to portal and click install:

I have the eisy and zmatter USB. I could run the usb adapter outside my rack with a USB extension cable, but I'd actually prefer to just put the antennas outside the rack. When my door is closed on front (wire mesh) I get bad reception. I could put a repeater somewhere as well, but was trying to get any thoughts on buying some extension cables to mount the antennas on the outside of my rack. Additionally, does anyone know the connector size/type?