Comments (13)
Hello,
@Miablo did an amazing job re-working the markdown card template - take a look at the new template in the development branch. I'll merge it into the main branch soon, I just need to adjust the instructions and generalize the usernames.
from homeassistant-peloton-sensor.
Hello! Thanks for reporting this issue.
The problem is that a few versions ago there was a single sensor with many state attributes and now there are many sensors with those same attributes broken out into individual sensors. This is the method the core HASS project would like integrations to follow.
Anyway - this not only breaks this card which is referencing state attributes, it's further broken because certain attributes are no longer being reported.
This can all be fixed but it's just slightly more complicated than finding/replacing names. I'll rework this soon and try to add back to the main sensor list the items that are missing.
Thanks!
Ed
from homeassistant-peloton-sensor.
@kylewilliams321 did you ever sort out an updated yaml/template for the new sensors?
from homeassistant-peloton-sensor.
Thanks, @edwork and @Miablo. That's the template that I'm using (with updated user/sensor names), but it's only showing the title with no data. The sensors appear to be working fine in ha/developer-tools/state
, though 🤷
from homeassistant-peloton-sensor.
@Cassock Can you add your code or a screenshot of it to the post so I can take a look?
from homeassistant-peloton-sensor.
https://hastebin.com/share/newujivese.bash
from homeassistant-peloton-sensor.
Can you try this to see if it renders correctly: https://hastebin.com/share/ibenupuvoh.bash - that should have your username added for the sensor
from homeassistant-peloton-sensor.
It doesn't :( No errors on the lovelace editor, but putting it into the dev tools template editor results in this:
from homeassistant-peloton-sensor.
Markdown with markup tags won't render in the template dev tools, that's working as intended. The first example provided seems to have stripped out the markup tags possibly breaking the card's formatting.
Can you create a new markdown card, add the text, and force refresh (shift+refresh) the page? In my testing client side caching was causing some errors when I first began testing the card.
from homeassistant-peloton-sensor.
Yeah I tried that first before going to dev tools. Here's what it looks like (even after hard refreshes):
And just to confirm, it appears I do have working sensors (I assume all of the unknown values correspond to active ride data)
from homeassistant-peloton-sensor.
There's something wrong with the copy-pasta that happens either in or out of GitHub, I'll work it out but for now try out this example.
from homeassistant-peloton-sensor.
Spent a few more minutes on this today and it looks like something on the Latest Workout Metrics
markdown is what's preventing the whole card from showing. If I delete that section, the rest of the data shows up as expected:
from homeassistant-peloton-sensor.
I did notice the problem occurs when for example my Cadence sensor is Home Assistant is displaying unknown. Is goes to unknown when I am not biking. During a ride is works as there is data, and the template works fine.
So I think we need a way to keep the latest sensor value for those sensor that go to unknown when not riding or when switching to a tread.
That goes for the Active Calories, Cadence, Resistance and Speed sensors, 10 total.
Or a change in the template ??
from homeassistant-peloton-sensor.
Related Issues (20)
- Not available in config flow HOT 5
- became unavailable HOT 3
- Heartrate HOT 6
- Add Workout Counter Sensor HOT 5
- Primary State HOT 3
- KeyError: 'ride' HOT 1
- Values do not reflect actuals HOT 3
- This entity is no longer being provided by the peloton integration. HOT 8
- No power output? HOT 4
- During a Ride Countdown the primary binary_sensor goes unavailable HOT 2
- fail in version 2023.3 HOT 1
- Various Peloton HA Integration Errors in Log HOT 2
- Error after reinstall HOT 4
- Can't change password HOT 2
- Updating to 10.0: Index out of Range HOT 3
- End Time always = Start Time during workout HOT 2
- Entities have become unavailable HOT 1
- Peloton errors when starting workout HOT 4
- Current values/sensors don't drop to zero when not in use HOT 1
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 homeassistant-peloton-sensor.