I tried the recipe for changing the names in the history graph, but I can’t get the ‘heating’ part to display. Current and Target both work.I have this:
Thanks interesting I will investigate that. I was trying to use same method as the receipt for the heating but create a binary sensor for hot water. I cannot get it to work for some reason as per my code above.
I love this integration - I’ve been using is for almost as long as I’ve had my HA setup - so a good year. It’s great being able to access features that the native app doesn’t expose - like the signal strength!
However, I’ve had the same issue described by PistolPete - of not being able to remove devices. I had a TRV that I removed from the Wiser hub and moved to a new room and now it shows up twice. I have restarted both the integration and HA several times and both ‘devices’ are still there. There does not appear to be a standard way to remove any of the devices manually in HA, and there are several discussion threads around the issue where the current policy seems to be that “the integration is responsible” - although an exception was made for MQTT. Can you please provide instructions for how to remove orphaned iTRVs?
Is it the same reference than this Drayton branded one? (Schneider Electric bought the company in 2014)
Second naive question, as all Wiser devices communicate in ZigBee, having some Danfoss eTRV (also ZigBee) do you think it is possible to pair the Wiser gateway with non wiser ZigBee devices? Anyone tried?
Thanks to the creators of the integration! Looks amazing! One thing I wanted to ask is whether it is possible to “override” the integrated temperature sensor of the TRV and use readings from another temperature sensor instead? I suppose how it is done with the Wiser room thermostat but using a different sensor.
I received an email within the last few days from Wiser stating their app has a new name and expect changes in the coming months. It also said new firmware will be rolled out within a couple of days, maybe something has changed in the API they use?
ah, see my bad as normal, yep after latest intergration update all battery levels disappeared, uninstalled the intergration and removed all trace of it, then reinstalled done secret key etc control works for the valves again but i have still not battery or signal sensors.
So today I tried a rollback and still not all entities are showing up, I have all the valves etc, just have lost battery levels and signal strength
Ok so I figured it out before update I had added wiser smart plugs into the app, they have caused the battery state and signal state of all heating elements not to show up in home assistant. because as soon as I went into wiser app and removed the plugs and reloaded the intergration the entities have showed up again…
Edited for a 2nd time as typing on the phone I should just stay clear of!!!
Hi all. Long time use of this integration and absolutely love it.
I hope someone can help me with this simple thing I’m trying to achieve. I’m trying to use history_stats to track the number of hours hearing is on for a given period of time. Basically tracking sensor.wiser_heating, but as we know history_stats uses binary sensors. However, sensor.wiser_heating doesn’t have an attribute one can use directly to get on/off state. Surely I’m missing something simple. Can someone point me in the right direction?
Is anyone else encountering this while calling set_schedule?
ERROR (MainThread) [custom_components.wiser.const] Error saving schedule file. Error is type object 'YAML' has no attribute 'save_yaml'
and this while calling get_schedule:
ERROR (MainThread) [custom_components.wiser.const] Error loading schedule file wiser_schedules/nursery_guest.yaml. Error is type object 'YAML' has no attribute 'load_yaml'
ERROR (MainThread) [custom_components.wiser.const] Error loading schedule data from file