text:
🛑 Reime ohne Sinn und Verstand is down

In 9aea3a1, Reime ohne Sinn und Verstand (https://www.reimeohnesinnundverstand.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Reime ohne Sinn und Verstand is back up in cfd46b8 after 8 minutes.


text:
🛑 LM Bogen WSV is down

In 40fc519, LM Bogen WSV (https://www.lmbogenwsv.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LM Bogen WSV is back up in ba7223e after 17 minutes.

source: gharchive/issue

repo: hjstrauss/MonitorMySites

license: MIT

license_type: permissive

license_source: github-api


text:
impl ci_python

概要

チケットリンク

やったこと

申し送り事項

特にレビューしてほしいこと

動作確認

memo: https://github.com/hashicorp/setup-terraform#usage を使うのにnodeが必要という話
手動でインストールするほうが幸せな気がする。（setup-terraform使えない環境でも利用できるようになるし）

source: gharchive/pull-request


text:
The length of samples

It seems each sample in the deita dataset consists of a lot of turns and is super long (>10k tokens). Your paper mentioned the max length of input is 2048 for SFT. Does that mean most text of each training sample is truncated and discarded?

Hi. Yes, for those samples whose length are longer than model_max_length, we simply truncate these samples to 2048.

repo: hkust-nlp/deita


text:
+eval/buffer in emacs-lisp-mode doesn't eval the whole buffer

HI, I'm not sure if this is the desired behavior. When doing +eval/buffer in elisp buffer, only the top first sexpr is evaluated. This is quite different from eval-buffer.

Found and fixed the issue. +emacs-lisp-eval wasn't wrapping the buffer's code in a progn, causing only the first form to be read. The fix is now in develop. I'll keep this open until it's in master.

authors: amosbird hlissner

repo: hlissner/doom-emacs


text:
org-roam v2 backlinks panel shows the whole link content instead of relevant part

What did you expect to happen?
When I open an org-roam node, the backlinks panel on the right should show all nodes that reference the currently open node, but only the backlinks' titles and the relevant paragraphs where the referenced node is linked.
What actually happened?
The backlinks panel show the whole backlinking node content, including the PROPERTIES drawer. That didn't happen in revision 4eeb3c7a19 (5 weeks ago, see comparison)

Describe your attempts to resolve the issue
No response
Steps to reproduce

Install org-roam by including (org +roam2) in Doom's init.el
Run doom sync
Open emacs
Create an org-roam node
Create a second org-roam node
Insert a link to the first node in the second node
Open the first node's window and the backlinks panel will appear automatically, showing the entire second node content.

System Information
https://pastebin.com/6brTeuQQ

Isn't the same problem as here https://github.com/org-roam/org-roam/issues/1934?

This issue should now be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

Hi @hlissner, sorry for the late response! I've just upgraded Doom and the issue is still there.
Doom emacs	v21.12.0-alpha   HEAD -> develop af7c1d79b 2021-12-18 01:13:37 +0100
Doom core	v3.0.0-alpha     HEAD -> develop af7c1d79b 2021-12-18 01:13:37 +0100

authors: brunoarine hlissner mandos


text:
Suggestion: a couple more modeline truncation options

Hey, this is not a huge deal, but allow me to make my case! :-)
I am currently working on a project that has stupidly-long namespaces (kind of like Java...) in Haskell. For instance, I can be working on such files as:
language-ocaml/test/Language/OCaml/Parser/Implementation/Test.hs
language-ocaml/test/Language/OCaml/PrettyPrinter/Implementation/Test.hs
language-ocaml/lib/Language/OCaml/Parser/Implementation.hs
language-ocaml/lib/Language/OCaml/PrettyPrinter/Implementation.hs

Unfortunately, the available options for +doom-modeline-buffer-file-name-style are never satisfactory:
truncate-upto-project shortens nothing.
truncate-upto-root only shortens the very first part (language-ocaml), but I still have the stupidly-long folders.
truncate-all gives:
l/t/L/O/P/I/Test.hs
l/t/L/O/P/I/Test.hs
l/l/L/O/P/Implementation.hs
l/l/L/O/P/Implementation.hs

which is too short to make sense of, and has collisions...
The relative options don't help much since most of the path is in the project.
What I would consider interesting alternatives:

defining the truncation length, for instance, I'd love a truncation length of 3:

lan/tes/Lan/OCa/Par/Imp/Test.hs
lan/tes/Lan/OCa/Pre/Imp/Test.hs
lan/lib/Lan/OCa/Par/Implementation.hs
lan/lib/Lan/OCa/Pre/Implementation.hs

being able to truncate keeping only uppercase letters, or dash/underscore-separated initials, for instance:

l-o/t/L/OC/P/I/Test.hs
l-o/t/L/OC/PP/I/Test.hs
l-o/l/L/OC/P/Implementation.hs
l-o/l/L/OC/PP/Implementation.hs

truncating up to parent folder:

l/t/L/O/P/Implementation/Test.hs
l/t/L/O/P/Implementation/Test.hs
l/l/L/O/Parser/Implementation.hs
l/l/L/O/PrettyPrinter/Implementation.hs

Have you considered any of these? I'd be happy trying to write some implementation if you'd like help, and would be happy adding them in the mix.
Best regards, thanks for all the hard work! <3

I have run up against this problem myself, so I'd happily welcome a PR for these. The 2.1 release has me swamped, so I'd appreciate the help.

I can see the use case. I will be having a look at bringing out a new version of shrink-path that has new functions to allow for more options.

Since this has been implemented in :ui doom-modeline and the new :ui modeline module (which will eventually replace :ui doom-modeline when Doom drops Emacs 25 support), I'll consider this resolved.
:ui modeline has the +modeline-buffer-path-function variable, which lets you use one of the predefined path builder functions or define your own.

authors: Ptival bandresen hlissner


text:
bin/doom command to update init.el based on init.example.el

There is currently no way to update init.el based on init.example.el.
I was thinking of something like bin/doom update-init-file, that, through el macros, would update init.el with missing entries from init.example.el.
That way, each time a new feature is pulled from develop into .emacs.d/init.el, if the user runs bin/doom update-init-file, their .doom.d/init.el would contain new features.
That would require to modify the current text schema (feature, comment) to be more lispy. Something like:
(doom! :feature
    eval               ; run code, run (also, repls))

(doom! :feature
    eval :enabled t :desc "run code, run (also, repls)")

If @hlissner thinks that's a valuable idea, I'd like to do a POC as an exercise on macros.

Spacemacs has a nice feature where it just opens ediff to merge the new
example file into your example. That'd do the job for me.
On Sun, 28 Oct 2018, 5:08 pm Quentin Le Guennec, notifications@github.com
wrote:

There is currently no way to update init.el based on init.example.el.
I was thinking of something like bin/doom update-init-file, that, through
el macros, would update init.el with missing entries from init.example.el.
That way, each time a new feature is pulled from develop into
.emacs.d/init.el, if the user runs bin/doom update-init-file, their
.doom.d/init.el would contain new features.
That would require to modify the current text schema (feature, comment) to
be more lispy. Something like:
(doom! :feature
eval               ; run code, run (also, repls))
(doom! :feature
eval :enabled t :desc "run code, run (also, repls)")
If @hlissner https://github.com/hlissner thinks that's a valuable idea,
I'd like to do a POC as an exercise on macros.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hlissner/doom-emacs/issues/984, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABRjt7VxXgG2c6ijBoSf_QNUYUxyXAuks5upeSogaJpZM4X-Ekf
.

I've had this sitting my local branch for a while. I'm not sure if it'll make it into Doom in its current incarnation, but it will eventually:
(defun doom--get-modules (file)
  (unless (file-exists-p file)
    (user-error "%s does not exist" file))
  (with-temp-buffer
    (insert-file-contents file)
    (when (re-search-forward "(doom! " nil t)
      (goto-char (match-beginning 0))
      (cdr (sexp-at-point)))))

(defun doom--put-modules (tmpfile modules)
  (with-temp-file tmpfile
    (delay-mode-hooks (emacs-lisp-mode))
    (insert (replace-regexp-in-string " " "\n" (prin1-to-string modules)))
    (indent-region (point-min) (point-max))))

;;;###autoload
(defun doom/what-has-changed ()
  "Open an ediff session to compare the module list in
~/.emacs.d/init.example.el and ~/.doom.d/init.el."
  (interactive)
  (let ((old-modules (doom--get-modules (expand-file-name "init.example.el" doom-emacs-dir)))
        (new-modules (doom--get-modules (expand-file-name "init.el" doom-private-dir)))
        (example-init-el "/tmp/doom-init.example.el")
        (private-init-el "/tmp/doom-private-init.el"))
    (doom--put-modules example-init-el old-modules)
    (doom--put-modules private-init-el new-modules)
    (ediff private-init-el example-init-el)))

Just realized this is a duplicate of #581, as well, so I'll close this.

authors: hlissner ocharles qleguennec


text:
fix multiframe.

I've tested it with 10+ multiframes, creation, deletion, and mixed terminal / GUI frames. It works quite well.

13bffc5 should address your issues. Please update and let me know.

Hmm, https://github.com/hlissner/doom-emacs/commit/13bffc54bd2b5aa4258fbb8e7317bc33488c19b2 doesn't load theme at emacs start using emacsclient -a


text:
feat: add martech plugin to connect to analytics and target

This PR adds integration with Target, Launch & ACDL via the martech library. It also moves the Analytics instrumentation to the martech library, and creates a more generic loader to combine the GTM and WebSDK logic and isolate it from the main scripts.js file.
At a high level:

lib-analytics.js is renamed to lib-martech-loaded.js

inline scripts are changed to direct execution to avoid HTML parsing
consent is updated to v2 API
conversion, GTM, alloy and click trackings are all moved to the martech loader
launch and analytics envs will be mapped as follows:

*.petwatch.com => prod
*.live / *.page urls => stage
everything else => dev

a new trackAnalyticsEvent method is exported to specifically track events in Analytics instead of GTM
updates alloy.js to v2.21.1

Adobe martech library is add as plugins/martech
head.html gets new preload/preconnect links for resources immediately imported, so we don't have to wait for scripts.js to be parsed.

Test URLs:

Before: https://main--24petwatch--hlxsites.hlx.live/
After: https://martech-lib--24petwatch--hlxsites.hlx.live/

@fe-lix- @ekremney @bohnertchris Since I did quite some heavy lib-analytics.js refactoring for this, if you know the various analytics events they were tracking before, could you perform a quick sanity check to make sure we didn't lose anything along the way?

@ramboz it has been almost 1 year since the custom analytics events were implemented for this project. I am afraid I cannot recall all the details. The most important events were tracked by GA4 via trackGTMEvent

authors: ekremney ramboz


text:
Yelp Integration

Fix #42
Test URLs:

After: https://feat-community-amenities--hsf-commonmoves--hlxsites.hlx.live/drafts/stopp/communities/acton

Missed text: "Explore the best restaurants, businesses, and activities near Acton". After section title

Yeah, it was on the preview page. Just a miss on publish link, not part of the integration block though.

repo: hlxsites/hsf-commonmoves


text:
[core] Provide a way to customize which elements get created

Right now, once you import "three-elements", all of Three.js will be imported, and custom elements will be generated for all of its (constructible) members. This is fine for quick hosted examples, but makes it impossible to just selectively import parts of Three.js, or perform tree-shaking in a build pipeline that offers this.
Suggestion:

Move the meat of the current three-elements package to a new package @three-elements/core and make importing that package side-effect free
Provide a way to selectively generate elements for a list of user-provided Three.js classes
(Maybe use the opportunity to also allow the user to customize the naming of the tags, eg. use a t- prefix instead if a three- one)
Reduce the three-elements package in scope so it just imports core and performs the brute-force initialization it's been doing so far.

This way, if you just want "everything", you can keep importing from "three-elements"; if you don't, you'll work with @three-elements/core and explicitly ask it to set up elements for you, following your configuration.

There's some good discussion in this webcomponents-cg issue that suggests we should think about this some more before doing anything crazy, so I'm deferring this to the next milestone.

repo: hmans/three-elements


text:
RDM-12097: Fortify Issue 13318075 - Null Dereference

JIRA link
https://tools.hmcts.net/jira/browse/RDM-12097
Change description
Fixed NULL dereference issue
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Code cleanup moved to RDM-12121

repo: hmcts/ccd-definition-store-api


text:
scheduler to act on stale PRs

scheduler to act on stale PRs
Fixing CVE - CVE-2022-38752

closing due to build error

repo: hmcts/civil-service


text:
CIV-9407 Trial Arrangements: Email Notification to Citizen on Completion of Trial Arrangements by the Defendant LiP

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-9407
Change description
Logic driving email notifications send to each party when the other completed their trial arrangements

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Closing PR as ticket is in Blocked

Removing enable helm and closing PR as ticket is dev blocked


text:
RST-6267 new password configuration

Jira link (if applicable)
https://tools.hmcts.net/jira/browse/RST-6267

Odd git log history

repo: hmcts/hwf-staffapp


text:
DTSPO-15909 - migrated Application Insights

Jira link (if applicable)
https://tools.hmcts.net/jira/browse/DTSPO-15909
Change description
Updating azurerm_application_insights resource and replacing it with module terraform-module-application-insights
This will allow us to migrate Classic Application Insights using https://github.com/hmcts/app-insights-migration-tool as Classic Application Insights will deprecated and will be retired in February 2024.

hi, could this be closed please? these files don't exist in this repo

odd - not sure how I have added those files, I can see app insights exist on the main.tf file and going to amend that and raise new PR.  Thanks

repo: hmcts/pre-shared-infrastructure


text:
Rwa 450 new

JIRA link (if applicable)
Change description
Unclaim Pact provider
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ x ] No

Closing in favour of re-created pr:
https://github.com/hmcts/wa-task-management-api/pull/253

repo: hmcts/wa-task-management-api


text:
CTCP-4613: Document type page

Hey Tega, it may be worth taking a look at what we've done in Documents. We prefixed the documents with the relevant document type so they could see which types they were adding


text:
[SASS-257] gift aid journey one off page

Description
Please include a brief summary of the change you've made and the issue that it fixes.
Add a link to the relevant story in Jira
SASS-257
Checklist PR Reviewer
Before Reviewing

[x]  Have you pulled the branch down?
[x]  Have you assigned yourself to the PR?
[x]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?

Whilst Reviewing

[x]  Have you run the tests?
[ ]  Have you run the journey tests?
[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ]  Have you checked for merge conflicts?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

Checklist PR Raiser
Before creating PR

[x]  Have you run the tests?
[x]  Have you run the journey tests?
[x]  Have you addressed warnings where appropriate?

After PRs been Reviewed

[ ]  Have you checked the PR Builder passes?
[ ]  Have you checked for merge conflicts?
[ ]  Have you checked code coverage isn’t lower than previously?

Will finish reviewing this on monday but can we address these warns?

authors: juamalBlackman robert-webb-hmrc


text:
[FEAT] : API Endpoint To Retrieve Product Categories

Description
Create an API endpoint that allows an authenticated user retrieve all product categories thus providing essential information for product navigation and filtering.
This endpoint will validate the user and then return all product categories stored in the database.
Acceptance Criteria

The endpoint allows an authenticated user retrieve a list of all product categories.
Returns a 200 status code and the correct response body when the data is successfully retrieved.
Returns a 401 status code when the user is not authenticated
Returns a 500 status code when a server error occurs

Requirements

Implement API endpoint for retrieving product categories.
Ensure response is properly structured.
Handle unexpected errors and return the appropriate status code.

Expected Outcome

Users should be able to send a request to the backend to retrieve all the product categories.

Endpoints
[GET] /api/v1/products/categories

Description: Get All Product Categories.

Responses

Success Response:

Status: 200 OK
Body:

{
  "success": true,
  "message": "Categories retrieved successfully",
  "status_code": 200,
  "data": [
     {
     "name": "Category_1",
     "id": "id_1",
   },
    {
     "name": "Category_2",
     "id": "id_2",
   }
  ]
}

Unauthorized Response:

Status: 401 Unauthenticated
Body:

{
  "success": false,
  "message": "Not authenticated",
  "status_code": 401
}

Server Error Response:

Status: 500 Server Error
Body:

{
  "success": false,
  "message": "<string>",
  "status_code": 500
}

Test Scenarios

Successful Retrieval of Product Categories

Ensure that the endpoint successfully retrieves all categories in the database.
Confirm that the status code is 200.
Verify that the response body contains the retrieved data.

Unauthenticated Request

Send a request without being authenticated.
Verify that the endpoint returns a 401 Unauthenticated status code.

Referred from the main Boilerplate repo https://github.com/hngprojects/hng_boilerplate_nestjs/issues/257


text:
#423 Avoidance of multiple parallel etl processes

Revised the /etl/scripts/run_etel.sh script to create a lockfile called ETLlock which prevents parallel execution of the script.
Closes #423

Looks good!

authors: DanielKraft mhendlich

repo: hochschule-darmstadt/einander-helfen


text:
Update: typo

update typo

@asashiho thanks!

authors: asashiho hoisjp

repo: hoisjp/MCW-Cloud-native-applications


text:
Cache bust generates triple query param

Grunt task
    grunt.initConfig({
        pkg: grunt.file.readJSON('package.json'),

        cacheBust: {
            build: {
                options: {
                    queryString: true,
                    baseDir: './assets/',
                    jsonOutput: true,
                    assets: ['css/**/*.css', 'js/**/*.js'],
                },
                files: [{
                    expand: true,
                    src: ['./views/**/*.ejs']
                }]
            }
    })

Result:
    <script src="/js/plugins/jquery.js?3210f0f7a3c99d2e?3210f0f7a3c99d2e?3210f0f7a3c99d2e"></script>

as I see relates to https://github.com/hollandben/grunt-cache-bust/pull/227

repo: hollandben/grunt-cache-bust

license: mit

license_source: bigquery


text:
SSH Server won't start (button goes Red....no entry in log)

I believe this is a known issue but I can't see that anyone has documented a solution so far. If I can't use the bash shell in the container to edit my yaml files (see previous issue logged) and I can't SSH in, then how are users managing their HA files?
Clearly I'm missing something!

Thank you for reaching out.  We use GitHub for tracking issues, not for providing support.
If you are in need of support, you should try our Community Forum or join our Discord chat server.
You are more likely to get the answer you are looking for in those places.
Thanks! 👍

authors: frenck jmesberg

repo: home-assistant/hassio-build


text:
Unable to install beta 0.95.0b1 on Tinkerboard

Description of problem:
Running Hassio on a Tinkerboard and receives this messages when trying to install the update.
Traceback (if applicable):
19-06-23 08:11:46 ERROR (SyncWorker_5) [hassio.docker.interface] Can't install homeassistant/tinker-homeassistant:0.95.0b1 -> 404 Client Error: Not Found ("manifest for homeassistant/tinker-homeassistant:0.95.0b1 not found").
19-06-23 08:11:46 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

Thanks for reporting this is. This is addressed and will be noticeable on the next release.

authors: KentEkl frenck

repo: home-assistant/hassio


text:
"hassio ho hardware" command returns "Error decoding json invalid character ':' after top-level value: 404: Not Found"

Typing hassio ho hardware
returns: Error decoding json invalid character ':' after top-level value: 404: Not Found
Versions:
Supervisor:
Version | 0.101
Channel | beta
Home Assistant
0.67.0b1

Yes, we need update the cli @ryanm101

/move home-assistant/hassio-cli

Fixed by https://github.com/home-assistant/hassio-cli/pull/73

I'm now getting this issue and am unsure how to resolve it. I've upgraded to hassio 70.0, but I'm not sure how to check version of the CLI or upgrade it.

@Burnett2k hassio --version
you may need to update the ssh addon

I'm currently at 1.2.1
I just ran hassio ad update --name core_ssh which updated my SSH addon from v3.4 to v3.6 . When I try to run most commands I still get an error.
Also, even when I completely reboot my machine it still gets in this bad state where I cannot even access the web interface at all. It has been down for about 3 days now.
core-ssh:~# **hassio -d ha restart**
DEBUG [CmdHomeassistant]: action->'restart', endpoint='restart', serverOverride->'', GET->'false', options->'', rawjson->'false', filter->''
DEBUG [ExecCommand]: basepath->'homeassistant', endpoint->'restart', serverOverride->'', get->'false', Options->'', Filter->'', RawJSON->'false'
DEBUG [GenerateURI]: basepath->'homeassistant', endpoint->'restart', serverOverride->''
DEBUG [RestCall]: data->'http://hassio/homeassistant/restart', GET->'false', payload->''
DEBUG [RestCall]: ResponseBody->'{"result": "error", "message": null}'
ERROR
panic: interface conversion: interface is nil, not string
goroutine 1 [running]:
panic(0x2c7050, 0x1070b720)
        /home/travis/.gimme/versions/go1.7.6.linux.amd64/src/runtime/panic.go:500 +0x33c
github.com/home-assistant/hassio-cli/command/helpers.DisplayOutput(0x107b6200, 0x24, 0x200, 0x0)
        /home/travis/gopath/src/github.com/home-assistant/hassio-cli/command/helpers/common.go:118 +0x3c8
github.com/home-assistant/hassio-cli/command/helpers.ExecCommand(0x2f6f83, 0xd, 0x7eb05e61, 0x7, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
        /home/travis/gopath/src/github.com/home-assistant/hassio-cli/command/helpers/common.go:155 +0x308
github.com/home-assistant/hassio-cli/command.CmdHomeassistant(0x10778420)
        /home/travis/gopath/src/github.com/home-assistant/hassio-cli/command/homeassistant.go:48 +0x540
github.com/urfave/cli.HandleAction(0x2af768, 0x324b14, 0x10778420, 0x0, 0x0)
        /home/travis/gopath/src/github.com/urfave/cli/app.go:503 +0xf0
github.com/urfave/cli.Command.Run(0x2f6f83, 0xd, 0x0, 0x0, 0x40bd10, 0x1, 0x1, 0x301e4d, 0x2f, 0x0, ...)
        /home/travis/gopath/src/github.com/urfave/cli/command.go:165 +0x6b8
github.com/urfave/cli.(*App).Run(0x107648c0, 0x1070a160, 0x4, 0x4, 0x0, 0x0)
        /home/travis/gopath/src/github.com/urfave/cli/app.go:259 +0x8b0
main.main()
        /home/travis/gopath/src/github.com/home-assistant/hassio-cli/main.go:22 +0x108

Error decoding json invalid character '\x1b' looking for beginning of value: 18-06-02 09:53:24 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 09:53:36 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 09:53:36 INFO (SyncWorker_12) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 09:53:38 INFO (SyncWorker_12) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 10:03:39 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 10:03:52 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 10:03:52 INFO (SyncWorker_14) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 10:03:53 INFO (SyncWorker_14) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 10:04:12 INFO (MainThread) [hassio.snapshots] Found 1 snapshot files
18-06-02 10:04:12 INFO (MainThread) [hassio.host.info] Update local host information
18-06-02 10:04:12 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
18-06-02 10:13:54 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 10:14:07 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 10:14:07 INFO (SyncWorker_4) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 10:14:09 INFO (SyncWorker_4) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 10:24:09 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 10:24:13 ERROR (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant API!
18-06-02 10:24:13 INFO (SyncWorker_10) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 10:24:15 INFO (SyncWorker_6) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 10:34:16 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 10:34:22 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 10:34:22 INFO (SyncWorker_1) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 10:34:25 INFO (SyncWorker_1) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 10:44:26 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 10:44:37 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 10:44:37 INFO (SyncWorker_15) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 10:44:39 INFO (SyncWorker_15) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 10:54:40 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 10:54:53 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 10:54:53 INFO (SyncWorker_4) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 10:54:55 INFO (SyncWorker_4) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 11:04:55 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 11:05:08 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 11:05:08 INFO (SyncWorker_6) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 11:05:10 INFO (SyncWorker_6) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 11:15:10 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 11:15:23 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 11:15:23 INFO (SyncWorker_1) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 11:15:25 INFO (SyncWorker_1) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 11:25:26 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 11:25:38 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 11:25:38 INFO (SyncWorker_15) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 11:25:40 INFO (SyncWorker_15) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 11:35:41 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 11:35:53 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 11:35:53 INFO (SyncWorker_4) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 11:35:55 INFO (SyncWorker_4) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 11:45:56 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 11:46:09 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 11:46:09 INFO (SyncWorker_6) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 11:46:10 INFO (SyncWorker_6) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 11:56:11 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 11:56:24 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 11:56:24 INFO (SyncWorker_1) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 11:56:26 INFO (SyncWorker_1) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 12:06:26 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 12:06:39 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 12:06:39 INFO (SyncWorker_15) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 12:06:42 INFO (SyncWorker_15) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 12:16:42 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 12:16:54 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 12:16:54 INFO (SyncWorker_4) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 12:16:56 INFO (SyncWorker_4) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 12:26:57 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 12:27:10 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 12:27:10 INFO (SyncWorker_6) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 12:27:12 INFO (SyncWorker_6) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 12:37:12 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 12:37:25 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 12:37:25 INFO (SyncWorker_1) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 12:37:28 INFO (SyncWorker_1) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 12:47:29 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 12:47:40 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 12:47:40 INFO (SyncWorker_15) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 12:47:42 INFO (SyncWorker_15) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 12:57:42 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 12:57:55 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 12:57:55 INFO (SyncWorker_4) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 12:57:57 INFO (SyncWorker_4) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 13:07:57 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-06-02 13:08:10 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home-Assistant docker!
18-06-02 13:08:10 INFO (SyncWorker_6) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-06-02 13:08:12 INFO (SyncWorker_6) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.70.0
18-06-02 13:09:28 INFO (MainThread) [hassio.api.security] /addons access from core_ssh
18-06-02 13:09:41 INFO (MainThread) [hassio.api.security] /addons/ssh_server/info access from core_ssh
18-06-02 13:11:58 INFO (MainThread) [hassio.api.security] /addons/core_ssh/info access from core_ssh
18-06-02 13:12:14 INFO (MainThread) [hassio.api.security] /addons/core_ssh/update access from core_ssh
18-06-02 13:12:14 INFO (SyncWorker_1) [hassio.docker.interface] Update docker 3.4 with homeassistant/armhf-addon-ssh:3.6
18-06-02 13:12:14 INFO (SyncWorker_1) [hassio.docker.interface] Pull image homeassistant/armhf-addon-ssh tag 3.6.
18-06-02 13:12:44 INFO (SyncWorker_1) [hassio.docker.interface] Tag image homeassistant/armhf-addon-ssh with version 3.6 as latest
18-06-02 13:12:44 INFO (SyncWorker_1) [hassio.docker.interface] Stop homeassistant/armhf-addon-ssh docker application
18-06-02 13:12:45 INFO (SyncWorker_1) [hassio.docker.interface] Clean homeassistant/armhf-addon-ssh docker application
18-06-02 13:12:45 INFO (SyncWorker_1) [hassio.docker.interface] Cleanup docker images: ['homeassistant/armhf-addon-ssh:3.4']
18-06-02 13:12:49 INFO (SyncWorker_16) [hassio.docker.addon] Start docker addon homeassistant/armhf-addon-ssh with version 3.6
18-06-02 13:13:42 INFO (MainThread) [hassio.api.security] /addons/core_ssh/info access from core_ssh
18-06-02 13:13:54 INFO (MainThread) [hassio.api.security] /homeassistant/restart access from core_ssh
18-06-02 13:13:54 ERROR (MainThread) [hassio.utils] Can't excute restart while a task is in progress
18-06-02 13:15:20 INFO (MainThread) [hassio.api.security] /homeassistant/restart access from core_ssh
18-06-02 13:15:20 ERROR (MainThread) [hassio.utils] Can't excute restart while a task is in progress
18-06-02 13:16:07 INFO (MainThread) [hassio.api.security] /supervisor/logs access from core_ssh

Unfortunately, my last snapshot is from ~6 months ago, but I do have all my configs stored in git so I'm thinking the best thing to do may be to just revert to the snapshot and get a new build of Hassio running?  Unfortunately, the logs don't seem to be giving any good indication of the problem.


text:
Cameras not updating 'last_changed' or 'last_updated'

Home Assistant release (hass --version):
0.20.3
Python release (python3 --version):
3.4.2
Component/platform:
Camera Component
Description of problem:
Cameras do not update their 'last_changed' or 'last_updated' values. They seem to set once each time HA restarts, and then they do not change.
Expected:
Cameras should update both of the mentioned values whenever the file has changed/updated.  For something like a Foscam camera, maybe both values would update with the date that the last image was grabbed.  For generic IP camera, maybe the values update the last time the still image changed.

My unifi micro shows the last change as the last reboot.

A camera is updating all the time so this wouldn't make any sense to update
the last updated attribute. It would spam the event bus, history and
logbook
On Sun, Jun 5, 2016, 16:33 Alex Harvey notifications@github.com wrote:

My unifi micro shows the last change as the last reboot.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/2216#issuecomment-223844744,
or mute the thread
https://github.com/notifications/unsubscribe/ABYJ2q6Xha67jQ37qD_KzInxfy1h5Dj5ks5qI1zVgaJpZM4ItB4s
.

Agreed. Will close. not a bug.

What about updating whenever "/api/camera_proxy/...." is called?

That would show last access, rather then event bus change.
Event exist to help with automation, I dont see how that would help with automation.

I found a way around the issue, thanks.
Does HA temporarily store any images that it grabs?  If so, are these accessible via the API?  If not, totally fine

authors: balloob infamy tySwift93

repo: home-assistant/home-assistant


text:
Update fails due to pip3

Home Assistant release with the issue:
0.90.2
Operating environment (Hass.io/Docker/Windows/etc.):
Ubuntu 18.04.2, venv install
Description of problem:
I run
homeassistant@server:/opt/homeassistant$ pip3 install --upgrade homeassistant
and I got some   Cache entry deserialization failed, entry ignored but then it completed.
I run it again and I got
Traceback (most recent call last):
File "/usr/bin/pip3", line 9, in
from pip import main
ImportError: cannot import name 'main'
I found these pages online:
https://stackoverflow.com/questions/49836676/error-after-upgrading-pip-cannot-import-name-main
https://askubuntu.com/questions/726850/pip-upgrade-not-working/726854#726854
I run
homeassistant@server:/opt/homeassistant/bin$ ./python3 -m pip install --upgrade homeassistant
and it worked. Maybe the documentation should be updated.

Are you sure you are in venv? Try pip --version to show which version it is and where is it.
You should execute pip install --upgrade homeassistant not pip3 if you are in the venv.
This is not a bug, if you feel that document can be improved please go to https://github.com/home-assistant/home-assistant.io.

authors: awarecan dewi-ny-je


text:
All components broke after restart

Home Assistant release with the issue: 0.97.1

Last working Home Assistant release (if known): 0.97.1
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io running on RPI3

Component/platform: Multiple

Description of problem:
After a restart almost all of my components that depend on internet broke.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Part of my log

2019-08-13 22:36:00 ERROR (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/customize.yaml contains duplicate key "device_tracker.google_maps_116461996308389920595". Check lines 131 and 163.
2019-08-13 22:36:01 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for blueiris which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-13 22:36:07 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for mind which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-13 22:37:06 ERROR (SyncWorker_11) [homeassistant.util.package] Unable to install package https://github.com/bramkragten/python-mind/archive/master.zip#python-mind==0.0.5: WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x756362d0>: Failed to establish a new connection: [Errno -3] Try again')': /bramkragten/python-mind/archive/master.zip
  WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x75636690>: Failed to establish a new connection: [Errno -3] Try again')': /bramkragten/python-mind/archive/master.zip
  WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x756362f0>: Failed to establish a new connection: [Errno -3] Try again')': /bramkragten/python-mind/archive/master.zip
  WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x756368d0>: Failed to establish a new connection: [Errno -3] Try again')': /bramkragten/python-mind/archive/master.zip
  WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x756321f0>: Failed to establish a new connection: [Errno -3] Try again')': /bramkragten/python-mind/archive/master.zip
ERROR: Could not install packages due to an EnvironmentError: HTTPSConnectionPool(host='github.com', port=443): Max retries exceeded with url: /bramkragten/python-mind/archive/master.zip (Caused by NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x756328f0>: Failed to establish a new connection: [Errno -3] Try again'))
2019-08-13 22:37:06 ERROR (MainThread) [homeassistant.requirements] Not initializing mind because could not install requirement https://github.com/bramkragten/python-mind/archive/master.zip#python-mind==0.0.5
2019-08-13 22:37:06 ERROR (MainThread) [homeassistant.config] Package mind setup failed. Integration mind unable to install all requirements (See /config/integrations/mind.yaml:3).
2019-08-13 22:37:07 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for zigbee2mqtt_networkmap which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-13 22:37:07 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for breaking_changes which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-13 22:37:07 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-13 22:37:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for syncthru which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-13 22:37:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for pushover which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-13 22:38:45 ERROR (SyncWorker_10) [homeassistant.util.package] Unable to install package pysyncthru==0.3.1: WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x757539b0>: Failed to establish a new connection: [Errno -3] Try again')': /simple/pysyncthru/
  WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x757461f0>: Failed to establish a new connection: [Errno -3] Try again')': /simple/pysyncthru/
  WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x75746fd0>: Failed to establish a new connection: [Errno -3] Try again')': /simple/pysyncthru/
  WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x75746b30>: Failed to establish a new connection: [Errno -3] Try again')': /simple/pysyncthru/
  WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x75743fb0>: Failed to establish a new connection: [Errno -3] Try again')': /simple/pysyncthru/
  WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7569d8b0>: Failed to establish a new connection: [Errno -3] Try again')': /alpine-3.10/armv7/
  WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7569d6d0>: Failed to establish a new connection: [Errno -3] Try again')': /alpine-3.10/armv7/
  WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7569d1d0>: Failed to establish a new connection: [Errno -3] Try again')': /alpine-3.10/armv7/
  WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7569da90>: Failed to establish a new connection: [Errno -3] Try again')': /alpine-3.10/armv7/
  WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7569db10>: Failed to establish a new connection: [Errno -3] Try again')': /alpine-3.10/armv7/
  ERROR: Could not find a version that satisfies the requirement pysyncthru==0.3.1 (from versions: none)
ERROR: No matching distribution found for pysyncthru==0.3.1
2019-08-13 22:38:45 ERROR (MainThread) [homeassistant.requirements] Not initializing syncthru because could not install requirement pysyncthru==0.3.1
2019-08-13 22:38:45 ERROR (MainThread) [homeassistant.config] Unable to install all requirements for sensor.syncthru
2019-08-13 22:38:55 ERROR (SyncWorker_18) [homeassistant.components.google.calendar] Unable to connect to Google
2019-08-13 22:38:55 ERROR (MainThread) [homeassistant.core] Error executing service <ServiceCall google.scan_for_calendars (c:7fbf0be4e3af4ffdba733bd3d76237ef)>

Traceback (if applicable):
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 249, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 417, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/components/template/sensor.py", line 220, in async_update
    self._state = self._template.async_render()
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 215, in async_render
    return compiled.render(kwargs).strip()
  File "/usr/local/lib/python3.7/site-packages/jinja2/asyncsupport.py", line 76, in render
    return original_render(self, *args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/jinja2/environment.py", line 1008, in render
    return self.environment.handle_exception(exc_info, True)
  File "/usr/local/lib/python3.7/site-packages/jinja2/environment.py", line 780, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python3.7/site-packages/jinja2/_compat.py", line 37, in reraise
    raise value.with_traceback(tb)
  File "<template>", line 1, in top-level template code
TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'
2019-08-13 23:14:03 WARNING (SyncWorker_7) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x6e04bbb0>: Failed to establish a new connection: [Errno -3] Try again')': /v3/circles.json
2019-08-13 23:14:11 WARNING (SyncWorker_18) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x6e11a050>: Failed to establish a new connection: [Errno -3] Try again')': /v3/circles.json
2019-08-13 23:14:11 WARNING (MainThread) [homeassistant.components.buienradar.sensor] Unable to retrieve json data from Buienradar.(Msg: Cannot connect to host data.buienradar.nl:443 ssl:None [Try again], status: None,)
2019-08-13 23:14:16 WARNING (SyncWorker_18) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x6e0faa30>: Failed to establish a new connection: [Errno -3] Try again')': /v3/circles.json
2019-08-13 23:14:21 ERROR (MainThread) [pyhaversion] Timeouterror fetching version information from PyPi,
2019-08-13 23:14:21 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.potential_breaking_changes fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 249, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 417, in async_device_update
    await self.async_update()
  File "/config/custom_components/breaking_changes/sensor.py", line 29, in async_update
    await update_data(self.hass)
  File "/config/custom_components/breaking_changes/__init__.py", line 113, in update_data
    remoteversion = pypiversion.version.split(".")[1]
AttributeError: 'NoneType' object has no attribute 'split'
2019-08-13 23:14:21 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 825, in _resolve_host
    self._resolver.resolve(host, port, family=self._family)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/resolver.py", line 30, in resolve
    host, port, type=socket.SOCK_STREAM, family=family)
  File "uvloop/loop.pyx", line 1464, in getaddrinfo
socket.gaierror: [Errno -3] Try again

Additional information:

I'm having problems since this morning (after rebooting).  May be related to this, my problem us DNS resolution is now broken on the homeassistant container. Im running hassos, the erver can resolve.  The hassos_supervisor, can resolved. other addons are wording (dnsmasq, dhcp).. but the homeassistant container is not resolvind dns requests.  Ex. ping www.google.com > bad address.

Issue was related to pi-hole and dns server settings in router, is fixed now


text:
Scene: light color temperature not being set when activated

Home Assistant release with the issue: 0.103.0

Last working Home Assistant release (if known): Unknown
Operating environment (Hass.io/Docker/Windows/etc.): Docker

Integration: Light

https://www.home-assistant.io/integrations/light/
Description of problem:
When creating a scene I have a color temperature set for my light. When I activate that scene it only changes the brightness and not the color temperature.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
light:
  - platform: group
    name: Bedroom Lights
    entities:
      - light.bedroom_lamp
      - light.bedroom_fan_light_1
      - light.bedroom_fan_light_2
      - light.bedroom_fan_light_3
      - light.bedroom_fan_light_4
      - light.bedroom_fan_light_5

Additional information:
Command coming from HA:
2019-12-17 00:20:38 DEBUG (SyncWorker_14) [light] Turning on: 2CAA8E325C52 with brightness: 1 and color temp: None

Hey, it looks like you're using JoshuaMulliken/ha-wyzeapi ? I had this problem too, and I think I might have fixed it with JoshuaMulliken/ha-wyzeapi#19.
Give https://github.com/Quantum-cross/ha-wyzeapi a try when you have some time and see if that fixes it for you.

Thank you @Quantum-cross it appears to fix the issue!

oh man I didn't realize that this was opened by you too :D

authors: JoshuaMulliken Quantum-cross


text:
google calendar offset not setting no

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
o.41
Component/platform:
google_calendar
Description of problem:
As per description off the component, when offset is reached the sensor should be set to on. But right now when offset i reached only the offset reached option is true.

Expected:
the sensor should be set to on if the offset i reached

Hallo @balloobbot, no the issue is still not fixed, even in the newest 45.1 version

I think this can be marked as "won't fix", as per @balloob's comment in #6476:

I am actually against any type of offset inside the calendar component. If I had more time I would have already removed it.
Instead of having an offset in the calendar component, a new calendar automation trigger should be added that implements offsets. This is also how it is done for example for the sun component.

authors: bymem fanaticDavid


text:
Lint cleanup

Description:
Clean up unneeded pylint disables and noqa's.
Checklist:

[ ] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

Thanks!

authors: balloob scop


text:
Add zones to evohome component

Description:
Currently, this component consists of a single Climate device, the Controller. This PR adds Zone devices and associated functionality to the evohome component (a later PR will add DHW functionality).
Related issue (if applicable): None
Pull request in home-assistant.io with documentation (if applicable): Yes, see below.
Example entry for configuration.yaml:
Unchanged from before.
evohome:
  username: YOUR_USERNAME
  password: YOUR_PASSWORD
# location_idx: 0

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io, PR #7486 and PR #7487

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] N/A Tests have been added to verify that the new code works.

@zxdavb Just wanted to let you know that I appreciate this work immensely! Let me know if you want me to help (test) in any way, might have some time next week.

Can be merged when the description is updated with link to docs PR. The docs PR should at least describe the new configuration options.

Right, I remember that the docs PR was already merged.

Looking at the linked PRs I can't find info on the new config options. Please update the open PR with that.

Looking at the linked PRs I can't find info on the new config options. Please update the open PR with that.

I am just trying to get my head around what happened with the docs PR - will chase it.
There is a minor change - added scan_interval.

They appear to be merged, but there's some issues - I will create/submit a new PR & update this PR when that is done.

OK, I've sent a PR for the docs: https://github.com/home-assistant/home-assistant.io/pull/7649

Great! Then we can merge here.

authors: MartinHjelmare rdeknijf zxdavb


text:
Baidu tts

Description:

Update the requirement version, from baidu-aip==1.6.6 to baidu-aip==2.2.8
the option range for speed&pitch, from[0..9] to [0..15]
use the options input in get_tts_audio, to support input options from service tts.baidu_say

Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[X] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

somebody has changed it:)


text:
Fix xiaomi gateway disappearing and builtin light/sensor updates

Description:
Related issue (if applicable): fixes #20329 #20383
This fix addresses next issues:

Gateway disappearing after 2.5 hours of HA uptime
Built-in illumination sensor updates only once (at restart of HA)
Built-in light switch works incorrectly

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @stsergo,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Can confirm code working with setup of 3 gateways.

Sorry for the noob question, I'd like to test it but how can I apply this fix in hassio? SSH or simply activating the beta repository?
Thank you

At the moment the component parses a multicast messages (gw ip -> 224.0.0.50:9898). We could call it "local push". This code change implements polling. It requests the current state of a sensor periodically (via udp). The gateway responds with a unicast message (gw ip -> home assistant ip). For bad networks with broken multicast support this will help somehow. I'm unsure if it's a good change or not. ;-)

At the moment the component parses a multicast message (gw ip -> 224.0.0.50:9898). We could call it "local push". This code change implements polling. It requests the current state of a sensor periodically (via udp). The gateway responds with a unicast message (gw ip -> home assistant ip). For bad networks with broken multicast support this will help somehow. I'm unsure if it's a good change or not. ;-)

My gateway sends only ip in heartbeat messages.
So there is no way to get sensors state without request it.
Example:
U 192.168.2.204:4321 -> 224.0.0.50:9898 #12
  {"cmd":"heartbeat","model":"gateway","sid":"04cf8c91566f","short_id":"0","token":"KknlKETfDUbAQEUa","data":"{\"ip\":\"192.168.2.204\"}"}
#
U 192.168.2.107:48879 -> 192.168.2.204:9898 #13
  { "cmd":"read","sid":"4cf8c91566f"}
#
U 192.168.2.204:9898 -> 192.168.2.107:48879 #14
  {"cmd":"read_ack","model":"gateway","sid":"4cf8c91566f","short_id":0,"data":"{\"rgb\":0,\"illumination\":708,\"proto_version\":\"1.1.2\"}"}```

I am not sure if this is a good idea.
It should at least be configurable, and not the default behavior.

My gateway sends only ip in heartbeat messages.
So there is no way to get sensors state without request it.

Which hardware version of the gateway do you own? It looks like a lumi.v3 with LAN protocol version 1.1.2. I assume there is something wrong with your network. Your log should look like this (without any requests):
2019-01-05 21:32:44 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'motion', 'sid': '158d0001aea71a', 'cmd': 'report', 'data': '{"no_motion":"180"}', 'short_id': 9483}
2019-01-05 21:32:44 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Motion Sensor_158d0001aea71a: off>: {'no_motion': '180'}
2019-01-05 21:33:02 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'magnet', 'sid': '158d0001876595', 'cmd': 'heartbeat', 'data': '{"voltage":3025,"status":"close"}', 'short_id': 1591}
2019-01-05 21:33:02 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Door Window Sensor_158d0001876595: off>: {'voltage': 3025, 'status': 'close'}
2019-01-05 21:34:23 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'weather.v1', 'sid': '158d0001f53706', 'cmd': 'report', 'data': '{"temperature":"1957"}', 'short_id': 18366}
2019-01-05 21:34:23 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'weather.v1', 'sid': '158d0001f53706', 'cmd': 'report', 'data': '{"humidity":"5296"}', 'short_id': 18366}
2019-01-05 21:34:23 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Pressure_158d0001f53706: 1008.3>: {'temperature': '1957'}
2019-01-05 21:34:23 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'weather.v1', 'sid': '158d0001f53706', 'cmd': 'report', 'data': '{"pressure":"100856"}', 'short_id': 18366}
2019-01-05 21:34:23 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Humidity_158d0001f53706: 52.7>: {'temperature': '1957'}
2019-01-05 21:34:23 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'weather.v1', 'sid': '158d0001f53706', 'cmd': 'heartbeat', 'data': '{"voltage":2985,"temperature":"1957","humidity":"5296","pressure":"100856"}', 'short_id': 18366}
2019-01-05 21:34:23 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Temperature_158d0001f53706: 19.6>: {'temperature': '1957'}
2019-01-05 21:34:23 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Pressure_158d0001f53706: 1008.3>: {'humidity': '5296'}
2019-01-05 21:34:23 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Pressure_158d0001f53706: 1008.3>: {'pressure': '100856'}
2019-01-05 21:34:23 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Humidity_158d0001f53706: 52.7>: {'pressure': '100856'}
2019-01-05 21:34:23 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Temperature_158d0001f53706: 19.6>: {'pressure': '100856'}
2019-01-05 21:34:23 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Pressure_158d0001f53706: 1008.6>: {'pressure': '100856', 'temperature': '1957', 'voltage': 2985, 'humidity': '5296'}

My gateway sends only ip in heartbeat messages.
So there is no way to get sensors state without request it.

Which hardware version of the gateway do you own? It looks like a lumi.v3 with LAN protocol version 1.1.2. I assume there is something wrong with your network. Your log should look like this (without any requests):
2019-01-05 21:32:44 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'motion', 'sid': '158d0001aea71a', 'cmd': 'report', 'data': '{"no_motion":"180"}', 'short_id': 9483}

You are right -  lumi.v3 with LAN protocol version 1.1.2
For now my setup is only gateway without any sensors connected to it.
Network setup simple as possible: Apple time capsule as wifi and router. HA at lan, gateway on wifi. No VLANS, no segments.
Due to apple bonjour works as expected I consider that there is no issues with multicast. I also check connectivity by omping tool from my linux laptop and there is no issues also.
My gateway send nothing about built-in sensors until we ask :(
Connected sensors work OK, as I can see from community discussions.

@stsergo This is the multicast message of the gateway. It publishs the state of the light and illumination sensor every 60 seconds:
2019-01-05 18:38:03 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'gateway', 'sid': '34ce0088db0b', 'cmd': 'report', 'data': '{"rgb":0,"illumination":371}', 'short_id': 0}
2019-01-05 18:38:03 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Illumination_34ce0088db0b: 273.0>: {'illumination': 371, 'rgb': 0}
2019-01-05 18:38:03 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Gateway Light_34ce0088db0b: off>: {'illumination': 371, 'rgb': 0}
2019-01-05 19:37:55 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'gateway', 'sid': '34ce0088db0b', 'cmd': 'report', 'data': '{"rgb":0,"illumination":371}', 'short_id': 0}
2019-01-05 19:37:55 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Illumination_34ce0088db0b: 71.0>: {'illumination': 371, 'rgb': 0}
2019-01-05 19:37:55 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Gateway Light_34ce0088db0b: off>: {'illumination': 371, 'rgb': 0}
2019-01-05 20:37:48 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'gateway', 'sid': '34ce0088db0b', 'cmd': 'report', 'data': '{"rgb":0,"illumination":372}', 'short_id': 0}
2019-01-05 20:37:48 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Illumination_34ce0088db0b: 71.0>: {'illumination': 372, 'rgb': 0}
2019-01-05 20:37:48 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Gateway Light_34ce0088db0b: off>: {'illumination': 372, 'rgb': 0

@stsergo This is the multicast message of the gateway. It publishs the state of the light and illumination sensor every 60 seconds:
2019-01-05 18:38:03 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'gateway', 'sid': '34ce0088db0b', 'cmd': 'report', 'data': '{"rgb":0,"illumination":371}', 'short_id': 0}
2019-01-05 18:38:03 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Illumination_34ce0088db0b: 273.0>: {'illumination': 371, 'rgb': 0}
2019-01-05 18:38:03 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Gateway Light_34ce0088db0b: off>: {'illumination': 371, 'rgb': 0}
2019-01-05 19:37:55 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'gateway', 'sid': '34ce0088db0b', 'cmd': 'report', 'data': '{"rgb":0,"illumination":371}', 'short_id': 0}
2019-01-05 19:37:55 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Illumination_34ce0088db0b: 71.0>: {'illumination': 371, 'rgb': 0}
2019-01-05 19:37:55 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Gateway Light_34ce0088db0b: off>: {'illumination': 371, 'rgb': 0}
2019-01-05 20:37:48 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'gateway', 'sid': '34ce0088db0b', 'cmd': 'report', 'data': '{"rgb":0,"illumination":372}', 'short_id': 0}
2019-01-05 20:37:48 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Illumination_34ce0088db0b: 71.0>: {'illumination': 372, 'rgb': 0}
2019-01-05 20:37:48 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Gateway Light_34ce0088db0b: off>: {'illumination': 372, 'rgb': 0

Mine sent only ip :(
What version of firmware do you have? I have 1.4.1_164.0158 out of box.
And how this traffic looks in ngrep?

@stsergo This is the multicast message of the gateway. It publishs the state of the light and illumination sensor every 60 seconds:
2019-01-05 20:37:48 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'gateway', 'sid': '34ce0088db0b', 'cmd': 'report', 'data': '{"rgb":0,"illumination":372}', 'short_id': 0}

I mixed things up: The message is called report.

Is it possible that some firmwares don't send that message and still it's working in HA? I don't see that in log, maybe I don't have enough debugging turned on? Should I see it in meanwhile of normal traffic?

Got it! It's a firmware issue. Firmware version 1.4.1_164.0158 doesn't publish the report message of the gateway anymore. There are some report message but the one of the gateway is missing:
#
U 192.168.130.29:4321 -> 224.0.0.50:9898
  {"cmd":"report","model":"motion","sid":"158d000119fd8c","short_id":56278,"data":"{\"no_motion\":\"300\"}"}
#
U 192.168.130.29:4321 -> 224.0.0.50:9898
  {"cmd":"report","model":"sensor_motion.aq2","sid":"158d00016dc0d8","short_id":14573,"data":"{\"lux\":\"122\"}"}
#
U 192.168.130.29:4321 -> 224.0.0.50:9898
  {"cmd":"report","model":"sensor_motion.aq2","sid":"158d00016dc0d8","short_id":14573,"data":"{\"status\":\"motion\"}"}
#

In this case polling is a workaround.

I'm running latest (at least as of yesterday):
#
U 192.168.x.x2:4321 -> 224.0.0.50:9898
  {"cmd":"heartbeat","model":"gateway","sid":"7811dcdad7a3","short_id":"0","token":"hoFklTtWx9Pxxx","data":"{\"ip\":\"192.168.x.x2\"}"}
#
U 192.168.x.x0:4321 -> 224.0.0.50:9898
  {"cmd":"heartbeat","model":"gateway","sid":"34ce008c0674","short_id":"0","token":"7ABTqZJM6tsxxx","data":"{\"ip\":\"192.168.x.x0\"}"}
#
U 192.168.x.x1:4321 -> 224.0.0.50:9898
  {"cmd":"heartbeat","model":"gateway","sid":"34ce008c136a","short_id":"0","token":"VikVbxsquqf2xxx","data":"{\"ip\":\"192.168.x.x1\"}"}
#

Those are the heartbeats, right?
GW itself identifies as lumi.v3 but some time ago it was lumi v2 (?) and protocol in APP changed from LAN to WiFi (mihome).

@andriej This is the message we are looking for:
# 'cmd': 'report'
{'model': 'gateway', 'sid': '34ce0088db0b', 'cmd': 'report', 'data': '{"rgb":0,"illumination":573}', 'short_id': 0}

You've posted the heartbeat used for key rotation. I've mixed this two messages types up in the past.

Then I can see those in ngrep:
U 192.168.7.81:4321 -> 224.0.0.50:9898
  {"cmd":"report","model":"gateway","sid":"7811dcdad7a3","short_id":0,"data":"{\"rgb\":0,\"illumination\":681}"}
#

Edit2:
Can confirm, they are not reporting that very often. Should be option to poll (gateways).

I moved my gateway away from dark room. Reports have really random gaps between.
U 2019/02/19 15:11:32.990091 192.168.2.204:4321 -> 224.0.0.50:9898 {"cmd":"report","model":"gateway","sid":"04cf8c91566f","short_id":0,"data":"{\"rgb\":0,\"illumination\":558}"}
U 2019/02/19 15:24:35.336748 192.168.2.204:4321 -> 224.0.0.50:9898 {"cmd":"report","model":"gateway","sid":"04cf8c91566f","short_id":0,"data":"{\"rgb\":0,\"illumination\":495}"}
U 2019/02/19 15:49:42.186527 192.168.2.204:4321 -> 224.0.0.50:9898 {"cmd":"report","model":"gateway","sid":"04cf8c91566f","short_id":0,"data":"{\"rgb\":0,\"illumination\":433}"}
U 2019/02/19 15:55:21.450549 192.168.2.204:4321 -> 224.0.0.50:9898 {"cmd":"report","model":"gateway","sid":"04cf8c91566f","short_id":0,"data":"{\"rgb\":0,\"illumination\":402}"}
U 2019/02/19 16:55:13.832239 192.168.2.204:4321 -> 224.0.0.50:9898 {"cmd":"report","model":"gateway","sid":"04cf8c91566f","short_id":0,"data":"{\"rgb\":0,\"illumination\":323}"}

@Danielhiversen

I am not sure if this is a good idea.
It should at least be configurable, and not the default behavior.

Why?

Do you own the 'new' hardware gateways with new firmware and have another working solution?
Does it break existing setups with this new default behavior?
Do you have any information present that the 'broken' firmware will be fixed soon by Xiaomi? Do they have any reason to 'fix' the current behavior? There seems none; everything works fine in their app..
Is there an EASY way for (new) users (using hassio) to change this behavior*?

If all are answered with: 'no' then I urge you to reconsider...

i have been searching on how to change this behavior and found no clue on how to do this in hassio except for
(1) adding a 'custom_components' folder to config. But this is no custom component, it is part of the system!
(2) do a complete classic (re)install
So how.....?

Quickie; Firmware 1.4.1_167 came out. Updated one of my gateways to test if this fixed current issue. Not so; behavior remains the same. We need this fix...

This would supposedly fix this https://github.com/home-assistant/home-assistant/issues/21250 right? I'm currently running Hassio on VM and doesn't work correctly the sensors (sometimes it does sometimes it doesn't). However running Hassio on my pi3 works perfect.
Is there a way I can apply this to Hassio to test it out?

Hope for the fix in hassio

I have a theory...One thing I have noticed, and including myself, is that the people who appear to have most problems all have MAC address of the gateway starting 04:XX:XX:XX:XX:XX.
When I get updates from a sensor, I can see in the debug these appearing as a PUSH and the sensor gets updated.
2019-02-24 20:24:33 DEBUG (Thread-23) [xiaomi_gateway] MCAST (heartbeat) << {'model': 'sensor_ht', 'sid': '158dXXXXXXXXXX', 'cmd': 'heartbeat', 'short_id': 63981, 'data': '{"voltage":2985,"
temperature":"1845","humidity":"5269"}'}
2019-02-24 20:24:33 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Humidity_158dXXXXXXXXXX: 52.7>: {'voltage': 2985, 'temperature': '1845', 'humidity': '5269'}
2019-02-24 20:24:33 DEBUG (MainThread) [homeassistant.components.xiaomi_aqara] PUSH >> <Entity Temperature_158dXXXXXXXXXX: 18.4>: {'voltage': 2985, 'temperature': '1845', 'humidity': '5269'
}
However when I get an illumination update from the gateway I don't get the corresponding PUSH debug message.
2019-02-24 20:20:27 DEBUG (Thread-23) [xiaomi_gateway] MCAST (report) << {'model': 'gateway', 'sid': '04XXXXXXXXXX', 'cmd': 'report', 'short_id': 0, 'data': '{"rgb":1694434079,"illumination
":336}'}
One thing I notice that the entity_id that home assistant set up, is
sensor.illumination_4XXXXXXXXXX
and
light.gateway_light_4XXXXXXXXXX
thus missing the leading zero.
Could this be causing a mismatch between the SID being broadcast and the HA entitiy?

Superseded by #21453.

authors: Danielhiversen andriej fernandex00 homeassistant jcastro peppekerstens sonartribe stsergo syssi zatarra77


text:
New component 'insteon_plm'

Description:
This PR adds a new component 'insteon_plm' for use with INSTEON PowerLinc USB/serial modems.  It includes constituent platforms: light, switch, and binary_sensor.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
insteon_plm:
    port: /dev/ttyUSB0

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Hi @nugget,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

This was premature, sorry.  I was trying to figure out the CLA stuff.

authors: homeassistant nugget


text:
Pull API / Wildcard Support

Re entity.get(“*”) can you talk a bit more about your use case? I ask because there are a lot of ways to go about implementing this. The underlying datalog DB does support patterns similar to this, but they have different tradeoffs when connecting them to React and doing the live updating. At the moment we treat entity.get(“specificAttribute”) as a whitelist, so we only cache data and rerender components when those specific attributes change. If debugging is the issue we just released custom chrome formatters so you can log out entities and inspect all their attributes in the console. We’re also working on a chrome extension to read and eventually write to the database from a GUI. If it’s something more like GraphQL that you want, we’re talking about exposing the pull syntax which is essentially GraphQL. I’m hesitant to just expose an entity.get(“*”) function since that would have severe performance costs in the context of React if used naively, and it’s ripe for naive use since it’s probably the first thing a new developer would try.
@smothers

re: entity.get("*"), this is roughly what I'm trying to do.
const onDragEnd = (event) => {
  if (event.condition) {
    transact([{
      entity: {
        name: baseEntity.get("name"),
        component: baseEntity.get("component"),
        width: baseEntity.get("width"),
        height: baseEntity.get("height"),
        ownerId: baseEntity.get("ownerId"),
        // +maybe some other props I don't know about? and those could vary depending on the entity too.
      }
    }])
  }
}

So again this is just querying the database directly, no need to subscribe to anything. but on the other hand if it is only exposed when querying the database directly, that could feel a bit inconsistent?
I'm actually not sure yet I will need it to be this dynamic, so hardcoding the props is okay in the meantime. but it was something I thought would be there and went looking for in the docs.
Cheers.
Originally posted by @MioQuispe in https://github.com/homebaseio/homebase-react/issues/80#issuecomment-834181587

@MioQuispe I think exposing the pull API would give you what you want.
E.g.
const id = 123
const [client] = useClient()
client.pull('*', id) // => { a1: 'v1', a2: 'v2, ... }

Additionally, if we want to make pulls reactive we can also expose the API over a hook directly
const id = 123
const [data] = usePull('*', id)
data // => { a1: 'v1', a2: 'v2, ... }

To better understand which APIs we should prioritize can you talk more about your use case? Why do you want to copy all attributes of one entity into another entity instead of referencing the original entity?

Cool! Yeah that would solve it. I don't actually need the reactivity here.
Im just trying to clone an entity (except for the id) to create a new one essentially. Maybe I should look them up from a schema tbh, but I havent thought everything through yet.

Hey @MioQuispe. I looked into this and it involves converting from EDN (the Clojure data format) to JSON. This is a feature we'd like to add, but it's a bit more complicated than just exposing one of the DB APIs. At the moment we make a bunch of assumptions when going from JSON -> EDN and never go from EDN -> JSON. Going in reverse would require precisely tracking all the assumptions and mapping them to the reverse transformation. Since this is not high on our priority list it will probably be a while before we get to it.

authors: MioQuispe smothers

repo: homebaseio/homebase-react


text:
Web interface needs to be separated out from JSON API

At the moment, we have two projects in one repository, which is kind of unwieldy.

The web interface
The JSON.cgi API

There's no reason to install the web interface on every device when it can control them all from a single location (on your desktop even), as long as you have the JSON.cgi API installed on the devices.
We should really separate these out, both to save space on the devices, but also to simplify development.

I've created a new repo to be the home for this: homedash/homedash-client.
Feel free to open relevant issues over there.

Yep, separate is the way to go.  Easier to play with front end ideas too.

We can simplify by using OpenWrt ubus
jshn can be used to generate JSON.
TBH the UI is anyway small and if anybody don't want UI the can just install json.sh

authors: Japh mattjoyce stokito

repo: homedash/kankun-json


text:
Improve Merkhet implementation

As merkhets are already on their own routines, it would make more sense to spin up a routine for a merkhet tast rather than a merkhet instance itself. Pushability tests can take longer than the time between the tests, and it would result in blocks

Fixed by #39

repo: homeport/watchful


text:
Avg_entropy in tensorboard

Hi, hongzi:
I'm confused about the actual meaning of the avg_entropy in tensorboard. I found that  you just computed the entropy of the lowest bit rate choice(action_prob[0]), right? So what does it mean?
Hope to get your reply!

It literally means the entropy (https://en.wikipedia.org/wiki/Entropy#Information_theory).
In our purpose, we use it to control the factor of exploration. Please refer to section 4.2 (especially the term H() in equation 4) of our paper, as well as reference [30], for more details.
Also, notice that in sim/README.md, we stated
As reported by the A3C paper (http://proceedings.mlr.press/v48/mniha16.pdf) and a faithful implementation (https://openreview.net/pdf?id=Hk3mPK5gg), we also found the exploration factor in the actor network quite crucial for achieving good performance. A general strategy to train our system is to first set ENTROPY_WEIGHT in a3c.py to be a large value (in the scale of 1 to 5) in the beginning, then gradually reduce the value to 0.1 (after at least 100,000 iterations).

Thank you for your reply! I see, but the question is, why did you compute the entropy using "action_prob[0]" instead of "action_prob"? I think action_prob[0] is just a scalar, which stands for the probability of choosing the lowest bit rate, and we need the all 6 probabilities to compute the entropy, isn't it?

I think action_prob is a 2D tensor and action_prob[0] is a vector. I admit it is not the most comprehensive way to implement this.

Yes, my mistake. Actually, action_prob[0] is a vector. Thank you for your help!

authors: hongzimao yangchaozhao

repo: hongzimao/pensieve


text:
fix(types): handle readonly array correctly

The author should do the following, if applicable
My apologies that JSONParsed didn't convert ReadonlyArray type correctly. Types of methods disappeared

[x] Add tests
[x] Run tests
[x] bun run format:fix && bun run lint:fix to format the code
[ ] Add TSDoc/JSDoc to document the code

@m-shaka
Thanks! Merging now.

authors: m-shaka yusukebe

repo: honojs/hono


text:
Hoow can I instantiate THSegmentedPager in UIViewController?

How can I instantiate THSegmentedPager in Timeline.m(inherit from UIViewController) rather than AppDelegate.m?
What I mean is I wanna show THSegmentedPager when user open the Timeline View Controller instead of THSegmentedPager when load when user open the app. Thank you.

I'm not really sure what you're asking about. The example APP is just an example... you could even add a button with a segue and let that point to the THSegmentedPager.
Instantiate it in a UIViewController is kind of a Problem, as the pager itself is a UIViewController
@interface THSegmentedPager : UIViewController<UIPageViewControllerDataSource,UIPageViewControllerDelegate>

so it would be a UIViewController in a UIViewController which makes only sense if you plan to push it on the Navigation stack or inside a ContainerView.

if i want to put in containerview, how can i do that? sorry i'm novice. hope you can help me. thank you. :)

I'll create an example for that (but I don't know if I'll have time today)
Do u use

Storyboard?
Obj-C or Swift?

sorry for late reply, I'm using storyboard and objective c. thank you.


text:
Squish HTML prior to sending over wire

Enhancement
A minor performance enhancement that sends fewer bits over the wire.

[x] My code follows the style guidelines of this project
[x] Checks (StandardRB & Prettier-Standard) are passing

I'm trying to think through use cases where you might not want squish enabled. The only one I'm coming up with is for <pre> and <code> tags. Let me know if anyone can think of other scenarios.

What you said; those seem to be blockers, no?
The bigger thing (not a blocker) is evaluating something like Jose Valim’s Leex in the context of Rails. I briefly investigated trying my hand at it, creating a sort of managed subset of erb with some more constraints around control flow, but frankly it was hard so i allowed myself to get sucked into other things.
I still think it would be pretty amazing to get an intercalated array of static/dynamic changed bytes happening.

Not necessarily a blocker. We could scan for such tags and omit squish for those but the check could mitigate the benefits of this PR. Another option could be to explicitly opt in to the squish behavior per reflex.


text:
🛑 Branex AE is down

In 2aeccc5, Branex AE (https://branex.ae) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Branex AE is back up in decf970 after 9 minutes.

repo: hostingnocteam/monitoring


text:
Prevent deleting user accounts when matched

Fixes #527
Côté pro :

Côté volontaire :

@carsso typo : "a confirmé" et "a supprimé" 😉

authors: MatthieuGariel carsso

repo: hostolab/covidliste


text:
Font Color

Describe the bug
Font color default seems to be 'white'.  How do I change/set "label", "Unit", "Value" font color, size, etc.?
To Reproduce
na
Expected behavior
Expected to use dashboard Theme and/or use of CSS settings (font size=1; font color= blue) as I do for node-red standard widgets.
Screenshots
na
Environment and versions (please complete the following information):
ui-level version:  0.0.20
C:\Users\dave>node-red
22 May 09:03:45 - [info]
Welcome to Node-RED
22 May 09:03:45 - [info] Node-RED version: v0.19.5
22 May 09:03:45 - [info] Node.js  version: v10.15.1
22 May 09:03:45 - [info] Windows_NT 10.0.17763 x64 LE
22 May 09:03:45 - [info] Loading palette nodes
22 May 09:03:48 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
22 May 09:03:48 - [info] Dashboard version 2.14.0 started at /red/ui
22 May 09:03:49 - [warn] ------------------------------------------------------
22 May 09:03:49 - [warn] [node-red/tail] Not currently supported on Windows.
22 May 09:03:49 - [warn] ------------------------------------------------------
22 May 09:03:49 - [info] Settings file  : \Users\dave.node-red\settings.js
22 May 09:03:49 - [info] HTTP Static    : C:\Users\dave.node-red
22 May 09:03:49 - [info] Context store  : 'default' [module=memory]
22 May 09:03:49 - [info] User directory : \Users\dave.node-red
22 May 09:03:49 - [info] Server now running at http://127.0.0.1:1880/red/
22 May 09:03:49 - [info] Active project : Collection_Template_Widgets
22 May 09:03:49 - [info] Flows file     : \Users\dave.node-red\projects\Collection_Template_Widgets\flow.json
22 May 09:03:49 - [info] Starting flows
Additional context
na

First advise will be to update node-red-dashboard. Since version 2.15 the dashboard exposes site properties for custom ui nodes and ui-level node should get the theme colors as expected.

That partially worked.  Thx.  Theme color now working.
Can I change/input "label", "Unit", "Value" font color, size, etc. as I do with other widgets?  If so, how?

Do you mean with msg.ui_control or with CSS overrides?

CSS overrides.

Well it is complicated thing. Text rendering with svg is not same as with html. I did simplest one solution to cover as many use cases as possible and avoiding needs to create edge cases. Things go messy with different devices but it has to be supported. So simplicity is the key rule I follow here and i try to keep it this way.
Of course if you have nice ideas how to wide up configuration and layout possibilities I am open to pull requests

OK.  I understand.
Still, thanks for getting my Theme colors working with your widget.

closed as agreed and solved

Things might be now a bit better for you in terms of widget text color:
https://discourse.nodered.org/t/announce-node-red-contrib-ui-level-new-feature/9793

Thank you for the font color change.  Tried it and it worked.  However, it still is not quite what I needed because your solution changes the colors of ALL widgets within a tab (which is good for some applications.)  I needed single widget font color control as is available with the basic nr-ui-nodes.  I can add <font=red> prior to a label or value to change the color of either or both; I can also change the font sizes though that can be trickier.
Again, thanks for the improvement and listening.  Much appreciated.
Dave
From: hotNipi notifications@github.com
Reply-To: hotNipi/node-red-contrib-ui-level reply@reply.github.com
Date: Friday, May 24, 2019 at 5:36 AM
To: hotNipi/node-red-contrib-ui-level node-red-contrib-ui-level@noreply.github.com
Cc: daveHounds dave@milehihounds.com, State change state_change@noreply.github.com
Subject: Re: [hotNipi/node-red-contrib-ui-level] Font Color (#14)
Things might be now a bit better for you in terms of widget text color:
https://discourse.nodered.org/t/announce-node-red-contrib-ui-level-new-feature/9793
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Started to develop configuration options for texts in widget. Font color and size will be open to be customized from widget config page.  I did reopen this issue to get more specific feedback from you as one sophisticated user. If you can more clearly describe your expectations how far you think the customizing may or should go. It will be cool if you can do some mock images what you are expecting the widget should be able to do.
Thanks in advance.

version 0.0.24 released

@hotNipi Thank you for the improvements.  I tested them and they work for me.

Very nice. Thank you.

authors: daveHounds hotNipi

repo: hotNipi/node-red-contrib-ui-level


text:
Implemented: Add time zone support and migrated from moment to luxon(#25k8h53)

Related Issues

Closes #
Short Description and Why It's Useful

Screenshots of Visual Changes before/after (If There Are Any)

IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance

[ ] I read and followed contribution rules

Dependent on #90

repo: hotwax/bopis


text:
Implemented code to display current OMS information on Settings page(…

…#1y2ract)

Change on the login page too
https://github.com/hotwax/ionic-sdk/blob/main/src/views/Login.vue#L9

Change on the login page too https://github.com/hotwax/ionic-sdk/blob/main/src/views/Login.vue#L9

Updated the label on login page.

repo: hotwax/ionic-sdk


text:
turbo-cable-stream-source is not getting replaced

Hello, hoping you're having a good day :)
So, i was surprised to find out that the turbo-cable-stream-source element yielded by turbo_stream_from is not being replaced. So, i have a show.turbo_stream.erb that looks like this,
<%= turbo_stream.replace "conversation-inbox", class: "w-full flex" do %>
  <%= turbo_stream_from @conversation %>
.......

When the request is made multiple times, the element is not being replaced, which results in a markup that looks like this,

This is weird because i saw that events that happened elsewhere(broadcasted to another stream) where showing up on wrong streams.
Any idea what i might be doing wrong?

When you render a <turbo-stream action="replace">, its <template> element's contents replace whichever element is targeted by the [target] or [targets] attribute.
If you were to inspect the response, does the <turbo-stream> element's nested <template> render the <turbo-cable-stream-source> as a descendant of the element with [id="conversation-inbox"], or a sibling?
Does the <template> element include an element with [id="conversation-inbox"]? If not, would a call to turbo_stream.update better suit your use case?

authors: rockwellll seanpdoyle

repo: hotwired/turbo