-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ v2.7.3 #171
Conversation
Ludy87
commented
Feb 20, 2023
- add Emoji for Message Markdown
- update user-agents
- add mapbox with API_KEY
- clean up and more
I dont know what iam doing wrong, even with the Automation and Markdown Sample (changed to the correct Sensor for my watch) the Markdown Card stays empty, the Message Sensor counter changed to 0 but the Sensor Attributes Shows the Last Receiver and send Messages |
is nothing displayed in the browser or in the app? |
both, inside the app and and chrome browser |
if you go to the message sensor, and then to attributes, is there a list? |
yes, a list is shown there - strange is that after todays update the message sensor changed from "12" Yesterday to "0" today, even that i send 3 new messages to the watch using the app today, this three messages are shown inside the list |
if a list is shown there, then something is wrong in the markdown layout. The counter is not reset by the integration! |
I used your Markdown File from Yesterday and changed the
sensor.xxx_xplora....... on top to the Message Sensor of my watch.
Ludy ***@***.***> schrieb am Do., 23. Feb. 2023, 09:22:
… if a list is shown there, then something is wrong in the markdown layout.
The counter is not reset by the integration!
—
Reply to this email directly, view it on GitHub
<#171 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABJ4EKHJQ5OFJHPNTVMOB3WY4M3XANCNFSM6AAAAAAVBTGMQI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |