Patch release just dropped. In interested in hearing how it’s working!
@gwww It’s still not parsing the file for me. I scoured the logs and found one issue with connecting to the IP PIM, so I disabled the password and it was able to connect. However, it still will not recognize the file. Here the last few lines of the log file.
2024-07-10 11:35:53.441 INFO (MainThread) [upb_lib.upb] Connecting to UPB PIM at tcp://10.1.30.16
2024-07-10 11:35:53.443 WARNING (MainThread) [upb_lib.upb] Could not connect to UPB PIM ([Errno 111] Connect call failed ('10.1.30.16', 2101)). Retrying in 2 seconds
2024-07-10 11:35:54.938 ERROR (SyncWorker_4) [upb_lib.parse_upstart] Cannot open UPStart file: [Errno 2] No such file or directory: '/current.upe'
2024-07-10 11:35:54.938 INFO (MainThread) [upb_lib.upb] Connecting to UPB PIM at tcp://10.1.30.16
2024-07-10 11:35:54.943 DEBUG (MainThread) [upb_lib.proto] connected callback
2024-07-10 11:35:54.943 INFO (MainThread) [upb_lib.upb] Connected to UPB PIM
2024-07-10 11:35:54.943 DEBUG (MainThread) [upb_lib.proto] queued write ''
2024-07-10 11:35:54.943 DEBUG (MainThread) [upb_lib.proto] write_data ''
2024-07-10 11:35:54.943 DEBUG (MainThread) [upb_lib.proto] queued write '70028E'
2024-07-10 11:35:54.943 DEBUG (MainThread) [upb_lib.upb] Synchronizing status of UPB network...
2024-07-10 11:35:54.948 ERROR (SyncWorker_21) [upb_lib.parse_upstart] Cannot open UPStart file: [Errno 2] No such file or directory: '/homeseer/config/current.upe'
2024-07-10 11:35:54.949 INFO (MainThread) [upb_lib.upb] Connecting to UPB PIM at tcp://10.1.30.16
2024-07-10 11:35:54.953 DEBUG (MainThread) [upb_lib.proto] connected callback
2024-07-10 11:35:54.953 INFO (MainThread) [upb_lib.upb] Connected to UPB PIM
2024-07-10 11:35:54.953 DEBUG (MainThread) [upb_lib.proto] queued write ''
2024-07-10 11:35:54.953 DEBUG (MainThread) [upb_lib.proto] write_data ''
2024-07-10 11:35:54.953 DEBUG (MainThread) [upb_lib.proto] queued write '70028E'
2024-07-10 11:35:54.953 DEBUG (MainThread) [upb_lib.upb] Synchronizing status of UPB network...
2024-07-10 11:35:54.958 DEBUG (MainThread) [upb_lib.proto] disconnected callback
2024-07-10 11:35:54.958 WARNING (MainThread) [upb_lib.upb] PIM at tcp://10.1.30.16 disconnected
2024-07-10 11:35:54.973 DEBUG (MainThread) [upb_lib.proto] disconnected callback
2024-07-10 11:35:54.973 WARNING (MainThread) [upb_lib.upb] PIM at tcp://10.1.30.16 disconnected
Are you sure that the path is correct? /homeseer/config/current.upe is not usual. /config/current.upe is more usual.
I just noticed that it seems to be connecting twice. Each one has a different path for the file.
I suggest deleting all UPB integrations and starting clean. Make sure the .upe file is in your HA /config directory.
I was never able to add a UPB integration. I never got past the screen to put in the file name. Those other connections were remnants of my trying every path I could think of.
I just blew away my VM and I’ll try it again with a clean install, though my hope is waning.
So a work around until I can get this straightened out is to fall back to 2024.6.0. Add the integration and then update to latest HA.
If someone could provide a debug log that would help. I have not been able to reproduce this in my setup. Instruction on how to turn on debugging here: UPB integration will not work with export file no matter what i do · Issue #121568 · home-assistant/core · GitHub and here. (read them both).
How do we get the patch? I’m sorry for the dumb question, I’m new to HA. I don’t know if the patch is already part of the UPM integration or if it’s something I need to download. Thanks.
OK… gotcha. I just rolled back to 2024.6.0. Let’s see if this works. If so I’ll create a new VM with current version and try the patch.
Rolled back and Upstart upe file loaded perfectly. 40 devices loaded. I’ll create a new VM with .2 update and try that way as well.
I just did the same thing. Rolled back and it worked perfectly. All my devices loaded.
@gwww I have debug logs for you from 2024.7.2. How do you want them?
@gwww I have debug logs for you from 2024.7.2 as well. Device names might have personally identifiable information in them. I’d rather send them directly via your preferred method. Please let me know.
Thank you for your help!
Sure, you can DM me on this platform. Or my email is in here: upb-lib/pyproject.toml at fe6d9d4ce73639de59df5913327cd769adb32546 · gwww/upb-lib · GitHub
I just pushed another fix. I’ve tested in all the scenarios I’ve read about here plus anything else I could think about. It all seems to work perfectly now. Thanks for your patience!
1 Like