You’re right. The NEFF integration.
I didn’t start the integration in debugging mode. As soon as I’m back home, I’ll do.
The remaining program time is only published when the dishwasher is on. Same with the oven and by the way with other errors (Mercedes integration charging end)…
Do you have a greater problem, with your router not fetching the correct time via NTP and allowing devices accessing it over the Internetz?
Check your router NTP settings and make sure a valid NTP server is configured and the local time zone and daylight savings parameters are correct. Use the NPT server local to you, not the global one. Verify the time on the router is updated and correct.
Do you have something filtering NTP traffic?
Your integration may be working correctly, just not getting the correct time. The debugging logs will probably give more clues. Turn on debugging mode, turn your dishwasher on, and then wait a few minutes and turn it back off. Please make sure any logs are posted in formatted format </>
Comment: The integration should allow for graceful degradation rather than crashing for what could be a common problem. Your help could unearth a bug that has been lurking…
I can exclude a NTP problem in the network. The router is well configured with a local NTP server (german one) and the devices in the network getting the published time without any problems.
I’ll do the debugging as soon as I’m on site…
The first suggestion shows the “actual time” if the device (time) is 0. The second shows the complete timestamp. I just want the time to end in HH:MM. So I did this:
- name: "Geschirrspueler Programmende"
unique_id: geschirrspueler_ende
state: >
{% set t = states('sensor.neff_geschirrspuler_remaining_program_time') | int(-1) %}
{% if t > 0 %}
{{ (now() + timedelta(minutes=t)).strftime('%H:%M') }}
{% else %}
Nicht verfügbar | Läuft nicht
{% endif %}