UPB integration will not work with export file no matter what i do #121568
Comments
|
Hey there @gwww, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) upb documentation |
|
Please provide debug logs. Add the following to your |
|
Added the above... no logs. (waited until .2 came out so I could test ... in hopes of saying it's fixed) updated to .2 still same issue Where will logs show up? sorry |
|
this is the only thing I see: |
|
i did see this too... right after... though not listed in my devices... had small hope... no luck: |
|
so tried again, same error... but with .2 it's definitely seeing it now and trying to talk to each device. after it says missing or invalid. |
|
A proper log will help. The log file will be in From the bit I can see above, it appears that your UPB network ID is |
|
|
sorry... yes network ID is 1 |
|
I’m on my phone but it appears that some devices are working and some are timing out. Is that right? So the bug that I introduced seems to be fixed. As to the timeouts that’s a problem with the UPB network. Has your PIM moved from where it was working? |
|
So kind of fixed it. Not all devices are connected … so it makes sense that they time out…. Problem is since I get the invalid error… no devices show up for me to control or see … only in the log
On Jul 10, 2024, at 4:50 PM, Glenn Waters ***@***.***> wrote:
I’m on my phone but it appears that some devices are working and some are timing out. Is that right?
So the bug that I introduced seems to be fixed.
As to the timeouts that’s a problem with the UPB network. Has your PIM moved from where it was working?
—
Reply to this email directly, view it on GitHub<#121568 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAJ44AQ6RIKO2SQZUQWWBCTZLW3B5AVCNFSM6AAAAABKRW4ILSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRRGY2TKNZZGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
To the |
|
I know why there is the log message about missing or invalid upe file. You can safely ignore it. I will figure out a fix but the message is erroneous. It's all around the async loading of the config file and the order of connecting versus loading. I'll leave this issue open until it is fixed. |
|
Is there a way to manually add the devices since HA sees them?
|
|
All the devices in your upe file will be added regardless of whether you can connect to them. There’s no other way to add devices. |
|
Ok. I’ll wait :/
|
|
I'm having the same problem adding UPB to HA 2024.7.0, 7.1, and 7.1. Home Assistant Core Missing or invalid UPB UPStart export file, check the name and path of the file. I get the above after entering I did a test install on Raspberry Pi 3B+ with HA 2024.6.x?? prior to the 2024.7.0. The file was recognized and loaded the .upe. I was having other problems staying connected. I did erase the password file. Accordingly, I decided to un-install the integration. I'm running the standard HA installation. I received an HA Yellow in the mail and did an initial installation of 2024.7.0. When I saw the new release, I also upgraded the Pi 3B+ installation, getting the sam error. When I tried to install the integration again, I never got passed the first page and the above error. Log details (WARNING) PIM at tcp://192.168.1.1 disconnected Logger: homeassistant Error doing job: Exception in callback _SelectorDatagramTransport._read_ready() (None) The home-assistant.log.fault file is empty. Here is the top of the home-assistant.log file: 2024-07-12 18:34:57.342 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback _SelectorDatagramTransport._read_ready() (None) |
|
Fix is submitted for not recognizing the file. Should be in .3 As to connecting and disconnecting that I see in your log that is something else. Feel free to open another issue for that. Warning there’s not much I can do for that though. The remote PIM is disconnecting. Is there more than one device trying to use the PIM? |
|
When the PCS Pulseworx Gateway connected to 2024.6.4, It was recognized but kept dropping the connections. Devices immediately went to unavailable. Does this integration work with the Pulseworx Gateway or just the prior PIM-IP. (I know, I have to wait for the .3 bug fix to retest or do anything meaningful) I did delete the user file on the UPB Gateway. I am also willing to contribute and update/test the code to support a login capability for the UPB Gateway and HA integration. I did make sure that UPStart was shut down. I'll double-check everything and see if I can clear that from the logs. Thank you. |
|
I only have a USB PIM so can only go by user reports. Try asking about your model here: https://community.home-assistant.io/t/upb-lighting/615/492 |
|
Thanks, I also have a PIM-U and older Serial. I'll give the PIM-U a try |
|
Works with .3. Thank you! |
|
Thanks. PIM-U now connecting with .3 |
The problem
I followed the advice on all the forums and cannot get this to work. I placed the file in the /config directory... tried changing permissions and even the name of the file... tried different puncuation. every time, it says invalid or missing.
What version of Home Assistant Core has the issue?
core-2024.7.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
UPB
Link to integration documentation on our website
https://www.home-assistant.io/integrations/upb
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: