(05.04.2020, 00:10)Erwin van der Zwart Wrote: Hi,

You should check if the table content is valid before drilling down deeper...

Code:

if data then
   if data.payload then
      if data.payload.power then
         grp.checkwrite('1/1/1’, data.payload.power)
      end
   end
end

BR,

Erwin

(07.01.2021, 19:12)Rune Wrote: Jørn and stemic01:

Could you give a short brief here about what you could do with Tibber and LM in combination? Did you get this working with Tibber API? Do you translate the hour prices to KNX GA?

(11.01.2021, 21:43)stemic01 Wrote:

(07.01.2021, 19:12)Rune Wrote: Jørn and stemic01:

Could you give a short brief here about what you could do with Tibber and LM in combination? Did you get this working with Tibber API? Do you translate the hour prices to KNX GA?

Hi.  
Group addresses: Yes, I translate the Tibber values into Logic Machine Group Addresses. Per now over the bus-range of addresses, but I plan to change this to virtual addresses treduce the traffic load on the KNX bus. If you plan to show tibber values on a KNX visualization panel you might need to stay in the standard group addresses range.

Tibber integration: Per now I only use this for visualization purposes. Highlighting when prices are high or when consumption are high. Plus trending on prices and consumption. 
So there is no magic going on with cutting power to items, lower heating, stop water heating etc according to prices. But it should be pretty straight forward. It would be pretty easy to make a for exmple a phillips HUE lamp to change color accodring to power prices or current power consumption if you wanted so.  

For electrical vehicle and charging when it is cheap - i do believe that the TIbber / Eeesy charging solution is more streamlined and better (I do not have EV, so I have not tested this). 

The Tibber integration has been working great for me - except one returning issue which is propably a programming error in one of my scripts (Scripts from this thread). It seems like the script either crashes or the Tibber API blocks the connection after some time. I don't know what is the problem, but I usually do the following: 
- Deactivate / activate the Tibber script 
- Restart the Logic Machine 
- Manually change the group address value in Logic machine (example just put in a value "1" in consumption and price. 

One or all of these usually solves the problem.

(12.01.2021, 20:37)Rune Wrote:

(11.01.2021, 21:43)stemic01 Wrote:

(07.01.2021, 19:12)Rune Wrote: Jørn and stemic01:

Could you give a short brief here about what you could do with Tibber and LM in combination? Did you get this working with Tibber API? Do you translate the hour prices to KNX GA?

Hi.  
Group addresses: Yes, I translate the Tibber values into Logic Machine Group Addresses. Per now over the bus-range of addresses, but I plan to change this to virtual addresses treduce the traffic load on the KNX bus. If you plan to show tibber values on a KNX visualization panel you might need to stay in the standard group addresses range.

Tibber integration: Per now I only use this for visualization purposes. Highlighting when prices are high or when consumption are high. Plus trending on prices and consumption. 
So there is no magic going on with cutting power to items, lower heating, stop water heating etc according to prices. But it should be pretty straight forward. It would be pretty easy to make a for exmple a phillips HUE lamp to change color accodring to power prices or current power consumption if you wanted so.  

For electrical vehicle and charging when it is cheap - i do believe that the TIbber / Eeesy charging solution is more streamlined and better (I do not have EV, so I have not tested this). 

The Tibber integration has been working great for me - except one returning issue which is propably a programming error in one of my scripts (Scripts from this thread). It seems like the script either crashes or the Tibber API blocks the connection after some time. I don't know what is the problem, but I usually do the following: 
- Deactivate / activate the Tibber script 
- Restart the Logic Machine 
- Manually change the group address value in Logic machine (example just put in a value "1" in consumption and price. 

One or all of these usually solves the problem.

Thank you for your report.

I got help from a colleague to make a script based on this thread and the only option I need now, is the price per hour. It's working now and it is pretty nice.

(11.01.2021, 21:43)stemic01 Wrote:

(07.01.2021, 19:12)Rune Wrote: Jørn and stemic01:

Could you give a short brief here about what you could do with Tibber and LM in combination? Did you get this working with Tibber API? Do you translate the hour prices to KNX GA?

Hi.  
Group addresses: Yes, I translate the Tibber values into Logic Machine Group Addresses. Per now over the bus-range of addresses, but I plan to change this to virtual addresses treduce the traffic load on the KNX bus. If you plan to show tibber values on a KNX visualization panel you might need to stay in the standard group addresses range.

Tibber integration: Per now I only use this for visualization purposes. Highlighting when prices are high or when consumption are high. Plus trending on prices and consumption. 
So there is no magic going on with cutting power to items, lower heating, stop water heating etc according to prices. But it should be pretty straight forward. It would be pretty easy to make a for exmple a phillips HUE lamp to change color accodring to power prices or current power consumption if you wanted so.  

For electrical vehicle and charging when it is cheap - i do believe that the TIbber / Eeesy charging solution is more streamlined and better (I do not have EV, so I have not tested this). 

The Tibber integration has been working great for me - except one returning issue which is propably a programming error in one of my scripts (Scripts from this thread). It seems like the script either crashes or the Tibber API blocks the connection after some time. I don't know what is the problem, but I usually do the following: 
- Deactivate / activate the Tibber script 
- Restart the Logic Machine 
- Manually change the group address value in Logic machine (example just put in a value "1" in consumption and price. 

One or all of these usually solves the problem.

(09.08.2021, 23:01)Erwin van der Zwart Wrote: Try this:

Code:

value = resp.data.viewer.homes[1].currentSubscription.priceInfo.today[1].total
grp.write('33/0/0', tonumber(value) * 100)

(06.01.2023, 10:00)mjaanes Wrote: Tibber seem to have updated their API (see  Tibber Developer).
Has anybody updated the LUA script to read consumption from HAN port via the Tibber API? 

My script has stopped working with the message:

string: connection failed: Websocket Handshake failed: Invalid Sec-Websocket-Accept (expected ******* = got nil)

(10.01.2023, 10:52)admin Wrote: Use updated user.websocket library attached to this post.

Change token / homeId as needed. Add object updates at line 78. Use grp.checkupdate or grp.checkwrite so that LM is not overloaded with unnecessary duplicate values.

Code:

ws = require('user.websocket')
json = require('json')
http = require('socket.http')
ltn12 = require('ltn12')

token = '12345'

payload = json.encode({ query = '{viewer { websocketSubscriptionUrl } }' })

res = http.request({
  url = 'https://api.tibber.com/v1-beta/gql',
  method = 'POST',
  headers = {
    ['Authorization'] = 'Bearer ' .. token,
    ['Content-Type'] = 'application/json',
    ['Content-Length'] = #payload,
  },
  source = ltn12.source.string(payload),
})

res = json.pdecode(res)

if type(res) == 'table' and res.data then
  url = res.data.viewer.websocketSubscriptionUrl

  client, err = ws.client('sync', 30)
  client.protocol = 'graphql-transport-ws'
  res, err = client:connect(url)

  query = [[
  subscription {
    liveMeasurement(homeId: "a-b-c-d") {
      timestamp
      power
      accumulatedConsumption
      accumulatedCost
      currency
      minPower
      averagePower
      maxPower
    }
  }
  ]]
else
  res = nil
end

if res then
  res, err = client:send(json.encode({
    type = 'connection_init',
    payload = {
      token = token
    }
  }))

  client:receive()

  ts, tu = os.microtime()

  res, err = client:send(json.encode({
    id = ts .. '-' .. tu,
    type = 'subscribe',
    payload = {
      query = query
    }
  }))

  while true do
    data, opcode, _, _, err = client:receive()

    if data then
      if opcode == ws.PING then
        client:send(data, ws.PONG)
      elseif opcode == ws.TEXT then
        data = json.pdecode(data)

        if type(data) == 'table' then
          -- update objects here
        end
      end
    else
      log('receive failed: ' .. tostring(err))
      break
    end
  end
else
  log('connection failed: ' .. tostring(err))
end

if client then
  client:close()
  client = nil
end