Set up connection to Genie CM7600IC via GoControl GD00Z-8 Z-Wave

Logging intallation cont'd from https://github.com/130s/hut_10sqft/issues/560#issuecomment-1144509587

No idea. Just asked on diy.stackexchange.com#250763.

Also sent an email to<EMAIL_ADDRESS>

Related but off topic: I found 2 pairs of terminals   instead of 1,each of which consists of blue and white-blue stripe cable.

Feel like figuring out what these 2 pairs are for (if these are connected to push button, I'm aware of only 1 button connected to this controller so why 2 pairs?).

Unwired the pair on right side

Pressing wall button triggers closing the garage, but once I release the button the garage started moving back.
Keeping button pressed let the garage closed til the end. But once I released the button, it went back all the way again.

Unwired both pairs. -> Wall button doesn't seem to trigger anything.
Unwired the left pair. -> Wall button doesn't seem to trigger anything.

I concluded terminals 1 and 2 are for wall button (3 - and4 are for something called safe-T, which I'm yet to figure out).

Z-Wave node kept failing to finish the initial interview.

It got connected w/o issues at the very 1st inclusion. But I saw HASS nor Z-WaveJS didn't see the detail of the device, so I thought inclusion didn't fully go well and re-did inclusion, many times as it stopped working.
After struggle, it somehow got included (removed a node on both Z-WaveJS and on the device by factorry reset). then re-included. It still shows unverified node on Z-WaveJS.

Now, I do see up/down arrows on HASS now on the entity, and it says garage door, but clicking them won't trigger anything.
Also on Z-WaveJS I don't see the detailed device info that I usually see with other devices that had interview go well.

"Unknown manufacturer 0xXXXX 	0xXXXX 	Unknown product 0xXXXX "

[ ] Fix Z-Wave inclusion.
[ ] Verify the tilt sensor is linked to the Z-Wave module.

[ ]  Fix Z-Wave inclusion.

Log from zwavejs2mqtt (<IP_ADDRESS>b502ed, zwave-js: 9.3.0). Node ID: 53.
Interview seems to finish w/o issue?
2022-06-09 21:42:56.133 INFO ZWAVE: Node 53: interview started
2022-06-09 21:42:56.190 INFO ZWAVE: Node 53: interview stage PROTOCOLINFO completed
2022-06-09 21:42:56.191 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>191, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:42:56.354 INFO ZWAVE: Node 53: interview stage NODEINFO completed
2022-06-09 21:42:56.356 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>355, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:42:58.676 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:58.683 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:58.702 INFO MQTT: MQTT client closed
2022-06-09 21:43:01.702 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:01.707 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:01.728 INFO MQTT: MQTT client closed
2022-06-09 21:43:04.728 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:04.733 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:04.752 INFO MQTT: MQTT client closed
2022-06-09 21:43:07.753 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:07.758 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:07.787 INFO MQTT: MQTT client closed
2022-06-09 21:43:08.120 INFO ZWAVE: Node 53: metadata updated: 102-0-targetState
2022-06-09 21:43:10.403 INFO ZWAVE: Node 53: metadata updated: 113-0-alarmType
2022-06-09 21:43:10.405 INFO ZWAVE: Node 53: metadata updated: 113-0-alarmLevel
2022-06-09 21:43:10.406 INFO ZWAVE: Node 53: interview stage COMMANDCLASSES completed
2022-06-09 21:43:10.407 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>407, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.410 INFO ZWAVE: Node 53: interview stage OVERWRITECONFIG completed
2022-06-09 21:43:10.411 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>411, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.413 INFO ZWAVE: Node 53: interview stage COMPLETE completed
2022-06-09 21:43:10.415 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>414, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.427 INFO ZWAVE: Node 53: value added 53-102-0-currentState => undefined
2022-06-09 21:43:10.428 INFO ZWAVE: Node 53: value added 53-102-0-position => undefined
2022-06-09 21:43:10.429 INFO ZWAVE: Node 53: value added 53-102-0-targetState => undefined
2022-06-09 21:43:10.430 DEBUG MQTT: Publishing to zwave/nodeID_53/102/0/targetState: { time:<PHONE_NUMBER>430, value: undefined } with options { qos: 1, retain: true }
2022-06-09 21:43:10.431 INFO ZWAVE: Node 53: value added 53-113-0-alarmType => undefined
2022-06-09 21:43:10.432 INFO ZWAVE: Node 53: value added 53-113-0-alarmLevel => undefined
2022-06-09 21:43:10.433 INFO ZWAVE: Node 53: value added 53-114-0-manufacturerId => undefined
2022-06-09 21:43:10.433 INFO ZWAVE: Node 53: value added 53-114-0-productType => undefined
2022-06-09 21:43:10.434 INFO ZWAVE: Node 53: value added 53-114-0-productId => undefined
2022-06-09 21:43:10.435 INFO ZWAVE: Node 53: value added 53-134-0-libraryType => undefined
2022-06-09 21:43:10.436 INFO ZWAVE: Node 53: value added 53-134-0-protocolVersion => undefined
2022-06-09 21:43:10.437 INFO ZWAVE: Node 53: value added 53-134-0-firmwareVersions => undefined
2022-06-09 21:43:10.439 DEBUG ZWAVE: Node 53: mapping value(s) of property 'level' (level) from CC 128 (Battery) to node property 'minBatteryLevel
2022-06-09 21:43:10.439 DEBUG ZWAVE: Node 53: mapping value(s) of property 'level' (level) from CC 128 (Battery) to node property 'batteryLevels
2022-06-09 21:43:10.440 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>440, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.442 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>442, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.445 INFO ZWAVE: Node 53 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
2022-06-09 21:43:10.456 INFO ZWAVE: Node 53: interview COMPLETED, all values are updated
2022-06-09 21:43:10.458 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>457, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.787 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:10.792 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:10.817 INFO MQTT: MQTT client closed
2022-06-09 21:43:13.817 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:13.823 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:13.857 INFO MQTT: MQTT client closed
2022-06-09 21:43:16.670 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66049: { time:<PHONE_NUMBER>669, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:43:16.671 INFO ZWAVE: Node 21: value updated: 50-0-value-66049 0 => 0
2022-06-09 21:43:16.857 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:16.863 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883

Longer log
2022-06-09 21:36:49.328 DEBUG MQTT: Publishing to zwave/nodeID_53/102/0/targetState: { time:<PHONE_NUMBER>327, value: 255 } with options { qos: 1, retain: true }
2022-06-09 21:36:49.329 INFO ZWAVE: Node 53: value updated: 102-0-targetState 255 => 255
2022-06-09 21:36:51.558 INFO MQTT: MQTT client reconnecting
2022-06-09 21:36:51.564 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:36:51.584 INFO MQTT: MQTT client closed
2022-06-09 21:36:53.105 DEBUG MQTT: Publishing to zwave/nodeID_53/102/0/targetState: { time:<PHONE_NUMBER>105, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:36:53.106 INFO ZWAVE: Node 53: value updated: 102-0-targetState 255 => 0
2022-06-09 21:36:54.585 INFO MQTT: MQTT client reconnecting
2022-06-09 21:36:54.591 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:36:54.611 INFO MQTT: MQTT client closed
2022-06-09 21:36:57.611 INFO MQTT: MQTT client reconnecting
2022-06-09 21:36:57.617 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:36:57.646 INFO MQTT: MQTT client closed
2022-06-09 21:37:00.645 INFO MQTT: MQTT client reconnecting
2022-06-09 21:37:00.651 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:37:00.681 INFO MQTT: MQTT client closed
2022-06-09 21:37:03.681 INFO MQTT: MQTT client reconnecting
2022-06-09 21:37:03.687 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:37:03.717 INFO MQTT: MQTT client closed
:

ZWaveJS2MQTT
Debug
Inclusion stopped

• ZwaveJS "Log to file" is enabled. Disable it in order to see ZwaveJS logs
2022-06-09 21:40:14.839 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:14.860 INFO MQTT: MQTT client closed
2022-06-09 21:40:17.860 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:17.869 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:17.898 INFO MQTT: MQTT client closed
2022-06-09 21:40:19.252 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66817: { time:<PHONE_NUMBER>252, value: 0.01 } with options { qos: 1, retain: true }
2022-06-09 21:40:19.254 INFO ZWAVE: Node 21: value updated: 50-0-value-66817 0 => 0.01
2022-06-09 21:40:20.898 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:20.914 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:20.931 INFO MQTT: MQTT client closed
2022-06-09 21:40:21.282 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/65537: { time:<PHONE_NUMBER>281, value: 2.236 } with options { qos: 1, retain: true }
2022-06-09 21:40:21.283 INFO ZWAVE: Node 21: value updated: 50-0-value-65537 2.236 => 2.236
2022-06-09 21:40:23.931 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:23.937 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:23.964 INFO MQTT: MQTT client closed
2022-06-09 21:40:24.451 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66817: { time:<PHONE_NUMBER>450, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:40:24.452 INFO ZWAVE: Node 21: value updated: 50-0-value-66817 0.01 => 0
2022-06-09 21:40:26.965 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:26.973 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:27.004 INFO MQTT: MQTT client closed
2022-06-09 21:40:29.188 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/66049: { time:<PHONE_NUMBER>188, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:40:29.190 INFO ZWAVE: Node 28: value updated: 50-0-value-66049 0 => 0
2022-06-09 21:40:30.003 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:30.009 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:30.036 INFO MQTT: MQTT client closed
2022-06-09 21:40:31.226 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/66561: { time:<PHONE_NUMBER>226, value: 122.38 } with options { qos: 1, retain: true }
2022-06-09 21:40:31.227 INFO ZWAVE: Node 28: value updated: 50-0-value-66561 122.77 => 122.38
2022-06-09 21:40:32.257 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/65537: { time:<PHONE_NUMBER>257, value: 0.836 } with options { qos: 1, retain: true }
2022-06-09 21:40:32.258 INFO ZWAVE: Node 28: value updated: 50-0-value-65537 0.836 => 0.836
2022-06-09 21:40:33.037 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:33.042 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:33.073 INFO MQTT: MQTT client closed
2022-06-09 21:40:36.072 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:36.076 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:36.109 INFO MQTT: MQTT client closed
2022-06-09 21:40:39.109 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:39.115 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:39.145 INFO MQTT: MQTT client closed
2022-06-09 21:40:42.145 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:42.151 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:42.172 INFO MQTT: MQTT client closed
2022-06-09 21:40:45.172 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:45.177 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:45.209 INFO MQTT: MQTT client closed
2022-06-09 21:40:45.516 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/66817: { time:<PHONE_NUMBER>516, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:40:45.517 INFO ZWAVE: Node 28: value updated: 50-0-value-66817 0 => 0
2022-06-09 21:40:48.208 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:48.213 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:48.242 INFO MQTT: MQTT client closed
2022-06-09 21:40:51.243 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:51.249 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:51.282 INFO MQTT: MQTT client closed
2022-06-09 21:40:54.282 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:54.288 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:54.320 INFO MQTT: MQTT client closed
2022-06-09 21:40:57.320 INFO MQTT: MQTT client reconnecting
2022-06-09 21:40:57.327 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:40:57.357 INFO MQTT: MQTT client closed
2022-06-09 21:41:00.357 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:00.363 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:00.394 INFO MQTT: MQTT client closed
2022-06-09 21:41:03.394 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:03.399 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:03.430 INFO MQTT: MQTT client closed
2022-06-09 21:41:06.431 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:06.439 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:06.457 INFO MQTT: MQTT client closed
2022-06-09 21:41:09.457 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:09.463 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:09.493 INFO MQTT: MQTT client closed
2022-06-09 21:41:12.494 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:12.500 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:12.531 INFO MQTT: MQTT client closed
2022-06-09 21:41:14.320 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66049: { time:<PHONE_NUMBER>320, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:14.321 INFO ZWAVE: Node 21: value updated: 50-0-value-66049 0 => 0
2022-06-09 21:41:15.326 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66561: { time:<PHONE_NUMBER>325, value: 120.84 } with options { qos: 1, retain: true }
2022-06-09 21:41:15.327 INFO ZWAVE: Node 21: value updated: 50-0-value-66561 120.86 => 120.84
2022-06-09 21:41:15.531 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:15.537 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:15.563 INFO MQTT: MQTT client closed
2022-06-09 21:41:18.536 INFO ZWAVE: Node 48: metadata updated: 49-0-Illuminance
2022-06-09 21:41:18.540 DEBUG MQTT: Publishing to zwave/nodeID_48/49/0/Illuminance: { time:<PHONE_NUMBER>540, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:18.542 INFO ZWAVE: Node 48: value updated: 49-0-Illuminance 0 => 0
2022-06-09 21:41:18.562 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:18.566 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:18.600 INFO MQTT: MQTT client closed
2022-06-09 21:41:21.600 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:21.606 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:21.636 INFO MQTT: MQTT client closed
2022-06-09 21:41:22.070 INFO ZWAVE: Node 46: metadata updated: 49-0-Illuminance
2022-06-09 21:41:22.074 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Illuminance: { time:<PHONE_NUMBER>073, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:22.075 INFO ZWAVE: Node 46: value updated: 49-0-Illuminance 0 => 0
2022-06-09 21:41:22.463 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/65537: { time:<PHONE_NUMBER>462, value: 2.236 } with options { qos: 1, retain: true }
2022-06-09 21:41:22.464 INFO ZWAVE: Node 21: value updated: 50-0-value-65537 2.236 => 2.236
2022-06-09 21:41:23.868 INFO ZWAVE: Node 46: metadata updated: 49-0-Illuminance
2022-06-09 21:41:23.871 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Illuminance: { time:<PHONE_NUMBER>871, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:23.873 INFO ZWAVE: Node 46: value updated: 49-0-Illuminance 0 => 0
2022-06-09 21:41:24.013 INFO ZWAVE: Node 46: metadata updated: 49-0-Illuminance
2022-06-09 21:41:24.016 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Illuminance: { time:<PHONE_NUMBER>016, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:24.017 INFO ZWAVE: Node 46: value updated: 49-0-Illuminance 0 => 0
2022-06-09 21:41:24.245 INFO ZWAVE: Node 46: metadata updated: 49-0-Illuminance
2022-06-09 21:41:24.249 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Illuminance: { time:<PHONE_NUMBER>249, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:24.251 INFO ZWAVE: Node 46: value updated: 49-0-Illuminance 0 => 0
2022-06-09 21:41:24.351 INFO ZWAVE: Node 46: metadata updated: 49-0-Illuminance
2022-06-09 21:41:24.354 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Illuminance: { time:<PHONE_NUMBER>353, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:24.355 INFO ZWAVE: Node 46: value updated: 49-0-Illuminance 0 => 0
2022-06-09 21:41:24.459 INFO ZWAVE: Node 46: metadata updated: 49-0-Illuminance
2022-06-09 21:41:24.463 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Illuminance: { time:<PHONE_NUMBER>463, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:24.464 INFO ZWAVE: Node 46: value updated: 49-0-Illuminance 0 => 0
2022-06-09 21:41:24.636 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:24.642 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:24.662 INFO MQTT: MQTT client closed
2022-06-09 21:41:25.522 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66817: { time:<PHONE_NUMBER>521, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:25.523 INFO ZWAVE: Node 21: value updated: 50-0-value-66817 0 => 0
2022-06-09 21:41:27.662 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:27.668 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:27.689 INFO MQTT: MQTT client closed
2022-06-09 21:41:28.232 INFO ZWAVE: Node 46: metadata updated: 49-0-Air temperature
2022-06-09 21:41:28.237 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Air_temperature: { time:<PHONE_NUMBER>236, value: 32.8 } with options { qos: 1, retain: true }
2022-06-09 21:41:28.238 INFO ZWAVE: Node 46: value updated: 49-0-Air temperature 32.8 => 32.8
2022-06-09 21:41:30.165 INFO ZWAVE: Node 46: metadata updated: 49-0-Air temperature
2022-06-09 21:41:30.173 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Air_temperature: { time:<PHONE_NUMBER>172, value: 32.8 } with options { qos: 1, retain: true }
2022-06-09 21:41:30.174 INFO ZWAVE: Node 46: value updated: 49-0-Air temperature 32.8 => 32.8
2022-06-09 21:41:30.354 INFO ZWAVE: Node 46: metadata updated: 49-0-Air temperature
2022-06-09 21:41:30.357 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Air_temperature: { time:<PHONE_NUMBER>357, value: 32.8 } with options { qos: 1, retain: true }
2022-06-09 21:41:30.359 INFO ZWAVE: Node 46: value updated: 49-0-Air temperature 32.8 => 32.8
2022-06-09 21:41:30.665 INFO ZWAVE: Node 46: metadata updated: 49-0-Air temperature
2022-06-09 21:41:30.669 DEBUG MQTT: Publishing to zwave/nodeID_46/49/0/Air_temperature: { time:<PHONE_NUMBER>668, value: 32.8 } with options { qos: 1, retain: true }
2022-06-09 21:41:30.670 INFO ZWAVE: Node 46: value updated: 49-0-Air temperature 32.8 => 32.8
2022-06-09 21:41:30.689 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:30.693 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:30.720 INFO MQTT: MQTT client closed
2022-06-09 21:41:30.839 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/66049: { time:<PHONE_NUMBER>838, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:30.840 INFO ZWAVE: Node 28: value updated: 50-0-value-66049 0 => 0
2022-06-09 21:41:32.473 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/66561: { time:<PHONE_NUMBER>473, value: 122.34 } with options { qos: 1, retain: true }
2022-06-09 21:41:32.475 INFO ZWAVE: Node 28: value updated: 50-0-value-66561 122.38 => 122.34
2022-06-09 21:41:33.505 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/65537: { time:<PHONE_NUMBER>505, value: 0.836 } with options { qos: 1, retain: true }
2022-06-09 21:41:33.507 INFO ZWAVE: Node 28: value updated: 50-0-value-65537 0.836 => 0.836
2022-06-09 21:41:33.720 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:33.727 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:33.753 INFO MQTT: MQTT client closed
2022-06-09 21:41:36.753 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:36.759 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:36.791 INFO MQTT: MQTT client closed
2022-06-09 21:41:39.791 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:39.797 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:39.828 INFO MQTT: MQTT client closed
2022-06-09 21:41:42.829 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:42.838 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:42.856 INFO MQTT: MQTT client closed
2022-06-09 21:41:45.857 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:45.862 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:45.883 INFO MQTT: MQTT client closed
2022-06-09 21:41:46.763 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/66817: { time:<PHONE_NUMBER>762, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:41:46.765 INFO ZWAVE: Node 28: value updated: 50-0-value-66817 0 => 0
2022-06-09 21:41:48.883 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:48.890 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:48.914 INFO MQTT: MQTT client closed
2022-06-09 21:41:51.914 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:51.918 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:51.952 INFO MQTT: MQTT client closed
2022-06-09 21:41:54.953 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:54.958 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:54.988 INFO MQTT: MQTT client closed
2022-06-09 21:41:57.989 INFO MQTT: MQTT client reconnecting
2022-06-09 21:41:57.999 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:41:58.029 INFO MQTT: MQTT client closed
2022-06-09 21:42:01.030 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:01.035 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:01.066 INFO MQTT: MQTT client closed
2022-06-09 21:42:04.066 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:04.072 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:04.104 INFO MQTT: MQTT client closed
2022-06-09 21:42:07.104 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:07.109 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:07.140 INFO MQTT: MQTT client closed
2022-06-09 21:42:10.141 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:10.148 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:10.178 INFO MQTT: MQTT client closed
2022-06-09 21:42:13.178 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:13.184 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:13.215 INFO MQTT: MQTT client closed
2022-06-09 21:42:15.491 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66049: { time:<PHONE_NUMBER>490, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:42:15.492 INFO ZWAVE: Node 21: value updated: 50-0-value-66049 0 => 0
2022-06-09 21:42:16.214 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:16.220 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:16.247 INFO MQTT: MQTT client closed
2022-06-09 21:42:16.508 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66561: { time:<PHONE_NUMBER>508, value: 121.22 } with options { qos: 1, retain: true }
2022-06-09 21:42:16.509 INFO ZWAVE: Node 21: value updated: 50-0-value-66561 120.84 => 121.22
2022-06-09 21:42:19.248 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:19.253 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:19.283 INFO MQTT: MQTT client closed
2022-06-09 21:42:21.685 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66817: { time:<PHONE_NUMBER>684, value: 0.01 } with options { qos: 1, retain: true }
2022-06-09 21:42:21.686 INFO ZWAVE: Node 21: value updated: 50-0-value-66817 0 => 0.01
2022-06-09 21:42:22.283 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:22.289 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:22.326 INFO MQTT: MQTT client closed
2022-06-09 21:42:23.645 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/65537: { time:<PHONE_NUMBER>644, value: 2.236 } with options { qos: 1, retain: true }
2022-06-09 21:42:23.646 INFO ZWAVE: Node 21: value updated: 50-0-value-65537 2.236 => 2.236
2022-06-09 21:42:24.887 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66817: { time:<PHONE_NUMBER>887, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:42:24.889 INFO ZWAVE: Node 21: value updated: 50-0-value-66817 0.01 => 0
2022-06-09 21:42:25.325 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:25.331 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:25.362 INFO MQTT: MQTT client closed
2022-06-09 21:42:28.362 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:28.369 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:28.399 INFO MQTT: MQTT client closed
2022-06-09 21:42:31.399 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:31.405 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:31.435 INFO MQTT: MQTT client closed
2022-06-09 21:42:31.677 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/66049: { time:<PHONE_NUMBER>676, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:42:31.678 INFO ZWAVE: Node 28: value updated: 50-0-value-66049 0 => 0
2022-06-09 21:42:33.716 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/66561: { time:<PHONE_NUMBER>716, value: 122.93 } with options { qos: 1, retain: true }
2022-06-09 21:42:33.718 INFO ZWAVE: Node 28: value updated: 50-0-value-66561 122.34 => 122.93
2022-06-09 21:42:34.436 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:34.447 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:34.465 INFO MQTT: MQTT client closed
2022-06-09 21:42:34.752 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/65537: { time:<PHONE_NUMBER>751, value: 0.836 } with options { qos: 1, retain: true }
2022-06-09 21:42:34.753 INFO ZWAVE: Node 28: value updated: 50-0-value-65537 0.836 => 0.836
2022-06-09 21:42:37.465 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:37.471 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:37.498 INFO MQTT: MQTT client closed
2022-06-09 21:42:40.498 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:40.509 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:40.528 INFO MQTT: MQTT client closed
2022-06-09 21:42:43.528 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:43.533 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:43.553 INFO MQTT: MQTT client closed
2022-06-09 21:42:46.554 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:46.559 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:46.579 INFO MQTT: MQTT client closed
2022-06-09 21:42:48.008 DEBUG MQTT: Publishing to zwave/nodeID_28/50/0/value/66817: { time:<PHONE_NUMBER>007, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:42:48.010 INFO ZWAVE: Node 28: value updated: 50-0-value-66817 0 => 0
2022-06-09 21:42:49.243 INFO ZWAVE: Node 45: metadata updated: 49-0-Illuminance
2022-06-09 21:42:49.247 DEBUG MQTT: Publishing to zwave/nodeID_45/49/0/Illuminance: { time:<PHONE_NUMBER>247, value: 1 } with options { qos: 1, retain: true }
2022-06-09 21:42:49.248 INFO ZWAVE: Node 45: value updated: 49-0-Illuminance 5 => 1
2022-06-09 21:42:49.578 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:49.583 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:49.603 INFO MQTT: MQTT client closed
2022-06-09 21:42:52.604 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:52.609 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:52.640 INFO MQTT: MQTT client closed
2022-06-09 21:42:55.640 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:55.645 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:55.675 INFO MQTT: MQTT client closed
2022-06-09 21:42:56.133 INFO ZWAVE: Node 53: interview started
2022-06-09 21:42:56.190 INFO ZWAVE: Node 53: interview stage PROTOCOLINFO completed
2022-06-09 21:42:56.191 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>191, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:42:56.354 INFO ZWAVE: Node 53: interview stage NODEINFO completed
2022-06-09 21:42:56.356 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>355, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:42:58.676 INFO MQTT: MQTT client reconnecting
2022-06-09 21:42:58.683 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:42:58.702 INFO MQTT: MQTT client closed
2022-06-09 21:43:01.702 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:01.707 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:01.728 INFO MQTT: MQTT client closed
2022-06-09 21:43:04.728 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:04.733 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:04.752 INFO MQTT: MQTT client closed
2022-06-09 21:43:07.753 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:07.758 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:07.787 INFO MQTT: MQTT client closed
2022-06-09 21:43:08.120 INFO ZWAVE: Node 53: metadata updated: 102-0-targetState
2022-06-09 21:43:10.403 INFO ZWAVE: Node 53: metadata updated: 113-0-alarmType
2022-06-09 21:43:10.405 INFO ZWAVE: Node 53: metadata updated: 113-0-alarmLevel
2022-06-09 21:43:10.406 INFO ZWAVE: Node 53: interview stage COMMANDCLASSES completed
2022-06-09 21:43:10.407 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>407, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.410 INFO ZWAVE: Node 53: interview stage OVERWRITECONFIG completed
2022-06-09 21:43:10.411 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>411, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.413 INFO ZWAVE: Node 53: interview stage COMPLETE completed
2022-06-09 21:43:10.415 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>414, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.427 INFO ZWAVE: Node 53: value added 53-102-0-currentState => undefined
2022-06-09 21:43:10.428 INFO ZWAVE: Node 53: value added 53-102-0-position => undefined
2022-06-09 21:43:10.429 INFO ZWAVE: Node 53: value added 53-102-0-targetState => undefined
2022-06-09 21:43:10.430 DEBUG MQTT: Publishing to zwave/nodeID_53/102/0/targetState: { time:<PHONE_NUMBER>430, value: undefined } with options { qos: 1, retain: true }
2022-06-09 21:43:10.431 INFO ZWAVE: Node 53: value added 53-113-0-alarmType => undefined
2022-06-09 21:43:10.432 INFO ZWAVE: Node 53: value added 53-113-0-alarmLevel => undefined
2022-06-09 21:43:10.433 INFO ZWAVE: Node 53: value added 53-114-0-manufacturerId => undefined
2022-06-09 21:43:10.433 INFO ZWAVE: Node 53: value added 53-114-0-productType => undefined
2022-06-09 21:43:10.434 INFO ZWAVE: Node 53: value added 53-114-0-productId => undefined
2022-06-09 21:43:10.435 INFO ZWAVE: Node 53: value added 53-134-0-libraryType => undefined
2022-06-09 21:43:10.436 INFO ZWAVE: Node 53: value added 53-134-0-protocolVersion => undefined
2022-06-09 21:43:10.437 INFO ZWAVE: Node 53: value added 53-134-0-firmwareVersions => undefined
2022-06-09 21:43:10.439 DEBUG ZWAVE: Node 53: mapping value(s) of property 'level' (level) from CC 128 (Battery) to node property 'minBatteryLevel
2022-06-09 21:43:10.439 DEBUG ZWAVE: Node 53: mapping value(s) of property 'level' (level) from CC 128 (Battery) to node property 'batteryLevels
2022-06-09 21:43:10.440 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>440, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.442 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>442, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.445 INFO ZWAVE: Node 53 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
2022-06-09 21:43:10.456 INFO ZWAVE: Node 53: interview COMPLETED, all values are updated
2022-06-09 21:43:10.458 DEBUG MQTT: Publishing to zwave/nodeID_53/status: { time:<PHONE_NUMBER>457, value: true, status: 'Alive', nodeId: 53 } with options { qos: 1, retain: true }
2022-06-09 21:43:10.787 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:10.792 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:10.817 INFO MQTT: MQTT client closed
2022-06-09 21:43:13.817 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:13.823 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
2022-06-09 21:43:13.857 INFO MQTT: MQTT client closed
2022-06-09 21:43:16.670 DEBUG MQTT: Publishing to zwave/nodeID_21/50/0/value/66049: { time:<PHONE_NUMBER>669, value: 0 } with options { qos: 1, retain: true }
2022-06-09 21:43:16.671 INFO ZWAVE: Node 21: value updated: 50-0-value-66049 0 => 0
2022-06-09 21:43:16.857 INFO MQTT: MQTT client reconnecting
2022-06-09 21:43:16.863 ERROR MQTT: Mqtt client error connect ECONNREFUSED <IP_ADDRESS>:1883
Error: connect ECONNREFUSED <IP_ADDRESS>:1883
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)

Requested an assistant in https://github.com/zwave-js/node-zwave-js/discussions/4705

Hey, the provided log doesn't help diagnose this. I need to see a driver log of an inclusion & interview attempt, loglevel debug or silly.
This is going to be long, so please attach it as a file.

Thanks to external assistances, I managed to resolve this. I report to each community about the detail of what seems to end up resolving.

Wiring to Genie garage controller diy.stackexchange.com#250763.
Z-Wave inclusion: https://github.com/zwave-js/node-zwave-js/discussions/4705

[ ] Verify the tilt sensor is linked to the Z-Wave module.

Not sure how it happeend, but this seems already done as I can see HASS node knows the garage door is closed when it physically is.


Setup router api

Allowing the user to create a router.
We explored ideas around more fine grained control instead of providing router functionality but I've reconsidered and think that's better to grow over time alongside providing routers.  We can deprecate the routers at a later date if we want to replace them with more fine grained methods.

I think we can do better with the name of serveDirectory but I couldn't think of anything better while coding it.

@natcarey changes make sense to me, would you mind updating the changelog in this PR?


[Linux][Docker] Unable to write log file to C:\ Windows

Hi,
I am using a Linux Docker container on a windows machine (my local) to test Nlog output to a C:/ Directory. However, I am unable to get the file to log to the chosen file path. It seems to create the file path below inside the bin\netcoreapp2.2 file path? It's like it is restricted to only that folder.
My nlog.config file:
<?xml version="1.0" encoding="utf-8" ?>
<nlog   xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <extensions>
    <add assembly="NLog.Web.AspNetCore" />
  </extensions>
  <targets>
    <target
            name="logfile"
            xsi:type="File"
            fileName="C:/ProjectLogs/Logging/Error-${shortdate}.log"/>
  </targets>
  <rules>
    <logger name="*" minlevel="Error" writeTo="logfile" />
  </rules>
</nlog>

The version package I am using:
 <PackageReference Include="NLog.Web.AspNetCore" Version="4.8.0" />
Maybe I am completely misunderstanding Docker/Container for Linux under a windows machine - but it seems to work fine with Windows Docker Container when setup - It logs accordingly to my chosen C:/ProjectLogs/Logging/ path.
What am I doing wrong?

Please check the internal log, it could give you insights in what's going on.

Please post the full internal log (trace level)

@jacklekk Sounds strange that a Linux Docker Image should suddenly recognize (or have access) to a path like C:/ProjectLogs (C:/ is Windows style and not Linux Style)
Would think that one would mount a local-path when running the docker image. And it would then become the root-path for the docker image. The docker image will only have access to folders below the root-path (unless mounting an external network drives).
But maybe better to ask on StackOverflow. Maybe someone there has more experience with running Linux Docker Images on Windows.

Closing this due to inactivity. Please let us know if this still an issue and please provide the requested info -
thanks!


Author initial not displaying correctly in bibxml entry for draft-vcelak-nsec5

Describe the issue
https://datatracker.ietf.org/doc/bibxml3/draft-vcelak-nsec5.xml:
 should be

Issue appears to come from "David C Lawrence" in the Authors' Addresses section.  Maybe the lack of a period after "C" results in an empty "initials" field?  It seems that if any initials are provided, the "initials" field should be populated appropriately.
The first-page header shows "D. Lawrence", so the bibxml entry should match.
Please see https://datatracker.ietf.org/doc/html/draft-vcelak-nsec5-08.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

Although this was reported for a datatracker bibxml entry, the same problem appears in bib.ietf.org. Please see https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.vcelak-nsec5.xml. Perhaps this is an issue similar to what was reported in https://github.com/ietf-tools/bibxml-service/issues/335 in which the use of unconventional punctuation (or lack of punctuation) causes errors in the capturing of the author initials.


Perhaps we can store the EC2 Points in compressed form (x coordinate plus sign) instead of x/y coordinates. This eliminates a whole bunch of cryptographic security vulnerabilities by construction

Perhaps we can store the EC2 Points in compressed form (x coordinate plus sign) instead of x/y coordinates. This eliminates a whole bunch of cryptographic security vulnerabilities by construction
Originally posted by @arianvp in https://github.com/arianvp/haskell-fido2/pull/21#issuecomment-646607028
Webauthn and COSE are footguns in this regard; and we should convert to compressed form as close to the boundary as possible. Check if cryptonite supports this.

I'm closing this.    Apparently compressed points are avoided literally everywhere in literature due to ip issues and nobody wants to talk about them.


Hang on opening macmap.vim

I saved the macmap.vim file linked on the /Wiki/Tips age to my disk. When I attempt to open it with goneovim, it hangs. If needed, I can provide the details captured after "Force Quit" in the "Send to Apple" option (2.2 MB). The file opens OK with nvim and with MacVim.

@proofer
Ummm, I can't reproduce it in my environment, but maybe some setting of yours is conflicting with macmap.vim and causing goneovim to hang.
Does the following command work correctly?
/Applications/goneovim.app/Contents/MacOS/goneovim -u NONE --cmd "source /path/to/macmap.vim"

@akiyosi
It opens to an empty buffer.
Here is the command I used:
/Applications/goneovim.app/Contents/MacOS/goneovim -u NONE --cmd "source /Users/proofer/.config/goneovim/macmap.vim"

But now whether I open macvim.app with Finder or with netrw browser it opens fine, either 0.6.3 or nightly-1-gccee4b8. Initial report was opening file with Finder, 0.6.3.  I think the only change since then is setting [Sidebar] visible=true.


Basket. Sign page. Wrong data for different operations

Description
When user select a few operations to sign with different amount, sign screen shows data only for first one
Steps to Reproduce

Add transfer on 0.01 WND to account_A to basket
Add transfer on 0.1 WND to account_B to basket
Go to basket
Select all operations
Proceed to signing

Expected Behavior
Each operation has its data on sign page
Actual Behavior
Are shown data of first operation for each operation

Example
https://github.com/novasamatech/nova-spektr/assets/40560660/1d2a990c-8174-460d-a59e-85a3327ac06f

Environment
https://github.com/novasamatech/nova-spektr/tree/feat/basket-transactions-sign

Status verification: ✅


feat: update usage cards for all services

fixes FTD-2079

📝 Changed routes:

…oard/settings/api-keys

(view full size)

Commit 902106e5c755811ccd8d41c1b00fd345cde296c7 (https://thirdweb-2ngxcl71t.thirdweb-preview.com).


Warlock: Combining the 10m t8 set pieces is not applying the set bonuses

I have Valorous Deathbringer hood and Conqueror's Deathbringer Robe Equipped. Mousing over one of the items shows that the set bonus is not active. It may be possible that it is just displayed incorrectly, but the sims seem to reflect that the set bonus is not applied. Switching to Valorous Deathbringer Robe did not apply the set bonus either. Only after have both 25m pieces equipped did the set bonus apply.

This is a visual bug with wowhead tooltips, there's nothing we can do about it, see also #2431.


Track notes for TS migration

This issue tracks notes we should come back to during the migration

Onyx.update
When using Onyx.update, the argument might need to be typed as any
Relevant discussion: https://github.com/Expensify/react-native-onyx/pull/267#discussion_r1276654750

This is just a tracking note. I'm just doing here so that I can be reminded about these notes during the migration

This is just a note, melvin

closing this


fix: minor issues

fix: remove non-printable character
fix: set GOBIN even if GOPATH was set but not GOBIN
fix: proper syntax for ENVTEST_ASSETS_DIR

@metacosm can you sign the commit?
In your local branch, run: git rebase HEAD~3 --signoff
Force push your changes to overwrite the branch: git push --force-with-lease origin updates


javascript and variables / function

Hello, I'm new here and I'm sorry if the question is too basic.
I use the monaco editor with the angular and created a component for it and everything works 100%.
I am a doubt and searched several places and did not find.
I will explain my scenario.
I retrieve a json in the database that is in string format and some possibilities can get variable reference function.
My doubt how I can inject and make available in the editor the scope (with variables and function), so I can reference in my json within the editor.
because the monaco component is a modal, so when i click edit it opens this modal and i pass the json code etc ..
I would need to inject the local variables, too, for reference inside.
Briefly, imagine the following.
const testVar = () => 3;
My javascript/json:
[
   {
      "key":testVar
   }
]

In the above scenario it works, because everything is in the same scope, now if I click on edit I am taking only the json and with that will return err, because there in the scope of the editor does not exist testVar
if anyone can help :)

Hello!
If you use javascript language you can give the editor a typescript definition lib
monaco.languages.typescript.javascriptDefaults.addExtraLib("declare const testVar : () => 3", "yourlibname.d.ts")

The variable will be accepted by the editor now :sunglasses:
Hope it helped you!

Thanks


fix(modal): Better modal handling

:tada: This PR is included in version 1.4.5 :tada:
Your semantic-release bot :package::rocket:


[models] Add adapter model registration funcs.

Description
This PR adds

Adapter model registration functions.
Removes/replaces traces of OAM with new models.

Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

// @gyohuangxin @leecalcote


Remove Flowdock notifications

I don't believe we're still using Flowdock for anything, are we?
@kevinhughes27 @maartenvg

👍

🚀


French translation strings

Why this is still open?

And why it was assigned to me?

@lyssdod -> #28 I tagged you on a PR if you wanted to look over


Setting 'DJANGOCMS_TEXT_EDITOR' or 'TEXT_EDITOR' ?

Describe the bug
Following README documentation i was using DJANGOCMS_TEXT_EDITOR to enable the ckeditor4 but the editor 'TipTap' was still used.
Finally searching from code i found that the really used setting name was TEXT_EDITOR:
https://github.com/django-cms/djangocms-text/blob/df9a540a2bd1b8e79283662b4d9f2313267fca19/djangocms_text/editors.py#L438
Environment
Describe your environment:

Plateform: Any
Python version: >=3.10
Django version: >=5.0
djangocms-text version: 0.3.3

Expected behavior
The documented setting name should be used in code. I imagine this is a typo error and DJANGOCMS_TEXT_EDITOR is the accurate setting name.

Well spotted! Thanks for pointing this out. I just fixed the README file.


Create images with randomized size?

Hi @mdbloice,
thanks for the Augmentor code! I am creating a pipeline, that has to create eventually images with randomized size, for example:
I have a single ground truth image of size 100pixel x 100pixel and after running the pipeline I would like to have images scaled with a RANDOM SCALE in the interval [1,2], so that output images have sizes 173x173, 189x189, 114x114, 133x133 etc. The closest to this functionallity I have found was crop_random, when the argument randomise_percentage_area is set to "True". But in this case percentage_area is an UPPER bound, while I need it to be a LOWER bound. Of course, for creating N output images I could run N times the pipeline, every time changing the scale factor, but I hope there is a handier alternative.
Therefore my question:
1.) is there a function in Augmentor that allows for output images with randomized size/scaling?
2.) alternatively, can percentage_area be set to be the LOWER limit, instead of the upper, when randomise_percentage_area=True?
Thanks for an answer!

Hi @Nestak2, thanks for making the issue and sorry for the delay in replying, I have not had much time for Augmentor recently.
Yeah, that would be a good feature to have. Right now I cannot think of a way you might be able to do what you are asking with the current operations as they exist now...
However, I can add this functionality in the next version, I think it would be useful. Until then though, I can't really help out any more.
If I can think of a way to do what you are asking as is, I'll post it here.

Thanks for replying! I actually managed to make my own pipeline out of opencv functions. Though it might be useful for others in the future to have the functionality in Augmentor.

Yeah OK good that you sorted it, thanks for opening the issue I will add it as a feature when I get the chance.

Hi, I would like also to have functionality to set lower and upper bound like in torchvision as torchvision.transforms.RandomResizedCrop(size, scale=(0.08, 1.0), ratio=(0.75, 1.3333333333333333), interpolation=2). Thanks for the great library anyway.


TexLive 2020 Problems

Hey,
I'm using moeptikz heavily for all my lectures and scientific documents which contains network-related elements. First of all, thanks for that!
However, since the last update from TexLive 2020, the images look very strage. Example of a server node is attached. Any ideas how to fix this?

If it helps, this is only a problem with xelatex and not pdflatex or lualatex.


Make --*-requires options to print package dependencies to stdout

How do people feel about adding —*-requires so that we can extract the kwargs of a setup.py and print to stdout:
e.g.
prompt# python setup.py —install-requires
click >= 5.0
aiohttp
jinja2
prompt# python setup.py —extras-requires NAME
...
Thoughts?
Side note: if I add a version into requires=['click >= 6.9'] I get a 'ValueError: expected parenthesized list: '>= 6.9'
Full Trace: https://pastebin.com/icT8CUaU

I would look to fix this too

Going through the code I see that this would need disutils diffs, or quite a decent change to setuptools. Thus why we are here I guess.

I don't think this is worth the time. Sorry for the noise.

Thanks for the interest and the follow-up. I note you can list the dependencies for an installed package. See jaraco.packaging for a routine that does just that.
Would you add one more detail - what is the use-case that's led you to wanting this feature?

I'm writing a system to automate building pypi pacakges in our environment (with our specific GCC etc.) and was looking to make it all asyncio, as pip is pretty slow (even with a local mirror). It was a nice to have, so I went back to wrapping pip, as reading how it deals with versioning + requirements etc. was very interesting and error prone to try and replicate.
I look forward to pipfile and warehouse making this more standards enforcing.


Error after upgrading to 0.8.0

Version of the custom_component

0.8.0
Describe the bug
The following error showing multiple times in HA logs after upgrading to 0.8.0.
Debug log

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/config/custom_components/zoom/binary_sensor.py", line 288, in async_event_received
    token = status.pop("token")
KeyError: 'token'

Only 1 of 5 binary sensors work. Any way to downgrade for now? Thanks.

Hi, can you enable debug logs for the integration? You should get a debug log message right before that exception that will tell you the payload that Zoom is sending to HA. Can you share that here? You may want to remove any personal details before posting it. Thanks!


Update dead links to latest version of Kubernetes docs

Thanks for updating this! You will also need to re-generate to update the API docs with this. Just run make generate-in-docker and commit the changes.

Unfortunately running make generate-in-docker seems not to be regenerating the docs.
I can see in the Makefile:81 generate: ... Documentation/*, however in the log of the build I can't find any reference to it (only to compatibility.md)

@The-smooth-operator Thanks for the contribution.
https://github.com/coreos/prometheus-operator/pull/1625 should fix your issue. Once it is merged, could you rebase and run make generate again? If that is not fixing it rm $GOPATH/bin/po-docgen && make generate should do.


NSJSON.DataWithJSONObjectTests fails on reference platform

NSJSONSerializationTests.m:56: Failure
Value of: actualResult
Actual: {"key":"value","nullkey":null,"array":[{"subnullkey":null}]}
Expected: expectedResult
Which is: {"key":"value","array":[{"subnullkey":null}],"nullkey":null}
FAILED: expected ({"key":"value","array":[{"subnullkey":null}],"nullkey":null}) != actual ({"key":"value","nullkey":null,"array":[{"subnullkey":null}]})
[  FAILED  ] NSJSON.DataWithJSONObjectTests (0 ms)
The windows JSON serializer does not serialize the json in the same order as reference platform.  This in itself is not an issue, just need to fix the test to not be so strict.

@aballway since you are looking for things to do...


Functions that read references return JSON on error

This is inconsistent with the rest of the functions; an ordinary record should be returned, with message and documentation_url fields populated from the response.

I'm reconsidering this. GitHub never returns HTTP code 200 if an error occurred, and 404s get converted into {err, JsonPayload} by http_proxy. I can't come up with any argument in favour of adding message and documentation_url fileds to all the records in the library.
Think I'll sleep on it and if I still can't, I'll just remove those fields from existing records and be done with it.

I can't come up with any argument in favour of adding message and documentation_url fileds to all the records in the library.

R-right, but we can introduce a new record instead, with just these two fields!


Siad node priority suggest.

Sia can have a parameter that supports the preferred node json file?
Like go-ethereum's static-nodes.json file.
This makes it easy for sia's fans in different countries to run a fast sync network.

siac gateway connect IP:PORT
force add any peer and it will be saved into DB forever(probably, since nodes db not removing any peers)

As @S-anasol suggested, you can use siac to manually connect to a set of nodes. This is a bit awkward to do programmatically (would require a bash script or equivalent), but once you are connected, you should stay connected.
Still, I think a preferred node list is a good idea. We don't have much development bandwidth to spare on it right now, but it would be a good project for a contributor.

Thanks! @S-anasol @lukechampine


Application starts up as WebMVC application

I'm trying to write 2 apps, one as a standard Spring Boot App and a Spring Cloud Function. I'm trying to avoid duplicate code, so I created a shared jar that contains some configuration (that is also used by other apps).
I'm having trouble with running the Spring Cloud Function app. I can deploy it in a container with the AWS adapter (I understand that it will run another app in the container), but I cannot run it locally as Cloud Function App, it starts up as a regular Spring Boot app. I think it has to do with some AutoConfiguration, but I'm not certain. I also tried to run some tests, but they don't work either.
I'm using Spring Boot 3.0.5 and Cloud Function 4.0.2.
Here is the app:
@SpringBootApplication
@Log4j2
@Import({PostgresDatasourceConfiguration.class})
public class FunctionsApplication {

    public static void main(String[] args) {
        SpringApplication.run(FunctionsApplication.class, args);
    }

    @Bean
    public Function<String, String> ping() {
        return value -> {
            return value == null ? "pong" : value;
        };
    }

}

I have only some configuration entries for postgres in my properties field.
Here are the dependencies in the gradle build file:
dependencies {
    implementation "org.springframework.cloud:spring-cloud-function-web:${springCloudFunctionVersion}"
    implementation 'org.springframework.boot:spring-boot-starter-web'
    implementation 'org.springframework.boot:spring-boot-starter-data-jpa'
    implementation 'org.springframework.cloud:spring-cloud-function-adapter-aws:3.2.1'
    implementation "com.amazonaws:aws-lambda-java-events:${awsLambdaEventsVersion}"
    implementation "com.amazonaws:aws-lambda-java-core:${awsLambdaCoreVersion}"

    implementation project(':shared')

    compileOnly 'org.projectlombok:lombok'
    runtimeOnly 'org.postgresql:postgresql'
    annotationProcessor 'org.projectlombok:lombok'

    testImplementation 'org.junit.jupiter:junit-jupiter-engine:5.9.2'
    testImplementation 'org.springframework.boot:spring-boot-starter-test'
    testImplementation 'org.mockito:mockito-junit-jupiter:5.2.0'
}

!!!UPDATE:
The shared code has the following dependencies that cause the issue:
    implementation 'org.springframework.boot:spring-boot-starter-security'
    implementation 'org.springframework.boot:spring-boot-starter-oauth2-resource-server'

Just the presence of these imports will trigger it to not start up the Function handler.
Here is the console output when I start up:
2023-05-02 07:32:20-930 [main] INFO  o.h.e.t.j.p.i.JtaPlatformInitiator - HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2023-05-02 07:32:20-935 [main] INFO  o.s.o.j.LocalContainerEntityManagerFactoryBean - Initialized JPA EntityManagerFactory for persistence unit 'default'
2023-05-02 07:32:21-057 [main] DEBUG o.s.b.a.AutoConfigurationPackages - @EnableAutoConfiguration was declared on a class in the package 'net.functional.test'. Automatic @Repository and @Entity scanning is enabled.
2023-05-02 07:32:21-261 [main] WARN  o.s.b.a.o.j.JpaBaseConfiguration$JpaWebConfiguration - spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
2023-05-02 07:32:21-393 [main] DEBUG o.s.w.s.m.m.a.RequestMappingHandlerAdapter - ControllerAdvice beans: 0 @ModelAttribute, 0 @InitBinder, 1 RequestBodyAdvice, 1 ResponseBodyAdvice
2023-05-02 07:32:21-430 [main] DEBUG o.s.w.s.m.m.a.RequestMappingHandlerMapping - 2 mappings in 'requestMappingHandlerMapping'
2023-05-02 07:32:21-442 [main] DEBUG o.s.w.s.h.SimpleUrlHandlerMapping - Patterns [/webjars/**, /**] in 'resourceHandlerMapping'
2023-05-02 07:32:21-447 [main] DEBUG o.s.w.s.m.m.a.ExceptionHandlerExceptionResolver - ControllerAdvice beans: 1 @ExceptionHandler, 1 ResponseBodyAdvice
2023-05-02 07:32:21-471 [main] DEBUG o.s.b.a.SpringApplicationAdminMXBeanRegistrar$SpringApplicationAdmin - Application Admin MBean registered with name 'org.springframework.boot:type=Admin,name=SpringApplication'
2023-05-02 07:32:21-560 [main] WARN  o.s.b.a.s.s.UserDetailsServiceAutoConfiguration -

Using generated security password: d455b419-5f6a-4228-9899-39cadd784b25

This generated password is for development use only. Your security configuration must be updated before running your application in production.

2023-05-02 07:32:21-648 [main] INFO  o.s.s.web.DefaultSecurityFilterChain - Will secure any request with [org.springframework.security.web.session.DisableEncodeUrlFilter@70a3b, org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@18baee88, org.springframework.security.web.context.SecurityContextHolderFilter@6e4ac3f5, org.springframework.security.web.header.HeaderWriterFilter@1ab780fd, org.springframework.security.web.csrf.CsrfFilter@642b2176, org.springframework.security.web.authentication.logout.LogoutFilter@f4b2d13, org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter@4d5d945d, org.springframework.security.web.authentication.ui.DefaultLoginPageGeneratingFilter@78ca8258, org.springframework.security.web.authentication.ui.DefaultLogoutPageGeneratingFilter@59e67a18, org.springframework.security.web.authentication.www.BasicAuthenticationFilter@4e2ad1f2, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@1798c749, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@33315925, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@37289e90, org.springframework.security.web.access.ExceptionTranslationFilter@53ce27fa, org.springframework.security.web.access.intercept.AuthorizationFilter@49314684]
2023-05-02 07:32:21-673 [main] INFO  o.s.c.f.w.mvc.FunctionHandlerMapping - FunctionCatalog: org.springframework.cloud.function.context.catalog.BeanFactoryAwareFunctionRegistry@21f27bb5
2023-05-02 07:32:21-697 [main] INFO  o.s.b.w.e.tomcat.TomcatWebServer - Tomcat started on port(s): 8080 (http) with context path ''

Here is the test I wrote:
@SpringBootTest(classes = FunctionsApplication.class,
    webEnvironment = WebEnvironment.RANDOM_PORT)
@ActiveProfiles("test")
public class WebFunctionTests {

    @Autowired
    private TestRestTemplate rest;

    @Test
    public void test() throws Exception {
        ResponseEntity<String> result = this.rest.exchange(
            RequestEntity.post(new URI("/ping")).body("{}}"), String.class);
        System.out.println(result.getBody());
    }
}

Any insight on how to get it running locally would be great.

OK ... figured it it (sometimes you have to spell it all out :-| ). The shared library I threw in common configuration classes and its dependencies are the issue, even so my code is not using any security configuration (excluded by a conditional) the added imports are doing some auto configuration that will switch the app to a regular MVC app.
If I exclude these to dependencies, everything is working fine.
    implementation 'org.springframework.boot:spring-boot-starter-security'
    implementation 'org.springframework.boot:spring-boot-starter-oauth2-resource-server'

Closing the issue.


Add MIME-Type to DesktopLexer

Thank you! Please also run tox -e mapfiles to regenerate the mapping created from these attributes, that should take care of the build failure.


Update mongochef.rb

update to 3.0.0

Thank you. Could you please squash your commits?

@vitorgalvao Squashing done too :)

Thank you for the contribution. It was merged directly as 29c030a833a210cdf45b754b78033da049fff345 to keep commit history cleaner. Your contribution is still credited to you.


UI: Volume detail page doesn't get refreshed for new snapshots

Reproduce:

Create a recurring job for backup/snapshot.
Look at the volume details page.

It won't change until refresh.

Thanks @LLParse . I think to implement the full solution would be hard for this release. Maybe there is something we can do with the new CSI snapshot design as well.
For now, let's just periodically poll the backend.

Fixed.


cannot find inference_model in  davarocr.davar_videotext.apis

cannot find inference_model in  davarocr.davar_videotext.apis，unable to run yoro/det/test.py

We just fix the path problem in the last commit 7cbd701274c0fddb412da1f50aac76629ad1429d.


Mark AVIF as Baseline low

Opening this after seeing @captainbrosset post https://mas.to/@patrickbrosset/111606297691549413.
Leaving this as draft until Edge 121 is released. The versions for the other browsers also need to be confirmed.

Related: MDN docs for AVIF being supported in Edge 121 have been added: https://github.com/mdn/content/pull/31145.
CanIUse PR also up: https://github.com/Fyrd/caniuse/pull/6924

Updated with the final release date from https://github.com/mdn/browser-compat-data/blob/4ffe27981b17180c2386bdb05f9b4a43e2573879/browsers/edge.json#L347-L352

@captainbrosset can you review/merge?


Table name validation

It seems that you are unable to use punctuation in table names, although it isn't clear what is and isn't allowed.
>>> ts = TableService()
>>> ts.create_table("foo")
True
>>> ts.create_table("routing_table")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Python27\lib\site-packages\azure\storage\tableservice.py", line 135, in create_table
    _dont_fail_on_exist(e)
  File "C:\Python27\lib\site-packages\azure\__init__.py", line 453, in _dont_fail_on_exist
    raise error
azure.WindowsAzureError: Unknown error (Bad Request)
>>> ts.create_table("routingtable")
True

It would be nice if some sort of client-side validation was done, if possible.

Issue Migrated to https://github.com/Azure/azure-storage-python/issues/20


when i try to run bash train_glow.sh i am getting error

FileNotFoundError: [Errno 2] No such file or directory: '../../config/glow/male.json'

change the directory to one of the model paths you downloaded but even after that there are multiple missing modules in requirements file

change the directory to one of the model paths you downloaded but even after that there are multiple missing modules in requirements file

can you please help me to train voice model


weave's docker pull will stop working on December 7

and hence weave setup and weave launch[-*]. Because we embed a Docker 1.3 client...
From https://blog.docker.com/2015/10/docker-hub-deprecation-1-5/

On November 19, 2015 Docker clients version 1.5 and earlier will not be able to push images to Docker Hub. They will still be able to pull images. And of course the repositories are fully accessible via newer versions of the Docker client.

On December 7, 2015, pulls via clients 1.5 and earlier will be disabled. Only version 1.6 or later will be supported.

I believe Bryan has seen some deprecation warnings already, so we should upgrade soon so that users aren't bombarded with these confusing messages (which will refer to a docker version they themselves aren't running).

As a work-around users can run weave setup --local.
Indeed I could see an argument for handling weave setup locally always, like we do weave version. It ends up pulling weaveexec locally anyway, and by the time that's done there's not much left to do.

The deprecation warning I saw was for a start api call with config that should go in create, so affects 3rd-party tools that do that.

Note that we pin the API version in the proxy to v1.15, which corresponds to 1.3. I don't think that will cause any problems, but we should probably update that too.


Semi-supervised learning algorithm

Thank you for your outstanding work! I want to know where the semi-supervised learning algorithm is embodied? Looking forward to your reply, thank you!

Hi, we apply transfer learning algorithms to leverage labeled source data to the unlabeled target data. You may consider TL as a corner case for SSL.

DANN? ok! Thank you !
------------------ 原始邮件 ------------------
发件人:                                                                                "xuyu0010/ARID_UG2_2.2"                                                                                @.>;
发送时间: 2022年2月17日(星期四) 晚上10:50
@.>;
<EMAIL_ADDRESS>主题: Re: [xuyu0010/ARID_UG2_2.2] Semi-supervised learning algorithm (Issue #2)
Hi, we apply transfer learning algorithms to leverage labeled source data to the unlabeled target data. You may consider TL as a corner case for SSL.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>


feat: S2 inclusion support

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 151 (1.32%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 30.051%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/plugins/socket.js
0
2
0.0%

src/store/mutations.js
0
6
0.0%

lib/ZwaveClient.ts
0
141
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/plugins/socket.js
1
0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
3615

Relevant Lines:
12645

💛  - Coveralls

I can't test this because of #1463. I spent two hours trying work through the changes but its a bridge too far. I can't get past the last few comments about yarn versions and RUN yarn install --production --frozen-lockfile


Generated shortcuts are invalid

This shortcut ...
programs.plasma.shortcuts = {
      "kwin"."Window Move" = "Meta+G,,Move Window";
};

... generates this line in kglobalshortcutsrc:
Window Move=Meta+G\\,\\,Move Window,,

Not only are there invalid (?) \\, but also 2 trailing ,. Upon restarting the computer, this invalid line will be reset to its default.
In contrast, generating the shortcut like this ...
programs.plasma.configFile.kglobalshortcutsrc = {
  kwin."Window Move".value = "Meta+G,,Move Window";
};

... generates a valid line, which KDE accepts:
Window Move=Meta+G,,Move Window

Am I missing something or is this a bug?

plasma-manager doesn't really support adding the description for keybindings (at least for now). Setting "kwin"."Window Move" = "Meta+G";  should work (that's what it expects). Maybe some more options for setting the descriptions will come in the future, but it isn't really the biggest priority.

Oh, I thought Meta+G,Alt+G,Move Window stood for <shortcut>,<default>,<description>.
programs.plasma.shortcuts."kwin"."Window Move" = "Meta+G" does not work for me. It sets the line in kglobalshortcutsrc to `Window Move = Meta+G'.
Upon restarting the computer all shortcuts are reset to their default :/

Oh, I didn't know that information was optional and contained e.g. the default value. Your suggestion works for me, I don't have a need for descriptions for now.
Thx for the help


add new nestjs template

Hi, am quite new at this!
basically here is the template that I would like to add
here

Hey @matcharr 👋🏽
Thanks for raising the issue. We already have a template for NestJS. So, you can propose your changes to this repository: template-nestjs 🙏🏽


[Snyk] Security upgrade react-scripts from 2.1.1 to 5.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

controller/ui/package.json
controller/ui/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

698/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 6.1
Cross-site Scripting (XSS) SNYK-JS-SERIALIZEJAVASCRIPT-6147607
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting (XSS)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


dentiparous, capiases

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[c,d]

/trunk merge


[UI] Sometimes active doc page isn't highlighted within menu panel.

Hi,
When I run sbt-microsites Doc section and when I choose some doc page from the left panel, sometimes it is not being highlighted as the active one. Please see the example below (taken from sbt-microsites microsite).
Here the Layouts menu is highlighted as the active one:

But here Build the microsite isn't:

If anyone could point me where I can fix that, I could try to handle it and submit PR.
Best regards,
Karol

Hi,
I think I know what's the root cause of that...
Please take a look here:
https://github.com/47deg/sbt-microsites/blob/master/docs/src/main/resources/microsite/data/menu.yml#L17
The title here is Build the microsite which isn't exactly the same string that is defined here (layout section - docs | Build the Microsite)
https://github.com/47deg/sbt-microsites/blob/master/docs/src/main/tut/docs/build-the-microsite.md
If there is any discrepancy then there are issues with highlighting selected doc page.
Best regards,
Karol

Hi @kczulko, the discrepancy on that specific case is the capitalization of Microsite. You can submit a PR for that setting the same value in both cases if you'd like to fix that in sbt-microsites documentation.
Also, if you want to improve this feature in general, maybe you can normalize capitalization when the comparison happens, which is made in this template:
https://github.com/47deg/sbt-microsites/blob/master/src/main/scala/microsites/layouts/DocsLayout.scala

Thanks for point it out BTW! :clap:


Debezium-mongodb - observe issue DBZ-2831, which blocks integration tests.

Issue DBZ-2831 blocks creation of integration tests for debezium-mongodb (therefore  blocks https://github.com/apache/camel-quarkus/issues/1190)

Please, assign to me. DBZ issue is fixed, I'll verify it with snapshot version.

This issue could be closed.
Version 1.4.0.Beta1 works correctly - verified on manual test from https://github.com/JiriOndrusek/debezium-reproducer-port
I'm returning to debezium-mongodb extension - https://github.com/apache/camel-quarkus/issues/1190. Hopefully there will be no other blocker.

Can this be closed, @JiriOndrusek ?

@ppalaga yes, it could be closed.


unskipping fixed tests

We have many tests that are marked skip/broken, but they are working now.
This PR unskips and cleans up some of these skipped tests.

is this ready for review?


move ner notebook to main

moved from https://github.com/openvinotoolkit/openvino_notebooks/pull/1163


Can't import macros in index.html of themes

Original: https://github.com/Keats/tera/issues/235
From a quick look the path do get rewritten correctly so it's not entirely clear what is happening

Ok found the issue, Tera only use the update paths in blocks in the rendered and use the AST ImportMacro node instead otherwise which is why it works in child pages but not the index one

@NuLL3rr0r
https://github.com/Keats/tera/pull/218/commits/b87a920ab384b64f2bc78e4eb91a67fb582ec5d6 will fix it (tried locally), I'll publish a new beta when I get some time and a few more changes in Tera.

Sorry, but it seems the issue still persists for me. I even checked out the after-dark theme and it's the same. I built the next branch with head pointing to the following commit:
commit 6db79e77e84add9879fdc6808e08477f5ec58d11
Author: Vincent Prouillet<EMAIL_ADDRESS>Date:   Fri Nov 24 17:52:24 2017 +0100

    Update to Tera 0.11 beta

The same error:
Error: Failed to render page '/home/babaei/dev/babaei-net-blog-source/babaei.net/content/blog/2016-04-29-discourse-as-a-blog-comment-service-on-freebsd-without-docker.md'
Reason: Failed to render 'after-dark/templates/page.html' (error happened in 'after-dark/templates/index.html').
Reason: Template 'post_macros.html' not found

Can you do a cargo update to make sure it's using tera beta.1? I don't know
if I updated the cargo.lock.
On 25 Nov 2017 16:34, "Mohammad S. Babaei"<EMAIL_ADDRESS>wrote:

Sorry, but it seems the issue still persists for me. I even checked out
the after-dark theme and it's the same. I built the next branch with head
pointing to the following commit:
commit 6db79e77e84add9879fdc6808e08477f5ec58d11
Author: Vincent Prouillet<EMAIL_ADDRESS>Date:   Fri Nov 24 17:52:24 2017 +0100
Update to Tera 0.11 beta

The same error:
Error: Failed to render page '/home/babaei/dev/babaei-net-blog-source/babaei.net/content/blog/2016-04-29-discourse-as-a-blog-comment-service-on-freebsd-without-docker.md'
Reason: Failed to render 'after-dark/templates/page.html' (error happened in 'after-dark/templates/index.html').
Reason: Template 'post_macros.html' not found
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Keats/gutenberg/issues/185#issuecomment-346947624,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApho6z3cwasvQ7RcLckv9Qjx7PJhXphks5s6DN8gaJpZM4QqBwX
.

That did it:
Updating registry `https://github.com/rust-lang/crates.io-index`
      Adding base64 v0.8.0
    Updating humansize v1.0.1 -> v1.0.2
    Updating plist v0.2.3 -> v0.2.4
    Updating tera v0.11.0-beta.0 -> v0.11.0-beta.1
    Updating xml-rs v0.6.1 -> v0.7.0

I rebuilt Gutenberg and it worked. Thank you!

Unrelated but if you have any opinions on https://github.com/Keats/gutenberg/pull/111 as you are writing in 2 languages!

Sure, I'll look into that and report back.


Updating install location to PATH instead of plugin directory

Updating README to use PATH as install location (instead of plugin location).

/lgtm
/approve


Extract tests files from demo project

Current coverage is 0.00%

Merging #31 into develop will not affect coverage as of 7800f88

No diff could be generated. No reports for #31 found.
Review entire Coverage Diff as of 7800f88

Powered by Codecov. Updated on successful CI builds.


Clarify documentation in Patchouli states that full sets are required for Sylvan, Wildwood armor

And/or reconsider.

Ideally I'd like to reconsider and increase the heal/amount reduced per piece of armor equipped.


Backend/case sensitivity

[ch-63334]
[ch-63463]
[ch-63821]

I've changed the unit tests, following your advices in this commit 89f22ca

Runtime: improved in 3ff4784
Logging : f7e4b87 (last version of tqdm init in d5f0241)


BDArmory.netkan version bump from 0.8.1 to 0.9.1

9.0 and 9.1 were released

Unsure if this is required or if this is suppose to happen automatically in some fashion. Apologies if the latter.

That's not the current version of the mod, that's an override for that particular version because it was deemed compatible with ksp_version 1.0.4. Updates to mods with .netkans should happen automatically. In the case of 0.9.0 and 0.9.1 we have them both indexed here and here. If you look at BDArmory's  collection of .ckan files you'll actually notice BDArmory-v0.8.3.ckan is the version of BDArmory that CKAN will try to install rather than  BDArmory-0.9.1.ckan because v0.8.3 is greater than 0.9.1. The fix is to force a v on the current and all future versions of BDArmory.
Thanks for bringing the situation to my attention.


System merge sequences while replacing selected monomers from the library in edit mode

Steps to Reproduce

Go to Macromolecules mode - Sequence mode

Load from file: System allow to change monomers on the canvase in view mode (that is not allowed).zip

Switch canvas to text-edit mode

Select some monomers

Go to Library - Peptides tab

Click on D peptide

Actual behavior
All selected monomers changed to D peptide and all sequences merged to one

Expected behavior
All selected monomers changed to D peptide and sequences remain in place
As per requirement:

If the user selects any number of monomers in text-editing mode, and clicks on the monomer card in the library, one chosen monomer form the library should replace all the selected monomer(s) on the canvas. (user selects 5 monomers -> user selects A in the library -> 5 monomers get replaced by 1 A)

Versions

Ketcher Version 2.24.0-rc.1 Build at 2024-08-06; 19:17:47
Indigo Toolkit Version 1.23.0-rc.1.0-g85f89b8f5-wasm32-wasm-clang-19.0.0
Windows 10 Pro
Chrome Version 127.0.6533.100 (Official Build) (64-bit)

Related issue - https://github.com/epam/ketcher/issues/4878

Fixed.

Ketcher Version 2.24.0-rc.2 Build at 2024-08-14; 19:00:14
Indigo Toolkit Version 1.23.0-rc.2.0-g6a2a7526a-wasm32-wasm-clang-19.0.0
Chrome Version 127.0.6533.100 (Official Build) (64-bit)
Win10


Allow users to take photo within app

Allow app to gain access to users device camera to display video and capture images that can be stored within the app.

Commit 528baef
Attempted to use navigator.mediaDevices to access camera and display video which worked great. But capturing the image into canvas  leads to a low quality image that is not ideal for capturing wildlife images especially from moving vehicles like boats.

Need to do additional research for other options - currently going to put feature on hold and stick with photo upload. Feature may be limited to mobile only app.


UnhandledPromiseRejectionWarning: ReferenceError: performance is not defined | HELP on ERROR

When I extract the template to a fresh file on the desktop, then open in Visual Code, ran Yarn.
Then I removed the Solana stuff. Then Ran node index.js
I get this error

In the error description it says to add this code to terminate the node process on unhandled promise rejection, so I did as so:

node --unhandled-restrictions=strict index.js

I watched both videos a couple times now, just reaching out to see if there's a solution.

Hi @ChitinNature, thank you for reporting this.
I guess you are using NodeJS version 14 as the performance global variable was introduced in version 16. I pushed a quick fix to the repo and I will publish a new alpha version after a few tests.
I can't guarantee we are gonna support Node 14 with our stable release since it's pretty old, but it's good to keep backward compatibility as much as possible atm.
I wish you a great day, please consider supporting us by joining the Open Devs Crew, this gives access to the dev team in case you need support for anything that is not a bug.

Oh man thanks for replying!
Did you see I found the fix, I should have posted it here as well! Its on
YouTube comments haha
On Sat., Mar. 11, 2023, 6:20 a.m. Marco Lipparini, @.***>
wrote:

Hi @ChitinNature https://github.com/ChitinNature, thank you for
reporting this.
I guess you are using NodeJS version 14 as the performance global
variable was introduced in version 16. I pushed a quick fix to the repo and
I will publish a new alpha version after a few tests.
I can't guarantee we are gonna support Node 14 with our stable release
since it's pretty old, but it's good to keep backward compatibility as much
as possible atm.
I wish you a great day, please consider supporting us by joining the Open
Devs Crew https://opendevs.io, this gives access to the dev team in
case you need support for anything that is not a bug.
—
Reply to this email directly, view it on GitHub
https://github.com/hashlips-lab/hashlips-lab/issues/6#issuecomment-1464889538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5TZAQ6U63OJNYRQCKPIAO3W3RNWLANCNFSM6AAAAAAVXKIB3A
.
You are receiving this because you were mentioned.Message ID:
@.***>


Cannot find module './nodeToWrapperMappings'

Hi, I'm trying to use v 12.4.0, but trying to import the package gives me this
Error: Cannot find module './nodeToWrapperMappings'
    at Function.Module._resolveFilename (module.js:536:15)
    at Function.Module._load (module.js:466:25)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/projects/cashfarm/disl/disl-architect-ddd-es/node_modules/ts-simple-ast/dist/factories/index.js:7:22)
    at Module._compile (module.js:635:30)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)

Looks like the filename was changed to kindToWrapperMappings

just out of curiosity, which npm / nodejs and typescript versions are you using  ? thanks

node v8.9.1
typescript 2.9.1
I modified factories/index.js to point do nodeToWrapperMappings.js and it worked

@svallory I think something went wrong with the install. Can you try deleting the node_modules folder and do a fresh install? I just looked at the source code and package and index.js is correctly pointing at kindToWrapperMappings.ts.

@dsherret I have no idea how that happened. But indeed, I reinstalled the package and factories/index.js now has the correct code. I'm closing the issue.


4.1.0 introduces a breaking change and should be revoked (and re-released as 5.0.0)

Firstly, thank you for working on this great project and providing it to us to use.
However, 4.1.0 changes from using findDOMNode to cloning the child node and adding a ref parameter to it in order to access the dom node. Unfortunately, this is a breaking change, as any use of react tiny popover that does not directly pass a host node as a child will now be broken and be required to update their code to use forwardRef.
If this approach of cloning the child to insert a ref is to be maintained, the release of version 4.1.0 should be revoked and relabelled as 5.0.0 as it is a breaking change. This is important, as many people have tools that automatically merge minor updates as 4.1.0 as they are not supposed to be breaking change.
Additionally, a warning should be added to the documentation that says refs need to be forwarded. It would be great to catch the error introduced when refs are not forwarded, and to make the error more descriptive too.

However, I'm not sure this is actually the best approach. Using cloneElement is kind of "magic", and it is only by reading the diff of the update that I was able to figure out why 4.1.0 broke our app and how to fix it.  Two alternative approaches if you wish to use refs is to automatically wrap the child with a div, and then use ref.current.firstChild to access the child, or to replace the child with a render function that you pass the ref. Both of these would also likely be considered breaking changes and require a 5.0.0 moniker.

Thank you for bringing this to my attention. I'll have this version revoked and release a major version update, likely changing Popover's child to a render function injected with a ref. That pattern, although slightly more complex, seems to be the best way to replace findDOMNode's functionality without adding anything like an extra div to the DOM. I do wonder though if a better way exists.
In any case, stay tuned for that update and associated docs. Apologies for the inconvenience in the interim.

Yep just broke my app after upgrading.
I can't use wrap children with elements.
Looking forward to the fix.

@volkandkaya this can be addressed in userland just by wrapping your component child in a forwardRef and passing the ref through to the host node manually.

Correct. The fix will require passing the ref manually regardless, so any functional component used as a Popover child will now have to consume an injected ref via ref forwarding.
This is a consequence of React phasing out the imperative nature of findDOMNode in favor of the declarative nature of refs (which I honestly approve of philosophically). I'm struggling to see if there's a way to accommodate functional components without inserting an extra div or injecting a ref to forward. I don't think there's any other proper way in Strict mode. Am I correct in this thinking?

@alexkatz your problem essentially is there's no way to force a child to have a prop if the child is not properly setup to forward those props to a host node – even if you used IDs or classNames instead of refs (which I wouldn't advise), you're going to rely on the user forwarding that too.
The only way I can think of avoiding having the user forward props (/ref) is to have a container that you control. But even that's probably a breaking change.

If it isn't possible that is fine just have some nice docs to help people swap.
And maybe up it to 5.0.0 as @nathggns said.

Yep, stay tuned for the update and associated docs. Working on it now.
I'm bummed that findDOMNode seemed to have this unique functionality that isn't possible in Strict mode. I guess that's just the path React is taking as a framework, which ultimately I approve of. findDOMNode was a rather hacky approach to begin with that kind of violated the principles of React itself. It certainly simplified things though in this case.

I'm bummed that findDOMNode seemed to have this unique functionality that isn't possible in Strict mode. I guess that's just the path React is taking as a framework, which ultimately I approve of. findDOMNode was a rather hacky approach to begin with that kind of violated the principles of React itself. It certainly simplified things though in this case.

@alexkatz I completely get where you're coming from. I guess the React team's argument would be that this change is making what was previously an unsafe implicit requirement, safe and explicit (that there is a single host node rendered to represent the containing box to attach the popover to). If you go down the supply the ref as a render prop method, then you're also giving the user the ability to specify exactly which host node to attach the popover to, rather than the implicit requirement of it being a single direct descendent.

Yup, you're right. Ultimately it's better that way, even if it makes this popover API slightly less elegant.

Version 5 is now out. Thank you guys for your patience. I'l go ahead and close this for now, but feel free to reopen if something is behaving oddly or remains unclear.
Thanks!

Hi @alexkatz.
I just did a minor version bump, and this broke our app. Could you please redact the 4.1.0 release since it is clearly breaking it's API? I mean it's an easy enough fix, and we'll just jump to version 5 now, -- but it is not a good practice to change API in a minor version.
If you cannot disable the 4.1.0 release on npm, maybe create a branch of the old 4.0.0 as 4.2.0 so anyone doing an minor update won't break their code like I did? :)
Thanks for your work on this!

Shit, it is deprecated, but yarn upgrade still upgraded to it. So yarn is the bad boy here.

I think re-releasing 4.0 as 4.2 is a good idea

Indeed, or even 4.1.1 would work.
Yarn did print the warning, but in a huge project those are hard to see, since it scrolls out of the screen right away with other output. :)


Catalyst tries to transcode before upload is complete

Because Mist sends us the RECORDING_END trigger before the segmenting uploads are complete, there's sometimes a race condition whereby we'll try to transcode with files that aren't in storage yet.
Initial strategy should be to wait 10s between segmenting and transcoding before coming up with a better approach.

Better idea: a new trigger that gets executed for each upload, and waits for it to finish before firing. Then just wait for all uploads to complete?

@Thulinma that would be ideal

This has been "solved" in the interim with retries and backoffs