General Discussions #70

asantaga · 2020-02-24T11:38:40Z

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!

msp1974 · 2020-02-24T17:00:25Z

I'm still getting over the excitement of R1.9. Good job!

asantaga · 2020-02-27T10:37:32Z

It is pretty damm complete now..

I think we should focus on getting into HA as a native component... I was reviewing docs yesterday and I think its pretty much done.. Give it a couple of weeks so we can make sure there isnt anything we should fix/enhance at the same time then we'll look at it..

asantaga · 2020-03-17T23:21:07Z

Hey all,

Mark has been super busy and made some changes which add config flow to the integration. Im not sure what else we need to do on this before publishing it to HA as a native component?

Can people please test dev?

Fulch · 2020-03-20T13:07:43Z

HA version 0.107.1 Dev branch testing.

Getting this error at one minute intervals.

2020-03-20 12:49:10 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 284, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
state = self.state
File "/usr/src/homeassistant/homeassistant/components/water_heater/init.py", line 137, in state
return self.current_operation
File "/config/custom_components/wiser/water_heater.py", line 78, in current_operation
WISER_TO_HASS_STATE[self.data.wiserhub.getHotwater.get("Mode")] or STATE_OFF
AttributeError: 'function' object has no attribute 'get'

Not sure if it's related but I don't think I had these water heater services before the update.

asantaga · 2020-03-20T15:31:36Z

I'll investigate tonight.. I didnt see them in my build, i wonder why...

, @msp1974 fyi

msp1974 · 2020-03-20T19:00:50Z

Hi, sorry been quiet for a while. Been dealing with the new C word!

This is my fault, I was playing with adding a water heater component to manage the hot water functions. I wont load if you do not have hot water capability on your hub and I dont have that on mine (only single channel). I should have pointed it out more clearly and that it needed testing by someone who has.

Couple of options

disable it loading in the config file entry by removing hot water from the list of components to load. I shouldn't have committed this in the last commit.
fix it from this error as we have someone to test it. I dont really know the json structure as cannot see on my hub.

Happy to do which ever option as my fault.

Fulch · 2020-03-20T19:24:53Z

I do actually have a hot water channel on my heat hub and use it daily via a schedule. I'm happy to test and report back if you have any changes to suggest that I could make.

asantaga · 2020-03-20T19:58:41Z

I'm puzzled, this is water_heater is for the hot water system right?

I've looked at my wiser app and I don't have the option to set the temperature or the "mode".

Currently we already have set_water_mode (on/off/auto) and I think the only one missing is the ability to set the away mode affects hw
(although there is button)

Perhaps just back these out until they are better understood?

msp1974 · 2020-03-20T20:18:57Z

I think that is probably right. i was looking at it as I had seen a few smart thermostats use it to manage HW. I think it is a good solution to manage the hot water functions as if you add the entity for this, you can change the mode from the UI and it has built in services, but probably best as a branch until fully understood and tested. Will send you a PR to back out (small change to init and remove water_heater.py) and then create another branch for this.

asantaga · 2020-03-20T20:34:03Z

ok, I think thats best.. Im not convinced its needed...., look forward to the PR.. Thanks

asantaga · 2020-03-22T21:57:17Z

@Fulch , all checked in and appears to be ok now , with no errors. Can we check this, if its all ok, I'll make a 2.0 release then 100% focus on pushing to native HA

I mean with this corona stuff theres nothing else to do eh?

Fulch · 2020-03-23T20:08:43Z

Running the latest Dev release since late yesterday and everything looks good!

asantaga · 2020-03-23T22:38:15Z

Same here.. I'll give it to the weekend and then push it as a 2.0 release..

asantaga · 2020-03-27T11:37:46Z

So far it works fine so I will release 2.0 this weekend,

just saw a issue (#79) which was closed by toby (unprintable characters in the SSID screwing up JSON).. Its not "really" a bug, the JSON produced is invalid. Toby may produce a PR and if he does it this weekend I'll wait for it.

not critical TBH~

Surprisingly cold outside isnt it

TobyLL · 2020-03-28T13:41:36Z

Hi all, I have the water heater functionality on my Wiser system. I think the reason for having the water heater component is so that you can use the Boost 30m/1h/2h/3h preset functionality, in the same way you can for each room. I'm happy to do some testing if needed.

asantaga · 2020-03-29T20:37:14Z

Hey all, anyone else got the same issue as m01 on entities (#81)?

@TobyLL , yeah makes sense, will do for 2.1
Im thinking the easiest option is to create a service which allows the boosting of hotwater (similar to wiser.boost_heating). Also enhance the sensor.wiser_hot_water to indicate if its boosted

asantaga · 2020-03-29T21:55:16Z

Published 2.0 :-)

asantaga · 2020-03-29T22:16:45Z

So how is all doing with self-isolation.. For me its turned out to mean I have even less time! (childcare etc)

phixion · 2020-03-29T23:09:46Z

moved to my parents place, away from the city to a more isolated landside spot. equipped them with a rpi hassos a couple of weeks ago and now setting up some basic automations and watch the corona sensor change states. hope yall good!

scooper1 · 2020-03-30T00:00:28Z

it appears that 2.0 release is broken
Breaks on two systems I have control of
It broke on startup - maybe insists on config flow via integrations page - No warning in release notes to convert yaml to config flow
it maybe to do with the latest superviser release changing to internal DNS server
returned back to 1.91 all is ok again
error for 2.0 is
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 123, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 163, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 50, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 92, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 130, in async_configure
result = await self._async_handle_step(flow, cur_step["step_id"], user_input)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 172, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File "/config/custom_components/wiser/config_flow.py", line 72, in async_step_user
ip=user_input[CONF_HOST], secret=user_input[CONF_PASSWORD]
File "/config/custom_components/wiser/config_flow.py", line 44, in _test_connection
return await self.hass.async_add_executor_job(self.wiserhub.getWiserHubName)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/wiserHeatingAPI/wiserHub.py", line 228, in getWiserHubName
return self.wiserNetworkData.get("Station").get("MdnsHostname")
AttributeError: 'NoneType' object has no attribute 'get'

asantaga · 2020-03-30T08:45:49Z

Logged #83

Fulch · 2020-03-30T08:56:09Z

Using 2.0 release.
Similar error, not quite the same though. Despite the error, Wiser appears to be fully functional!
Dropping back to Dev version still produces the error, is this due to the API update?

2020-03-30 00:05:52 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry WiserHeat036CB1 for wiser
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 216, in async_setup
hass, self
File "/config/custom_components/wiser/init.py", line 156, in async_setup_entry
await data.async_update_device_registry()
File "/config/custom_components/wiser/init.py", line 232, in async_update_device_registry
connections={(CONNECTION_NETWORK_MAC, self.wiserhub.getMACAddress())},
File "/usr/local/lib/python3.7/site-packages/wiserHeatingAPI/wiserHub.py", line 231, in getMACAddress
return self.wiserNetworkData.get("Station").get("MacAddress")
AttributeError: 'NoneType' object has no attribute 'get'

asantaga · 2020-03-30T08:57:06Z

created patch, see #83 , available for testing.
Easy workaround today is to not use config flow but use configuration.yaml parameters..

(reason for bug is wiser upgraded the hub firmware and broke us)

asantaga · 2020-03-30T14:18:09Z

Ive pulled the R2.0 Release from HACS, until we are sure whats broken it its best to not use it..

Love firmware updates

msp1974 · 2020-03-30T18:26:45Z

@scooper1 fyi

created patch, see #83 , available for testing.
Easy workaround today is to not use config flow but use configuration.yaml parameters..

(reason for bug is wiser upgraded the hub firmware and broke us)

Have posted this on another issue also but don't know how to link that comment into this issue so apologies for posting it twice.

the config flow in v2.0 of this component will do one of 3 things.

If you have an entry in config.yaml, it will import this into a config flow config. This is to support all those using prior to v2.0 (like most of us here!). Once it has done so, entry in config.yaml can be removed (of left alone if you want but it won't use it anymore). This is how it needs to work if you want to support config flow.
You can manually add by adding through the integration page. In which case it will ask for ip and secret key and create a config from it. It has to be able to connect to the hub when creating this way to get the other devices attached to be created.
When this is integrated into the main HA repo, it will support discovery of the hub and just ask for the key. Zeroconf discovery is only supported for core components.

msp1974 · 2020-03-30T18:28:17Z

See issue #83 . Appears to be a bug in the wiserHub.py api. A PR has been submitted to fix this. Once @asantaga has had chance to update api I think v2.0 will work fine.

asantaga · 2020-03-30T21:29:54Z

New Release , R2.1_beta1 released..

If this is all good then I'll simply make a new release R2.1

ps because I made it a pre-release it will only show if you say show beta

scooper1 · 2020-03-30T23:40:54Z

still broken for me
first set of errors from config.yaml
second set from integrations

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 109, in async_init
result = await self._async_handle_step(flow, flow.init_step, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 172, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File "/config/custom_components/wiser/config_flow.py", line 203, in async_step_import
return await self.async_step_user(user_input=user_input)
File "/config/custom_components/wiser/config_flow.py", line 72, in async_step_user
ip=user_input[CONF_HOST], secret=user_input[CONF_PASSWORD]
File "/config/custom_components/wiser/config_flow.py", line 44, in _test_connection
return await self.hass.async_add_executor_job(self.wiserhub.getWiserHubName)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/wiserHeatingAPI/wiserHub.py", line 228, in getWiserHubName
return self.wiserNetworkData.get("Station").get("MdnsHostname")
AttributeError: 'NoneType' object has no attribute 'get'

2020-03-31 00:25:55 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 123, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 163, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 50, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 92, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 130, in async_configure
result = await self._async_handle_step(flow, cur_step["step_id"], user_input)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 172, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File "/config/custom_components/wiser/config_flow.py", line 72, in async_step_user
ip=user_input[CONF_HOST], secret=user_input[CONF_PASSWORD]
File "/config/custom_components/wiser/config_flow.py", line 44, in _test_connection
return await self.hass.async_add_executor_job(self.wiserhub.getWiserHubName)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/wiserHeatingAPI/wiserHub.py", line 228, in getWiserHubName
return self.wiserNetworkData.get("Station").get("MdnsHostname")
AttributeError: 'NoneType' object has no attribute 'get'

asantaga · 2020-07-06T09:48:12Z

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 #110 to remind me

asantaga · 2020-07-08T10:25:22Z

guys @msp1974

looks like I need to log a number of PRs to get this integration included into HA core
(home-assistant/architecture#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 · 2020-07-13T19:30:53Z

mmmm 83% of people say "stay with HACS"

Oh well thats it then!

jimmyburnworld · 2020-10-17T15:29:03Z

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 · 2020-10-29T10:59:05Z

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 · 2020-10-29T17:23:31Z

@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 · 2020-10-29T17:33:22Z

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 · 2020-10-31T18:09:36Z

@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 · 2020-10-31T20:16:58Z

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:

Is it possible to split the functionality in such a way, that the core repo contains some mandatory part and this contains some optional parts in a clever way, so that if you have both installed there's no change? Python's namespace packages in principle allow packaging code from the same import namespace into multiple distribution packages, but I'm not sure if this would work with HA's setup specifically
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?

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 · 2020-11-15T22:04:01Z

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 · 2020-11-15T22:04:50Z

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 · 2020-11-15T22:08:51Z

@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 · 2021-10-17T22:28:00Z

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 · 2021-11-02T10:11:19Z

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 · 2021-11-02T18:56:35Z

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 · 2021-11-03T20:27:24Z

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 · 2021-11-13T10:14:04Z

@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 · 2021-11-13T10:19:46Z

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 · 2021-11-23T15:26:35Z

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 · 2021-11-23T21:28:29Z

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 · 2021-11-24T00:36:14Z

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 · 2021-11-24T02:43:00Z

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 · 2021-11-24T07:59:59Z

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>.

robinmarlow · 2021-12-02T16:54:08Z

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 · 2021-12-08T10:00:33Z

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 · 2021-12-08T10:00:59Z

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 · 2021-12-08T10:01:22Z

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 · 2021-12-08T10:01:52Z

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

asantaga changed the title ~~R2.0 Discussions~~ General Discussions Mar 29, 2020

asantaga changed the title ~~General Discussions~~ 2.0+ General Discussions Mar 29, 2020

asantaga changed the title ~~2.0+ General Discussions~~ General Discussions Oct 17, 2021

asantaga closed this as completed Dec 8, 2021

General Discussions #70

General Discussions #70

Comments

asantaga commented Feb 24, 2020

msp1974 commented Feb 24, 2020

asantaga commented Feb 27, 2020

asantaga commented Mar 17, 2020

Fulch commented Mar 20, 2020

asantaga commented Mar 20, 2020 • edited Loading

msp1974 commented Mar 20, 2020

Fulch commented Mar 20, 2020

asantaga commented Mar 20, 2020 • edited Loading

msp1974 commented Mar 20, 2020

asantaga commented Mar 20, 2020

asantaga commented Mar 22, 2020 • edited Loading

Fulch commented Mar 23, 2020

asantaga commented Mar 23, 2020

asantaga commented Mar 27, 2020

TobyLL commented Mar 28, 2020

asantaga commented Mar 29, 2020 • edited Loading

asantaga commented Mar 29, 2020

asantaga commented Mar 29, 2020

phixion commented Mar 29, 2020

scooper1 commented Mar 30, 2020

asantaga commented Mar 30, 2020

Fulch commented Mar 30, 2020

asantaga commented Mar 30, 2020 • edited Loading

asantaga commented Mar 30, 2020

msp1974 commented Mar 30, 2020

msp1974 commented Mar 30, 2020

asantaga commented Mar 30, 2020 • edited Loading

scooper1 commented Mar 30, 2020

asantaga commented Jul 6, 2020

asantaga commented Jul 8, 2020

asantaga commented Jul 13, 2020

jimmyburnworld commented Oct 17, 2020

technofreak74 commented Oct 29, 2020

msp1974 commented Oct 29, 2020

scooper1 commented Oct 29, 2020 via email

technofreak74 commented Oct 31, 2020

m01 commented Oct 31, 2020

asantaga commented Nov 15, 2020 • edited Loading

asantaga commented Nov 15, 2020

asantaga commented Nov 15, 2020

asantaga commented Oct 17, 2021

olbasoil commented Nov 2, 2021

msp1974 commented Nov 2, 2021 via email

phixion commented Nov 3, 2021 • edited Loading

msp1974 commented Nov 13, 2021 • edited Loading

msp1974 commented Nov 13, 2021

robinmarlow commented Nov 23, 2021

ZuluWhiskey commented Nov 23, 2021

asantaga commented Nov 24, 2021

wizmo2 commented Nov 24, 2021 • edited Loading

olbasoil commented Nov 24, 2021 via email

robinmarlow commented Dec 2, 2021 • edited Loading

asantaga commented Dec 8, 2021

asantaga commented Dec 8, 2021

asantaga commented Dec 8, 2021

asantaga commented Dec 8, 2021

asantaga commented Mar 20, 2020 •

edited

Loading

asantaga commented Mar 20, 2020 •

edited

Loading

asantaga commented Mar 22, 2020 •

edited

Loading

asantaga commented Mar 29, 2020 •

edited

Loading

asantaga commented Mar 30, 2020 •

edited

Loading

asantaga commented Mar 30, 2020 •

edited

Loading

asantaga commented Nov 15, 2020 •

edited

Loading

phixion commented Nov 3, 2021 •

edited

Loading

msp1974 commented Nov 13, 2021 •

edited

Loading

wizmo2 commented Nov 24, 2021 •

edited

Loading

robinmarlow commented Dec 2, 2021 •

edited

Loading