For those users out there that has Tibber and Pulse for monitoring their power consumption you can find a web socket implementation for receiving live updates here.
Features:
Live power consumption pushed directly from the Tibber API
An estimate of the power consumption within the current hour based on actual consumption and current power consumption
A few concerns: I have not been able to find a way of controlling the update frequency from the Tibber server, hence I am a bit concerned with the hub being bugged down with requests. I have added a switch feature so that the websocket can be opened and closed conveniently from a dashboard if needed. If the websocket fails it will not auto reconnect, this should be easy enough to implement, and might be added soon.
Norway is about to implement a new price scheme for the fixed part of the electricity bill, where you are charged different fixed rates based on maximum hourly consumption. Hence, my idea is to also implement an app that turns off power hungry appliances if the hourly consumption potentially will break into a new price limit.
Love it! More stuff for Tibber is allways nice. (If I can keep Tibber with those insanly high electric prices we see right now, but that is another story… )
An updated version is available in the repository with the following features added:
Configurable run schedule (continuous, every 3 min, 5 min, 10 min, 15m min, etc.)
Auto reconnect on failed connection.
Motion sensor output for notifying other devices/apps in the system about possible over consumption.
I use the motion sensor output to trigger a Rule Machine app that turns off my domestic hot water heater to save power. The app then monitors the available power and turns on my water heater again when there is enough power for the water heater to run.
Ivar
Thank you l making this code available to the community. This is my first try in using the Hubitat and with your very good instructions I got this working on first try. Still have not figured out how to access the different output variables on the tiles though or to use this information for something useful like controlling the heaters etc.
Gunnar
Another "interesting" number is to look at is the calculated remaining available power to go over the set threshold, i.e. how much power can you use before you reach the threshold:
Tibber is discontinuing the current websocket sub-protocol, hence the TibberLiveConsumption driver has to be update. Updated version can be found here for those of you using this in Hubitat:
Hi Ivarho, do you see a way to expand your driver to include the functionality of the price? In the Tibber app you can see the price per hour, so you could have an existing battery storage automatically charged with a switch whenever the price is cheapest. Merci and greetings.
Can someone please explain to me how this is upposed to work, because I can't get it going. If I install the outlet controller app I get error "expecting ')', found 'command' @ line 26, column 5." and if I install the price switch controller (which I don't understand how it differs from the outlet one) it installs, but I get an error in the log after setting it up "java.lang.NullPointerException: Cannot invoke method currentValue() on null object on line 117 (method turnOffSwitch)"
I'm fairly new to Hubitat so I guess I'm doing something wrong, but I just can't figure out what.