Thanks john, that is what i ment
1 Like
filtering on device_class: power on the states screen makes things more manageable for me
Still think some sort of namespace for the entity entity class would be ideal, just not sure how to go about it myself
1 Like
Is sense working in the latest version. .97 was broken for me with python 3 install. Anyone else have this work?
using 0.98 and sense is working
Sense had an SSL certificate issue previously - but seems that was resolved in this release
1 Like
0.98.2 hasbian and still getting
ssl.SSLError: [SSL: WRONG_SIGNATURE_TYPE] wrong signature type (_ssl.c:1056)
2019-09-03 16:56:56 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.energy_production fails
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity.py", line 261, in async_update_ha_state
await self.async_device_update()
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity.py", line 439, in async_device_update
await self.async_update()
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/sense/sensor.py", line 120, in async_update
await self.update_sensor()
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/sense/sensor.py", line 60, in update_active
await data.update_realtime()
File "/srv/homeassistant/lib/python3.7/site-packages/sense_energy/asyncsenseable.py", line 41, in update_realtime
await self.async_realtime_stream(single=True)
File "/srv/homeassistant/lib/python3.7/site-packages/sense_energy/asyncsenseable.py", line 47, in async_realtime_stream
async with websockets.connect(url) as ws:
File "/srv/homeassistant/lib/python3.7/site-packages/websockets/client.py", line 519, in __aenter__
return await self
File "/srv/homeassistant/lib/python3.7/site-packages/websockets/client.py", line 537, in __await_impl__
transport, protocol = await self._create_connection()
File "/usr/lib/python3.7/asyncio/base_events.py", line 986, in create_connection
ssl_handshake_timeout=ssl_handshake_timeout)
File "/usr/lib/python3.7/asyncio/base_events.py", line 1014, in _create_connection_transport
await waiter
File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
ssldata, appdata = self._sslpipe.feed_ssldata(data)
File "/usr/lib/python3.7/asyncio/sslproto.py", line 189, in feed_ssldata
self._sslobj.do_handshake()
File "/usr/lib/python3.7/ssl.py", line 763, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: WRONG_SIGNATURE_TYPE] wrong signature type (_ssl.c:1056)
@undertoe, I’m using the sense integration in 0.98.3 and it’s working great. Has been working for a long time and I upgrade my home assistant regularly. I’m using Hass.io however.
Stopped working for me after upgrading to .101.3
Tue Nov 12 2019 21:55:52 GMT-0600 (Central Standard Time)
Update for sensor.energy_usage fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 270, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 448, in async_device_update
await self.async_update()
File "/usr/src/homeassistant/homeassistant/components/sense/sensor.py", line 120, in async_update
await self.update_sensor()
File "/usr/src/homeassistant/homeassistant/components/sense/sensor.py", line 60, in update_active
await data.update_realtime()
File "/usr/local/lib/python3.7/site-packages/sense_energy/asyncsenseable.py", line 41, in update_realtime
await self.async_realtime_stream(single=True)
File "/usr/local/lib/python3.7/site-packages/sense_energy/asyncsenseable.py", line 51, in async_realtime_stream
ws.recv(), timeout=self.wss_timeout)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/site-packages/websockets/protocol.py", line 350, in recv
yield from self.ensure_open()
File "/usr/local/lib/python3.7/site-packages/websockets/protocol.py", line 501, in ensure_open
self.close_code, self.close_reason) from self.transfer_data_exc
websockets.exceptions.ConnectionClosed: WebSocket connection is closed: code = 1000 (OK), no reason'''
I’d also find it helpful if the official Sense component added “sense” (or some configurable string) to the names of the binary sensors. ‘binary_sensor.always_on’ is confusing, ‘binary_sensor.sense_always_on’ would be much easier to understand.
The Enphase Envoy component does this: ‘sensor.envoy_current_energy_production’ and it makes it much easier to read.
1 Like
could not agree more, in fact i wish all sensors were name-spaced with their respective component / integration
Came here to search for a solution to the lack of “sense” namespace on detected entities.
Anyone know what the correct channel/process is to request this feature in the official sense integration?
Also just installed a Sense (well, Wiser Energy hardware) and also annoyed by the integrations generated entities. Seems like we just need to figure out who maintains this component.
Yes, just added two Sense units, and it is a PITA to have to rename them all.
How do I monitor L1 and L2 voltage in HA?
With emulated Kasa, this is more of an issue.
ATM I’m getting the energy monitoring from the plug then since it is emulated, it is showing up in the sense integration as well.
@claytonjn How does the Sense Energy Monitor detect if the stove is left on? Or is this only for electric stoves? Would like to monitor the oven as well. Thanks
Would only be for electric stovetops/ovens/etc.
1 Like
+1 from me on adding “sense” to the sensors would be great.
Any luck here? I’m having issues with grafana seeing the newly renamed items within sense.