It took me a little time to finally find the right settings for the Homematic module HMIP-MOD-HO (Amazon Affiliate Link) in Yahka. Finally, the garage door control now works via Apple’s Home app and Siri.

Once the device is set up in the Yahka adapter, we focus on the CurrentDoorState -> DOOR_STATE and TargetDoorState -> DOOR_COMMAND data points.

Settings for CurrentDoorState

InOut: ioBroker.State
State: hm-rpc.X.XXXXXXXXXXXXXX.1.DOOR_STATE
Conversion: map
0 -> is simple value 1
1 -> is simple value 0
2 -> is simple value 2
3 -> is simple value 3

Settings for TargetDoorState

InOut: ioBroker.State
State: hm-rpc.X.XXXXXXXXXXXXXX.1.DOOR_COMMAND
Conversion: map
1 -> 0 (don’t check “is simple value”)
3 -> 1 (don’t check “is simple value”)

Der Beitrag Configure Homematic module HmIP-MOD-HO in Yahka for Apple Homekit erschien zuerst auf Pixelfriedhof.

In the analysis, I found that the adapter always failed between 22:00 and 23:00. However, there were no entries in the log, even with Verbose setting. After restarting the Yahka adapter, everything worked as usual again – until the next crash.

I had moved my ioBroker installation including the Yahka adapter from the Raspberry Pi to a Docker container on the Synology NAS a few weeks earlier. I had created a backup with Backitup and then restored it in the Docker container.

In the directory /iobroker_data/iobroker-data/yahka.0.hapdata I noticed that there were four files in this directory instead of the usual two files “AccessoryInfo” and “IdentifierCache”. According to the last modification date, the two superfluous files probably still came from the old installation.

I deleted all four files and restarted the Yahka adapter. The two legitimate files were created again. The problem did not occur again since then.

Der Beitrag Yahka Adapter sporadically without connection – No devices found erschien zuerst auf Pixelfriedhof.

First I looked for the cause of the error in ioBroker and checked the settings of the IoT adapter and requested new certificates. Unfortunately, none of this helped, but it should be tested.

I was only able to solve the problem by deactivating the Alexa skill and reactivating the ioBroker skill in the Alexa app. The best thing is that you do not have to reconfigure your devices in the Alexa app, the previous devices and settings are retained.

After reactivation, all devices will work again.

Der Beitrag “Something went wrong” when operating io.Broker devices via Alexa erschien zuerst auf Pixelfriedhof.

You want to update your ioBroker. Although you have stopped the service with “iobroker stop”, the next command “iobroker upgrade self” fails with the error message “Controller is running. Please stop ioBroker first”.

Solution

ioBroker does not stop properly for some reason. This is related to the new installation routine. Stop IoBroker as follows:

Method 1:

sudo systemctl stop iobroker

Now all services should really be dead and you can continue with “iobroker upgrade self”.
Background: systemctl is the successor of init.d.

Method 2, when running in Docker-Container e.g. on Synology:

pkill -u iobroker

Der Beitrag “Controller is running. Please stop ioBroker first.” – Although iobroker is already stopped. erschien zuerst auf Pixelfriedhof.