Comments (25)
Is your Input and Output named the same in the IoTaWatt web interface?
The Input and Output should be created in HA just that the Output will have appended _2 to the name so it does not conflict with the Input.
If there is still an issue can you look in the logs, are there any errors from IoTaWatt?
from iotawatt_ha.
Also how are you looking for the sensors? Through the Entities page? Developer Tools? Or from the drop down selection list in the Energy Dashboard configuration?
from iotawatt_ha.
After upgrading to 0.1.1 new sensors were created. As per warning notice iotawatt_something prefix was removed. However, only input sensors are present. I wonder how it is expected to work if I name output sensor the same as input?
Regardless, it is simply broken.
I tried this 2021.9 embedded one with exactly the same result.
The output sensors are not showing in the iotawatt integration; instead they are showing up as a plain sensor.
It's how the HA iotawatt integration, and it's plain silly.
I opened a bug there: home-assistant/core#55489 but it was closed.
from iotawatt_ha.
Logger: homeassistant.helpers.event
Source: components/integration/sensor.py:163
First occurred: 10:00:40 AM (3 occurrences)
Last logged: 10:00:40 AM
Error while processing state change for sensor.mainsconsumption
Error while processing state change for sensor.mainsexport
Error while processing state change for sensor.notmonitored
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 272, in _async_state_change_dispatcher
hass.async_run_hass_job(job, event)
File "/usr/src/homeassistant/homeassistant/core.py", line 433, in async_run_hass_job
hassjob.target(*args)
File "/usr/src/homeassistant/homeassistant/components/integration/sensor.py", line 163, in calc_integration
or new_state.state in (STATE_UNKNOWN, STATE_UNAVAILABLE)
AttributeError: 'NoneType' object has no attribute 'state'
I'm not seeing the input data in energy-devices-graph either. It was there yesterday after the update.
from iotawatt_ha.
@bmorgan99 What version of HA are you running?
from iotawatt_ha.
2021.9.0
from iotawatt_ha.
@bmorgan99 The custom_component of the IoTaWatt only supports up to HA 2021.8.x
For 2021.9.0 you would have to use the official integration bundled with HA 2021.9.0. After uninstalling the custom component, restarting HA, and adding the official integration you will need to create a sensor for each input and output that is from the IoTaWatt that has a unit type of Watts. The template format is documented here IoTaWatt
from iotawatt_ha.
Yes, I uninstalled the HACS version, created the 2 integration sensors per the doc, upgraded to 9.0 and installed the core integration. I didn't see anything about creating each input, but they now look like this:
sensor.iotawatt_input_oven_wh
type: Input
channel: 3
unit_of_measurement: Wh
friendly_name: Oven (E)
device_class: energy
sensor.iotawatt_input_oven
state_class: measurement
type: Input
channel: 3
unit_of_measurement: W
friendly_name: Oven (W)
device_class: power
so create this in sensor.yaml?
- platform: integration
source: sensor.iotawatt_input_oven
name: Oven (k)
unit_prefix: k
from iotawatt_ha.
this is due to an unfortunate last minute change in the HA integration.
Note that if you use the version propose here #30
not only the sensor will work with the energy graph, but you’ll get much better accuracy than the integration in HA offers
platform: integration
source: sensor.iotawatt_input_oven
name: Oven (k)
unit_prefix: k
your source is incorrect, the sensors have been renamed. The prefix iotawatt_input is gone
from iotawatt_ha.
Is your Input and Output named the same in the IoTaWatt web interface?
The Input and Output should be created in HA just that the Output will have appended _2 to the name so it does not conflict with the Input.
If there is still an issue can you look in the logs, are there any errors from IoTaWatt?
Initially I installed your integration early 2021.8. I ran REST too as there was an issue with non-volt/watt values.
It was fine on 0.0.8.
I updated HA to 2021.9 and it was still fine.
Then I saw your recent update. I deconfigured integration, removed it from hacs install and reconfigured using embedded integration. It created 19 sensors for all input channels and that's it. Alright, I reverted snap I took before changes. Got back on previous version working as before. I ran update via hacs instead and... same result. 19 new sensors and my previous 37 still there marked missing now. Created new output for test - has not been discovered.
Reverted snap again and left it as it was.
No errors in log.
from iotawatt_ha.
I ran REST too as there was an issue with non-volt/watt values.
It was fine on 0.0.8.
I've noticed the same ; the sensor are there ; but they are disabled by default ; another last minute change that broke a lot of things :(
from iotawatt_ha.
Is your Input and Output named the same in the IoTaWatt web interface?
The Input and Output should be created in HA just that the Output will have appended _2 to the name so it does not conflict with the Input.
If there is still an issue can you look in the logs, are there any errors from IoTaWatt?
Initially I installed your integration early 2021.8. I ran REST too as there was an issue with non-volt/watt values.
It was fine on 0.0.8.
I updated HA to 2021.9 and it was still fine.
Then I saw your recent update. I deconfigured integration, removed it from hacs install and reconfigured using embedded integration. It created 19 sensors for all input channels and that's it. Alright, I reverted snap I took before changes. Got back on previous version working as before. I ran update via hacs instead and... same result. 19 new sensors and my previous 37 still there marked missing now. Created new output for test - has not been discovered.
Reverted snap again and left it as it was.
No errors in log.
@darek-margas Where are you looking for the test output sensor that was created? Entities page? Developer Tools? Or another area?
from iotawatt_ha.
@darek-margas Where are you looking for the test output sensor that was created? Entities page? Developer Tools? Or another area?
I looked in entities filtered by integration. I see from the above they might appear as unrelated thus out of filter scope.
from iotawatt_ha.
@darek-margas If you clear the filter you should see your Output sensors on the Entities page. The Outputs will have an Integration of Sensor
. Did you find them?
from iotawatt_ha.
@darek-margas If you clear the filter you should see your Output sensors on the Entities page. The Outputs will have an Integration of
Sensor
. Did you find them?
As I mentioned earlier I reverted this change to continue with my monitoring and automation. Now it is as if I never updated it. I'll wait for a few tags on 2021.9 (already has 1) and re-attempt one day. Knowing sensors will appear as unrelated I may have better chance (and still lots of work to rename my 37 sensors back as they are referred in so many places...
from iotawatt_ha.
Can I close this issue then?
from iotawatt_ha.
I think it would be better to actually change it and make all sensor related to integration.
from iotawatt_ha.
Please comment in home-assistant/core#55489 and open a new bug referring to that issue.
Hopefully if enough people mention it they will revisit this very unfortunate choice.
from iotawatt_ha.
Can I close this issue then?
Alright, I attempted to do it again. it turned badly anyway.
I found all these missing sensors. I was able to rename these not missing back to what they were. Then, I found these "missing" ones lost their unique ID and as such they can't be modified in UI. Previous integration gave unique IDs to all.
I like idea of this integration but if someone believes removing IDs was good idea, then I will be better of running REST instead. At least no hassle and nothing gets vanished.
from iotawatt_ha.
Can I close this issue then?
Alright, I attempted to do it again. it turned badly anyway.
I found all these missing sensors. I was able to rename these not missing back to what they were. Then, I found these "missing" ones lost their unique ID and as such they can't be modified in UI. Previous integration gave unique IDs to all.
I like idea of this integration but if someone believes removing IDs was good idea, then I will be better of running REST instead. At least no hassle and nothing gets vanished.
Unfortunately, this was forced by the HA author who believe they should be modified from the iota watt directly. He's the one who made that change despite Greg's opposition
This HACS version adds new feature such as high resolution energy reads (so you can use them with the energy screen). But is otherwise identical to the one found now in HA.
That way you can switch between the HA one and the HACS one without having to rename anything.
What I will try to do is see if I can simulate a unique_id for output (which is what is needed to allow to rename them) but done in such a way that it will be compatible with the internal HA naming, so that it won't require to rename everything everywhere which takes forever.
from iotawatt_ha.
What I will try to do is see if I can simulate a unique_id for output (which is what is needed to allow to rename them) but done in such a way that it will be compatible with the internal HA naming, so that it won't require to rename everything everywhere which takes forever.
Sensors from 0.8.0 had it as I was able to edit.
from iotawatt_ha.
Sensors from 0.8.0 had it as I was able to edit.
Being able to make it editable is trivial. Make it in such a way that you don’t have to edit your entire setup because the internal name changed is another.
For now the HA people have decided that it shouldn’t be editable and instead you should rename it on the iotawatt itself. It was a very shortsighted approach particularly because doing it that way will cause to lose all your history
from iotawatt_ha.
Definitely works now. Any hope for that version to be in core?
from iotawatt_ha.
Definitely works now. Any hope for that version to be in core?
The latest changed for merged in HA earlier today. But still no editable output.
from iotawatt_ha.
I found all these missing sensors.
Can you elaborate how?
I somehow am missing all mine after a recent update and I don't know why or how to fix it.
from iotawatt_ha.
Related Issues (20)
- Unable to prepare setup for platform iotawatt.sensor: Platform not found (cannot import name 'VOLT' from 'homeassistant.const' HOT 3
- Need graphic/logo for IoTaWatt HOT 2
- Issues with wh for a particular "solar surplus" output
- wh issue when using Iotawatt with calculations HOT 4
- Multi-IoTaWatt setup issue with identical inputs HOT 13
- Sensor isn't updated until a new different value is read HOT 2
- Sensor state isn't updated unless the value change. HOT 1
- Energy sensors created from an IotaWatt output can yield an incorrect result HOT 8
- Sensors based on output and returning frequency or power factor return 0 HOT 1
- Entering wrong credentials does not stop setup
- Remove last_reset attribute HOT 6
- Confused with current versioning, and HACS vs HA built-in. HOT 3
- Entity sensor.main_2_wh from integration iotawatt has state class total_increasing, but its state is not strictly increasing. HOT 1
- Can't find integration in HACS HOT 1
- Unexpected state class HOT 1
- Unremovable Duplicated Output Entities HOT 5
- Energy use - wh vs wh_accumulated?
- After creating aggregoators these are not being discovered/added to HA HOT 1
- Error starting integration since HA 2023.5 upgrade HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from iotawatt_ha.