Sounds odd… how should I know which of the on options to use then?
Yeah, it’s a good point, but I already added the possibility for on/off devices and heaters so why not. Although I am a bit unsure how to proceed, so I sketched down a proposal at Add support for Easee car charger and generic charging devices · Issue #4 · frodeheg/no.sparegris · GitHub Please feel free to review and add further suggestions there.
How does the setting for price work? On compared to off if emergency. Seems like the latter never turns device on, only off if over treshold?
Hi @foni , you can find a description for that if you click here:
This is a readout value, you can’t set it.
The Bluelink device provides flow cards for starting and stopping charging.
So. Turn on/off shold be used for swtching heating, varm water etc. on/off depending on price? If on and max power limit is reached will it then be turned off and on again when there are available power? And where does the insight get the current price from? I have selcted NO1, current price dhows up as 0,82321 kr/kWh, but tibber shows current price as 225 øre.
Right, it was read-only, I didn’t notice.
But I see there is one writeable capability named “charging”, So I can use this.
However I cannot see any power-meter readings or controller, so it’s only on/off and it uses what it uses, right?
If it has a thermostat capability I would recommend you to turn on temperature control, this will be much more convenient for price control.
Yes
The prices are fetched from Entsoe, it should be the same prices as Noordpool except in euros. I use the day to day conversion rates from Norges bank to convert to NOK. Then on top of that, VAT and grid cost is added.
However… as you speak about it… I’m not sure if I did reset the prices when you change price zone. So maybe you have discovered a bug. Let me know if the prices are still off in 24 hours.
EDIT: I checked the code and it is indeed a bug. I will fix it in the next version. You can track it here
That’s right!
Version 0.18.2 is now out for testing:
Support for new devices:
Someone sent me a few device lists that I should add support for, but I need some help understanding this so some feedback would be great:
se.husdata:H60 - This is a thermostat device without on/off. Neither does it have a mode so I do not know whether it always heats or if it works in auto mode (heating + cooling).
com.home-connect:dryer - I will add this to the ignore-list as I see no reason for PB to control this device (neither does it appear that it is possible given the limited capabilities it has)
com.fibaro: FGWPE-101 - Will be added
I also got the following feedback:
target_temperature OutOfRangeError: 39 is greater than 35 (out_of_range)
Can whoever sent this report mention which device this was for? Was it an experimental device? If so, then I need a device report for it… All supported devices have different min/max caps, so I need to know the device before adding it to the supported list.
Finally I got this report:
Validate error: TypeError: Cannot read properties of null (reading ‘length’)
Please elaborate on what you did before this report was sent, that will ease my debug considerably.
Whoever is sending reports about the device
please note that I did add improved reliability feedback in the test version so you will get more feedback from this. Other than that Your device seem to be very unreliable and unresponsive from the log, I would like to know if this is a common thing for this device. Please get in touch so I can understand how we can improve this.
I wonder if I should make the email-field for device reports required? so I don’t have to spam all this feedback through the forum?
App seems very promising - now I am faced with a dilemma: should I switch to this app for all my power control needs: floors and hot water, or use my already working advanced flows… One advantage with my flows is that everything is logged to PaperTrails, so I know exactly what is going on.
I ran into an odd issue after I installed Piggy Bank last night: I activated it, saw that my 4 floors (HeatIt Z-TRM3), heat pump (Sensibo) and water heater (Aeotec switch) were all added and controllable. But I did not configure anything, except hook up the output from Pulse to it.
Today I noticed that my Aeotec Heavy Duty Switch (hot water) automatically turned back on 2-10 seconds after I turned it off from Homey, or from my flows - and since nothing was logged, I somehow thought the Aeotec was not functioning right. However, once I de-activated Piggy Bank, the Aeotec would switch off and stay off as commanded. I have now re-activated Piggy Bank, but turned off the Aeotec in its options. I am sure this behavior is intended, or unavoidable. I will study the Piggy Bank configuration further and see if it can replace my flows. I am sure it can, it’s more a matter of throwing away my existing flows or not 
It’s a very self-willed pig. It doesn’t like competition 
I may add more options later if someone fancy more configurability.
Not sure if it’s a bug or not, but I noticed some weird behavior today.
At 2pm today, a few devices was turned off. Nothing unusual in itself, but the devices that were turned off did not reflect the priority I have set up in the app.
The marked devices did turn off, while the rest remained on. So my top priority devices were turned off, while my lowest priority devices remained on. One of the lowest priority devices was drawing power at the time. So did my top two.
Are there other factors taken into consideration other then priority order, when the app decides to turn a device off, or is this a bug?
I’d really welcome a flowchart, pseudocode or something which clarifies why something is off or on. I keep seeing cases which I struggle to understand.
Or a device status option on the devices screen, which explains/logs the last few actions taken on a particular device.
Example:
I’d like my hourly limit at 5kWh.
Heat pump device is “always on” (top priority) + “change temp 0”.
Total consumption is safely below 5kW.
Why would PB keep toggling the device on and off just a few seconds apart? (I think it started happening soon after a reboot.)
Raising limit to 10kWh stopped it.
If it keeps happening without my supervision, I worry about wear and tear on the device.
This is my recipe on weird behaviour:
If a device does not respond:
When the prioritization logic tries to find the least priority device to turn off, it only search through the devices that are not marked as problematic. This is to make sure we can reduce the power the power before it is too late.
So if you see any devices in your home screen with a low reliability this could be it. If not, it could still be. You can check the reliability by going to the device reporting and generate a report because reliability is written there (e.g. reliability 0.9 = 90%)
having said that, the reliability checking is quite new so it may not be working properly. Especially the part that tries again every 5 minute is a bit untested as all my devices are 100% reliable, I need someone with unreliable devices to give me feedback
I think you may have encountered a bug, this should not happen…
It’s being tracked here
Not sure I understand what you mean here.
If I create a report for the devices, they all give a reliability of 1. Guess this means 100%.
I can’t see any way to reduce this or mark a device as problematic?
Just to check, The priorities you observed, did they by any chance fit with the priorities for another mode?
No, same priority for all modes. Don’t use the mode function at all actually, but checked the settings for them anyway, and they are in the same order.
Ok. If it was related to lost signals then it could be a one time incident. If it doesn’t resolve then we probably should make a bug report at it here: Issues · frodeheg/no.sparegris · GitHub
