OK, that is an easy fix but not tonight. Tomorrow afternoon it should be done. I appreciate you finding this bug for me before it goes into the main Home Assistant program.
OK, I actually just posted a quick change. If you can try again that would be great. If you still have issues I will have to look at it tomorrow.
wait for it. BTW i have a PLM USB and a hub 2. Which gonna work better in this case?
ok, the open/close appears now but when i try to use it:
Logger: homeassistant.components.websocket_api.http.connection.1750367280
Source: custom_components/insteon2/cover.py:66
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 11:51:54 PM (3 occurrences)
Last logged: 11:51:59 PM
async_open() got an unexpected keyword argument 'position'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 130, in handle_call_service
connection.context(msg),
File "/usr/src/homeassistant/homeassistant/core.py", line 1247, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1282, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
self._platforms.values(), func, call, required_features
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 453, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 596, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 484, in _handle_entity_call
await result
File "/config/custom_components/insteon2/cover.py", line 66, in async_set_cover_position
position=position, group=self._insteon_device_group.group
TypeError: async_open() got an unexpected keyword argument 'position'
Both the Hub and the PLM should work equally well. I have fixed that most recent issue you have found.
it is working now! thanks!
I have issues with the keypadlinc, I can control the buttons from the frontend but when i push any button it doesn’t update on HA.
I did the group 3,4,5,6 all linking process as responder and don’t work either.
Is it a switch or a dimmer?
It is a switch. HA can’t update the main button either.
after updating to 0.110 it is worse. The swichlinc pad doesn’t appears anywhere. I re-linked and nothing.
Can you put the system in logging mode? Add the following to your configuration.yaml file:
logger:
default: info
logs:
pyinsteon.topics: debug
pyinsteon.messages: debug
custom_components.insteon2: debug
What is the ID of your KeyPadLinc and your SwitchLinc? Did you turn them on and off in this log?
Sorry in my past msg i wrote a wrong device name, the faulting device is the KeyPadLinc only.
In this logs, i pushed on and off the keypadlinc 50.A3.31
The on and off messages are definitely coming from the device and seen by the modem so it is not a linking issue. However, it appears to be the wrong device type. It should be a cat: 0x02, subcat: 0x05 but in the log you can see:
2020-05-21 11:37:52 INFO (MainThread) [pyinsteon.managers.device_manager] Adding device to INSTEON devices list: 50a331
2020-05-21 11:37:52 DEBUG (MainThread) [pyinsteon.topics] Topic: device_id data: {'device_id': DeviceId(address=50a331, cat=0, subcat=0, firmware=0)}
So it is showing up as a cat: 0x00, subcat: 0x00. I would not even think that would show up in HA at all.
ok!! i’ll override the device cat and sub cat and should work.
Before you do that, can you just delete your insteon_devices.json and insteon_plm_device_info.dat file from your configuration directory? I would like to see why it showed up as the wrong device type.
sorry i didn’t read your msg but this turns more rare. I override the device and it didn’t show up.
insteon2:
port: /dev/ttyUSB0
device_override:
- address: 50a331
cat: 0x02
subcat: 0x05
OK, I see why the device is not showing up after the override. If you delete the two files above and remove the device_override it should still show up as the correct device as long as the device responds with a proper device ID.
i deleted the 2 files and comment the override. Still not here the KeyPAd
EDIT:
after few minutes, is here, the keypad appears.