I have a newbie question regarding UPB lighting …
The UPB integration is set up correctly and I can control the lights from the HA interface. However when I control the lights with the wall switch, Home Assistant never sees the change. I have the option for lights to report their statuses enabled in the UpStart programming as well.
Any ideas or is this a downfall of UPB?
It appears it may be a ‘downfall’ in your configuration.
All of my UPB devices are configured to report their status when manually operated. As a result, when I manually turn on/off a light or change its brightness, the device reports its status, the information is received by the UPB integration, and corresponding entities report the new value.
Are you certain the UPB integration is using the latest version of your UPB export file?
Yes. It is using the latest version of my UPB export. Here is some info from log.
'Logger: upb_lib.upb
Source: /usr/local/lib/python3.9/site-packages/upb_lib/upb.py:148
First occurred: 7:56:10 PM (5 occurrences)
Last logged: 7:56:51 PM
Timeout communicating with UPB device ‘Master Bedroom Kyle’s Lamp’ (73_24_0)
Timeout communicating with UPB device ‘Mudroom Lights’ (73_1_0)
Timeout communicating with UPB device ‘Exterior Back Porch Light’ (73_12_0)
Timeout communicating with UPB device ‘Dining Room Chandelier’ (73_2_0)
Timeout communicating with UPB device ‘Kitchen Lights’ (73_3_0)’
You should probably start closer to the source which would be in upstart and see if you can replicate the problem there before getting into home assistant.
I have and everything works correctly in Upstart. I just went through and reprogramed all of my devices verifying that they all have the “update status” option selected. Imported a new file in to home assistant and I’m still getting the same timeout error and no status reporting.
I see five devices timed out. Do you have more devices? Are any of them communicating? Are you getting any status? Can you control any of your devices? What make and model are the devices?
I can’t think of any more questions. I’m with the rest of the comments… seems to be your network somehow, just no clue as to why.
I have made some progress…
PulseWorx Pim-U connected to Home Assistant through the UPB integration allows you to control the lights through HA, but does not track statuses.
PulseWorx Pim-E connected to my ELK M1 and to Home Assistant via the ELK M1 integration works as expected with control and status updates.
The UPB HA integration does not like the PIM-U for some reason. What PIM are you guys using?
I’m using SAI UMC-DB9-W
So I’m guessing you’re not using a raspberry pi with HA.
My production system (old laptop) is equipped with a Simply Automated CIM UMC-USB. It is running Home Assistant Supervised on Debian.
My test system (RPI3) is equipped the same way. It also uses Debian because, at the time, the operating system in Home Assistant OS didn’t have the required driver to support the USB version of the CIM (there’s a discussion about it within this thread). Perhaps that changed in the latest version of Home Assistant OS but I have not tested it.
Which installation method was used for your Raspberry Pi? Home Assistant OS or something else?
I used Home Assistant OS on my raspberry pi.
In that case, it would appear that its operating system now includes the necessary driver to detect the PIM-U and, at the very least, allow the UPB integration to successfully transmit commands. What is subject to debate is whether it is able to successfully receive commands.
An interesting experiment would be to activate a UPB link (a.k.a. scene) and check if the UPB integration receives it using Developer Tools > Events > Listen to events.
Click ‘Start listening’ then activate/deactivate a UPB scene (can be done in UPstart) and you should see events reporting the link number and other information. If you don’t then nothing was received from the PIM-U and suggests the driver might be the culprit.
Let us know what, if any, results you get.
How many devices do you have, as I only see timeouts for 5 devices? Are some devices not timing out?
I agree, it appears writing to the PIM works and reading does not. Don’t know why.
Around 25 devices currently. They were all timing out. Just snapped that error at the beginning.
For those joining this game late, and being puzzled by the lack of /dev/ttyUSB0 device when plugging in the Simply Automated UMC-USB-W into the Home Assistant OS – this is because it’s missing the usb serial module for cypress_m8, which this device uses. So far I have not been able to figure out how to work around this.
Is there a way to change device type from light to switch or fan? I have read the entire thread. I see this was mentioned but I do think it was resolved. Thanks.
Not sure but I’m guessing you would have to create a template. I have a fan that appears as a light light.upb_bathroom_fan. In the GUI I just changed the icon next to the switch to a fan icon. For other projects (not UPB) I have used fan template but that’s much more involved.
Check out Devices and Services. Click Helpers. Add helper. Choose switch.
Does that help?
I know this is 2 1/2 years late but I got the HA UPB integration to work with the PIM-IP. The short answer is to disable authentication by unchecking the “Enable User Logins” on the PIM-IP.
I own a PCS PulseWorx UPB Powerline Interface Module IP (PIM-IP). I use it to run Upstart and configure my lights from my Windows PC over the net. I got HA running and decided to try the UPB integration, but I got a “Could not Connect” error. After reading this thread I noticed there was a connection problem due to the PIM-IP requiring authentication. So here is how to fix the authentication problem:
–Using your browser go to the URL of the PIM-IP and login to the web UI using “root”.
This is the user with configuration privileges.
–Go to Configuration, Users
–uncheck "Enable User Login
That’s it! When you go back to the HA UPB integration and configure the TCP address and file name it will connect and bring up your lights.
BTW, you can not use Upstart unless you disable the HA UPB integration first.
I only see an option to create a helper that converts a switch to something else. Not to convert a light to a switch or a fan. I resolved my issue by inserting the device code in yaml for the blueprint I was trying to utilize.
On another issue it seems a core OS update may have changed the usb device IDs. Any idea how to change the serial port the PIM is connected to after the initial configuration?
