-
Notifications
You must be signed in to change notification settings - Fork 69
missing 1 required positional argument: 'sensors' #222
Comments
Hi @Mariusthvdb, sure, I'll check it. I only tested it locally over HA dev, and after that, over HA 106.4 in my production system, but there I only use the Could you provide more details?
Also, have you 'jumped' more than 1 version, right? Another strange thing is the line in your exception log: |
My file is a heavily modified file which only creates the PHD sensor, found elsewhere in this Github Repo. I am using Hassio 106.5, and if I use the full Custom integration up to the changes you made, the Custom integration works perfectly, creating all (binary_)sensors and remotes. Note I need the bridge_id for the PHD sensor to create unique sensors for multiple bridges. Would that be an issue now?
the remote file is working fine using the new technique here, as is the device_tracker, which isn't very useful though, because it hardly ever (if ever) changes state....) Using the core binary and regular sensor. I'll copy it here so you can see what I am doing. I hope to have adapted all changes you made in the new way of retrieving data from the Hub:
|
small update:
to
results in:
only other big change is:
in the original (old) binary_sensor.py. |
@robmarkcole, this issue should be closed, as relates to custom code, not present in Sure @Mariusthvdb agrees on that |
yes I am fine with that, especially since I added the PHD sensor to your refactored setup and it works very nicely indeed. Only wish is we could add a bridgeid to the sensor_id, to make them hub specific in the multiple hubs setup configurations, like I had it. Could you help me realize that please? Do we have the bridged in the custom integration available?
thanks for having a look! |
@Mariusthvdb please create a feature request |
will do, thought it wasn't allowed since it isn't a feature (yet). Done: #227 |
u[on updating the new binary_sensor, this is logged:
which in my local file is the line:
@azogue please have a look?
before, this was:
could it be you accidentally cut that, or is this the wanted change to the new data source, and another issue has been introduced.
The text was updated successfully, but these errors were encountered: