[–] 2 points 2 months ago

Vorsicht bei Garmin mit Gadgetbridge - Meine Venu funktionierte damit problemlos. Nach einigen Monaten dann Probleme mit der Aufzeichnung, kein GPS-Fix oder erst nach ein bis zwei Kilometer. "Mein" Garmin-Außendienst verriet mir dann, dass die Uhr wohl Positionsdaten aus der App online zieht um den GPS-Fix zu bekommen. Ein mal mit Garmin Connect gesynct und siehe da: GPS sofort wieder da.

  • source
  •  

    crosspost from: https://feddit.org/post/26317173

    Hi,

    I build my own UserModel with email instead of username and now the PasswordResetConfirmView does not render the form for setting a new password. Form is None and Title "Password reset unsuccessful". All other forms are working correct.

    I am using the standard "django.contrib.auth".

    My user-class:

    class MyUser(AbstractUser):
        username=None
        email=models.EmailField(_('email address'),unique=True)
        USERNAME_FIELD='email'
        REQUIRED_FIELDS=[]
    

    My urls.py

    from django.urls import path, include
    from django.contrib.auth import views as auth_views
    
    urlpatterns = [
        path('password_reset/', auth_views.PasswordResetView.as_view(template_name='password_reset.html', html_email_template_name='password_reset_email.html'), name='password_reset'),
        path('password_reset/done/', auth_views.PasswordResetDoneView.as_view(template_name='password_reset_done.html'), name='password_reset_done'),
        path('password_reset/confirm/<uidb64>/<token>/', auth_views.PasswordResetConfirmView.as_view(template_name='password_reset_confirm.html'),name='password_reset_confirm'),
        path('password_reset/complete/', auth_views.PasswordResetCompleteView.as_view(template_name='password_reset_complete.html'),name='password_reset_complete'),
    ]
    

    The reset link in console looks a bit wired:

    Please go to the following page and choose a new password:
    
    http://127.0.0.1:8000/accounts/password_reset/confirm/Mg/d4khhw-79d3d64161aaf=
    78fe9f0542f1883e48c/
    

    Also, there is no redirect to: http://127.0.0.1:8000/accounts/password_reset/confirm/Mg/set-password/

    I tried clicking the link, copying it. Nothing works. What am I missing here. Some tips would be appreciated.

    [–] 6 points 1 year ago

    Habe Tibber. Eine Person tagsüber zu Hause. E-Auto. Beste Wahl bisher. Habe gerade mal bei Check24 geguckt. Komme mit Festpreis in Hamburg aktuell auf 34 Cent. Unser Nutzungsprofil bei Tibber ca. 27 Cent im Schnitt. Ginge günstiger, wenn wir zu billigeren Zeiten vorkochen würden. Um eine App wirste vermutlich nicht rum kommen.

  • source
  • [–] 3 points 1 year ago

    Genau das. Für mich liest sich der Artikel so, als müsste möglichst oft Lichtbilck drin stehen. Normalerweise habe ich einen EnBW-Vertrag, war aber letztens in einer Gegend ohne EnBW. Konnte an Ladesäulen parken ohne Parkgebühren (muss man also rausrechnen) und teilweise AdHoc-Laden für 49 Cent bei 50 kW

  • source
  • parent
  • context
  •  

    Hi guys. Got some curious behavior.

    HA (automation) switches the TRV from off to heat to off to heat...

    As I changed the TRVs (Bosch to Sonoff) a few days before, I first thought, it is the new one. Looking through the logs, it also happened with the old one. I am not sure, but it looks like it happens since the last HA Update. Currently running 2025.1.4.

    The automation checks on every room-temperature change if it is over or under the target temp. It switches from heat to off after the room has reached the target and switches from off to heat if the temp is under the target.

    For example a is 20°C, it happens between 20°C and 21°C. If the setting is heat and the temperature is between 20 and 21 the TRV is switched to off or the other way, if it is on off. I tried to round the temp, but this does not change the behavior. It is always switching to the other setting in this 1°C range. If the room temperature in this example is over 21°C it stays off. Under 20°C it stays on heat.

    I never noticed this before, so I think something has changed with 2025.1 but I don't know what and can't find a solution.

    Maybe somebody can point me in the right direction to find the error.

    view more: next ›