NOTE!!! (this is now resolved)
I am getting reports that the new version is consuming too much memory and/or CPU so the app is at risk of being killed (most likely if you have HP2019). If you have not tried the test version yet, please do not install the test version before I have resolved these issues.
Version 0.22 is now available for testing
What is new:
- Added a new device named piggy_charger that will replace the current charge control. From now on the charger device must be installed to control chargers. It will no longer be possible to create the old flows for charge control as these will be deprecated soon. They will still work for a limited time during the transition.
- Added a video stream to the charging device to give feedback during the setup phase and the charging phase.
- Added json-token for charging.
- Added an image-token for the camera interface
- Added phase and voltage selectors for the main fuse.
- Minor ui-changes
- Improvement in reliability for the setup interface.
- Bugfix: Removed forced crash when an invalid state was detected on MeterUpdate
- Added support for:
- com.scinan.api:SASWELL_THERMOSTAT
- com.tesla.car:battery
- net.filllip-namron:451275_X
- no.osoincharge:water-heater
- no.thermofloor:Z-HAN2
This test version will stay in testing until this checklist has been completed. Please help with feedback.
Note:
If you have issues with this test version, please install the stable version over the test version. There is no difference in settings so it’s completely safe to go back to the stable version.
Resolved issues:
(improved in 0.22.2) A crash might occur due to high memory usage- (improved in 0.22.2) A crash might occur due to high CPU usage
- (fixed in 0.22.2) The flow “Stop charging ahead of time” has invalid code in it.
- (fixed in 0.22.2) The image stream of the charge device halted when there was no power prices
- (fixed in 0.22.2) Fixed an error in the bottom two lines of the charge controller images.
- (fixed in 0.22.2) Fixed graph status outside of charge plans
- (fixed in 0.22.2) Charging was not started due to not all settings being updated when a charge controller is added
- (fixed in 0.22.2) device.changePowerInternal is not a function
- (fixed in 0.22.2) Added support for forcing the charger mode on or off according to the mode state and override controls
- (fixed in 0.22.3) The camera image may during initialization show an invalid image for a power supply flow to be created when it is not needed.
- (fixed in 0.22.3) When resetting the charge controller state a timer was not killed so it would cause the timer to crash after a while.
- (fixed in 0.22.3) The charger testing was waiting too much and could seem to hang in the camera interface during the trigger test
- (fixed in 0.22.4) The flow based controller showed the text (timeout is not a property of null)
- (fixed in 0.22.4) May crash on init with the message: “Error: flowtoken_already_exists” if the device is initialized more than once. (e.g. app is disabled and then enabled again)
- (fixed in 0.22.4) When the response test for charging times out it may display (null > 300)
- (fixed in 0.22.5) Uninstalling the device caused ‘Error: device_not_found’ crash.
- (done in 0.22.6) Added feedback that a car needs to be connected in the validation test
- (fixed in 0.22.7) The app doesn’t run the onChargeStart / onChargeEnd commands during testing of chargers
- (fixed in 0.22.7) The app doesn’t run the onChargeStart / onChargeEnd commands during charging
- (fixed in 0.22.7) Firefox and iPhone will cache the first image instead of the latest image, which makes the camera interface look wrong. (changed to a descriptive image for the first image)
- (fixed in 0.22.7) Fixed the video display when having always on mode.
- (fixed in 0.22.7) Price data is not always fetched for the charger device.
- (added in 0.22.7) Changed the waiting images so it’s clearer when to wait and how long.
- (added in 0.22.7) Change the final validation cycle so it doesn’t say failed “on” test. Instead, it should say “Congratulations, all tests passed, you may now turn the controller on.”
- (updated in 0.22.8) The validation procedure no longer shows as failed if the controller is turned off (now it shows informative that you can turn it on)
- (fixed in 0.22.8) The app crashed when removing a charge controller device.
- (fixed in 0.22.8) Fixed validation check for flow charge controllers (didn’t check the state)
- (fixed in 0.22.8) Fixed issue where an uncontrolled charge controller could not be turned off
- (fixed in 0.22.8) When marking a charge controller as not controlled in the app settings the device was not automatically turned off.
- (fixed in 0.22.9) Added workaround for bugs in the iOS Homey app when it comes to refreshing images.
- (fixed in 0.22.10) Voltage and phases selected during pairing is not stored
- (added in 0.22.10) When enabling a charge controller, the old direct control is now disabled
- (added in 0.22.10) If enabling a charge controller in device settings, then give feedback and do not enable it if the validation has not been done.
- (fixed in 0.22.10) Made sure Tesla is not listed as a prioritized device (only the charge controller should be listed at the top)
- (added in 0.22.10) Allow selection of battery update already in the pairing process.
- (added in 0.22.10) Add images to show how to set up flows. The images should be available in the device pairing.
- (added in 0.22.10) Made sure the validation procedure fails if the device is being controlled by other sources (during validation).
- (added in 0.22.11) Added image token for camera interface
- (fixed in 0.22.12) The time zone of the charge controller camera device is displayed incorrectly.
- (fixed in 0.22.12) When using charge x cheapest hours the charging can continue after the charge cycle is complete if more hours was requested than the length of the charge cycle.
- (fixed in 0.22.12) The price graphs for charging were always scaled from 0.
- (fixed in 0.22.12) Fixed status indicator when aborting an already started charging cycle.
- (fixed in 0.22.12) Fixed issue where the last part of the charge plan could disappear from the video interface
- (fixed in 0.22.12) The cost of charging was displayed with a 1000x too high value.
- (fixed in 0.22.12) Toggling of flow devices didn’t work.
- (fixed in 0.22.13) Fixed 2 crash bugs when setting target_power and measure_battery to negative values
Known issues in version 0.22.14 and planned improvements (not published yet):
- (added in 0.22.15) Disabled the uiQuickAction for the charge controller
- (added in 0.22.15) Added tag for active limiters
- (added in 0.22.15) Add timestamp on the generated images
- (fixed in 0.22.15) Made sure two chargers work smoothly together
(not added yet) Add flow to charge up to x % battery- (not added yet) Improve the estimate on how long a charge cycle will take.
