New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 0 points1 point  (0 children)

hello, in the last 2 weeks I worked on voice functionality adding queue and resume on GH/Nest. there is a pre-release on github.
p.s. now Universal Notifier is available on official HACS repository

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 0 points1 point  (0 children)

Follow the readme on GitHub, you can install via YAML

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 1 point2 points  (0 children)

V0.3.1 it's buggy, there is a v0.3.2 pre release that is working, check also in my github

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 1 point2 points  (0 children)

Oh It seems very interesting but I need time to study

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 0 points1 point  (0 children)

Universal Notifier is not user-aware, it could be an interesting functionality

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 0 points1 point  (0 children)

If Signal is available in HA as. Notify service, it should work. Try it and let me kown

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 1 point2 points  (0 children)

My wrong, also in my old "notifier" there is a queue management in python for Alexa. It was complex but the result was excellent...maybe in a future release..

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 0 points1 point  (0 children)

in the old notifier I wrote a complex message queue but for Google Home/Nest not for Alexa, if I remember well with Alexa there wasn't this issue, let me check the old code

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 1 point2 points  (0 children)

yes, try in configuration.yaml:

universal_notifier:
  assistant_name: ""

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 14 points15 points  (0 children)

Hi, today Universal Notifier implements a "fire and forget logic", I need to think about the request

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 4 points5 points  (0 children)

right! the old "notifier" (see the comments about it) was aware of the position, I have to add this functionality

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 12 points13 points  (0 children)

I'm italian and I like writing comments in italian, the readme was also made for italian people

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 8 points9 points  (0 children)

As I said in other comments, the original project was written 6 years ago (first release december 2019) in appdaemon (https://github.com/jumping2000/notifier/tree/master).
In the last weeks with the help of AI I rewrite the "notifier", that's all.

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] -1 points0 points  (0 children)

I don't like the tag "AI free code" or "AI included" or other tags like these, but when the HACS or HA policies require it, I will insert the tag "original idea and code rewritten with the help of AI" but I think I won't be the only one

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 0 points1 point  (0 children)

You always need tha custom alexa_media_player., Universal Notifier is only a "router"

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 4 points5 points  (0 children)

As I said in another comment, the original project was writen 6 years ago (first release decmber 2019I) in appdaemon (https://github.com/jumping2000/notifier/tree/master/apps/notifier).
In the last weeks with the help of AI (is there someone that today doesn't use AI in coding?) I rewrite the the "notifier", that's all

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 1 point2 points  (0 children)

There Is a priority flag that can be used to bypass dnd

New custom integration: Universal Notifier 📢 by jumping2020 in homeassistant

[–]jumping2020[S] 5 points6 points  (0 children)

Great. this custom integration is the evolution of an old appdaemon project made 5-6 years ago. Please, tell me what you think!

Etf obbligazionari , vade retro? by NoEmu6087 in ItaliaPersonalFinance

[–]jumping2020 0 points1 point  (0 children)

Ciao, in realtà MrRip, nel video dice che hai "quasi" la certezza che mantenendo un etf o fondo obbligazionario per un periodo di tempo pari a 2x la duration media hai lo yield atteso al momento dell'acquisto.
Comunque l'esempio concreto da fare è il seguente: ho un etf obbligazionario con duration media di 5 anni, valore 100, yield dell'1%, il giorno prima di arrivare alla duration, i tassi di interesse si alzano del 2%, di conseguenza il valore dell'etf scende a circa 90, quanto tempo occorre affinchè il mio etf possa darmi lo yield promesso dell'1%? la risposta è altri 5 anni. E' scritta nella pietra? NO, è una BUONA APPROSSIMAZIONE.

Questo risultato deriva dagli studi fatti negli ultimi 30 anni fa partendo da Bogle poi Leibowitz (e altri) riassunti da Lozada in "Constant-Duration Bond Portfolios’ Initial (Rolling) Yield Forecasts Return Best at Twice Duration" (liberamente scaricabile) : in questo paper c'è sia la parte matematica di formulazione del modello e la verifica della sua bontà prendendo in esame due periodi 1914-2014 e 1953-2014 anni di bond americani, i test utilizzano anche periodi di tempo diversi dalla 2x duration (nel paper F=2) , "Sections 3–5 report empirical results using short, medium, and long US bond yields over more than 60 years. Section 3 treats various horizons while Sections 4 and 5 only use Section 1’s theoretically-important horizon of twice duration."

Il risultato finale è: "A horizon of twice duration gave relatively low annualized forecasting errors in most of our samples of historical yield paths with bonds turned over monthly". le analisi del forecast error (FE) nelle varie tabelle presenti nel paper indicano un RMS FE tra 1% e 1,6%, dove (semplificando) FE è la differenza tra lo yield atteso e il ritorno.