Lovelace Rpi Monitor Card Versions Save

Various small updates

• Card Age is now expressed in hours/days if RPi has gone offline and the card is still showing
• Suppressed count of OS updates when = -1 (#49)
• Described the newly available update count in top-level README (#49)
• Ensure older card age is still colored red

Full Changelog: https://github.com/ironsheep/lovelace-rpi-monitor-card/compare/v1.4.1...v1.4.2

Adds display of Pending OS Updates

• The count of pending OS updates is now shown (#18)

NOTE: the count of updates value is provided by MQTT Daemon v1.8.0 and later.

Full card functionality is now restored!

• BUGFIX card now keeps refreshing (bad interaction w/lit fixed) (#38)
• BUGFIX cards no longer show bad values during startup (#45)
• Fixed display of date-of-last update (now using localized format)

In the end, we replaced the use of some underlying external utilities with our own and fix an interaction with underlying libraries that was causing a runtime exception from within lit/lit-html.

Work-in-progress release! - Updates to handle latest Daemon fixes, Repair regression on show/hide titles.

This WIP release takes the following actions:

• Repair loss of control of show/hide titles (#43)
• Adjust disk space sensor display for updated Daemon (#41) - keep values from older daemon, working too.
• Add support for the newer Daemon form of reporting memory used (fall back to older form when newer not present)

Lastly, this is still an interim release as I'm seeing an instability that I'm still chasing. (#38) When found and fixed I'll post another release. The effect this has is that cards appear to slow down their updates (or lose the ability to update?) over time. The workaround is to reload the page. Internally there is an uncaught exception that I'm trying to locate and then catch. But it's taking some time to find. I am asking the community for help but it has been slow going...

Work-in-progress release! - Minor color changes, and more indicator fixes.

Same as v1.3.2 but removed the debug console log output... oops!

NOTE: v1.2.8 had underlying code that was not working in all cases. (it determines the date/time of the last time the data underlying a card was received from MQTT.) (In this case, the "{bad value}" indicator is displayed when values are not what was expected from the underlying code.)

This WIP release takes the following actions:

• Adjusted Daemon update indicator to not show if op-to-date (seem to have missed a case(#36))
• Adjusted the coloring indicators (moved all yellow to orange) (#40)
• Replaced the card age calculation code - this should eliminate the {bad value} indications (#37, #39)

Lastly, this is still an interim release as I'm seeing an instability that I'm still chasing. (#38) When found and fixed I'll post another release. The effect this has is that cards appear to slow down their updates (or lose the ability to update?) over time. The workaround is to reload the page. Internally there is an uncaught exception that I'm trying to locate and then catch. But it's taking some time to find.

Work-in-progress release! - Minor color changes, and more indicator fixes.

NOTE: v1.2.8 had underlying code that was not working in all cases. (it determines the date/time of the last time the data underlying a card was received from MQTT.) (In this case, the "{bad value}" indicator is displayed when values are not what was expected from the underlying code.)

This WIP release takes the following actions:

• Adjusted Daemon update indicator to not show if op-to-date (seem to have missed a case(#36))
• Adjusted the coloring indicators (moved all yellow to orange) (#40)
• Replaced the card age calculation code - this should eliminate the {bad value} indications (#37, #39)

Lastly, this is still an interim release as I'm seeing an instability that I'm still chasing. (#38) When found and fixed I'll post another release. The effect this has is that cards appear to slow down their updates (or lose the ability to update?) over time. The workaround is to reload the page. Internally there is an uncaught exception that I'm trying to locate and then catch. But it's taking some time to find.

Work-in-progress release! - card layout repairs, minor color changes

• Updated DRAFT of new indicator to show if RPi has pending Reporter Daemon Update (#36) [If you have time, please read and comment]

NOTE: v1.2.8 had underlying code that was not working in all cases. (it determines the date/time of the last time the data underlying a card was received from MQTT.) (In this case, the "{bad value}" indicator is displayed when values are not what was expected from the underlying code.)

This WIP release takes the following actions:

• Repairing card layout - labels float with card width as they should have
• Adjust the coloring of the RPI update indicator labels
• Generally, preserve the work in progress as I'm cleaning up the original code that needs to be much better

So, if any of you see this "{bad value}..." status I would appreciate it if you could locate the console message: HCUTE (DBG) ( hostname ) card_timestamp_value=[...] and report it back to me within the issue (#37)

Lastly, this is still an interim release as I'm seeing an instability that I'm still chasing. When found and fixed I'll post another release. The effect this has is that cards appear to slow down their updates (or lose the ability to update?) over time. The workaround is to reload the page. Internally there is an uncaught exception that I'm trying to locate and then catch. But it's taking some time to find.

Work-in-progress release! Daemon update needed code now works - update your RPi and flag goes away as it should

• Updated DRAFT of new indicator to show if RPi has pending Reporter Daemon Update (#36) [If you have time, please read and comment]

NOTE: v1.2.8 had underlying code that was not working in all cases. (it determines the date/time of the last time the data underlying a card was received from MQTT.) (In this case, the "{unexpected value}" indicator is displayed when values are not what was expected from the underlying code.)

This WIP release takes the following actions:

• Finish the determination of when an RPi Daemon is out of date and needs an update. Status should now clear when the RPi is updated to the latest.

So, if any of you see this "{unexpected value}..." status I would appreciate it if you could locate the console message: HCUTE (DBG) ( hostname ) card_timestamp_value=[...] and report it back to me within the issue (#37)

Lastly, this is still an interim release as I'm seeing an instability that I'm still chasing. When found and fixed I'll post another release. The effect this has is that cards appear to slow down their updates (or lose the ability to update?) over time. The workaround is to reload the page. Internally there is an uncaught exception that I'm trying to locate and then catch. But it's taking some time to find.

Work-in-progress release! to get everyone back on the air

My bad this obsoletes and replaces v1.2.9 as the github build action failed!

• Partial repair for The values appear and disappear (#37)
• DRAFT of new indicator to show if RPi has pending Reporter Daemon Update (#36) [If you have time, please read and comment]

NOTE: v1.2.8 apparently had underlying code that was not working in all cases. (it determines the date/time of the last time the data underlying a card was received from MQTT.) Additionally, the breakage invoked an additional mechanism that wiped out the card values when it was not known when the last time data was obtained from MQTT. (In this case the "waiting for report" indicator is displayed when values are not what was expected from the underlying code.)

So, this release takes the following actions:

1. Update to the latest version of the underly code.
2. Remove the mechanism that clears card values. (I am not sure if I'll ever put this back in.)
3. Changes the message to "{unexpected value}..." and now logs the unexpected value it got to console.log() at the same time

So, if any of you continue to see this new "{unexpected value}..." status I would appreciate it if you could locate the console message : HCUTE (DBG) ( hostname ) card_timestamp_value=[...] and report what you get back to the issue (#37)

Lastly, this is an interim release as I'm seeing an instability that I'm still chasing. When found and fixed I'll post another release. The effect this has is that cards appear to slow down their updates (or lose the ability to update?) over time. The workaround is to reload the page. Internally there is an uncaught exception that I'm trying to locate and then catch. But it's taking some time to find.

Work-in-progress release! to get everyone back on the air

• Partial repair for The values appear and disappear (#37)
• DRAFT of new indicator to show if RPi has pending Reporter Daemon Update (#36) [If you have time, please read and comment]

NOTE: v1.2.8 apparently had underlying code that was not working in all cases. (it determines the date/time of the last time the data underlying a card was received from MQTT.) Additionally, the breakage invoked an additional mechanism that wiped out the card values when it was not known when the last time data was obtained from MQTT. (In this case the "waiting for report" indicator is displayed when values are not what was expected from the underlying code.)

So, this release takes the following actions:

1. Update to the latest version of the underly code.
2. Remove the mechanism that clears card values. (I am not sure if I'll ever put this back in.)
3. Changes the message to "{unexpected value}..." and now logs the unexpected value it got to console.log() at the same time

So, if any of you continue to see this new "{unexpected value}..." status I would appreciate it if you could locate the console message : HCUTE (DBG) ( hostname ) card_timestamp_value=[...] and report what you get back to the issue (#37)

Lastly, this is an interim release as I'm seeing an instability that I'm still chasing. When found and fixed I'll post another release. The effect this has is that cards appear to slow down their updates (or lose the ability to update?) over time. The workaround is to reload the page. Internally there is an uncaught exception that I'm trying to locate and then catch. But it's taking some time to find.