Today I finally received my Pow-K+ HAN port reader which I ordered before Christmas as a gift to myself. Also before Christmas, I prepared for this project by sending an e-mail to N1 (my power grid company) requesting the needed encryption keys. Shortly after, I received my GPK 60 and GPK 61 keys and information that they had activated the HAN port on my power meter.

The waiting time was hard, but worth it. I have been very excited about this product, and now I need to share why.

Inside the envelope I found my board:

I immediately realized that I must have made a mistake when I placed my order, since I didn’t have anything to hold or cover this board. Luckily, the STL file for the 3D model is freely available. So I asked a friend for help, who happens to be quite proficient and well-equipped when it comes to 3D printing. So a few hours later I could pick up a nice holder for the board.

Installation

In the meantime I had also received confirmation that this board doesn’t need power from an external source, so can simply be plugged in. Like this (the cable on the picture is not related to this module):

Configuration

And now the impressive part – the configuration. Through the big hole seen on the picture a small button is accessible. After holding it for a few seconds, the module created its own access point, and I could connect to it and make the initial Wi-Fi configuration from my phone (remembering 192.168.4.1 which I had read in the documentation earlier). So I configured my IoT SSID and nothing more, since I planned to assign a static IP from my DHCP server later when knowing its MAC address.

After restarting from this initial configuration, it connected to my Wi-Fi and I could now go to my PC and finish the configuration (and also restart it after configuring a fixed IP address on my router). This required only very few steps, like entering the GPK 60 key as “Encryption key” and the GPK 61 key as “Authentication key”. I also had to select parity, which for Denmark is 8N1. Already at this point I was able to see some useful live data on the main webpage. Literally it was fully working and showing data within a few minutes from plugging it in for the first time.

Now it was time to configure MQTT so I could integrate the meter with my home automation and start logging values in my database. So I went to the MQTT configuration page and entered the hostname of my MQTT broker, a publish topic (I chose “omnimeter”) and “Raw values (minimal)” as payload. That’s it. On my openHAB server, which is also hosting mosquitto, I could then have a peek at the published data:

mosquitto_sub -h localhost -t omnipower/# -d

So with a few more minutes of configuration in openHAB, I started to receive the data I have been so eager to get access to. Like this – from log perspective:

2022-12-29 22:59:52.667 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Omnipower_RSSI' changed from -61 dBm to -62 dBm
2022-12-29 23:00:02.716 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Omnipower_Phase3_Voltage' changed from 238 V to 237 V
2022-12-29 23:00:02.730 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Omnipower_Active' changed from 540 W to 563 W
2022-12-29 23:00:07.901 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Omnipower_Accumulated' changed from 14510.99 kWh to 14511.57 kWh
2022-12-29 23:00:07.928 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Omnipower_Active' changed from 563 W to 499 W
2022-12-29 23:00:14.096 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Omnipower_Active' changed from 499 W to 569 W
2022-12-29 23:00:22.610 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Omnipower_Active' changed from 569 W to 520 W

For now, no graphs, just integration. And a sitemap as seen from the openHAB Android app:

Conclusion

I’m very impressed by this product because it just works, and without any issues when installing and configuring it. Meter configuration, Wi-Fi configuration and even MQTT just worked without any hassle or problems. Thank you Egil Opsahl and Gunnar Skjold for making this possible, and I can only give my warm recommendation of this product.

Oh, I forgot to mention that Pow-K+ will receive data every 10 seconds and can be purchased for approximately a third of the price of a SmartMe HAN module which has a cloud dependency (basically making it an inferior product). And it’s Open Source!

Lauritz Knudsen by Schneider Electric just released a range of new ZigBee-based products for the Danish market, and today I got my hands on the LK Fuga Wiser Wireless Dimmer:

This dimmer is ZigBee-certified and should work with any ZigBee-gateway (like Philips Hue or IKEA Trådfri) as well as their own Wiser Gateway, which was also introduced in Denmark this week. And which, by the way, seems to be replaced soon by this Wiser Basic Hub.

My expectation is that this dimmer should identify itself as a dimmable light and work the same way as a Sunricher dimmer or any Philips Hue, IKEA Trådfri, Osram Smart+ or other dimmable ZigBee bulb. In other words, I would not expect any problems adding this dimmer to my Philips Hue bridge. So let’s see if my expectations will be fulfilled…

Pairing the device with Philips Hue bridge was painless. After three fast clicks on upper left button, it was found by the bridge as a dimmable bulb. Perfect. Now tried to control the connected LED bulb through the Philips Hue app and experienced some weird behavior: Light cannot be switched off! It can be switched on and dimmed up and down without much delay, but it can’t be switched off. When using the buttons on the dimmer to control the light, there is some delay until reflected in Philips Hue, but this is somewhat expected. Within a minute it will be there.

Compatibility/integration

Now decided to investigate this switching off issue a bit more, so added the dimmer to openHAB through the Hue API to monitor exact values with timestamps etc. and try to control it with specific values. It turns out that using openHAB I was able to switch it off by simply setting brightness to 0 like any dimmable light.

So without openHAB, I thought, will I be able to somehow switch it off from within Hue itself? I configured one of my Friends of Hue switches to control the dimmer, and without any problems was able to turn it on as well as off.

Last, I tried configuring a Philips Hue motion sensor for controlling the room where I added the dimmer. This doesn’t work either. Just before it’s about to switch it off, Hue dims a tiny bit as a warning. This part works, but it stays like that and doesn’t switch off.

So it seems that the problem is a very specific compatibility issue with the Philips Hue app and accessories – perhaps some slight difference in the way it turns off lights and dims to 0%. I have ruled out my bridge/configuration since the same problem has been reported by others. LK Dimmer FW version: 001.002.021.R.

Digging deeper

In openHAB the dimmer is represented by a single item, Brightness. However, this kind of item can be used as a dimmer/slider as well as a switch. So in a sitemap I tried to create both types to be able to compare the difference, since dimming to 0% actually works. Here is the result:

Switch it on:

2021-03-07 15:37:26.109 [INFO ] [openhab.event.ItemCommandEvent ] – Item ‘Wiser_Brightness’ received command ON
2021-03-07 15:37:26.129 [INFO ] [penhab.event.ItemStatePredictedEvent] – Item ‘Wiser_Brightness’ predicted to become ON
2021-03-07 15:37:26.136 [INFO ] [openhab.event.ItemStateChangedEvent ] – Item ‘Wiser_Brightness’ changed from 0.0 to 100

Swith it off – this didn’t work:

2021-03-07 15:37:35.408 [INFO ] [openhab.event.ItemCommandEvent ] – Item ‘Wiser_Brightness’ received command OFF
2021-03-07 15:37:35.427 [INFO ] [penhab.event.ItemStatePredictedEvent] – Item ‘Wiser_Brightness’ predicted to become OFF
2021-03-07 15:37:35.434 [INFO ] [openhab.event.ItemStateChangedEvent ] – Item ‘Wiser_Brightness’ changed from 100 to 0

Dim it to 0%, effectively switching it off (this worked):

2021-03-07 15:37:43.178 [INFO ] [openhab.event.ItemCommandEvent ] – Item ‘Wiser_Brightness’ received command 0.0
2021-03-07 15:37:43.194 [INFO ] [penhab.event.ItemStatePredictedEvent] – Item ‘Wiser_Brightness’ predicted to become 0.0
2021-03-07 15:37:43.217 [INFO ] [openhab.event.ItemStateChangedEvent ] – Item ‘Wiser_Brightness’ changed from 100 to 0.0

Did you notice the difference? When setting brightness to “0”, nothing happened. When setting it to “0.0” it works. This should give some indication of the type of bug/incompatibility. Until Lauritz Knudsen hopefully fixes this issue, this can be used as temporary work-around in openHAB:

rule "Wiser work-around"
when
    Item Wiser_Brightness changed to 0
then
    Wiser_Brightness.sendCommand("0.0")
end

This will detect all attempts to switch off the dimmer, also attempts made by accessories like a motion sensor.

Update, March 16th 2021: Although the description above might give some indication about the problem, it’s still only that – an indication. Today I decided to investigate a little deeper to be able to understand the problem without distraction from openHAB. So I created a Hue Developer account to access the Hue documentation and tested directly using the Hue API. Here’s my new finding – this doesn’t work:

URL: /api/<username>/lights/<id>/state
Method: PUT
Body: {"on":false}

But with this body, it works:

{"on":false, "transitiontime":0}

It seems to work with any transitiontime value. As documented:

The duration of the transition from the light’s current state to the new state. This is given as a multiple of 100ms and defaults to 4 (400ms). For example, setting transitiontime:10 will make the transition last 1 second.

To be very specific: It turns off almost immediately with 0, and in 400 ms with the value 4. This is supposed to be the default value, but without it, it doesn’t work. So the Hue app most likely doesn’t include transition time when using the on/off switch, and the same seems to be the case for openHAB. I believe I found the explanation in the binding source code:

           case CHANNEL_BRIGHTNESS:
                if (command instanceof PercentType) {
                    newState = LightStateConverter.toBrightnessLightState((PercentType) command);
                    newState.setTransitionTime(fadeTime);
                } else if (command instanceof OnOffType) {
                    newState = LightStateConverter.toOnOffLightState((OnOffType) command);
                } else if (command instanceof IncreaseDecreaseType) {
                    newState = convertBrightnessChangeToStateUpdate((IncreaseDecreaseType) command, group);
                    if (newState != null) {
                        newState.setTransitionTime(fadeTime);
                    }
                }

So when brightness is set from a switch (OnOffType), the transitionTime attribute is not set, thus it will not work.

With this knowledge work-arounds are possible, although no generic work-around that would fix all integrations. For example for a Hue motion sensor, transitiontime can be added through the Rules API (this has been tested and works):

URL: /api/<username>/rules
Method: POST
Body:
{
     "name": "Wiser motion sensor work-around",
     "conditions": [
         {
             "address": "/sensors/1/state/presence",
             "operator": "eq",
             "value": "false"
         }
     ],
     "actions": [
         {
             "address": "/lights/1/state",
             "method": "PUT",
             "body": {
                 "on": false,
                 "transitiontime": 0
             }
         }
     ]
 }

Update, November 23rd 2021: I’ve created a workaround in the Hue binding in openHAB: https://github.com/openhab/openhab-addons/pull/11572 – it will be included in release 3.2, but a JAR file is also available, and it can be used with 3.1 installations. With this fix, everything works from openHAB, but of course each integration (including the Philips Hue app) will need to provide own workarounds until the LK Wiser bug is fixed.

Power consumption

No post without some mentioning of power consumption. Measured switched off over 24 hours with SparOmeter it used 0.009 kWh, so just below 0.4 W in average. This is exactly as specified in the manual with 0.4 W as max. power consumption. Sunricher dimmer box in comparison uses 0.015.kWh in 24 hours, i.e. roughly 0.6 W.

Dimming characteristics

This is probably a difficult topic with a lot of compatibility concerns, but it’s important to know how well this dimmer can actually dim. I don’t have the equipment or knowledge to measure this. I used an IKEA 1000 Lumen LED bulb for testing, and it went from ~15 W to 3.4 W when fully dimmed. In comparison, a Sunricher dimmer was able to dim below 1 W. The bulb used in my test can only be dimmed to ~2.6 W, after that it starts flickering and eventually it will turn off. However, to be able to dim this much, the minimum level should be configurable. This does not seem to be the case with this LK Dimmer, at least not by using the buttons (when not using their own Wiser gateway).

For the same bulb the LK Touch LED 180 IR will dim this bulb to 4.0 W, so here Wiser is a slight improvement.

Price

This dimmer is the most expensive dimmer I have ever seen. LK LED Touch is cheap in comparison, so is IHC Wireless in general. I really hope prices will drop sooner than later in order to sell more. I bought one after waiting for a product like this for years, but won’t be buying more until prices will drop. The same goes for the double relay switch. At the time of writing, the cheapest I have been able to find has a price tag of 899,- DKK.

Functionality

Unfortunately, and this is also the reason for the price tag, almost no competition exists. This is only because of the small Danish market for LK Fuga design. Currently, this is the best solution on the market for LK Fuga, if:

• You don’t have anywhere to put a Sunricher (or similar) dimmer.
• You want to be able to control your light through ZigBee and using a wall switch (without the wall switch taking your light offline).
• You want to be able to control your light always, even when your gateway is down or wireless signal is disturbed.
• You want to be able to control your light without any concern about batteries running low.
• Until switching off bug is fixed: Replace “ZigBee” by “Wiser app”.

Conclusion

I have wanted this product for years. Now that it’s here, I wish it would work better with Philips Hue, and I wish I could use it everywhere in my house. Unfortunately I can’t/won’t because of the price tag. Summary:

• Price: Too high.
• Software: Too buggy (switching off doesn’t work).
• Dimming: Can’t dim as much as some other dimmers on the market, and minimum level can’t be configured.

If LK would fix the problem of not being able to turn off the dimmer without supplying transition time, this would actually be a pretty decent product. Pricey, but decent, and I would instantly install this dimmer in my family room for controlling our PH5 lamps.

It’s been a while since my last post, so just a short one this time. I invested in VELUX ACTIVE with NETATMO in 2019 for controlling my skylights. I knew it was a cloud-based solution with all its cons, and even without any API for integration. This obviously sucks, but suddenly ClientID and ClientSecret was published in an openHAB Community thread, so I no longer had the excuse that I didn’t want to spend time reverse engineering the APK for Android. Now it was just a matter of implementing an integration.

Since I didn’t have experience with Python yet, I decided I wanted to try to use that for an implementation. It was my impression that it had everything I needed: HTTPS, JSON and MQTT. And I was right, so after 90 minutes of google-coding, this is my implementation for fetching my data from my sensor switch (CO2, temperature and humidity). Implementation is based on https://github.com/nougad/velux-cli.

First script is run to get a token which will be used for authentication. Script will ask for the password for the corresponding Velux account:

#!/usr/bin/python3

import getpass
import requests

URL='https://app.velux-active.com/oauth2/token'

# From Android app reverse engineering
CLIENT_ID=''
CLIENT_SECRET=''

# My account
USERNAME='veluxaccount@email.address'

try:
        password = getpass.getpass()
except Exception as error:
        print('Error:', error)

data = {
        'grant_type': 'password',
        'client_id': CLIENT_ID,
        'client_secret': CLIENT_SECRET,
        'username': USERNAME,
        'password': password,
        'user_prefix': 'velux'
}

response = requests.post(URL, data=data)

if response.status_code == 200:
        file = open('token.json', 'w')
        file.write(response.text)
        file.close()
else:
        print('Error:', response)

A file ‘token.json’ will be saved in current directory. Next script will refresh the token, so this must be run once per every few hours. I don’t remember exact expiration period, but it’s in the response.

#!/usr/bin/python3

import json
import requests

URL='https://app.velux-active.com/oauth2/token'

# From Android app reverse engineering
CLIENT_ID=''
CLIENT_SECRET=''

file = open('token.json', 'r')
body = file.read()
file.close()

token = json.loads(body)

data = {
        'grant_type': 'refresh_token',
        'refresh_token': token['refresh_token'],
        'client_id': CLIENT_ID,
        'client_secret': CLIENT_SECRET
}

response = requests.post(URL, data=data)

if response.status_code == 200:
        file = open('token.json', 'w')
        file.write(response.text)
        file.close()
else:
        print('Error:', response)

And finally this last script is run every 5 minutes which seems to be the frequency for new measurements:

#!/usr/bin/python3

import json
import requests
import paho.mqtt.client as mqtt

URL='https://app.velux-active.com/api/homestatus'
MQTT_BROKER='192.168.0.236'
HOME_ID='your_home_id'

file = open('token.json', 'r')
body = file.read()
file.close()

token = json.loads(body)

data = {
        'access_token': token['access_token'],
        'home_id': HOME_ID
}

response = requests.post(URL, data=data)

if response.status_code != 200:
        print('Error:', response)
        exit()

data = json.loads(response.text)
home = data['body']['home']
rooms = home.get('rooms')

if rooms:
        room = rooms[0]
else:
        print('Unexpected response:', response.text)
        exit()

client = mqtt.Client()
client.connect(MQTT_BROKER)

client.publish('velux/hallway/co2', payload=room['co2'], qos=0, retain=False)
client.publish('velux/hallway/humidity', payload=room['humidity'], qos=0, retain=False)
client.publish('velux/hallway/temperature', payload=(room['temperature']/10), qos=0, retain=False)
client.publish('velux/hallway/lux', payload=room['lux'], qos=0, retain=False)

for module in data['body']['home']['modules']:
        if module['type'] == 'NXD': # Departure switch
                client.publish('velux/departure_switch/battery_percent', payload=module['battery_percent'], qos=0, retain=False)
        if module['type'] == 'NXS': # Sensor
                client.publish('velux/sensor1/battery_percent', payload=module['battery_percent'], qos=0, retain=False)

In openHAB I have configured a thing to receive these MQTT updates, so I have them persisted in MySQL, shown in sitemaps, etc.

Inspired by my own LockU2 utility and Useless Box, I came up with a simple and stupid, yet effective, openHAB rule to prevent my kids from watching YouTube when they are not allowed to do so. So first requirement was ability to turn this lock on or off – just added a new switch item for this, and added it to a sitemap.

The rule makes use of the LGTV binding as well as HarmonyHub binding. Without any of these, I don’t think it would be possible to pull off.

Here goes:

rule "Lock YouTube"
when
    Item LGTV_Application changed to "youtube.leanback.v4" or
    Item LGTV_Application changed to "youtube.leanback.kids.v4"
then
    if (Lock_YouTube.state == ON)
    {
        //HarmonyLGTV_ButtonPress.sendCommand("Exit")
        LGTV_Application.sendCommand("com.webos.app.livetv")
    }
end

rule "Enable Lock YouTube"
when
    Item Lock_YouTube changed to ON
then
    if (HarmonyHub_CurrentActivity.state == "Watch TV" &&
        (LGTV_Application.state == "youtube.leanback.v4" || LGTV_Application.state == "youtube.leanback.kids.v4"))
    {
        //HarmonyLGTV_ButtonPress.sendCommand("Exit")
        LGTV_Application.sendCommand("com.webos.app.livetv")
    }
end

This YouTube blocker won’t actually block the YouTube app on the television, but will instead immediately quit the app once it’s launched. If YouType (or YouTube Kids) is already running when activating the lock, it will also quit the app. Update: Changed to use LGTV binding for quitting YouTube – old method commented out.

I almost couldn’t wait for the premiere which was last Saturday morning. I also have a rule in place for generating notifications when the lock has been triggered. After explicitly instructing my son that YouTube was not allowed that morning, only five minutes later I received the first notification that an attempt was made. After that four more identical notifications. Then a final notification that YouTube Kids had also been attempted. Success.

After upgrading UniFi Controller to version 5.12.35 last week, the openHAB binding started having problems with the Online channel. Going from OFF to ON is still detected correctly, but not the other way around. I’m still not sure if this is a problem in the binding, the controller or in my configuration. Only thing I know for sure is that after upgrading the controller image in Docker and the access point firmware at the same time, binding stopped detected our phones disconnecting from the access point.

openHAB is version 2.5.1. I have asked in the openHAB forums, but is still waiting for feedback.

In the meantime I’ve created a work-around using rules. Problem is that once client goes offline, it seems to be excluded from the list fetched by the binding, and channel stops receiving updates. For LastSeen it makes sense, but Online should be updated to OFF, when client is no longer listed. So I used LastSeen to mimic this desired logic in my rule:

var Timer timerUniFiJacob = null

rule "UniFi work-around Jacob"
when
    Item UniFi_OnePlus5_LastSeen changed
then
    if (Jacob_Home.state == OFF)
    {
        Jacob_Home.sendCommand(ON)
    }

    if (timerUniFiJacob === null)
    {
        timerUniFiJacob = createTimer(now.plusSeconds(180), [ |
            Jacob_Home.sendCommand(OFF)
        ])
    }
    else
    {
        timerUniFiJacob.reschedule(now.plusSeconds(180))
    }
end

This rule simply restarts a 3 minute timer on each LastSeen update. When client goes offline, these updates will stop and after three minutes, item Jacob_Home will be set to OFF.