asantaga / wiserHomeAssistantPlatform

Platform and related climate/sensors to support the Drayton Wiser Home Heating System
MIT License
234 stars 44 forks source link

General Discussions #70

Closed asantaga closed 2 years ago

asantaga commented 4 years ago

Hey all, feel free to use this issue to ask questions ideas for our next release 2.0./

For bugs please log an issue For other queries either use this issue or the Home Assistant forum https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration/80965/47

thanks!

asantaga commented 4 years ago

@djashjones I sympathise , I dont think its as bad as that but sure I get the idea.. For now just install a single HA and use our wiser component.. then never upgrade it :-)

If you want help building the hubitat integration just let us know, we'll help as much as we can

phixion commented 4 years ago

I'm finding HA with every update, something breaks and hence high maintenance, So I am moving all my devices (z-wave & Zigbee) over to Hubitat. I like HA, it is the best software out there but it is just not stable enough.

I'm considering moving away from homassistant aswell for the same reasons. HA might be good to get started with automation but is far away from a reliable core of a smart-home. I get to a point where its causing a lot of maintanance, and with the upcoming changes to yaml, I have no reason to stick with HA. I realize I dont really need a GUI so im considering a node-red approache for my devices or hubitat but I have to learn either. Does hubitat go well with esphome or tasmota and is easy to figure?

djashjones commented 4 years ago

Not sure about that as I will replace my tasmota devices to z-wave But I do have a node-red automation turning on a light via mqtt

mrvladis commented 4 years ago

I personally use HA as front-end only, while NodeRed for any automation I have.

djashjones commented 4 years ago

I just set up 5 of my tasmota shellies into Hubitat and they to work so far, so mqtt is not required now. Got one less node-red automation to sort and for me that would make node-red redundant.

asantaga commented 4 years ago

I installed nodered once, played with it and it was nice.. but is it much better than the ootb HA automations?? I'll have a tinker though as I hear about it a lot...

mrvladis commented 4 years ago

I installed nodered once, played with it and it was nice.. but is it much better than the ootb HA automations?? I'll have a tinker though as I hear about it a lot...

I'd say it is much better. It is more like a Logic Apps, where you can just use graphic blocks to define the flow or add some Javascript functions if there is not enough functionality in the flows.

Before this module has been released for Wiser - I was just using Nodered to get a Json and was pushing it to MQTT for HA. I did switch to the current plugin in HA, but all my automation for Wiser in Nodered still fully autonomous.

While for other components, like bulbs, lite switches and other stuff from Xiaomi - I use HA in node-red as source of data and action point.

asantaga commented 4 years ago

Just listening to a tutorial on u tube.. Its very familar to me, actually very much like the integration bus's Im used to using at work..

Im happy with HA Automations but I will admit they are limited and messy to create , maybe NodeRed is a better solution. For example, It would be nice to send a message when a trv's battery is low. Yes it can be done (and Ive done it) but it was a bit of a pain to do.. Here with NR I think I can just write a javascript loop...

In many ways I think HA could dump their automation editor and just delegate to NR...

good discussion , thanks!

mrvladis commented 4 years ago

For example, It would be nice to send a message when a trv's battery is low. Yes it can be done (and Ive done it) but it was a bit of a pain to do.. Here with NR I think I can just write a javascript loop...

Yep, but you don't even need a loop, as you'll be able to capture the state change. I didn't yet bother to create notifications for batteries, but did it for water leak sensors. Looks nice and simple: image

asantaga commented 4 years ago

Niiiiiiiiiiiice

Im sold... !

On Thu, 4 Jun 2020 at 13:11, mrvladis notifications@github.com wrote:

For example, It would be nice to send a message when a trv's battery is low. Yes it can be done (and Ive done it) but it was a bit of a pain to do.. Here with NR I think I can just write a javascript loop...

Yep, but you don't even need a loop, as you'll be able to capture the state change. I didn't yet bother to create notifications for batteries, but did it for water leak sensors. Looks nice and simple: [image: image] https://user-images.githubusercontent.com/16118553/83754944-b6adb800-a664-11ea-8d13-3d96db2d776d.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/asantaga/wiserHomeAssistantPlatform/issues/70#issuecomment-638808688, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWN2QESNXFDBSZAFGV57YDRU6FPZANCNFSM4K2GQLYQ .

--

Angelo

asantaga commented 4 years ago

So im having a tinker with NR. I decided to use the "poll" component, how do you " merge" these into one so you only send one message saying that some radiators have low batteries.. Ive worked itout using javascript but wondering about how do it using the components.

mrvladis commented 4 years ago

So im having a tinker with NR. I decided to use the "poll" component, how do you " merge" these into one so you only send one message saying that some radiators have low batteries.. Ive worked itout using javascript but wondering about how do it using the components.

I didn't use poll, but rather "Trigger: State". So I receive and event when Object is transitioning from one state to another. In case with TRVs (which I didn't yet implement) - I think I'll just send an email when battery status will transition to "Low" from "One Third".

As for the Poll - I think I'll potentially use for the reminders, may be once a day or once a week. But in this scenario - I will indeed need to merge it to avoid receiving reminder for each one of them. Simple way, if you don't want to send the details of which TRVs are low on battery is to set a flag for the first action in the day, so the rest would be ignored.

DrJohnT commented 4 years ago

Angelo, I finally figured out why my Wiser integration kept losing its connection. My old router provided a new IP address and this integration relies on the IP address which is buried deep inside .storage/core.config_entries. With my new router, I have static IP addresses assigned, so will not be a problem now. Perhaps the documentation needs to mention that the Wiser kit should be assigned a static IP or the integrations page needs to expose the IP address for editing???

asantaga commented 4 years ago

thats a good idea.. I thought I had, but obviously havent..

I'll update the readme when I have time

On Thu, 2 Jul 2020 at 05:26, Dr John Tunnicliffe notifications@github.com wrote:

Angelo, I finally figured out why my Wiser integration kept losing its connection. My old router provided a new IP address and this integration relies on the IP address which is buried deep inside .storage/core.config_entries. With my new router, I have static IP addresses assigned, so will not be a problem now. Perhaps the documentation needs to mention that the Wiser kit should be assigned a static IP or the integrations page needs to expose the IP address for editing???

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/asantaga/wiserHomeAssistantPlatform/issues/70#issuecomment-652773717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWN2QFX7TIE4QHZOICFVKDRZQD6XANCNFSM4K2GQLYQ .

--

Angelo

asantaga commented 4 years ago

Angelo, I finally figured out why my Wiser integration kept losing its connection. My old router provided a new IP address and this integration relies on the IP address which is buried deep inside .storage/core.config_entries. With my new router, I have static IP addresses assigned, so will not be a problem now. Perhaps the documentation needs to mention that the Wiser kit should be assigned a static IP or the integrations page needs to expose the IP address for editing???

logged https://github.com/asantaga/wiserHomeAssistantPlatform/issues/110 to remind me

asantaga commented 4 years ago

guys @msp1974

looks like I need to log a number of PRs to get this integration included into HA core (https://github.com/home-assistant/architecture/issues/408)

There will be a period where HA Core will have the Wiser API but only a subset of it..

So.. How important is it to have this integration within HA Core? or is HACS just fine

please vote by thumbs up 👍 if its important or thumbs down 👎 if HACS is just fine or don't care

thanks

asantaga commented 4 years ago

mmmm 83% of people say "stay with HACS"

Oh well thats it then!

jimmyburnworld commented 4 years ago

Loving this new way of being able to use my Wiser heating controls. I have quite a distributed network so have been experimenting with positions of smart plugs to improve signal coverage and originally the only way to get an update on device signal was by emailing Wiser support each time I moved a plug!

Anyway; Is it possible to get access to the Opentherm data used by some of the Wiser base modules? My existing boiler does not have Opentherm, however if I could get a reading for the demand from the Wiser Opentherm module, I could use a servo to vary the circulation temperature knob on the boiler.

technofreak74 commented 3 years ago

Is the poll still open for integrating into HA? 🙂 It's not that surprising that users on here are ok with HACS, people that aren't might not even know your brilliant integration exists! I'd be really up for helping do the work to get it moved over if that's what's holding it back.. I can understand that there are lots of other reasons why you wouldn't want to do it though...

msp1974 commented 3 years ago

@technofreak74 the reason we backed off from moving this into HA core was the fact that they wouldn't accept it as is. Ie we had done all the recoding to pass all the tests but we were asked to strip it back to a very low functional integration to be accepted. This would mean that everyone who is using today would loose a lot of the functionality until we could get enhancements reviewed and implemented in future HA releases. As this could be months, we decided that we did not want to put our user base through such a painful process just to get into HA core.

scooper1 commented 3 years ago

As a idea could we split in two versions.  One basic in core and advance versions in hacs  is that allowed Has anyone talked to manufacture to get a bit of sponsorship for the core version On 29 Oct 2020 17:23, Mark Parker notifications@github.com wrote: @technofreak74 the reason we backed off from moving this into HA core was the fact that they wouldn't accept it as is. Ie we had done all the recoding to pass all the tests but we were asked to strip it back to a very low functional integration to be accepted. This would mean that everyone who is using today would loose a lot of the functionality until we could get enhancements reviewed and implemented in future HA releases. As this could be months, we decided that we did not want to put our user base through such a painful process just to get into HA core.

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

technofreak74 commented 3 years ago

@technofreak74 the reason we backed off from moving this into HA core was the fact that they wouldn't accept it as is. Ie we had done all the recoding to pass all the tests but we were asked to strip it back to a very low functional integration to be accepted. This would mean that everyone who is using today would loose a lot of the functionality until we could get enhancements reviewed and implemented in future HA releases. As this could be months, we decided that we did not want to put our user base through such a painful process just to get into HA core.

That makes sense. It is a shame though, you guys have done so much work and it would definitely reach more people that way (I got HACS to use this integration!). You presumably lose a lot of control over the integration too if you did it. I think that is why they like all the heavy lifting to be done in a separate python lib, so they don't have to review it 😄.

m01 commented 3 years ago

I think longer term it would be better for this integration to live in the Home Assistant core.

In preparation for that, it might firstly make sense to check if there's any non-HomeAssistant specific code in this repo, and move it to the wiser-heating-api repo. I don't think there's a lot, but perhaps e.g. WiserSensor.calculate_device_battery_pct is one candidate? To be honest, I couldn't find anything else with a quick skim.

The second thing I would consider is figuring out the logistics of moving the code over in small chunks. Some ideas:

This repo doesn't feel soooo big that this problem could not be solved.

I do also understand that as open source maintainers you may not deem this to be sufficiently important to warrant the extra work. In general I wouldn't mind helping with giving the move a go, but I'd have to check with my employer and find time as well.

asantaga commented 3 years ago

Is the poll still open for integrating into HA? 🙂 It's not that surprising that users on here are ok with HACS, people that aren't might not even know your brilliant integration exists! I'd be really up for helping do the work to get it moved over if that's what's holding it back.. I can understand that there are lots of other reasons why you wouldn't want to do it though...

Hey @technofreak74 technofreak74 , I got annoyed with the process. This integration is quite advanced and complete and to publish it as a native HA integration we would need to break it down to a single platform and then publish it, then adding sensors/platforms one at a time until its all published. I explained to the HA guys that its kinda silly , we've used HACS as an incubator and now deciding to publish it on HA natively (for the reasons you mention) and they said tough...

I'll be honest , the integration works, people know about it through the forums and thought.. meh.. not worth the effort..

asantaga commented 3 years ago

ps baby now 6 weeks old, life getting back to normal :) and Yes @msp1974 been baby sitting for me :-) best partner I could have :-)

asantaga commented 3 years ago

@m01 totally agree..

I moved most code out to the wiser-heating-api module as you say, but you are right there might be one/two more bits which have organically added themselves... I'll check.

Last time I checked HA did weekly releases - is it feasible to split the repo and prepare a list of PRs that build on each other, get >them "reviewed in principle", but press the merge button on 1 PR a day or so over the course of a week?

From what I understood, we can issue 10 Cumulative PRs and as you say hit merge as soon as the previous one is done..

I may revisit the idea of going to HA.... Sigh..

asantaga commented 3 years ago

Just an update for all. I've been offline for a number of reasons recently, one of the reasons is we've moved house! Whoop whoop but also stressful. Now settled in and today Wiser is finally installed, however my HA machine isnt up and running yet, but will be soon.

Mean whilst, sods law, HA changes caused our integration to break .. boo hoo, thankfully my co-collaborator and co-author of the integration (Mark Parker @msp1974) , has been fantastic in manning the fort and fixing a ton of changes today!

Thanks Mark!!! Thanks all!!

olbasoil commented 2 years ago

Are there any events generated when the climate.wiser changes temperature? I am trying to keep a (display only) Nest thermostat in sync with the (real) Wiser system. Using Nodered I can read the temperatures from each, and react if I find it has changed, but I'd rather have an event notify me, than a continuous loop.

msp1974 commented 2 years ago

Currently there are no events in the integration.  However, the integration only polls the hub for updates every x seconds, depending on your options settings.  So you could reduce the overhead by only reading every x seconds too.We can look at this for future releases or happy for a PR if you want to do that.MarkSent from my Galaxy -------- Original message --------From: olbasoil @.> Date: 02/11/2021 10:11 (GMT+00:00) To: asantaga/wiserHomeAssistantPlatform @.> Cc: Mark Parker @.>, Mention @.> Subject: Re: [asantaga/wiserHomeAssistantPlatform] General Discussions (#70) Are there any events generated when the climate.wiser changes temperature? I am trying to keep a (display only) Nest thermostat in sync with the (real) Wiser system. Using Nodered I can read the temperatures from each, and react if I find it has changed, but I'd rather have an event notify me, than a continuous loop.

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

phixion commented 2 years ago

Just an update for all. I've been offline for a number of reasons recently, one of the reasons is we've moved house! Whoop whoop but also stressful. Now settled in and today Wiser is finally installed, however my HA machine isnt up and running yet, but will be soon.

Mean whilst, sods law, HA changes caused our integration to break .. boo hoo, thankfully my co-collaborator and co-author of the integration (Mark Parker @msp1974) , has been fantastic in manning the fort and fixing a ton of changes today!

Thanks Mark!!! Thanks all!!

thats great news! and yes msp is doing a great job! with the recent changes to hassio's docker runtime I decided to seperate hassio completly from my docker stack to remain "supported" ....turned out to be much more work that I expected :)

msp1974 commented 2 years ago

@olbasoil sorry its a little late but got chance this week to look at your request and i think you can already do in standard HA. I will put this in the recipees when i get chance for others if needed but below is an automation that will fire when target temp is changed and call a service to set target temp on another climate device. Not sure whether this is exactly what you wanted but maybe give you the idea to do your use case.

If you want to use current temp instead of target temp use current_temperature as attribute. For the service, call whatever service/climate device is your nest thermostat.


alias: Keep room in sync with another room
description: ''
trigger:
  - platform: state
    entity_id: climate.wiser_guest_room
    attribute: temperature
condition:
  - condition: template
    value_template: >-
      {% if trigger.to_state.attributes.temperature != 
      trigger.from_state.attributes.temperature %} true {% endif %}
action:
  - service: climate.set_temperature
    target:
      entity_id: climate.wiser_master_bedroom
    data:
      temperature: '{{ state_attr(''climate.wiser_guest_room'', ''temperature'') }}'
mode: queued
max: 10
msp1974 commented 2 years ago

Should also say that there is already a trigger on a climate device for current_temperature_changed but it seems to need to have a from and/or to value needed so i cant see how to make it trigger for any temp change. You could also look into that or I will look further when i get time.

robinmarlow commented 2 years ago

Really loving this integration - thank you so much! I got prompted by the wiser app yesterday to buy a bit of kit (https://shop.se.com/uk/en/thd-pcktr004.html) to link my smart meter into the Wiser app for £14 - which seemed worth a punt. Is anyone else interested in seeing if this can be wrangled into feeding into the home assistant energy monitoring?

ZuluWhiskey commented 2 years ago

Really loving this integration - thank you so much!

I got prompted by the wiser app yesterday to buy a bit of kit (https://shop.se.com/uk/en/thd-pcktr004.html) to link my smart meter into the Wiser app for £14 - which seemed worth a punt. Is anyone else interested in seeing if this can be wrangled into feeding into the home assistant energy monitoring?

Didn't know about this, I'm eligible and as you say would be really cool to integrate - It may be agnostic of the existing kit though as the new device connects to WiFi rather than the ZigBee network 🤔

asantaga commented 2 years ago

Really loving this integration - thank you so much! I got prompted by the wiser app yesterday to buy a bit of kit (https://shop.se.com/uk/en/thd-pcktr004.html) to link my smart meter into the Wiser app for £14 - which seemed worth a punt. Is anyone else interested in seeing if this can be wrangled into feeding into the home assistant energy monitoring?

Didn't know about this, I'm eligible and as you say would be really cool to integrate - It may be agnostic of the existing kit though as the new device connects to WiFi rather than the ZigBee network 🤔

Looks interesting but i cant work out if Im eligible...

wizmo2 commented 2 years ago

Looks interesting but i cant work out if Im eligible...

@asantaga - had the same question. Figured out that after I updated to the latest app, there is a splash at the top of the Insights page that you can start a questionnaire. First question is if your address matches some database.

I stopped there as (a) I dont have a smart meter and (b) I'm a little neurotic and I gave a false address!

olbasoil commented 2 years ago

I completed the eligibility check, but was told I was not eligible because my smart meter was not SMETS2. It is SMETS1 but there has been a program to upgrade SMETS1 to be SMETS2 compatible (mostly to allow a free market in changing energy supplier) and mine is registered in the national database, so there is probably some more obscure criteria. I was on a support call to Drayton yesterday about something else, and mentioned this. and hope they will come back with an answer. It is impossible to get a working SMETS1 replaced with a SMRTS2 (though non smart meters can be replaced).

On Wed, Nov 24, 2021 at 2:43 AM wizmo2 @.***> wrote:

Looks interesting but i cant work out if Im eligible... @asantaga https://github.com/asantaga - had the same question. Figured out that after I updated to the latest app, there is a splash at the top of the Insights page that you can start a questionnaire. First question is if your address matches some database.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/asantaga/wiserHomeAssistantPlatform/issues/70#issuecomment-977445123, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKVCV33STFYRC24QTWABHXTUNRGMBANCNFSM4K2GQLYQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

robinmarlow commented 2 years ago

An update: The monitor arrived today - it's a Geo Trio II. I connected it to my wifi and after a few hours it had magically linked to my smart meter (I guess when I gave the number as the eligibility check they stored it to link against). I followed the instuctions here from Mr T: https://community.home-assistant.io/t/uk-smart-energy-meters/16545/102 and it works brilliantly.

asantaga commented 2 years ago

I completed the eligibility check, but was told I was not eligible because my smart meter was not SMETS2. It is SMETS1 but there has been a program to upgrade SMETS1 to be SMETS2 compatible (mostly to allow a free market in changing energy supplier) and mine is registered in the national database, so there is probably some more obscure criteria. I was on a support call to Drayton yesterday about something else, and mentioned this. and hope they will come back with an answer. It is impossible to get a working SMETS1 replaced with a SMRTS2 (though non smart meters can be replaced). On Wed, Nov 24, 2021 at 2:43 AM wizmo2 @.***> wrote: Looks interesting but i cant work out if Im eligible... @asantaga https://github.com/asantaga - had the same question. Figured out that after I updated to the latest app, there is a splash at the top of the Insights page that you can start a questionnaire. First question is if your address matches some database. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#70 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKVCV33STFYRC24QTWABHXTUNRGMBANCNFSM4K2GQLYQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Im in same boat.. Waiting for my no so smart meter to die :-)

asantaga commented 2 years ago

An update: The monitor arrived today - it's a Geo Trio II. I connected it to my wifi and after a few hours it had magically linked to my smart meter (I guess when I gave the number as the eligibility check they stored it to link against). I followed the instuctions here from Mr T: https://community.home-assistant.io/t/uk-smart-energy-meters/16545/102 and it works brilliantly.

NIce... Im feeling left out (see comment above)

asantaga commented 2 years ago

Im sure everyone knows this but there is also a healthy discussion on https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration/80965/292eibcccvntcdlbkrnvidlrH

asantaga commented 2 years ago

Im sure everyone knows this but there is also a healthy discussion on https://community.home-assistant.io/t/drayton-wiser-home-assistant-integration