[bug] Devices unavailable after HA restart - till before manual re-interview of all of them

Version
Checklist:

[X] I am not using HomeAssistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog problem was not mentioned there.

Build/Run method

[X] HA Add-on

zwavejs2mqtt: 3.0.3
zwave-js: 7.0.1
Describe the bug
Yesterday happened short power outage. HA node successfully started.
After some time I discovered: all ZWave nodes still unavailable.
In short - only manual re-interview for all nodes + integration restart helped.
Aeotec Stick was Ok, but other nodes not - only friendly name in list.
After every node re-interview: device info in Control Panel appears, like model etc.
But HA still not getting any data. Integration restart solved this las issue.
Initially reported on HA Add-on Github (https://github.com/hassio-addons/addon-zwavejs2mqtt/issues/109).
To Reproduce
Not sure, it happened after HA restart.
Expected behavior
Expected: all devices become available w/out user intervention - after HA server was restarted.
Additional context
All Z-Wave devices was unavailable. In Control Panel they looks like:

Logs attached. Hope it will find the issue.
zwavejs2mqtt-store_20210405_11.zip
zwavejs2mqtt-store_20210405_12.zip

@AlCalzone

Possibly a duplicate of:

https://github.com/zwave-js/zwavejs2mqtt/issues/893
https://github.com/zwave-js/zwavejs2mqtt/discussions/875

Like I wrote in the discussion, I'll need context to even begin narrowing this down. When this happens, please provide:

A full list of affected node IDs
A zwave-js logfile around the time of the restart
Cache files <homeid>.json and <homeid>.values.jsonl directly after the problem appears - no manual fixing attempts!
If possible (e.g. through backups), cache files <homeid>.json and <homeid>.values.jsonl directly before the problem appears
Any possible hints (e.g. Docker logs of the restart itself or whatever)

As I'm not using Docker, I could also use a 2nd or 3rd set of eyes from the devs that do. I've never had this happen in the 2 years that I'm using zwave-js in production, so I'm 99.9% certain this has to do with Docker.

A full list of affected node IDs
nodes_dump_20210406.zip
Affected was all except ZWave Aeotec stick ^^

A zwave-js logfile around the time of the restart
zwavejs2mqtt-store_20210405_12.zip

Cache files <homeid>.json and <homeid>.values.jsonl directly after the problem appears - no manual fixing attempts!
Unfortunately can't provide :(

If possible (e.g. through backups), cache files <homeid>.json and <homeid>.values.jsonl directly before the problem appears
dd893180.zip
Nightly backup on 2021-04-05 00:05 EEST.

Any possible hints (e.g. Docker logs of the restart itself, the hardware you're running on, or whatever...)
Raspberry RPi4 4G, HA OS 5.12, HA core-2021.3.4.

Only record in HA Core log while devices was unavailable (2021-04-05 ~18-19 EEST):
2021-04-05 18:51:21 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet. Retrying in background

HA_log_host_20210405.zip
HA host log from last startup.

I'm running HASS OS on an intel NUC with an aeotec stick and I'm getting the same thing. I'm not sure when it happened as I haven't restarted recently, but it was within the last week or two.

This could be a problem strictly related to docker environments, seems that for some reason docker isn't stopping containers the right way and the filesystem in volumes is corrupted

This could be a problem strictly related to docker environments, seems that for some reason docker isn't stopping containers the right way and the cache files in volumes are corrupted

In my case - it was unexpected power interruption. May be some issues with open / not flushed / cached files etc.
Nothing else on this server suffered from that specific interruption - in my case.

it was unexpected power interruption

Yep I think docker does some weird stuff with volumes that could cause issues like this when containers are not closed gracefully

It would be important to understand if it is happening in all Docker environments or only the zwavejs2mqtt container. A few HA devs claim it's not happening with the native addon.

let me know how I can provide all the information you need.

See my comment above - especially the cache files before and after the issue happens are important.
https://github.com/zwave-js/zwavejs2mqtt/issues/998#issuecomment-813933464

Alright, another day in this saga.  Last night before I went to sleep I updated everything, rebooted, and initiated a re-discovery on all nodes displaying the Unknown Manufacturer/Unknown Product failure mode.  Again, these are identical to devices correctly discovered and listed in the device list above the broken ones.  I know that the ZWave network is sound as each device is listed in the Network Graph.  It's just a problem with their entries in ZWaveJS.
I've set all logs to silly, and toggled "log to file" in both the ZWave and General tabs (in ZwaveJS to MQTT).  Hope these help
zwavejs2mqtt-store, 4-9-21.zip

rebooted

Does that give the containers enough time to shutdown? Maybe the reboot causes problems.

How long does zwavejs2mqtt need to shutdown?
From the docker docs:
The main process inside the container will receive SIGTERM, and after a grace period, SIGKILL.

The default docker grace period is only 10 seconds. Try bumping it to something longer. I'm currently setting up a z-wave / hassio system using docker-compose on raspbian and had this same problem yesterday. After bumping the grace period it hasn't happened.
If using docker-compose you can use stop_grace_period: 40s under the service, or --time=40s for the docker commands.
https://docs.docker.com/compose/compose-file/compose-file-v3/#stop_grace_period

I've done a number of experiments with docker stop. I am using docker-compose and the compose file from: https://github.com/zwave-js/zwavejs2mqtt/blob/master/docker/README.md

stop time (10 runs) with 10 seconds warmup: 0.437s +/- 0.046

Thus, the grace period should not be hit. This is when giving the container 10 seconds to complete initialization after issuing docker start. When reducing this warmup period to 0 seconds, the results are quite different:

stop time (10 runs) with 0 seconds warmup: 10.494s +/- 0.064

Clearly the grace period is exceeded in that case, and SIGKILL is sent.
Interestingly, the docker-compose from the docs changes the stop signal to SIGINT instead of SIGTERM (stop_signal: SIGINT). For the sake of testing, changing this to the default SIGTERM signal changes nothing however:

stop time (10 runs) with 10 seconds warmup (SIGTERM): 0.465s +/- 0.065

The results are similar to using SIGINT.

stop time (10 runs) with 0 seconds warmup (SIGTERM): 10.473s +/- 0.069

Again the grace period is exceeded when we don't allow the container to initialize for some time. It seems the handlers for graceful shutdown are not registered on time?
10 seconds warmup docker log:
2021-04-10 13:13:04.763 WARN STORE: scenes.json not found
/bin/sh: git: not found
2021-04-10 13:13:06.808 INFO APP: Version: 3.2.0
2021-04-10 13:13:06.809 INFO APP: Application path:/usr/src/app
2021-04-10 13:13:06.921 INFO MQTT: MQTT is disabled
2021-04-10 13:13:06.946 INFO ZWAVE: Connecting to /dev/ttyZwave
2021-04-10 13:13:06.991 INFO APP: Listening on port 8091 host <IP_ADDRESS> protocol HTTP
2021-04-10 13:13:14.932 WARN APP: Shutdown detected: closing clients...
2021-04-10 13:13:14.936 INFO GATEWAY: Closing Gateway...
2021-04-10 13:13:14.949 INFO ZWAVE: Client closed

0 seconds warmup docker log:
2021-04-10 13:20:45.436 WARN STORE: scenes.json not found
/bin/sh: git: not found
2021-04-10 13:20:47.486 INFO APP: Version: 3.2.0
2021-04-10 13:20:47.487 INFO APP: Application path:/usr/src/app
2021-04-10 13:20:47.600 INFO MQTT: MQTT is disabled
2021-04-10 13:20:47.624 INFO ZWAVE: Connecting to /dev/ttyZwave
2021-04-10 13:20:47.671 INFO APP: Listening on port 8091 host <IP_ADDRESS> protocol HTTP

It is clear that the shutdown handler is not called in the latter case. Though this scenario is probably unrealistic. I also repeated these runs with MQTT enabled, the results are the same.
I think the question now is, as soon as zwavejs2mqtt detects a shutdown (e.g. 2021-04-10 13:13:14.932 WARN APP: Shutdown detected: closing clients...), is there any way that it could take longer than 10 seconds (docker's grace period) to close the gateway, the clients, and MQTT? There might be an edge case where this is true, in that case docker kills the container and this might lead to an unsafe shutdown (?).
Test script used: https://gist.github.com/Br-ian/a05df5b53410e62d46ffcddb25c2296f

I’ve been working on my setup today. I’ve struggled a bit with getting things working, had a dead node, then three. I’ve had to exclude, factory reset and so on a few devices. At some point when I seemingly had things working pretty well I thought I’d do a backup and reboot my pi.  After that I rebooted the pi. When it came back up and I started the containers again z-wavejs had lost everything. Re-interviewing brought most of my nodes back, only had to completely start over with one (more on that one later).
I found this error message in the startup log:
zwavejs2mqtt     | 2021-04-10 15:52:36.682 INFO MQTT: Message received on homeassistant/status, 'online'
zwavejs2mqtt     | 2021-04-10 15:52:36.684 INFO GATEWAY: Home Assistant is ONLINE
zwavejs2mqtt     | 2021-04-10 15:52:43.032 INFO ZWAVE: Controller status: Driver: Restoring the network from cache failed: Synta
xError: Unexpected end of JSON input
zwavejs2mqtt     | 2021-04-10 15:52:43.067 INFO ZWAVE: Zwave driver is ready
zwavejs2mqtt     | 2021-04-10 15:52:43.068 INFO ZWAVE: Controller status: Driver ready

Looking at my backup, the cache json file that’s got the most recent timestamp was empty (it’s buddy jsonl files are not empty). The other files are days old. Just to make sure, the other files don’t seem corrupted in any way, the python json library parses the .json files just fine and each line in the  .jsonl files also parse.
I’ve also encountered this bug a few times today https://github.com/zwave-js/zwavejs2mqtt/issues/1031. Actually just recently too after excluding my one corrupted device. The cache file seem fine still.

2021-04-10 15:52:43.032 INFO ZWAVE: Controller status: Driver: Restoring the network from cache failed: Synta
xError: Unexpected end of JSON input

This should only happen for the .json file, the .jsonl files are a bit more resilient because they can skip invalid lines. So if I understand it correctly, the docker-compose down caused the file to get corrupted. Any chance you could make a backup of your json and jsonl files in the working state and try to corrupt them again by shutting down the container?

I think I might finally have an idea what's causing this. Both node-zwave-js and zwavejs2mqtt try to handle the SIGINT signal. node-zwave-js has the first handler registered, so it receives the signal first and starts shutting down the driver.
zwavejs2mqtt then receives it and also wants to shut down the driver. Because zwave-js got the signal first, the destroy() call returns immediately and zwavejs2mqtt ends the process while zwave-js is still busy saving the file to disk.

@jengdal can you try the block-duplicate-destroy-calls branch please?
https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/docker_custom_builds explains how you can build the container against another branch.

Any chance you could make a backup of your json and jsonl files in the working state and try to corrupt them again by shutting down the container?

Yes, took a few tries, but I got it reproduced!
🎉

can you try the block-duplicate-destroy-calls branch please?

Very cool that you probably already have it fixed, but it's getting late here, I'll try to be back on this in ~10 hours :)

I'm going to merge the PR which is going to close this issue. If the issue persists with the next version (zwave-js@7.2.2), feel free to reopen.

The latest docker image is working well. The cache survived multiple restarts and no new issues have surfaced.

Got same problem today. a power failure, and all my nodes says "Unknown manufacturer 0xXXXX". Only way to get it up again was to re-interview all nodes.
Running in docker.
zwavejs2mqtt: 4.0.1
zwave-js: 7.3.0

Same problem today after power failure. Logs from 'docker logs'. Hope is can help.
The dead nodes are actually correct (as one more fuse was still tripped).
19:37:09.545 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.547 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.548 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.549 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.551 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.552 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.553 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.554 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.556 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.557 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.560 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.562 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.565 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.566 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.568 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.573 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.576 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.578 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.579 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.583 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.584 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.585 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.586 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.587 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.592 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.594 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.596 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.596 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.597 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.598 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.599 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.600 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.601 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.603 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.604 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.606 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.607 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.611 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.613 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.613 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.614 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.615 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.616 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.617 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.618 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.620 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.621 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.622 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.624 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.627 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.628 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.629 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.630 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.631 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.636 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.638 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.640 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.642 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.644 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.645 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.647 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.653 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.656 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.660 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.661 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.663 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.666 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.668 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.669 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.671 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.674 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.676 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.678 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.679 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.682 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.688 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.689 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.691 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.693 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.694 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.695 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.697 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.698 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.700 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.701 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.703 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.705 DRIVER   Node 23, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.707 DRIVER   Node 23, Endpoint 2: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.708 DRIVER   Node 23, Endpoint 3: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.711 DRIVER   Node 23, Endpoint 4: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.714 DRIVER   Node 23, Endpoint 5: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.717 DRIVER   Node 23, Endpoint 6: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.718 DRIVER   Node 23, Endpoint 7: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.724 DRIVER   Node 23, Endpoint 8: Trying to access endpoint instance before Multi Channel i
nterview
19:37:09.744 CNTRLR   setting serial API timeouts: ack = 1000 ms, byte = 150 ms
19:37:09.838 CNTRLR   serial API timeouts overwritten. The old values were: ack = 1500 ms, byte = 15
0 ms
19:37:09.862 CNTRLR   Interview completed
2021-05-23 19:37:09.893 INFO ZWAVE: Zwave driver is ready
2021-05-23 19:37:09.894 INFO ZWAVE: Controller status: Driver ready
2021-05-23 19:37:10.062 INFO ZWAVE: Scanning network with homeid: 0xd10e7639
2021-05-23 19:37:10.065 INFO ZWAVE: Node 1 is alive
19:37:10.088 CNTRLR   [Node 001] The node is alive.
19:37:10.092 CNTRLR » [Node 001] requesting node neighbors...
19:37:10.348 CNTRLR   [Node 001] The node is ready to be used
19:37:10.364 CNTRLR » [Node 004] pinging the node...
19:37:10.392 CNTRLR » [Node 005] pinging the node...
19:37:10.405 CNTRLR » [Node 007] pinging the node...
19:37:10.424 CNTRLR » [Node 008] pinging the node...
19:37:10.446 CNTRLR » [Node 010] pinging the node...
19:37:10.461 CNTRLR » [Node 013] pinging the node...
19:37:10.478 CNTRLR » [Node 014] pinging the node...
19:37:10.497 CNTRLR » [Node 015] pinging the node...
19:37:10.507 CNTRLR » [Node 016] pinging the node...
19:37:10.516 CNTRLR » [Node 017] pinging the node...
19:37:10.529 CNTRLR » [Node 018] pinging the node...
19:37:10.534 CNTRLR » [Node 019] pinging the node...
19:37:10.540 CNTRLR » [Node 020] pinging the node...
2021-05-23 19:37:10.549 INFO ZWAVE: Node 21 is asleep
19:37:10.564 CNTRLR   [Node 021] The node is asleep.
19:37:10.570 CNTRLR » [Node 021] requesting node neighbors...
19:37:10.572 CNTRLR   [Node 021] The node is ready to be used
19:37:10.583 CNTRLR » [Node 021] Assigning SUC return route...
2021-05-23 19:37:10.590 INFO ZWAVE: Node 22 is asleep
19:37:10.618 CNTRLR   [Node 022] The node is asleep.
19:37:10.621 CNTRLR » [Node 022] requesting node neighbors...
19:37:10.628 CNTRLR   [Node 022] The node is ready to be used
19:37:10.634 CNTRLR » [Node 022] Assigning SUC return route...
19:37:10.646 CNTRLR » [Node 023] pinging the node...
19:37:10.669 CNTRLR » [Node 024] pinging the node...
2021-05-23 19:37:10.709 INFO ZWAVE-SERVER: ZwaveJS server listening on port 3500
19:37:10.796 CNTRLR « [Node 001] node neighbors received: 4, 5, 7, 15, 17, 19, 20, 21, 22, 23
2021-05-23 19:37:10.817 INFO ZWAVE: Node 1 ready: Unknown manufacturer 0x0086 - Unknown product 0x005a (0x0001)
19:37:10.888 CNTRLR « [Node 021] node neighbors received: 1, 4, 5, 8, 10, 13, 15, 17, 19
2021-05-23 19:37:10.897 INFO ZWAVE: Node 21: value added 21-128-0-level => undefined
2021-05-23 19:37:10.900 INFO ZWAVE: Node 21: value added 21-128-0-isLow => undefined
2021-05-23 19:37:10.902 INFO ZWAVE: Node 21: value added 21-132-0-wakeUpInterval => undefined
2021-05-23 19:37:10.903 INFO MQTT: Subscribing to zwave/+/+/+/+/+/set
2021-05-23 19:37:10.904 INFO ZWAVE: Node 21: value added 21-132-0-controllerNodeId => undefined
2021-05-23 19:37:10.905 INFO ZWAVE: Node 21: value added 21-134-0-libraryType => undefined
2021-05-23 19:37:10.905 INFO ZWAVE: Node 21: value added 21-134-0-protocolVersion => undefined
2021-05-23 19:37:10.906 INFO ZWAVE: Node 21: value added 21-134-0-firmwareVersions => undefined
2021-05-23 19:37:10.906 INFO ZWAVE: Node 21: value added 21-134-0-hardwareVersion => undefined
2021-05-23 19:37:10.911 INFO ZWAVE: Node 21 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
19:37:10.937 CNTRLR « [Node 022] node neighbors received: 1, 4, 5, 7, 8, 10, 13, 14, 15, 16, 17, 18,
19
2021-05-23 19:37:10.969 INFO ZWAVE: Node 22: value added 22-114-0-manufacturerId => undefined
2021-05-23 19:37:10.970 INFO ZWAVE: Node 22: value added 22-114-0-productType => undefined
2021-05-23 19:37:10.970 INFO ZWAVE: Node 22: value added 22-114-0-productId => undefined
2021-05-23 19:37:10.970 INFO ZWAVE: Node 22: value added 22-128-0-level => undefined
2021-05-23 19:37:10.988 INFO ZWAVE: Node 22: value added 22-128-0-isLow => undefined
2021-05-23 19:37:10.988 INFO ZWAVE: Node 22: value added 22-132-0-wakeUpInterval => undefined
2021-05-23 19:37:10.989 INFO ZWAVE: Node 22: value added 22-132-0-controllerNodeId => undefined
2021-05-23 19:37:10.989 INFO ZWAVE: Node 22: value added 22-134-0-libraryType => undefined
2021-05-23 19:37:10.990 INFO ZWAVE: Node 22: value added 22-134-0-protocolVersion => undefined
2021-05-23 19:37:10.990 INFO ZWAVE: Node 22: value added 22-134-0-firmwareVersions => undefined
2021-05-23 19:37:10.991 INFO ZWAVE: Node 22: value added 22-134-0-hardwareVersion => undefined
2021-05-23 19:37:11.014 INFO ZWAVE: Node 22 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
2021-05-23 19:37:11.318 INFO ZWAVE: Node 4 is alive
19:37:11.350 CNTRLR   [Node 004] The node is alive.
19:37:11.376 CNTRLR » [Node 004] requesting node neighbors...
19:37:11.459 CNTRLR   [Node 004] The node is ready to be used
19:37:11.478 CNTRLR « [Node 004] ping successful
19:37:11.496 CNTRLR » [Node 004] Assigning SUC return route...
2021-05-23 19:37:12.684 INFO ZWAVE: Node 5 is alive
19:37:12.685 CNTRLR   [Node 005] The node is alive.
19:37:12.685 CNTRLR » [Node 005] requesting node neighbors...
19:37:12.688 CNTRLR   [Node 005] The node is ready to be used
19:37:12.688 CNTRLR « [Node 005] ping successful
19:37:12.688 CNTRLR » [Node 005] Assigning SUC return route...
19:37:12.810 CNTRLR « [Node 004] node neighbors received: 1, 5, 8, 19, 20, 21, 22
2021-05-23 19:37:12.962 INFO ZWAVE: Node 4: value added 4-37-0-currentValue => undefined
2021-05-23 19:37:12.963 INFO ZWAVE: Node 4: value added 4-37-0-targetValue => undefined
2021-05-23 19:37:12.964 INFO ZWAVE: Node 4: value added 4-114-0-manufacturerId => undefined
2021-05-23 19:37:12.964 INFO ZWAVE: Node 4: value added 4-114-0-productType => undefined
2021-05-23 19:37:12.965 INFO ZWAVE: Node 4: value added 4-114-0-productId => undefined
2021-05-23 19:37:12.965 INFO ZWAVE: Node 4: value added 4-134-0-libraryType => undefined
2021-05-23 19:37:12.966 INFO ZWAVE: Node 4: value added 4-134-0-protocolVersion => undefined
2021-05-23 19:37:13.019 INFO ZWAVE: Node 4: value added 4-134-0-firmwareVersions => undefined
2021-05-23 19:37:13.035 INFO ZWAVE: Node 4: value added 4-134-0-hardwareVersion => undefined
2021-05-23 19:37:13.038 INFO ZWAVE: Node 4 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
19:37:13.406 CNTRLR « [Node 005] node neighbors received: 1, 4, 8, 13, 18, 19, 21, 22, 23
2021-05-23 19:37:13.497 INFO ZWAVE: Node 5: value added 5-37-0-currentValue => undefined
2021-05-23 19:37:13.498 INFO ZWAVE: Node 5: value added 5-37-0-targetValue => undefined
2021-05-23 19:37:13.498 INFO ZWAVE: Node 5: value added 5-38-0-targetValue => undefined
2021-05-23 19:37:13.536 INFO ZWAVE: Node 5: value added 5-38-0-duration => NaNs
2021-05-23 19:37:13.553 INFO ZWAVE: Node 5: value added 5-38-0-currentValue => undefined
2021-05-23 19:37:13.561 INFO ZWAVE: Node 5: value added 5-91-0-slowRefresh => undefined
2021-05-23 19:37:13.577 INFO ZWAVE: Node 5: value added 5-114-0-manufacturerId => undefined
2021-05-23 19:37:13.578 INFO ZWAVE: Node 5: value added 5-114-0-productType => undefined
2021-05-23 19:37:13.580 INFO ZWAVE: Node 5: value added 5-114-0-productId => undefined
2021-05-23 19:37:13.591 INFO ZWAVE: Node 5: value added 5-134-0-libraryType => undefined
2021-05-23 19:37:13.592 INFO ZWAVE: Node 5: value added 5-134-0-protocolVersion => undefined
2021-05-23 19:37:13.593 INFO ZWAVE: Node 5: value added 5-134-0-firmwareVersions => undefined
2021-05-23 19:37:13.593 INFO ZWAVE: Node 5: value added 5-134-0-hardwareVersion => undefined
2021-05-23 19:37:13.595 INFO ZWAVE: Node 5: value added 5-134-0-sdkVersion => undefined
2021-05-23 19:37:13.676 INFO ZWAVE: Node 5: value added 5-134-0-applicationFrameworkAPIVersion => undefined
2021-05-23 19:37:13.677 INFO ZWAVE: Node 5: value added 5-134-0-applicationFrameworkBuildNumber => undefined
2021-05-23 19:37:13.677 INFO ZWAVE: Node 5: value added 5-134-0-hostInterfaceVersion => undefined
2021-05-23 19:37:13.678 INFO ZWAVE: Node 5: value added 5-134-0-hostInterfaceBuildNumber => undefined
2021-05-23 19:37:13.678 INFO ZWAVE: Node 5: value added 5-134-0-zWaveProtocolVersion => undefined
2021-05-23 19:37:13.678 INFO ZWAVE: Node 5: value added 5-134-0-zWaveProtocolBuildNumber => undefined
2021-05-23 19:37:13.723 INFO ZWAVE: Node 5: value added 5-134-0-applicationVersion => undefined
2021-05-23 19:37:13.733 INFO ZWAVE: Node 5: value added 5-134-0-applicationBuildNumber => undefined
2021-05-23 19:37:13.788 INFO ZWAVE: Node 5 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
19:37:19.241 CNTRLR   [Node 007] Node 7 did not respond after 1 attempts, it is presumed dead
2021-05-23 19:37:19.242 INFO ZWAVE: Node 7 is dead
19:37:19.243 CNTRLR   [Node 007] The node is dead.
19:37:19.249 CNTRLR   [Node 007] ping failed: Failed to send the command after 1 attempts (Status No
Ack)
2021-05-23 19:37:22.046 INFO ZWAVE: Node 5: metadata updated: 50-0-value-65537
2021-05-23 19:37:22.111 INFO ZWAVE: Node 5: value added: 50-0-value-65537 => 5.93
2021-05-23 19:37:22.136 INFO ZWAVE: Node 5: value added 5-50-0-value-65537 => 5.93
2021-05-23 19:37:22.210 INFO ZWAVE: Node 4: metadata updated: 50-0-value-65537
2021-05-23 19:37:22.230 INFO ZWAVE: Node 4: value added: 50-0-value-65537 => 2844.87
2021-05-23 19:37:22.238 INFO ZWAVE: Node 4: value added 4-50-0-value-65537 => 2844.87
2021-05-23 19:37:22.397 INFO ZWAVE: Node 24: metadata updated: 50-0-value-65537
2021-05-23 19:37:22.448 INFO ZWAVE: Node 24: value added: 50-0-value-65537 => 1.25
19:37:24.579 CNTRLR   [Node 008] Node 8 did not respond after 1 attempts, it is presumed dead
2021-05-23 19:37:24.657 INFO ZWAVE: Node 8 is dead
19:37:24.678 CNTRLR   [Node 008] The node is dead.
19:37:24.848 CNTRLR   [Node 008] ping failed: Failed to send the command after 1 attempts (Status No
Ack)
19:37:30.400 CNTRLR   [Node 010] Node 10 did not respond after 1 attempts, it is presumed dead
2021-05-23 19:37:30.443 INFO ZWAVE: Node 10 is dead
19:37:30.447 CNTRLR   [Node 010] The node is dead.
19:37:30.495 CNTRLR   [Node 010] ping failed: Failed to send the command after 1 attempts (Status No
Ack)
19:37:36.028 CNTRLR   [Node 013] Node 13 did not respond after 1 attempts, it is presumed dead
2021-05-23 19:37:36.029 INFO ZWAVE: Node 13 is dead
19:37:36.031 CNTRLR   [Node 013] The node is dead.
19:37:36.040 CNTRLR   [Node 013] ping failed: Failed to send the command after 1 attempts (Status No
Ack)
2021-05-23 19:37:41.062 INFO MQTT: Message received on homeassistant/status, 'online'
2021-05-23 19:37:41.065 INFO GATEWAY: Home Assistant is ONLINE
19:37:41.693 CNTRLR   [Node 014] Node 14 did not respond after 1 attempts, it is presumed dead
2021-05-23 19:37:41.696 INFO ZWAVE: Node 14 is dead
19:37:41.697 CNTRLR   [Node 014] The node is dead.
19:37:41.740 CNTRLR   [Node 014] ping failed: Failed to send the command after 1 attempts (Status No
Ack)
19:37:48.176 CNTRLR   [Node 015] Node 15 did not respond after 1 attempts, it is presumed dead
2021-05-23 19:37:48.177 INFO ZWAVE: Node 15 is dead
19:37:48.178 CNTRLR   [Node 015] The node is dead.
19:37:48.185 CNTRLR   [Node 015] ping failed: Failed to send the command after 1 attempts (Status No
Ack)
19:37:53.893 CNTRLR   [Node 016] Node 16 did not respond after 1 attempts, it is presumed dead
2021-05-23 19:37:53.894 INFO ZWAVE: Node 16 is dead
19:37:53.894 CNTRLR   [Node 016] The node is dead.
19:37:53.900 CNTRLR   [Node 016] ping failed: Failed to send the command after 1 attempts (Status No
Ack)
19:37:59.446 CNTRLR   [Node 017] Node 17 did not respond after 1 attempts, it is presumed dead
2021-05-23 19:37:59.447 INFO ZWAVE: Node 17 is dead
19:37:59.448 CNTRLR   [Node 017] The node is dead.
19:37:59.475 CNTRLR   [Node 017] ping failed: Failed to send the command after 1 attempts (Status No
Ack)
19:38:05.419 CNTRLR   [Node 018] Node 18 did not respond after 1 attempts, it is presumed dead
2021-05-23 19:38:05.434 INFO ZWAVE: Node 18 is dead
19:38:05.438 CNTRLR   [Node 018] The node is dead.
19:38:05.482 CNTRLR   [Node 018] ping failed: Failed to send the command after 1 attempts (Status No
Ack)
2021-05-23 19:38:05.675 INFO ZWAVE: Node 19 is alive
19:38:05.679 CNTRLR   [Node 019] The node is alive.
19:38:05.688 CNTRLR » [Node 019] requesting node neighbors...
19:38:05.699 CNTRLR   [Node 019] The node is ready to be used
19:38:05.738 CNTRLR « [Node 019] ping successful
19:38:05.742 CNTRLR » [Node 019] Assigning SUC return route...
2021-05-23 19:38:07.045 INFO ZWAVE: Node 20 is alive
19:38:07.049 CNTRLR   [Node 020] The node is alive.
19:38:07.059 CNTRLR » [Node 020] requesting node neighbors...
19:38:07.071 CNTRLR   [Node 020] The node is ready to be used
19:38:07.108 CNTRLR « [Node 020] ping successful
19:38:07.114 CNTRLR » [Node 020] Assigning SUC return route...
19:38:07.311 CNTRLR « [Node 019] node neighbors received: 1, 4, 5, 7, 8, 10, 13, 17, 21, 22, 23, 24
2021-05-23 19:38:07.348 INFO ZWAVE: Node 19: value added 19-32-0-currentValue => undefined
2021-05-23 19:38:07.366 INFO ZWAVE: Node 19: value added 19-32-0-targetValue => undefined
2021-05-23 19:38:07.370 INFO ZWAVE: Node 19: value added 19-114-0-manufacturerId => undefined
2021-05-23 19:38:07.374 INFO ZWAVE: Node 19: value added 19-114-0-productType => undefined
2021-05-23 19:38:07.377 INFO ZWAVE: Node 19: value added 19-114-0-productId => undefined
2021-05-23 19:38:07.380 INFO ZWAVE: Node 19: value added 19-128-0-level => undefined
2021-05-23 19:38:07.383 INFO ZWAVE: Node 19: value added 19-128-0-isLow => undefined
2021-05-23 19:38:07.386 INFO ZWAVE: Node 19: value added 19-132-0-wakeUpInterval => undefined
2021-05-23 19:38:07.390 INFO ZWAVE: Node 19: value added 19-132-0-controllerNodeId => undefined
2021-05-23 19:38:07.398 INFO ZWAVE: Node 19: value added 19-134-0-libraryType => undefined
2021-05-23 19:38:07.401 INFO ZWAVE: Node 19: value added 19-134-0-protocolVersion => undefined
2021-05-23 19:38:07.406 INFO ZWAVE: Node 19: value added 19-134-0-firmwareVersions => undefined
2021-05-23 19:38:07.410 INFO ZWAVE: Node 19: value added 19-134-0-hardwareVersion => undefined
2021-05-23 19:38:07.426 INFO ZWAVE: Node 19 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
19:38:07.513 CNTRLR « [Node 020] node neighbors received: 1, 4
2021-05-23 19:38:07.565 INFO ZWAVE: Node 20: value added 20-98-0-currentMode => undefined
2021-05-23 19:38:07.574 INFO ZWAVE: Node 20: value added 20-98-0-targetMode => undefined
2021-05-23 19:38:07.580 INFO ZWAVE: Node 20: value added 20-98-0-outsideHandlesCanOpenDoor => undefined
2021-05-23 19:38:07.587 INFO ZWAVE: Node 20: value added 20-98-0-insideHandlesCanOpenDoor => undefined
2021-05-23 19:38:07.595 INFO ZWAVE: Node 20: value added 20-98-0-latchStatus => undefined
2021-05-23 19:38:07.598 INFO ZWAVE: Node 20: value added 20-98-0-boltStatus => undefined
2021-05-23 19:38:07.601 INFO ZWAVE: Node 20: value added 20-98-0-doorStatus => undefined
2021-05-23 19:38:07.607 INFO ZWAVE: Node 20: value added 20-98-0-lockTimeout => undefined
2021-05-23 19:38:07.610 INFO ZWAVE: Node 20: value added 20-98-0-operationType => undefined
2021-05-23 19:38:07.614 INFO ZWAVE: Node 20: value added 20-98-0-outsideHandlesCanOpenDoorConfiguration => undefined
2021-05-23 19:38:07.617 INFO ZWAVE: Node 20: value added 20-98-0-insideHandlesCanOpenDoorConfiguration => undefined
2021-05-23 19:38:07.621 INFO ZWAVE: Node 20: value added 20-98-0-lockTimeoutConfiguration => undefined
2021-05-23 19:38:07.625 INFO ZWAVE: Node 20: value added 20-114-0-manufacturerId => undefined
2021-05-23 19:38:07.628 INFO ZWAVE: Node 20: value added 20-114-0-productType => undefined
2021-05-23 19:38:07.632 INFO ZWAVE: Node 20: value added 20-114-0-productId => undefined
2021-05-23 19:38:07.635 INFO ZWAVE: Node 20: value added 20-128-0-level => undefined
2021-05-23 19:38:07.640 INFO ZWAVE: Node 20: value added 20-128-0-isLow => undefined
2021-05-23 19:38:07.643 INFO ZWAVE: Node 20: value added 20-134-0-libraryType => undefined
2021-05-23 19:38:07.646 INFO ZWAVE: Node 20: value added 20-134-0-protocolVersion => undefined
2021-05-23 19:38:07.649 INFO ZWAVE: Node 20: value added 20-134-0-firmwareVersions => undefined
2021-05-23 19:38:07.653 INFO ZWAVE: Node 20: value added 20-139-0-dateAndTime => undefined
2021-05-23 19:38:07.684 INFO ZWAVE: Node 20 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
2021-05-23 19:38:07.853 INFO ZWAVE: Node 23 is alive
19:38:07.872 CNTRLR   [Node 023] The node is alive.
19:38:07.903 CNTRLR » [Node 023] requesting node neighbors...
19:38:07.905 CNTRLR   [Node 023] The node is ready to be used
19:38:07.919 CNTRLR « [Node 023] ping successful
19:38:07.919 CNTRLR » [Node 023] Assigning SUC return route...
2021-05-23 19:38:08.185 INFO ZWAVE: Node 24 is alive
19:38:08.185 CNTRLR   [Node 024] The node is alive.
19:38:08.212 CNTRLR » [Node 024] requesting node neighbors...
19:38:08.214 CNTRLR   [Node 024] The node is ready to be used
19:38:08.214 CNTRLR   All nodes are ready to be used
2021-05-23 19:38:08.215 INFO ZWAVE: Controller status: Scan completed
2021-05-23 19:38:08.215 INFO ZWAVE: Network scan complete. Found: 18 nodes
19:38:08.268 CNTRLR « [Node 024] ping successful
19:38:08.269 CNTRLR » [Node 024] Assigning SUC return route...
19:38:08.369 CNTRLR « [Node 023] node neighbors received: 1, 5, 7, 8, 10, 13, 14, 15, 17, 18, 19
2021-05-23 19:38:08.388 INFO ZWAVE: Node 23: value added 23-114-0-manufacturerId => undefined
2021-05-23 19:38:08.389 INFO ZWAVE: Node 23: value added 23-114-0-productType => undefined
2021-05-23 19:38:08.389 INFO ZWAVE: Node 23: value added 23-114-0-productId => undefined
2021-05-23 19:38:08.395 INFO ZWAVE: Node 23: value added 23-121-0-defaultVolume => undefined
2021-05-23 19:38:08.396 INFO ZWAVE: Node 23: value added 23-121-0-defaultToneId => undefined
2021-05-23 19:38:08.403 INFO ZWAVE: Node 23: value added 23-121-0-toneId => undefined
2021-05-23 19:38:08.403 INFO ZWAVE: Node 23: value added 23-121-0-volume => undefined
2021-05-23 19:38:08.404 INFO ZWAVE: Node 23: value added 23-134-0-libraryType => undefined
2021-05-23 19:38:08.405 INFO ZWAVE: Node 23: value added 23-134-0-protocolVersion => undefined
2021-05-23 19:38:08.411 INFO ZWAVE: Node 23: value added 23-134-0-firmwareVersions => undefined
2021-05-23 19:38:08.412 INFO ZWAVE: Node 23: value added 23-134-0-hardwareVersion => undefined
2021-05-23 19:38:08.414 INFO ZWAVE: Node 23 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
19:38:08.533 CNTRLR « [Node 024] node neighbors received: 19
2021-05-23 19:38:08.551 INFO ZWAVE: Node 24: value added 24-37-0-currentValue => undefined
2021-05-23 19:38:08.567 INFO ZWAVE: Node 24: value added 24-37-0-targetValue => undefined
2021-05-23 19:38:08.568 INFO ZWAVE: Node 24: value added 24-38-0-targetValue => undefined
2021-05-23 19:38:08.575 INFO ZWAVE: Node 24: value added 24-38-0-duration => NaNs
2021-05-23 19:38:08.577 INFO ZWAVE: Node 24: value added 24-38-0-currentValue => undefined
2021-05-23 19:38:08.595 INFO ZWAVE: Node 24: value added 24-50-0-value-65537 => 1.25
2021-05-23 19:38:08.596 INFO ZWAVE: Node 24: value added 24-91-0-slowRefresh => undefined
2021-05-23 19:38:08.596 INFO ZWAVE: Node 24: value added 24-114-0-manufacturerId => undefined
2021-05-23 19:38:08.597 INFO ZWAVE: Node 24: value added 24-114-0-productType => undefined
2021-05-23 19:38:08.607 INFO ZWAVE: Node 24: value added 24-114-0-productId => undefined
2021-05-23 19:38:08.607 INFO ZWAVE: Node 24: value added 24-134-0-libraryType => undefined
2021-05-23 19:38:08.608 INFO ZWAVE: Node 24: value added 24-134-0-protocolVersion => undefined
2021-05-23 19:38:08.621 INFO ZWAVE: Node 24: value added 24-134-0-firmwareVersions => undefined
2021-05-23 19:38:08.693 INFO ZWAVE: Node 24: value added 24-134-0-hardwareVersion => undefined
2021-05-23 19:38:08.733 INFO ZWAVE: Node 24: value added 24-134-0-sdkVersion => undefined
2021-05-23 19:38:08.774 INFO ZWAVE: Node 24: value added 24-134-0-applicationFrameworkAPIVersion => undefined
2021-05-23 19:38:08.814 INFO ZWAVE: Node 24: value added 24-134-0-applicationFrameworkBuildNumber => undefined
2021-05-23 19:38:08.841 INFO ZWAVE: Node 24: value added 24-134-0-hostInterfaceVersion => undefined
2021-05-23 19:38:08.881 INFO ZWAVE: Node 24: value added 24-134-0-hostInterfaceBuildNumber => undefined
2021-05-23 19:38:08.890 INFO ZWAVE: Node 24: value added 24-134-0-zWaveProtocolVersion => undefined
2021-05-23 19:38:08.899 INFO ZWAVE: Node 24: value added 24-134-0-zWaveProtocolBuildNumber => undefined
2021-05-23 19:38:08.900 INFO ZWAVE: Node 24: value added 24-134-0-applicationVersion => undefined
2021-05-23 19:38:08.907 INFO ZWAVE: Node 24: value added 24-134-0-applicationBuildNumber => undefined
2021-05-23 19:38:08.936 INFO ZWAVE: Node 24 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
2021-05-23 19:38:22.031 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:38:22.076 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:38:22.128 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:38:22.236 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:38:43.977 INFO APP: GET / 200 20.698 ms - 1371
2021-05-23 19:38:44.950 INFO APP: GET /static/css/app.58e718f18996a85e37a0.css 200 4.935 ms - 641856
2021-05-23 19:38:45.030 INFO APP: GET /static/js/app.ec16c48b540283ee36c8.js 200 2.614 ms - 1811026
2021-05-23 19:38:45.906 INFO APP: GET /static/favicons/apple-touch-icon.png 200 1.590 ms - 7413
2021-05-23 19:38:45.924 INFO APP: GET /static/favicons/favicon-16x16.png 200 1.448 ms - 1113
2021-05-23 19:38:48.393 INFO APP: GET /api/auth-enabled 304 5.812 ms - -
2021-05-23 19:38:48.880 INFO APP: GET /static/logo.png 200 2.950 ms - 10014
2021-05-23 19:38:51.247 INFO APP: GET /static/fonts/MaterialIcons-Regular.fa3334f.woff2 200 3.204 ms - 82492
2021-05-23 19:38:52.278 INFO APP: GET /api/settings 200 905.091 ms - 3930
2021-05-23 19:38:52.312 INFO APP: GET /api/auth-enabled 304 13.945 ms - -
19:39:09.629 DRIVER   Could not check for config updates: Failed to download package information!
2021-05-23 19:39:09.632 INFO ZWAVE: Next update scheduled for: Mon May 24 2021 00:00:00 GMT+0200 (Central European Summer Time)
2021-05-23 19:39:22.032 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:39:22.078 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:39:22.088 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:40:21.990 INFO ZWAVE: Node 4: value updated: 50-0-value-65537 2844.87 => 2844.97
2021-05-23 19:40:22.010 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:40:22.189 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:41:22.000 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:41:22.264 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:42:22.083 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:42:22.129 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:42:22.169 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:42:22.200 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:42:22.238 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
19:43:12.430 CNTRLR « [Node 022] received wakeup notification
2021-05-23 19:43:12.441 INFO ZWAVE: Node 22 is now awake
19:43:12.452 CNTRLR   [Node 022] The node is now awake.
2021-05-23 19:43:21.995 INFO ZWAVE: Node 4: value updated: 50-0-value-65537 2844.97 => 2845.07
2021-05-23 19:43:22.089 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:43:22.115 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:44:21.989 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:44:22.099 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:44:23.499 INFO ZWAVE: Node 19: metadata updated: 49-0-Air temperature
2021-05-23 19:44:23.501 INFO ZWAVE: Node 19: value added: 49-0-Air temperature => 13.4
2021-05-23 19:44:23.501 INFO ZWAVE: Node 19: value added 19-49-0-Air temperature => 13.4
2021-05-23 19:44:23.776 INFO ZWAVE: Node 19: metadata updated: 49-0-Humidity
2021-05-23 19:44:23.782 INFO ZWAVE: Node 19: value added: 49-0-Humidity => 70
2021-05-23 19:44:23.785 INFO ZWAVE: Node 19: value added 19-49-0-Humidity => 70
2021-05-23 19:44:24.702 INFO ZWAVE: Node 19: value added: 128-0-level => 100
2021-05-23 19:44:24.706 INFO ZWAVE: Node 19: value added 19-128-0-level => 100
2021-05-23 19:44:24.713 INFO ZWAVE: Node 19: value added: 128-0-isLow => false
2021-05-23 19:44:24.715 INFO ZWAVE: Node 19: value added 19-128-0-isLow => false
2021-05-23 19:44:24.902 INFO ZWAVE: Node 19: metadata updated: 49-0-Illuminance
2021-05-23 19:44:24.913 INFO ZWAVE: Node 19: value added: 49-0-Illuminance => 166
2021-05-23 19:44:24.915 INFO ZWAVE: Node 19: value added 19-49-0-Illuminance => 166
2021-05-23 19:44:25.140 INFO ZWAVE: Node 19: metadata updated: 49-0-Ultraviolet
2021-05-23 19:44:25.149 INFO ZWAVE: Node 19: value added: 49-0-Ultraviolet => 0
2021-05-23 19:44:25.151 INFO ZWAVE: Node 19: value added 19-49-0-Ultraviolet => 0
2021-05-23 19:45:21.970 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:45:22.070 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:45:55.702 INFO APP: GET / 200 3.747 ms - 1371
2021-05-23 19:45:55.779 INFO APP: GET /static/css/app.58e718f18996a85e37a0.css 200 2.718 ms - 641856
2021-05-23 19:45:55.808 INFO APP: GET /static/js/app.ec16c48b540283ee36c8.js 200 3.062 ms - 1811026
2021-05-23 19:45:56.565 INFO APP: GET /api/auth-enabled 304 2.009 ms - -
2021-05-23 19:45:56.576 INFO APP: GET /static/favicons/favicon-32x32.png 200 1.882 ms - 1831
2021-05-23 19:45:56.968 INFO APP: GET /static/logo.png 200 45.673 ms - 10014
2021-05-23 19:45:57.006 INFO APP: GET /static/favicons/favicon-32x32.png 304 25.638 ms - -
2021-05-23 19:45:57.295 INFO APP: GET /api/settings 200 370.806 ms - 3930
2021-05-23 19:45:57.345 INFO APP: GET /api/auth-enabled 304 10.754 ms - -
2021-05-23 19:45:57.357 INFO APP: GET /static/fonts/MaterialIcons-Regular.fa3334f.woff2 200 26.202 ms - 82492
2021-05-23 19:45:59.422 INFO APP: GET /api/store 200 19.571 ms - 944
2021-05-23 19:46:08.062 INFO APP: GET /api/store?path=%2Fusr%2Fsrc%2Fapp%2Fstore%2FUtyT68TlYx_lSDj7sx4GWzuMq2FLhcW6.json 200 3.817 ms - 190
2021-05-23 19:46:10.197 INFO APP: GET /api/store?path=%2Fusr%2Fsrc%2Fapp%2Fstore%2Fd10e7639.json 200 7.511 ms - 200561
2021-05-23 19:46:13.571 INFO APP: GET /api/store?path=%2Fusr%2Fsrc%2Fapp%2Fstore%2Fd10e7639.metadata.jsonl 200 2.128 ms - 2714
2021-05-23 19:46:15.281 INFO APP: GET /api/store?path=%2Fusr%2Fsrc%2Fapp%2Fstore%2Fd10e7639.values.jsonl 200 13.727 ms - 7374
2021-05-23 19:46:16.315 INFO APP: GET /api/store?path=%2Fusr%2Fsrc%2Fapp%2Fstore%2Fnodes.json 200 10.008 ms - 994
2021-05-23 19:46:18.613 INFO APP: GET /api/store?path=%2Fusr%2Fsrc%2Fapp%2Fstore%2Fsettings.json 200 10.051 ms - 911
2021-05-23 19:46:19.389 INFO APP: GET /api/store?path=%2Fusr%2Fsrc%2Fapp%2Fstore%2Fusers.json 200 4.563 ms - 221
2021-05-23 19:46:21.978 INFO ZWAVE: Node 4: value updated: 50-0-value-65537 2845.07 => 2845.17
2021-05-23 19:46:22.016 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:46:22.070 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:46:22.086 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:46:25.458 INFO ZWAVE: Calling api _getScenes with args: [ [length]: 0 ]
2021-05-23 19:46:25.461 INFO ZWAVE: Success zwave api call _getScenes {
success: true,
message: 'Success zwave api call',
result: [ [length]: 0 ]
}
2021-05-23 19:46:26.551 INFO APP: GET /api/settings 304 249.796 ms - -
2021-05-23 19:46:26.609 INFO APP: GET /api/auth-enabled 304 1.907 ms - -
2021-05-23 19:46:28.266 INFO ZWAVE: Calling api refreshNeighbors with args: [ [length]: 0 ]
19:46:28.268 CNTRLR » [Node 001] requesting node neighbors...
19:46:28.300 CNTRLR « [Node 001] node neighbors received: 4, 5, 7, 15, 17, 19, 20, 21, 22, 23
19:46:28.304 CNTRLR » [Node 004] requesting node neighbors...
19:46:28.354 CNTRLR « [Node 004] node neighbors received: 1, 5, 8, 19, 20, 21, 22
19:46:28.361 CNTRLR » [Node 005] requesting node neighbors...
19:46:28.410 CNTRLR « [Node 005] node neighbors received: 1, 4, 8, 13, 18, 19, 21, 22, 23
19:46:28.414 CNTRLR » [Node 007] requesting node neighbors...
19:46:28.462 CNTRLR « [Node 007] node neighbors received: 1, 8, 15, 17, 18, 19, 22, 23
19:46:28.466 CNTRLR » [Node 008] requesting node neighbors...
19:46:28.511 CNTRLR « [Node 008] node neighbors received: 4, 5, 7, 13, 15, 16, 18, 19, 21, 22, 23
19:46:28.512 CNTRLR » [Node 010] requesting node neighbors...
19:46:28.539 CNTRLR « [Node 010] node neighbors received: 13, 15, 16, 17, 19, 21, 22, 23
19:46:28.540 CNTRLR » [Node 013] requesting node neighbors...
19:46:28.559 CNTRLR « [Node 013] node neighbors received: 5, 8, 10, 15, 16, 17, 18, 19, 21, 22, 23
19:46:28.560 CNTRLR » [Node 014] requesting node neighbors...
19:46:28.574 CNTRLR « [Node 014] node neighbors received: 15, 17, 22, 23
19:46:28.574 CNTRLR » [Node 015] requesting node neighbors...
19:46:28.588 CNTRLR « [Node 015] node neighbors received: 1, 7, 8, 10, 13, 14, 16, 17, 18, 21, 22, 2
3
19:46:28.590 CNTRLR » [Node 016] requesting node neighbors...
19:46:28.611 CNTRLR « [Node 016] node neighbors received: 8, 10, 13, 15, 22
19:46:28.612 CNTRLR » [Node 017] requesting node neighbors...
19:46:28.623 CNTRLR « [Node 017] node neighbors received: 1, 7, 10, 13, 14, 15, 18, 19, 21, 22, 23
19:46:28.624 CNTRLR » [Node 018] requesting node neighbors...
19:46:28.634 CNTRLR « [Node 018] node neighbors received: 5, 7, 8, 13, 15, 17, 22, 23
19:46:28.639 CNTRLR » [Node 019] requesting node neighbors...
19:46:28.669 CNTRLR « [Node 019] node neighbors received: 1, 4, 5, 7, 8, 10, 13, 17, 21, 22, 23, 24
19:46:28.670 CNTRLR » [Node 020] requesting node neighbors...
19:46:28.693 CNTRLR « [Node 020] node neighbors received: 1, 4
19:46:28.693 CNTRLR » [Node 021] requesting node neighbors...
19:46:28.710 CNTRLR « [Node 021] node neighbors received: 1, 4, 5, 8, 10, 13, 15, 17, 19
19:46:28.712 CNTRLR » [Node 022] requesting node neighbors...
19:46:28.748 CNTRLR « [Node 022] node neighbors received: 1, 4, 5, 7, 8, 10, 13, 14, 15, 16, 17, 18,
19
19:46:28.751 CNTRLR » [Node 023] requesting node neighbors...
19:46:28.765 CNTRLR « [Node 023] node neighbors received: 1, 5, 7, 8, 10, 13, 14, 15, 17, 18, 19
19:46:28.766 CNTRLR » [Node 024] requesting node neighbors...
19:46:28.781 CNTRLR « [Node 024] node neighbors received: 19
2021-05-23 19:46:28.792 INFO ZWAVE: Success zwave api call refreshNeighbors {
success: true,
message: 'Success zwave api call',
result: {
'1': [ 4, 5, 7, 15, 17, 19, 20, 21, 22, 23, [length]: 10 ],
'4': [ 1, 5, 8, 19, 20, 21, 22, [length]: 7 ],
'5': [ 1, 4, 8, 13, 18, 19, 21, 22, 23, [length]: 9 ],
'7': [ 1, 8, 15, 17, 18, 19, 22, 23, [length]: 8 ],
'8': [ 4, 5, 7, 13, 15, 16, 18, 19, 21, 22, 23, [length]: 11 ],
'10': [ 13, 15, 16, 17, 19, 21, 22, 23, [length]: 8 ],
'13': [ 5, 8, 10, 15, 16, 17, 18, 19, 21, 22, 23, [length]: 11 ],
'14': [ 15, 17, 22, 23, [length]: 4 ],
'15': [ 1, 7, 8, 10, 13, 14, 16, 17, 18, 21, 22, 23, [length]: 12 ],
'16': [ 8, 10, 13, 15, 22, [length]: 5 ],
'17': [ 1, 7, 10, 13, 14, 15, 18, 19, 21, 22, 23, [length]: 11 ],
'18': [ 5, 7, 8, 13, 15, 17, 22, 23, [length]: 8 ],
'19': [ 1, 4, 5, 7, 8, 10, 13, 17, 21, 22, 23, 24, [length]: 12 ],
'20': [ 1, 4, [length]: 2 ],
'21': [ 1, 4, 5, 8, 10, 13, 15, 17, 19, [length]: 9 ],
'22': [ 1, 4, 5, 7, 8, 10, 13, 14, 15, 16, 17, 18, 19, [length]: 13 ],
'23': [ 1, 5, 7, 8, 10, 13, 14, 15, 17, 18, 19, [length]: 11 ],
'24': [ 19, [length]: 1 ]
}
}
2021-05-23 19:46:31.802 INFO APP: GET /api/store 200 3.698 ms - 944
2021-05-23 19:47:21.958 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:47:22.050 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:48:21.962 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:48:22.061 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:49:21.958 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:49:22.051 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:49:57.933 INFO ZWAVE: Node 4: value updated: 50-0-value-65537 2845.17 => 2845.28
2021-05-23 19:50:21.946 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:50:22.046 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:51:21.949 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:51:22.041 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:52:21.947 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:52:22.048 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:52:57.944 INFO ZWAVE: Node 4: value updated: 50-0-value-65537 2845.28 => 2845.38
2021-05-23 19:53:04.843 INFO ZWAVE: Node 22: metadata updated: 49-0-Illuminance
2021-05-23 19:53:04.849 INFO ZWAVE: Node 22: value added: 49-0-Illuminance => 55
2021-05-23 19:53:04.849 INFO ZWAVE: Node 22: value added 22-49-0-Illuminance => 55
2021-05-23 19:53:21.973 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:53:22.067 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:54:21.985 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:54:22.614 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:54:23.476 INFO ZWAVE: Node 19: metadata updated: 49-0-Air temperature
2021-05-23 19:54:23.480 INFO ZWAVE: Node 19: value updated: 49-0-Air temperature 13.4 => 13.9
2021-05-23 19:54:23.658 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:54:23.775 INFO ZWAVE: Node 19: metadata updated: 49-0-Humidity
2021-05-23 19:54:23.786 INFO ZWAVE: Node 19: value updated: 49-0-Humidity 70 => 70
2021-05-23 19:54:23.935 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:54:24.695 INFO ZWAVE: Node 19: value updated: 128-0-level 100 => 100
2021-05-23 19:54:24.707 INFO ZWAVE: Node 19: value updated: 128-0-isLow false => false
2021-05-23 19:54:24.892 INFO ZWAVE: Node 19: metadata updated: 49-0-Illuminance
2021-05-23 19:54:24.895 INFO ZWAVE: Node 19: value updated: 49-0-Illuminance 166 => 212
2021-05-23 19:54:25.131 INFO ZWAVE: Node 19: metadata updated: 49-0-Ultraviolet
2021-05-23 19:54:25.133 INFO ZWAVE: Node 19: value updated: 49-0-Ultraviolet 0 => 0
2021-05-23 19:55:21.975 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:55:22.036 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:55:57.979 INFO ZWAVE: Node 4: value updated: 50-0-value-65537 2845.38 => 2845.48
2021-05-23 19:56:21.986 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:56:22.086 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:56:31.117 INFO ZWAVE-SERVER: Client disconnected
2021-05-23 19:57:21.975 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:57:22.089 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:58:21.987 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:58:22.038 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:58:57.990 INFO ZWAVE: Node 4: value updated: 50-0-value-65537 2845.48 => 2845.58
2021-05-23 19:59:21.982 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 19:59:22.059 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 19:59:43.067 INFO ZWAVE: Node 21: value added: 128-0-level => 100
2021-05-23 19:59:43.067 INFO ZWAVE: Node 21: value added 21-128-0-level => 100
2021-05-23 19:59:43.070 INFO ZWAVE: Node 21: value added: 128-0-isLow => false
2021-05-23 19:59:43.070 INFO ZWAVE: Node 21: value added 21-128-0-isLow => false
2021-05-23 19:59:43.552 INFO ZWAVE: Node 21: metadata updated: 49-0-Air temperature
2021-05-23 19:59:43.560 INFO ZWAVE: Node 21: value added: 49-0-Air temperature => 11.5
2021-05-23 19:59:43.561 INFO ZWAVE: Node 21: value added 21-49-0-Air temperature => 11.5
19:59:43.731 CNTRLR « [Node 021] received wakeup notification
2021-05-23 19:59:43.737 INFO ZWAVE: Node 21 is now awake
19:59:43.745 CNTRLR   [Node 021] The node is now awake.
19:59:45.727 CNTRLR » [Node 021] Sending node back to sleep...
2021-05-23 19:59:45.918 INFO ZWAVE: Node 21 is now asleep
19:59:45.930 CNTRLR   [Node 021] The node is now asleep.
2021-05-23 20:00:21.991 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 20:00:22.106 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 20:01:21.991 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 20:01:22.088 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 20:01:57.982 INFO ZWAVE: Node 4: value updated: 50-0-value-65537 2845.58 => 2845.68
2021-05-23 20:02:21.985 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 20:02:22.007 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 20:02:22.051 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 20:02:22.081 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 20:03:21.993 INFO ZWAVE: Node 24: value updated: 50-0-value-65537 1.25 => 1.25
2021-05-23 20:03:22.017 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93
2021-05-23 20:03:22.070 INFO ZWAVE: Node 5: value updated: 50-0-value-65537 5.93 => 5.93

@AlCalzone

Only problem though is that everyone reports his issues here after re-interviewing the nodes, but I need to see the cache files directly after it broke.

👆🏻

I'm going to merge the PR which is going to close this issue. If the issue persists with the next version (zwave-js@7.2.2), feel free to reopen.

I have a system that encountered this issue last week. At the time, it was running 7.2.1. I've since upgraded to 7.7.1 and the issue persists (not having re-interviewed the nodes). Is that expected? Asking not to sound daft but in case the log would be useful to you. Thanks.

@nop-ad-infinitum If you can share a driver log of the startup and the cache files before re-interviewing, that would be good.
It might be necessary to re-interview to fix the lost info (if it was really lost) - so maybe what you're seeing just didn't fix itself yet.

Apologies, I realized I may be confused by the terms "re-interviewing" and/or "manually re-interviewing" (from OP) and quite possibly wasting your time. My log and cache files are attached, however.
zwavejs_2021-05-31.tar.gz

I can't tell exactly, because the loglevel is too low - but it looks like your stick hangs. Try power cycling it.

I ended up solving this issue with a backup, but it has happened to me multiple times. Aeotec stick, virtual machine on windows, power failure leads to losing all my nodes. They've all shown up as dead, and I also got an error "info zwave: controller status: driver: failed to initialize the driver: timeout while waiting for an ack from the controller". I don't have nay logs to share, but I did get that from my google search history. According to various forum searches with the same error, it looks like a similar error happens when you have the Zwave JS integration installed and forget to uncheck to use the default add-on. But of course I had everything working correctly beforehand, so it does appear to be something with losing power.
Unplugging and replugging in the stick from my physical machine and the virtual machine also helped, but only after reinstalling the add-on and the integration, and so I lost the names of all my nodes. Ended up just going for a system restore and the problem went away.
Hope some of that info helps, but if not: allow me to push everyone to get the google drive snapshot backup add-on. I learned my lesson the first time this happened, so it was much easier to fix this most recent time.

@ALCalzone My bad- I thought I had the log level set to silly. I did try rebooting the host and unplugging the stick.
Oddly enough, that system suffered another power outage as you posted your reply. The host is still online, but since not all nodes are on a UPS, I'll wait until power is restored to re-run and upload new files.
@drphungky Good tips. In my case it's a simple dev setup so no worries.

Here's my level 6 log and cache. I must be doing something wrong with Driver.updateLogConfig(), but the constructor option works.
zwavejs_2021-05-31.tar.gz

Hey all, this is unfortunately either still not resolved, or regressed back alive partially.
After a power failure, all my nodes are still seem configured (compared to previously where all columns in the table became unknown)  and there's still data coming from them (e.g. I can map the network, they respond to ping and they send data to zwavejs). But all secure nodes display "unknown" in their "security" column. They don't seem to accept any device specific commands (e.g. moving a shutter) until I reinterview the node.
E.g. writes error with
2021-07-06 03:47:53.097 INFO ZWAVE: Calling api writeValue with args: [
{ nodeId: 20, commandClass: 38, endpoint: 1, property: 'Up' },
true,
{},
[length]: 3
]
2021-07-06 03:47:53.100 INFO ZWAVE: Writing true to 20-38-1-Up
2021-07-06 03:47:53.152 INFO ZWAVE: Success zwave api call writeValue undefined

After reinterviewing the node, the secure entry in their column gets updated from unknown to yes and everything works again.

As always, this needs more info.

Which driver version?
How do the cache files look like after the power failure but before re-interviewing?
Driver logs of the startup

I see you opened a new issue - let's continue there.

Where do we find these different logs you require? I couldnt find them last time I searched for them

For zwavejs2mqtt, it is documented here: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report?id=driver-logs


Next.js project setup

migrate from react webapp to next js so we can take advantage of key management for twitter API

This project is not using Next.js.
Feel free to open it late if there is a plan to migrate it to Next.js


Updated checkout action in workflow to v3, to kill warnings

Tiny change, to stop getting warnings from Github Actions every time I check something new in ;-)

I don't know why the status checks are refusing to run here 😬

looks at date
💀

Hey, it's less than a year!

Merged via #19 since the CI went wonky (or probably expired sigh here)
Thank you!


[Feature] Upgrade API to 1.9

Proposal
Upgrade the API from Django 1.8 to 1.9.
Repercussions
Although I have started this process there are a few catches that might not be great:

api.base.serializer ~443 has a line that gets back what looks to be a dictionary, but is actually a string.
hasattr is used a few times in the API, but might be causing significant recursion.

Hopefully other issues are related to these, so fixing them will fix many other test failures.

Stopped build checks because there are obvious failures.

This is better done by #5242


When publishing, hidden fields become unhidden

I think this might've been related to 85001bcf49f322fcf33ef6aab4fbed066ebe05f1, but I can't repro this. @Ryan-McMillan can you provide more details if this is still happening?


Ikea round remote can't change colour temp correctly

Hey so i have the config in deconz setup so that the left button is colder and the right button is warmer but both buttons only make the bulb warmer. Can change colour temp in software fine - let me know if you need more info

Hi there @hell1337hound,
Add-ons implement/wrap existing software. In this case the Phoscon/deCONZ application.
This issue you are reporting it within the application itself. Please report your issue with the authors of the software, as from an add-on perspective, there is not much we can do.
If a bug gets fixed, and the software updated, the add-on will be updated as well.
Thanks 👍


no master router defined

Hello, i have a warning:
WARNING: There is no master router defined!
on the status line and the Fritz!Box is not shown on "Devices"
Do you have an idea what i have to change in the config file.
"master = true" is set.
Best regards
Thomas

Can u post ur config pls

Here it is:
{
"name": "FritzPlatform",
"devices": [
{
"name": "Firitz!6360",
"username": "",
"password": "",
"ssl": true,
"tr064": true,
"igd": true,
"master": true,
"connection": "cable",
"options": {
"wps": "switch",
"led": "characteristic"
}
}
],
"presence": [
{
"ping": false
}
],
"smarthome": [
{
"accType": "false"
}
],
"callmonitor": {
"active": false,
"port": 1012
},
"extras": {
"alarm": {
"active": false
},
"wakeup": {
"active": false
},
"ringlock": {
"active": false
},
"phoneBook": {
"active": true,
"accType": "switch"
}
},
"options": {
"polling": {
"timer": 10
}
},
"telegram": {
"active": false
},
"platform": "FritzPlatform"
}

@tmgraeter
You have no host defined for the router

I have filled out the field in the UI config but as you say it is not in the config.
can you tell me the setting for this "host": <IP_ADDRESS> for example or something in addition ?

@tmgraeter
Oh it seems i have forgotten to add it into config ui x
Yes something like <IP_ADDRESS>

Ok thank you ... now it connects ... haveing still some changes to do ..
have a nice evening

Thx, also :)


getVideoByUrl() & getUser() are always false

Describe the bug
I use the method getVideoByUrl for almost 6 months and since January 17 it started returning only false.
We use the WebShare proxy as suggested.
I did some debugging and I observed that the code fails at the regex part:
In Api.php:488
$result = Helper::string_between($result, '{"props":{"initialProps":{', "</script>");

And  the page source returned by the curl call does not contain this string anymore.
The same happens for getUser method.
To Reproduce
Steps to reproduce the behavior:

PHP Version: 7.3
Package Version:2.0.0
Used Method: getVideoByUrl
Used options: with and without proxy
Do you use this package with VPS, VPN or proxy? Yes, I tried with multiple paid proxies
Can you access TikTok website without captcha or forced login screen? yes
Is the profile you are tyring to get data from is private? No
Preferably provide URL to the profile,hashtag,video and etc page: any page

Screenshots
$api = new \Sovit\TikTok\Api([
"proxy-host" => config('proxy.host'),
"proxy-port" => config('proxy.port'),
"proxy-username" => config('proxy.username'),
"proxy-password" => config('proxy.password')
]);

$result = $api->getUser('moniquedias961'); // returns false
$result = $api->getVideoByUrl('https://www.tiktok.com/@ravmalik/video/7030873814435138821'); // returns false

[alina-ami] I got the same problem. how do you solve it?

Re-open if issue still persists

@ssovit the issue is still there


Need Support for Node.js

It will be great to provide support for node.js web services primarily built on express.js framework. Let me know if i could contribute.

Hi @invalidred
I do not have immediate plan for supporting this, however you are free to extend the code and contribute. I'll work on this as soon as I get some bandwidth!

Hi navneet,
I have started working on Node.js part. Hopefully i should submit a pull request within a week or so. So stay tuned.

Great! keep me posted.


Enable HRD calling in TN workflow

Reference: https://trello.com/c/3Ww9alsI/1179-dragen-hrd-results

Related to https://github.com/umccr/infrastructure/pull/335

Had turn flags on as part of Portal T/N automation input template side - ditto diff
https://github.com/umccr/infrastructure/pull/335/files

 Portal Release - Ocicat: Add Dragen HRD results


Text colour of the Paragraph.

Description

The para in https://play.meshery.io/ in light mode is not visible.
Expected Behavior

The paragraph should be clearly visible
Screenshots

Enviroment:

OS: Mac Linux Windows
Browser: Chrome Safari Firefox
Version:
Device: Desktop Mobile

Contributor Guides and Handbook
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

if this issue get's approved, I would like to work on it.

Thanks, @ShivangRawat30 👍


pdfload operations

Safe operations for vips_pdfload/vips_pdfload_buffer/vips_pdfload_source (and the _with_opts counterparts) would be useful. The unsafe bindings are currently available, but it looks like the safe wrappers have not been generated. Were these filtered out during the generation process?
Happy to help with the implementation 😄

I think this is due to building libvips without pdf support - poppler is not included in the list of dependencies installed in the generator container https://github.com/olxgroup-oss/libvips-rust-bindings/blob/147b481b6788b76ace38cff58c3a70d9473caad9/generator/Dockerfile#L6.


added loading via bytes

I would rename "Bytes" property to "FileBytes" or "ImageBytes" for better understanding.


GitPod doesn't allow creationg of account from many countries

We have had many users coming on the forum saying that GitPod is asking for verification through phone number and then it doesn't accept it, making it really difficult to create an account.
Plus the limit of 50 hours per month.
Are there alternative platforms we could use?

I looked around and found this. Perhaps VS Code for the Web could be an alternative?

Alternatively, we could use CodeSpaces. However, this is another config we need to create and maintain, and I am not sure if 100% eliminates the issues.
I never needed to verify with my phone number. So, is this a new thing?
It also has hour limits, and account creation location limits: https://docs.github.com/en/site-policy/other-site-policies/github-and-trade-controls#on-which-countries-and-territories-are-us-government-sanctions-applied

So, is this a new thing?

I don't know if it's a new thing, but it has become apparent as we have added it more to the curriculum. While I wasn't looking there are various new posts on the forum on this issue (both usage limit and account creation limit), if CodeSpaces doesn't have these limits it could be beneficial for the campers to switch over

an other one having issues with gitpod phone verification: https://forum.freecodecamp.org/t/learn-bash-by-building-a-boilerplate-build-a-boilerplate/712816

I've reached Gitpod 50hrs limit, now I couldn't be able to use Gitpod for freecodecamp projects, Is upgrading the plan is the only solution, or Is there any other way I could get it for free?

Can freecodecamp help me increase my limit?


Allow rolling back to a specified snapshot in asset manager

This patch improves the asset-delete workflow operation handlöer to not only allow for deleting all or all except the latest snapshot of an event, but also allows deleting all version newer than a given version. This essentially means that you can roll back to a given event in the asset manager.
Along the way, this also fixes the problem of this operation creating errors since it may delete files the current workflow requires to work on. This could previously be worked around using ingest-download, but is actually quite unnecessary.
This keeps the current behavior (e.g. if you were already working around the problem using ingest-download) unchanged
Your pull request should…

[x] have a concise title
[x] close an accompanying issue if one exists
[x] be against the correct branch
[x] include migration scripts and documentation, if appropriate
[x] pass automated tests
[x] have a clean commit history
[x] have proper commit messages (title and body) for all commits

So far that wasn't a big deal because we either kept the latest snapshot […]or we threw the whole event away anyway.

Actually, just deleting all snapshots but not the event was the default behavior of this operation before and isn't new. So you already had the problem in the old code. But I see your point.

e.g. keeping the publication references when rolling back

That's not impossible since the publication information are versioned, and you cannot roll back to version n and modify it. You would need to roll back, modify the publication and create a new version n' in the asset manager which would contain the modifications.
To address the problems, I made a few changes which we can hopefully agree on:

Add a warning to the documentation, that this is a dangerous operation
Target develop due to the additional changes
Don't allow removing all versions. We agreed that this never really made sense
Have the operation return the media package from the snapshot you rolled back to, but with the current publications transferred over. This has two advantages over how things worked before:

No more need for keeping old files in the workspace. The remainder of the workflow will continue to run on valid data.
If you want to keep your current publications, you can easily do that with a snapshot operation which will then create a new version with the updated publication data.

I've added the publication problems to the docummentation

Fair enough. Since we disagree. Let's just close this. Let's leave it in the broken state it is right now :shrug:
There is a big warning block already.
I strongly disagree with modifying old snapshots. I also wouldn't automatically create new snapshots. Again, that's not the idea of a rollback.
Sure, the publications in the snapshots are not a great idea in the first place. They shouldn't be stored in a versioned way since they are not versioned. But we shouldn't do weird stuff just because of that.

Let's leave it in the broken state it is right now. 🤷

This feels a bit passive aggressive to me tbh, and I don't really understand why. I agree that the state this WOH is in is not great right now. But I don't think that means we should not be critical of a potential fix (and this PR is a bit more than that), and I don't think you do either.
It's unfortunate that we can't come to an agreement here, not even in regards to a rewording of the warning. While we can (and should) argue about the solutions (and I do see their drawbacks), I stand by my opinion that the current documentation downplays the potential data inconsistencies after this operation.
I'm open to discuss this some more, but if that's not something you have time for right now, I guess we can leave it closed and maybe somebody else can get back to this later.


Development status?

Hi, this library is perfect for a project I have in mind, it's lightweight and small.
However, there are a few open issues and pull requests, plus a variety of other minor problems I've seen. What do you think about fixing them up? If not, I am prepared to fork and continue development with the assistance of other coders.
Thanks

Fine by me 👍

Ian Harcombe
On Thu, 28 Oct 2021, 23:18 robinpaulson, @.***> wrote:

@alihakimtaskiran https://github.com/alihakimtaskiran and @barrald
https://github.com/barrald and @MrHarcombe
https://github.com/MrHarcombe
It's been a while since the owner of the code has made any changes, so I'm
going to fork and continue development. I'd like to include your pull
requests, they fix a few important bugs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Broham/suncalcPy/issues/10#issuecomment-954267949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQU6A5OUL3HDHLZWDHKN7DUJHD4NANCNFSM5GHTVVKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi @robinpaulson ,
I have fixed these bugs and made it object based in Martan Solar Power Plant  when there was no response from @Broham .  If you wish you can join Martian Solar Power Plant . We can continue to develop it and make it compatible with all planets not just Earth.
Best Regards,

@alihakimtaskiran and @barrald and @MrHarcombe It's been a while since the owner of the code has made any changes, so I'm going to fork and continue development. I'd like to include your pull requests, they fix a few important bugs.
https://github.com/robinpaulson/suncalcPy

Hi @alihakimtaskiran thanks for getting back to me, that sounds like a really interesting project! However, i want to keep the code as small as possible, i intend to run it on a device with very limited storage (a raspberry pi pico), so expanding for other celestial objects, while interesting would cause me problems and distract me from the thing I want to do with it.
I will keep an eye on what you're doing though, perhaps there are some commits I can pull to my fork.
Cheers!

I would just point out that the author has, in the last hour, merged my pull request; so they may be in the process of tidying up ready to update (or readying to close down and handover - who knows). Either way, there was recent activity... watch this space?

Thanks for the heads up @MrHarcombe ; I'll keep my eye on what the owner does and see how it fits with my fork.


feat: add jsonify

Jsonify is a simple and efficient online tool designed to convert, format, and validate JSON data.

Fixes Issue #2512
Changes proposed
Jsonify is a powerful API platform that quickly converts complex data into structured JSON format for seamless integration and analysis.
Screenshots

Note to reviewers

@rajneesh-18 please resolve merge conflicts


how communicate with Qt by fastapi websocket?

My endpoints(Iot, such as temperature sensor control, coding with Qt) want to send data to server,how can I communicate by fastapi websocket.I got a err 403.

It sounds like you aren't sending authentication in your request?

Um, but I can run with gevent-websocket without any authentication.
Qt's websocket also no authentication.

Your error is 403 - forbidden.
Maybe see what errors are in your server console?

WebSockets 403 will be returned in case of an HTTP 404. So your path may not exist.

Been trying to do the same. @wolfishboy , Have you figured it out?

Thanks for the help here everyone! 👏  🙇
If you solved your problem @lang101, then you can close this issue ✔
If anyone else has similar problems, please create a new issue following the template and creating a self-contained example that shows your intention and the problem, and that I (or someone else) can copy-paste and run to check it out.

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Install build-essential on ground-up provisioning

Closes #115

😅 I was doing it also

🙈  Sorry!


Product pages (blank pages only)

Description

Update Header to show sub menus
Skeleton product pages

@taariq
They are hidden for now. This PR is just layout updates.
I am focusing the blog and event pages at the moment


Code cleanup

[ ] Fix any typos in documentation and comments
[ ] Replace print() statements with info() from python logging

Hey there, Can you please explain more about your issue.

@m-a-g-g See this pr: https://github.com/tfukaza/harvest/pull/103 . Could you add typing and code comments to parts you think might need them? Also if you see any parts where we use print('blah') can you replace that with some function from the logger package https://docs.python.org/3/library/logging.html. Feel free to use which log level you think is appropriate. Thanks!

I also updated the issue description, sorry it was confusing at first. Feel free to ask if you have questions, and thanks for contributing!


How can I make the player start from a specific time (File)?  Thanks =)

Be sure to search for your issue before opening a new one.
Current Behavior

Expected Behavior

Steps to Reproduce

Environment

URL attempting to play:
Browser:
Operating system:
jsFiddle example: https://jsfiddle.net/sv5x3ug1

Other Information

Try this: https://stackoverflow.com/a/25235578


Strange nesting when discussion has nested headings

https://en.wikipedia.org/wiki/Wikipedia:Teahouse/Questions/Archive_143#Deletionism.3F produces:
== Deletionism? ==
=== Deletionism? (Edit Break 1) ===
    User:AugurNZ | Time:01:51, 18 September 2013 (UTC)
        User:Writ_Keeper | Time:02:16, 18 September 2013 (UTC)
            User:AugurNZ | Time:02:52, 18 September 2013 (UTC)
                User:Cullen328 | Time:03:02, 18 September 2013 (UTC)
                    User:Cullen328 | Time:03:29, 18 September 2013 (UTC)
                        User:AugurNZ | Time:03:46, 18 September 2013 (UTC)
                            User:LtPowers | Time:14:38, 18 September 2013 (UTC)
                                User:Safetyprofessional | Time:19:30, 18 September 2013 (UTC)
    User:AugurNZ | Time:20:57, 18 September 2013 (UTC)
        User:Anne Delong | Time:21:03, 18 September 2013 (UTC)
            User:AugurNZ | Time:21:52, 18 September 2013 (UTC)
                User:Konveyor_Belt | Time:22:45, 18 September 2013 (UTC)
                    User:AugurNZ | Time:22:55, 18 September 2013 (UTC)
                        User:LukeSurl | Time:23:08, 18 September 2013 (UTC)
                            User:LukeSurl | Time:23:20, 18 September 2013 (UTC)
                                User:Konveyor_Belt | Time:23:27, 18 September 2013 (UTC)
    User:AugurNZ | Time:23:37, 18 September 2013 (UTC)
        User:Writ_Keeper | Time:23:52, 18 September 2013 (UTC)
            User:AugurNZ | Time:00:17, 19 September 2013 (UTC)
                User:Writ_Keeper | Time:00:53, 19 September 2013 (UTC)
                    User:AugurNZ | Time:01:30, 19 September 2013 (UTC)
                        User:Salvidrim | Time:02:04, 19 September 2013 (UTC)
                            User:AugurNZ | Time:18:34, 19 September 2013 (UTC)

where I'd expect the secondary heading to be somewhere in the middle. Not sure if this is a parsing issue or a pretty-print issue

Also in https://en.wikipedia.org/wiki/Wikipedia:Teahouse/Questions/Archive_420#Draft:Mike_.22Greeny.22_Green_.28again.29 so consistently reproducible.

This and https://github.com/earwig/mwparserfromhell/issues/55 are the only obvious issues I still have left from all the Teahouse archives. Given how fickle these are, amazing work :D

Where was this fixed? I'm trying to find the commit...

It looks like I didn't quiet give this enough attention when I was first looking at it. I had thought that it would also be fixed by pull request #11. After merging that I am now getting this output
== Deletionism? ==
=== Deletionism? (Edit Break 1) ===
    User:AugurNZ | Time:01:51, 18 September 2013 (UTC)
        User:Writ_Keeper | Time:02:16, 18 September 2013 (UTC)
            User:AugurNZ | Time:02:52, 18 September 2013 (UTC)
                User:Cullen328 | Time:03:02, 18 September 2013 (UTC)
                    User:Cullen328 | Time:03:29, 18 September 2013 (UTC)
                        User:AugurNZ | Time:03:46, 18 September 2013 (UTC)
                            User:LtPowers | Time:14:38, 18 September 2013 (UTC)
                                User:Safetyprofessional | Time:19:30, 18 September 2013 (UTC)
    User:AugurNZ | Time:20:57, 18 September 2013 (UTC)
        User:Anne Delong | Time:21:03, 18 September 2013 (UTC)
            User:AugurNZ | Time:21:52, 18 September 2013 (UTC)
                User:Konveyor_Belt | Time:22:45, 18 September 2013 (UTC)
                    User:AugurNZ | Time:22:55, 18 September 2013 (UTC)
                        User:LukeSurl | Time:23:08, 18 September 2013 (UTC)
                            User:LukeSurl | Time:23:20, 18 September 2013 (UTC)
                                User:Konveyor_Belt | Time:23:27, 18 September 2013 (UTC)
    User:AugurNZ | Time:23:37, 18 September 2013 (UTC)
        User:Writ_Keeper | Time:23:52, 18 September 2013 (UTC)
            User:AugurNZ | Time:00:17, 19 September 2013 (UTC)
                User:Writ_Keeper | Time:00:53, 19 September 2013 (UTC)
                    User:AugurNZ | Time:01:30, 19 September 2013 (UTC)
                        User:Salvidrim | Time:02:04, 19 September 2013 (UTC)
                            User:AugurNZ | Time:18:34, 19 September 2013 (UTC)
=== Deletionism? (Edit Break 1) ===
    User:AugurNZ | Time:23:37, 18 September 2013 (UTC)
        User:Writ_Keeper | Time:23:52, 18 September 2013 (UTC)
            User:AugurNZ | Time:00:17, 19 September 2013 (UTC)
                User:Writ_Keeper | Time:00:53, 19 September 2013 (UTC)
                    User:AugurNZ | Time:01:30, 19 September 2013 (UTC)
                        User:Salvidrim | Time:02:04, 19 September 2013 (UTC)
                            User:AugurNZ | Time:18:34, 19 September 2013 (UTC)

So  === Deletionism? (Edit Break 1) === ends up in its super-section as well as just underneath it. I think that there is an argument in mwparserfromhell.get_sections that should let me fix it pretty easily.
Definitely my bad, I shouldn't have closed this one yet. Reopening.
This input also illustrates a problem with {{od|:::::::}}, but I will open a separate issue for that.

Commit message was a little confusing, real issue is fixed in https://github.com/kjschiroo/WikiChatter/commit/08c2e38f9c87926476e7ad346001bf2a8271ab47


Various security fixes (mostly Snyk)

These are suggested merge fixes from Snyk, Dependabot, or some other code analysis tool.

Thanks @EricSherrill. I think we've fixed all these via cleanup and various updates in other PRs.


[ci] make JTAG tests blocking

This PR:

removes the jtag tag from opentitan_functests that was used to run a separate non-blocking CI job for tests that used the OpenOCD/JTAG infra (this was hard to maintain as it was manually maintained), and
removes the separate non-blocking JTAG test job from CI as the JTAG tests are now run in either the test ROM tests or ROM tests stages and are blocking.

Looks like combining the tests into the test ROM / ROM test run stages in CI causes it to time out. Let me see if I can get the JTAG tests (or at least the manufacturing tests) to run a separate CI stage that is also blocking.

To get these tests blocking asap, I just updated the manufacturing tests to run in a separate CI stage that is blocking, by tagging them with the "manuf" tag.
However, as we saw with the "jtag" tag, manually maintaining tags to enforce CI job separation is difficult and error-prone. So I will file an issue to track a follow up PR that can better handle this. I think ideally, we would be able to get a list of all ROM and test ROM FPGA tests and run them across N different parallel CI stages.


Basic write-path logging

Pretty basic, not fancy. @pauldix

Add write tracing to the handler. If it's enabled we should output the string JSON data that is posted to /write. Also worth adding to the other input plugins too.
Also, add the option and a comment about what it does if its set to true to the config.sample.toml file.

Oh yeah, forgot about the sample file.

Updated with changes to config file flag, and tracing also added to handler, which dumps JSON data.

Verbal +1 form @pauldix

Green build, merging now.


Need ability to force connections to close bypass keepalive.

In some cases it is preferred to force connections to close. Sending a "Connection: close" header will force the client to close the connection even if keep alive is requested. The current code does not allow to set the Connection header as it will be replaced depending on client request for keep alive.
I need a way to force state machine to close the connection so I can reserve my limited connections and avoid this problem.
[HTTPS:E] Could not accept() new connection

That's already part of #52. But as that PR combines many features and changes, I'm not really able to merge it right now.
I think to solve the root issue (new connections not being accepted), we should set two measures into place:

Not ignoring Connection: close when set by the application developer (assuming he/she has a reason)
If all connection slots are currently used, and a connection comes in, then use a least-recently-used mechanism to close one of the existing connections in favor of the new one (that's what is implemented in the aforementioned PR)

I'll take care of implementing the first one. For the latter, I've still some concerns that a malicious client can repeatedly request connections and force the ESP into dropping all existing connections with legitimate clients. Maybe the decision has to be made not only LRU-based but also w.r.t. the client IP.

PR #78 will handle the first problem, I'll merge it as soon as the dependent PRs are merged, too. Issue #79 tracks the implementation LRU connection handling.


switch to pip install of edm sampler

Modulus Pull Request
Description

Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[ ] The CHANGELOG.md is up to date with these changes.
[x] An issue is linked to this pull request.

Dependencies

edm_sampler for resdiff is slightly different from the original sampler in the EDM repo. Therefore, our previous idea of getting the code directly from the EDM repo doesn't work. I've packaged the updated sampler here https://github.com/mnabian/modulus/tree/main, and can be pip installed.
Verified test.sh works with this change.

/blossom-ci


Flowtype error

node_modules/iterall/index.js:98:6

Unable to determine module type (CommonJS vs ES) if both an export statement and module.exports are used in the same
module!

It should have been fixed, I will upgrade the package.

According to my investigating, the reason should be that the built index.js is CommonJS modules.export, but the flow comment is ES module export.

Thanks for the report. @calebmer also mentioned this. I’ll look into a fix.

@calebmer, I merged the flow definitions into the source file via flow comments, but the compilation to CJS is what results in the difference. If I create an index.js.flow will that suffice? I shouldn’t need one for index.mjs since that had the flow defs matching, right?

If I create an index.js.flow will that suffice?

This was my initial thought upon encountering this issue and FWIW would work for my use case.
However, the bummer with including types in a package is that newer versions of Flow might break older type definitions.  In a pre-1.0.0 world, I generally lobby for type defs in https://github.com/flowtype/flow-typed, since they are scoped to compatible Flow versions.


Feature: Job-hunt tracking

Add a feature to help job-hunters track resume submissions, interview requests, etc. Use JSON-compatible schema, command-line support, and GUI support through FD.

Added to backlog.


Added wallaby.js configuration

Hey,
I have been asked to create wallaby.js config for the project, so I thought I'd create the pull request in case if someone wants to use wallaby.js for contributing to RxJs. Even though the original build process is pretty tricky and tests are written against the compiled code, this wallaby config works for the original TypeScript, allowing to do realtime continuous testing/development (in Atom/WebStorm/Visual Studio):

Whoa... what is this? Fancy.  @kwonoj... is this something you're using for development?
It doesn't seem to be invasive to the project... How can I test this out to make sure it works before I'd merge it?

@blesh Yes, this is tool I started using for running test against. I've originally used similar test runner for C#, and found extremely useful for TDD.
to test out this by yourself, you may need

install atom.io (https://atom.io/) : if you have one, go ahead to second step.
install package wallaby.js in atom.io (https://atom.io/packages/atom-wallaby)
put above config file, right click on those file in file list pane - set as wallaby.js config
ctrl-shift-T R to start it. (or ctrl-shift-p then type wallaby to find relative menus)

*disclaimer: full license required to run wallaby.js without any limitation.

It doesn't seem to be invasive to the project.

Yes it is not invasive. It can be considered as same as any other test runner configuration like karma, etcs. If you use wallaby.js for test runner it'll work for you, otherwise this won't do anything to codebase.

@kwonoj ... I want to review this, can you please pull this branch down and be sure it works... if it does or doesn't let me know in this PR and I'll merge if you give the thumbs up.
git fetch upstream pull/619/head:pr-619
git checkout pr-619

Just confirmed it's working nicely. Attached screenshot pr-619 correctly trigger test runner.

Merged with acda6e8 ... thanks @ArtemGovorov for the help! That looks like a really fun/interesting tool.

(Also thanks @kwonoj for helping me test)


I cannot log in as a bot

I am trying to use tdsharp as a wrapper around the tdlib API for .NET.
Whenever I try to call CheckAuthenticationBotTokenAsync with my bot-token. I get the error: TdLib.TdException: 'ACCESS_TOKEN_INVALID' although the exact same token is used for Bot API and it's working just fine.
Would be nice to get help here since the documentation is super confusing and there is no direction for people like me as to where to go.
Thanks in advance.

Are you sure that you use the correct token as provided by BotFather starting with digits and not "bot"?
Did you correctly specify use_test_dc == false in setTdlibParameters?

Are you sure that you use the correct token as provided by BotFather starting with digits and not "bot"? Did you correctly specify use_test_dc == false in setTdlibParameters?

Dear @levlam
Thanks for your reply I was able to find the issue, yes indeed I was using use_test_dc to true. I thought it sort of make sense, since I am actually testing locally.
Any reason why it doesn't if we are passing use_test_dc = true?
Anyways this can be safely closed.
Thanks alot!

Test environment is a completely independent environment. You can create accounts and bots there independently and can transfer no data between test and production environment.

Test environment is a completely independent environment. You can create accounts and bots there independently and can transfer no data between test and production environment.

Thanks for the clarification @levlam


fix Issue [#2178] and Issue [#2167]

Changes
fix Issue [#2178] and Issue [#2167].
Checklist

[x] An issue to be fixed by this PR is listed above.
[ ] New tests are added to ensure new features are working. Please refer to this page to see how to add a test.
[ ] ./frb_internal precommit --mode slow (or fast) is run (it internal runs code generator, does auto formatting, etc).
[ ] If this PR adds/changes features, documentations (in the ./website folder) are updated.
[ ] CI is passing. Please refer to this page to see how to solve a failed CI.

Remark for PR creator

./frb_internal --help shows utilities for development.
If fzyzcjy does not reply for a few days, maybe he just did not see it, so please ping him.

I hope that this PR is OK. I did my best 😃

Other things to do before merging

[ ] Make CI green (just run the commands mentioned before and it should be automatically ok)


\text accepts nested $...$ fragments but not (...)

In LaTeX and MathJax, this works fine:
\[
  x = z \quad \text{because $x = y$ and \(y = z\)}
\]

KaTeX doesn't like the nested \(...\) fragment, though.
This is documented and probably well-known, but I didn't find an issue on it.
This could probably be generalized to accepting only the delimiters passed in to renderMathInElement with display: false, but I don't know if the structure of the code makes that easy.

Good idea!  We should definitely support nested \(...\).  I originally added $ support, and can try to do the same for \(.
I don't think we want to have any connection to autorender though. That's about getting from HTML into LaTeX.  Once in LaTeX, we should just support LaTeX syntax.

Ah, good point, forgot that they were separate! I agree.


Feature subproj library refs

This is a fairly risky change, and basically makes up for an Xcodeproj gem failure anyway. I think we should file a bug there instead of monkeypatching.