Well, perhaps I am getting it wrong. Currently I activate the A/C and set it to 21C. However, that doesn’t automatically also start the rear window heating. For that I have to push the “button” on the screen to start the rear window heating. It is included in “Defrost” which I can start from the app, but that means the temperature is set to 28C or 30C or whatever the maximum is.
Perhaps the work around is to activate “Defrost” and after that lower the temperature to 21C.
You could simplify it by not exposing all properties. Just offer one schedule (fixed id) with an add, an update (=add but the schedule already exists so gets updated instead of created) and a remove. Lat/lon could be Homey coords and days_of_week could default to all. Then all you have in the cards is:
start_time (not optional, time)
end_time (not optional, time)
one_time (boolean), default true
enabled (boolean), default true
Card: Set charge window (enabled=true) with fields:
start_time
end_time
one_time
Optional card: Charge until (start_enabled=false, end_enabled=true, enabled=true) with fields:
end_time
one_time
Optional card: Charge from (start_enabled=true, end_enabled=false, enabled=true) with fields:
start_time
one_time
Card: Remove charge schedule (no fields)
And the same for preconditioning.
The current cards are either/or: if you use one, all the others get disabled. This messes up any existing schedule you had in the app. Quite inconvenient. Also, you can never have a charge plan with a start and a stop time. This doesn’t work for smart charging, where you want the car to charge during a specific window. There’s also no way to remove the schedule you created, which will quickly make a mess in the Tesla app because they keep accumulating, each time you use a different time… So the new cards are badly needed!
Hi, can you please refresh the widget (refresh button or reopen the dashboard). Then directly send a diagnostics report from app settings page. I think there is a data conversion error. Thanks.
Perhaps there is a capability with an invalid (unexcepted) value that’s causing an error in the HTML view. Can you please check the device data (especially battery device) if there is somewhere a null value (shown as - sign). Otherwise it’s hard to debug it because ir’s just a html frame in the Homey dashboard.
Yes, I have an old NewMotion charger (before Shell Recharge). I want to wait to replace it until there are chargers available with support for bidirectional charging and right now certification and rules aren’t clear. So it’ll have to serve me a few more years. Then I can replace the charger and switch to a better CPO. Until then I’m stuck with 50five.
If this has been answered before, I’m sorry, but I can’t seem to find anything about it..
My qestion is:
Is there any if cards, that can check if the doors on the car is closed (not locked, but closed)
I’d like to make a flow that goes like this:
WHEN “My button is pressed”
IF “Car doors are closed” <------ this is the one I’m wondering about
Then “Lock doors”
Edit: Nevermind. The whole idea waas to have a button that could also unlock the doors, and after 5min it’d check if the doors where closed and then relocking them.
But I see now that there aren’t any unlocking “THEN” cards so I guess its not possible then
There is no condition for closed door I think, only for locked state (true/false). Only trunk/frunk has a capability that holds the state. I will check this tomorrow.
For doors lock/unlock commabd, use the “(…) doors” card from car device and select “lock” or “unlock” inside the card.
Perhaps you can use “user present” trigger cards. That triggers if a driver is present or leaving the car. I’m not really sure, but I think it’s based on car key presence.
Added dynamic Homey/domain registration.
If the domain registration is not possible (e.g. 2nd hand Homey with already registeres domain), then a client id specific domain is used.
@Tariq FYI and test. The domain registration should work now