bigDvette

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?

@bpwwerhave you seen anyone else with this problem. Trying to decide if I need to report it somewhere else.

Not sure if this just started with 3.1.21 or if it is even a node server issue but suspect it is. my occupancy node server just disappears. I have to go to portal and go to occupancy Node Server configuration and click configure Node Server/. Then I have to restart pg3x on eisy and then it works for a while. its cold here and it keeps setting my thermostats back based on occupancy and pissing off my wife

yes, that is what I was trying to say. Since I had trial licenses installed (when I did it unless they changed it), it complained I had trial licenses when I did that and didn't transfer them.

yes

after seems to be teh correct procedure. If you install trial licenses it complains and doesn't move the license. Personal experience here. However, given all the Node Server issues until 3.1.17, I wanted to make sure node servers were working so I ended up having Michael move my licenses.

Mine works fine. My only issue was 2 aerotec repeaters. It would pair them but not create any nodes.

I have the same experience. No nodes created. Something about "not a multifunction device".

That point was actually in the migration wiki. I have found you have to do this basically any time you restore a backup.

yeah, something is definitely off with caching credentials. I have had this happen multiple times. Many times just unsing another browser will work. An I can't auto find isy anymore, have to add it manually in launcher.

I know it may sound dumb, but click logout in upper right and log back in. Also, if it doesn't prompt you to lockin to portal when you do that, then reboot your computer. I've gotten stuck in that loop. I've also sometime only been able to fix that by doing an SSH reboot of the eisy. what does it look like under teh menu when you click on iox configuration?

2 - Well this is what I did. At the time all the node servers would not come up until 3.1.17. So I set them up as test licenses. Now you can do a backup and restore which didn't work when I was working on this. I also wanted to keep my Polisy up until I knew everything would work. 5 - When you restore the Polisy backup, the node servers get installed in ISY AC. The IP address on them was the IP address of the Polisy. I also has the UUID in there, so I had to manually change them. I don't think purchasing doesn't anything different, but 3.1.17 gave an backup restore option and it uses the internal IP. I did, Michael moved them for me. I tried to migrate them from portal but it said I already had licenses in the slot.