Did anybody succeed to setup a Homematic Wired Dimmer? I struggle to expose the right channel. The device shows up in the UI, but I can only operate the switches on channel 1 and 2, while the dimmer is on channel three.
At start up the following Log is generated:
17-03-14 23:28:22 WARNING (Thread-12) [pyhomematic._hm] RPCFunctions.addDeviceNames: Could not access XML-API: timed out
17-03-14 23:28:23 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_DEVICE on LEQ0975979:0 Exception: <Fault -1: ‘Failure’>
17-03-14 23:28:24 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: WORKING on LEQ0975979:1 Exception: <Fault -1: ‘Failure’>
17-03-14 23:28:24 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: LEVEL on LEQ0975979:1 Exception: <Fault -1: ‘Failure’>
17-03-14 23:28:25 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_DEVICE on LEQ0975979:0 Exception: <Fault -1: ‘Failure’>
17-03-14 23:28:25 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: WORKING on LEQ0975979:2 Exception: <Fault -1: ‘Failure’>
17-03-14 23:28:25 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: LEVEL on LEQ0975979:2 Exception: <Fault -1: ‘Failure’>
I have made a small change. Could you please replace pyhomematics actors.py within the HASS dependency-folder with the actors.py from the fixing branch and report if it fixes the issue?
17-03-17 13:59:01 ERROR (MainThread) [homeassistant.setup] Error during setup of component homematic
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/setup.py”, line 187, in _async_setup_component
None, component.setup, hass, processed_config)
File “/usr/lib/python3.4/asyncio/futures.py”, line 388, in iter
yield self # This tells Task to wait for completion.
File “/usr/lib/python3.4/asyncio/tasks.py”, line 286, in _wakeup
value = future.result()
File “/usr/lib/python3.4/asyncio/futures.py”, line 277, in result
raise self._exception
File “/usr/lib/python3.4/concurrent/futures/thread.py”, line 54, in run
result = self.fn(*self.args, **self.kwargs)
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/homematic.py”, line 241, in setup
from pyhomematic import HMConnection
File “/home/homeassistant/.homeassistant/deps/pyhomematic/init.py”, line 2, in
from pyhomematic.connection import HMConnection
File “/home/homeassistant/.homeassistant/deps/pyhomematic/connection.py”, line 3, in
from pyhomematic import _hm
File “/home/homeassistant/.homeassistant/deps/pyhomematic/_hm.py”, line 11, in
from pyhomematic import devicetypes
File “/home/homeassistant/.homeassistant/deps/pyhomematic/devicetypes/init.py”, line 2, in
from pyhomematic.devicetypes import generic, misc, sensors, actors, thermostats
File “/home/homeassistant/.homeassistant/deps/pyhomematic/devicetypes/actors.py”, line 7
^
SyntaxError: invalid syntax
17-03-17 13:59:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/lib/python3.4/asyncio/tasks.py”, line 237, in _step
result = next(coro)
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity.py”, line 200, in async_update_ha_state
“No entity id specified for entity {}”.format(self.name))
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity Dining Room
Could you please double-check that there has been no error during the transfer of the file? When pushing changes to the repository files are automatically checked for valid syntax, and I didn’t get any error. Hence the error must have been introduced later.
I believe the messages you see are something that’s new with 0.40.0. Haven’t upgraded yet.
Anyways, does the dimmer now work as you would expect it to work?
The dimmer works, yes. But it seems that the status is not returned correctly. While the slider works correctly, the switch is returning to off, even though the lights remain on.
Could it be, that you have restarted the CCU while HASS was running? Switches not displaying the actual state often is caused by HASS not receiving the updates the CCU sends to HASS. Which is the case after the connection between HASS and the CCU has dropped (for whatever reason).
If this behavior persists, then the problem this time probably is on the HASS side.
Well, you are right again - after running in some issues with the XML extension I reinstalled and rebooted the CCU without rebooting the Hassbian Pi. Now, it works fine.