Scott847

Wow, thanks for the quick work! I started using the new version and am also using the new direct local query for a PurpleAir sensor. For a couple of locations I'm using the median of three nearby sensors so don't have a local sensor to query. It's great that the API call is now using 25 points per API call instead of 155. When I let PurpleAir know about the change they said they're "working on a process to automatically assign points to sensor owners but we are not quite there" and to email them in the meantime as I need more free points. Not sure if it's unique to my system but FYI I had to update a program line that uses the plugin perhaps because a "μg/m3" unit of measure was added at some point.

PurpleAir is starting to charge for API usage and sent me an email to let me know this would take effect for me on 11/28/2023. There is a cost per point and the number of points used is based on the number of API calls as well as the fields that are returned for each call. In looking at the code I realized that the current PG3x PurpleAir plugin isn't specifying the "fields" parameter, which defaults to returning all data fields for the sensor even though most aren't sent to IoX. As a result each API call is currently using 155 points. I've been pulling data from seven PurpleAir sensors at the default short poll time of 600 seconds, which means I would be getting charged for about 4,700,000 points per month. PurpleAir will be charging $1 per 100,000 points so this means my monthly charge if nothing changes would be about $47.00. @bpwwer, could you look into using the "fields" parameter in the API calls to reduce points usage? FYI PurpleAir support also provided this link that had more info about efficiently using their API calls: https://community.purpleair.com/t/how-to-make-efficient-api-calls/6906 Also FYI they'll be giving points credits to owners of PurpleAir sensors to offset any usage for API access to their devices. In an email to me they said "We don't want sensor owners to pay for API access for purchased sensors if the point use is reasonable and the API pulls are optimized." I originally obtained an API key from them by email but since then they've created an API account management system where you can manage API keys and monitor usage at https://develop.purpleair.com/

As a test I modified the text-to-speech TTS0 "Message 0" to "testing 1 2 3 testing 1 2 3" and didn't have to restart my Polisy nor IoX. The change showed up in the IoX admin console after restarting the YoLink node server and closing/opening the admin console. One other "secret" I noticed is to wait a sufficient amount of time for the YoLink node server to fully restart. In my case it takes nearly 2 minutes to complete the restart. Thanks for your work on the YoLink node server!

Using a Polisy with a YoLink Speaker Hub the following steps worked for adding new text-to-speech messages: In YoLink node server increase configuration key NBR_TTS by the number of new text-to-speech messages, in my case increased from 1 to 5 Restart YoLink node server and new keys TTS1 through TTS4 appeared and I added the text I wanted it to say (for example, "side gate opened" for TTS3) Restart YoLink again, which I think may be needed to make the new text-to-speech messages active Close and reopen the IoX admin console so that the new messages appeared as an option for the Speaker Hub device "Select Message" function (I didn't have to restart Polisy nor IoX, only the admin console) Added the Set 'Speaker Hub' Select Message "side gate opened" and Set 'Speaker Hub' Play Message to a program Thanks @whywork, @Bumbershoot and @Panda88 for your notes on this!

Some answers based on my experience but others may have better info.... Q: Exclude and re-include Schlage lock... Not sure what you mean here, are you referring to removing the lock completely from the controller and adding it back in? Yes, in admin console I did a "Z-Wave / Remove a Z-Wave Device" followed by a "Z-Wave / Add a Z-Wave Device." Q: "The reason is even if I remove it, it will still have ghost objects reappear under certain circumstances and the only way to clear those and not have them come back is to do a reset on the ZWave controller." I haven't often seen ghost objects but there's a "Z-Wave / Synchronize / New & Deleted" that might get rid of them. Restarting the admin console is also a good step between significant changes. It's been a few years since I've had to do a Z-Wave reset. For my ISY to Polisy conversion I was able to restore from the ISY but excluded/included a few devices. Q: BTW - I used to have an BE469NX and changed it out to the one I have now. Your old one is on S0, isn't it? Yes, I believe my old BE469NX security setting is S0. Q: When you did your include did use the standard old school ZWave include or scan the DSK via UDM? I used the old school "Add a Z-Wave Device." I believe my lock was manufactured before there was a scan code.

Don't know if these steps would help but my Schlage BE469NX (purchased 2015, firmware MAIN_6.8) so far seems to be reporting reliably after I upgraded from my ISY to a Polisy with ZMatter a few days ago. After some initial problems it's working now after some combination of the following: - In admin console: Z-Wave / Network / Communication Speed = 100 (Slowest) - In admin console: Z-Wave / Network / Interview Timeout = 30 Seconds - In admin console: Z-Wave / Network / Heal Network -- Network Heal can take a long time, watch progress in Tools / Diagnostics / Event Viewer - Exclude and re-include Schlage lock - Right click on lock and Z-Wave / Update Neighbors - Right click on lock and Z-Wave / Synchronize / Update with interview It still shows "Interview Not Done" when looking at Z-Wave / X-Ray / DH All Devices / Go but I'm not seeing any side effects. These are the nodes showing up for the lock: - ZY 022 Door Lock -- ZY 022 Access Control Alarm -- ZY 022 Hardware Failure Alarm -- ZY 022 Home Security Alarm -- ZY 022 Intrusion Alarm -- ZY 022 Power Alarm -- ZY 022 System Alarm

My understanding is that for battery operated devices like the ZSE44 there's no way for IoX to wake it up after restarting and it doesn't remember the last reading before restart. So there won't be any reading in IoX until either a threshold is crossed (e.g., a 2 degree temperature change from last report) or the maximum reporting interval is exceeded (e.g., every 4 hours for temperature). If you leave your AC running for awhile you can look at Tools / Diagnostics / Event Viewer and download that to a file. Scanning through that I found that my ZSE44 device reported temperature changes at the following times today for device ID ZY023_118: 12:28:57 AM 04:31:11 AM 08:33:31 AM 09:10:49 AM

One possibility is the battery-friendly default settings for the ZSE44. For example, the default for temperature reporting is to update only for changes > 2 degrees, or every 4 hours. The manual has info about the default settings, how to force wake the sensor and more: https://www.getzooz.com/downloads/zooz-z-wave-plus-700-series-temperature-humidity-xs-sensor-zse44-manual.pdf I installed one recently for humidity monitoring. It's been working great after I changed the humidity threshold from the default of a 10% change triggering reporting.

It hasn't successfully updated all devices for the initial YoLink installation on this Polisy. I sent you the debug log from the time I did a restart just now.

I'm installing the YoLink node server on a 2nd Polisy. Although it seems to install correctly and finds all devices, it starts reporting "not online" messages from initNode for all devices after the 9th device. The 10th device is a motion sensor, but not sure if that has anything to do with the problem. In this log the "4GD Leak Sink" device successfully reports status to IoX but nothing after that. 2023-03-23 14:37:52,703 Thread-4 udi_interface INFO udi-YoLink:addNodes: adding/checking device : 4GD Leak Sink - LeakSensor 2023-03-23 14:37:52,704 Thread-4 udi_interface INFO udi-YoLink:addNodes: Adding device 4GD Leak Sink (LeakSensor) as 8b4c0200006ec5 2023-03-23 14:37:52,716 Thread-4 udi_interface.interface INFO interface:addNode: Adding node 4GD Leak Sink(8b4c0200006ec5) [None] 2023-03-23 14:37:52,718 Thread-4 udi_interface.custom INFO custom:_save: Sending data customparams to Polyglot. 2023-03-23 14:37:52,872 Thread-161 udi_interface INFO udi-YoLink:handleLevelChange: New log level: {'name': 'INFO', 'level': 20} 2023-03-23 14:37:52,883 Thread-162 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-23 14:37:52,963 Thread-163 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-23 14:37:52,967 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparams 2023-03-23 14:37:53,011 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-03-23 14:37:53,053 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-03-23 14:37:53,156 Thread-165 udi_interface INFO udiYoLeakSensorV2:start: start - YoLinkLeakSensor 2023-03-23 14:37:53,161 Thread-165 udi_interface INFO yoLink_init_V3:subscribe_mqtt: Subscribing deviceId d88b4c0200006ec5 to MQTT 2023-03-23 14:37:56,528 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0200006ec5 :: GV0 to 0 UOM 25 2023-03-23 14:37:56,624 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0200006ec5 :: GV1 to 4 UOM 25 2023-03-23 14:37:56,760 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0200006ec5 :: ST to 1 UOM 25 2023-03-23 14:37:57,123 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c0200006ec5 :: CLITEMP to 13 UOM 4 2023-03-23 14:37:58,507 Thread-6 udi_interface ERROR yoLink_init_V3:on_disconnect: Unintentional disconnect - Reacquiring connection 2023-03-23 14:37:58,900 Thread-4 udi_interface INFO udi-YoLink:addNodes: adding/checking device : 4GD Motion Living Room - MotionSensor 2023-03-23 14:37:58,902 Thread-4 udi_interface INFO udi-YoLink:addNodes: Adding device 4GD Motion Living Room (MotionSensor) as 8b4c01000260ea 2023-03-23 14:37:58,915 Thread-4 udi_interface.interface INFO interface:addNode: Adding node 4GD Motion Living Room(8b4c01000260ea) [None] 2023-03-23 14:37:58,917 Thread-4 udi_interface.custom INFO custom:_save: Sending data customparams to Polyglot. 2023-03-23 14:37:59,165 Thread-189 udi_interface INFO udi-YoLink:handleLevelChange: New log level: {'name': 'INFO', 'level': 20} 2023-03-23 14:37:59,182 Thread-190 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-23 14:37:59,256 Thread-191 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-23 14:37:59,260 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparams 2023-03-23 14:37:59,304 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-03-23 14:37:59,346 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-03-23 14:37:59,441 Thread-193 udi_interface INFO udiYoMotionSensorV2:start: start - udiYoLinkMotionSensor 2023-03-23 14:37:59,444 Thread-193 udi_interface INFO yoLink_init_V3:subscribe_mqtt: Subscribing deviceId d88b4c01000260ea to MQTT 2023-03-23 14:38:00,541 Thread-6 udi_interface INFO yoLink_init_V3:connect_to_broker: Connecting to broker... 2023-03-23 14:38:00,966 Thread-6 udi_interface INFO yoLink_init_V3:connect_to_broker: Retrieving YoLink API info 2023-03-23 14:38:04,504 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200003985 2023-03-23 14:38:04,507 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c02000853dd 2023-03-23 14:38:04,510 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200005e4a 2023-03-23 14:38:04,512 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c02000853ef 2023-03-23 14:38:04,514 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c02000039f5 2023-03-23 14:38:04,516 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200006fbd 2023-03-23 14:38:04,519 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200006eb0 2023-03-23 14:38:04,521 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c02000067ab 2023-03-23 14:38:04,523 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200006ec5 2023-03-23 14:38:04,526 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c01000260ea 2023-03-23 14:38:05,697 Thread-6 udi_interface ERROR yoLink_init_V3:on_connect: Authentication error 2 - Token no longer valid - Need to reconnect 2023-03-23 14:38:05,699 Thread-6 udi_interface INFO yoLink_init_V3:refresh_token: Refreshing Token 2023-03-23 14:38:07,511 Thread-193 udi_interface ERROR yolink_mqtt_classV3:initNode: MotionSensor not online 2023-03-23 14:38:08,043 Thread-4 udi_interface INFO udi-YoLink:addNodes: adding/checking device : 4GD TH Basement - THSensor 2023-03-23 14:38:08,044 Thread-4 udi_interface INFO udi-YoLink:addNodes: Adding device 4GD TH Basement (THSensor) as 8b4c010002acc7 2023-03-23 14:38:08,058 Thread-4 udi_interface.interface INFO interface:addNode: Adding node 4GD TH Basement(8b4c010002acc7) [None] 2023-03-23 14:38:08,061 Thread-4 udi_interface.custom INFO custom:_save: Sending data customparams to Polyglot. 2023-03-23 14:38:08,138 Thread-6 udi_interface INFO yoLink_init_V3:connect_to_broker: Connecting to broker... 2023-03-23 14:38:08,139 Thread-6 udi_interface INFO yoLink_init_V3:connect_to_broker: Retrieving YoLink API info 2023-03-23 14:38:08,226 Thread-217 udi_interface INFO udi-YoLink:handleLevelChange: New log level: {'name': 'INFO', 'level': 20} 2023-03-23 14:38:08,245 Thread-218 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-23 14:38:08,322 Thread-219 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-23 14:38:08,324 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparams 2023-03-23 14:38:08,335 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-03-23 14:38:08,418 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-03-23 14:38:08,493 Thread-221 udi_interface INFO udiYoTHsensorV2:start: Start udiYoTHsensor 2023-03-23 14:38:08,495 Thread-221 udi_interface INFO yoLink_init_V3:subscribe_mqtt: Subscribing deviceId d88b4c010002acc7 to MQTT 2023-03-23 14:38:11,696 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200003985 2023-03-23 14:38:11,700 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c02000853dd 2023-03-23 14:38:11,702 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200005e4a 2023-03-23 14:38:11,704 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c02000853ef 2023-03-23 14:38:11,707 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c02000039f5 2023-03-23 14:38:11,709 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200006fbd 2023-03-23 14:38:11,711 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200006eb0 2023-03-23 14:38:11,714 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c02000067ab 2023-03-23 14:38:11,716 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c0200006ec5 2023-03-23 14:38:11,719 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c01000260ea 2023-03-23 14:38:11,721 Thread-6 udi_interface INFO yoLink_init_V3:update_mqtt_subscription: update_mqtt_subscription d88b4c010002acc7 2023-03-23 14:38:12,595 Thread-234 udi_interface ERROR yoLink_init_V3:transfer_data: Error 4 during publishing {'time': '1679596691560', 'method': 'THSensor.getState', 'targetDevice': 'd88b4c010002acc7', 'token': 'E8867B438B4D0193CB6C9C85618B907A'} 2023-03-23 14:38:14,616 Thread-221 udi_interface ERROR yolink_mqtt_classV3:initNode: THSensor not online 2023-03-23 14:38:17,219 Thread-4 udi_interface INFO udi-YoLink:addNodes: adding/checking device : 4GD TH Dining Room - THSensor 2023-03-23 14:38:17,220 Thread-4 udi_interface INFO udi-YoLink:addNodes: Adding device 4GD TH Dining Room (THSensor) as 8b4c010002b356 2023-03-23 14:38:17,235 Thread-4 udi_interface.interface INFO interface:addNode: Adding node 4GD TH Dining Room(8b4c010002b356) [None] 2023-03-23 14:38:17,237 Thread-4 udi_interface.custom INFO custom:_save: Sending data customparams to Polyglot. 2023-03-23 14:38:17,395 Thread-247 udi_interface INFO udi-YoLink:handleLevelChange: New log level: {'name': 'INFO', 'level': 20} 2023-03-23 14:38:17,413 Thread-248 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-23 14:38:17,484 Thread-249 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-23 14:38:17,488 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparams 2023-03-23 14:38:17,573 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-03-23 14:38:17,576 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-03-23 14:38:17,669 Thread-251 udi_interface INFO udiYoTHsensorV2:start: Start udiYoTHsensor 2023-03-23 14:38:17,672 Thread-251 udi_interface INFO yoLink_init_V3:subscribe_mqtt: Subscribing deviceId d88b4c010002b356 to MQTT 2023-03-23 14:38:20,696 Thread-265 udi_interface ERROR yoLink_init_V3:transfer_data: Error 4 during publishing {'time': '1679596700694', 'method': 'THSensor.getState', 'targetDevice': 'd88b4c010002b356', 'token': '29A682732F75E02A910E4D9C7379E1E7'} 2023-03-23 14:38:22,733 Thread-251 udi_interface ERROR yolink_mqtt_classV3:initNode: THSensor not online

While you're looking into this could you also check leak sensors? In the YoLink app the leak sensor details show temperatures, which could be useful.

VUE installed successfully after doing the "Install Dev. Packages." Thanks for the quick response. FYI after clicking the option to install dev packages the 2nd and 3rd Polisy lights continued to flash. I waited ~30 minutes and then did a Polisy Reboot from the admin console. It booted successfully and then I installed the VUE node server.

@bpwwer I'm getting an error when I try to install the VUE node server on a Polisy. Perhaps related to the python-jose[cryptography]==3.3.0 requirement? It looks like it tries to build pycryptodome and runs into a compile error when it can't find stdint.h. Following are some log excerpts showing the problem: 1/27/2023, 12:46:35 [pg3] info: NSChild: VUE(7) /bin/sh: Collecting python-jose[cryptography]==3.3.0 1/27/2023, 12:46:35 [pg3] info: NSChild: VUE(7) /bin/sh: Downloading python_jose-3.3.0-py2.py3-none-any.whl (33 kB) <snip> 1/27/2023, 12:46:54 [pg3] info: NSChild: VUE(7) /bin/sh: Collecting pycryptodome<3.4.0,>=3.3.1 1/27/2023, 12:46:55 [pg3] info: NSChild: VUE(7) /bin/sh: Downloading pycryptodome-3.3.1.tar.gz (3.1 MB) 1/27/2023, 12:46:55 [pg3] info: NSChild: VUE(7) /bin/sh: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.1/3.1 MB 16.2 MB/s eta 0:00:00 1/27/2023, 12:46:55 [pg3] info: NSChild: VUE(7) /bin/sh: 1/27/2023, 12:46:55 [pg3] info: [00:0d:b9:53:2a:14_7] Retrieved customparams 1/27/2023, 12:46:55 [pg3] info: [00:0d:b9:53:2a:14_7] Retrieved oauth 1/27/2023, 12:46:56 [pg3] info: NSChild: VUE(7) /bin/sh: Preparing metadata (setup.py): started 1/27/2023, 12:46:58 [pg3] info: NSChild: VUE(7) /bin/sh: Preparing metadata (setup.py): finished with status 'done' 1/27/2023, 12:46:59 [pg3] info: NSChild: VUE(7) /bin/sh: Requirement already satisfied: pycparser in /usr/local/lib/python3.9/site-packages (from cffi>=1.12->cryptography>=3.4.0->python-jose[cryptography]==3.3.0->-r requirements.txt (line 6)) (2.21) 1/27/2023, 12:47:01 [pg3] info: NSChild: VUE(7) /bin/sh: Building wheels for collected packages: pycryptodome 1/27/2023, 12:47:01 [pg3] info: NSChild: VUE(7) /bin/sh: Building wheel for pycryptodome (setup.py): started 1/27/2023, 12:47:05 [pg3] info: NSChild: VUE(7) /bin/sh: Building wheel for pycryptodome (setup.py): finished with status 'error' <snip> running build_ext warning: no support for Intel AESNI instructions building 'Crypto.Hash._MD2' extension creating build/temp.freebsd-13.1-RELEASE-p5-amd64-cpython-39 creating build/temp.freebsd-13.1-RELEASE-p5-amd64-cpython-39/src cc -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -DLTC_NO_ASM -Isrc/ -I/usr/local/include/python3.9 -c src/MD2.c -o build/temp.freebsd-13.1-RELEASE-p5-amd64-cpython-39/src/MD2.o In file included from src/MD2.c:28: src/pycrypto_common.h:47:10: fatal error: 'stdint.h' file not found #include <stdint.h> ^~~~~~~~~~ 1 error generated. error: command '/usr/bin/cc' failed with exit code 1 [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for pycryptodome 1/27/2023, 12:47:05 [pg3] info: NSChild: VUE(7) /bin/sh: Running setup.py clean for pycryptodome 1/27/2023, 12:47:05 [pg3] info: set to expire on 2023-02-20T00:39:32.000Z 1/27/2023, 12:47:05 [pg3] info: set to expire on 2023-02-16T22:03:49.000Z 1/27/2023, 12:47:06 [pg3] info: [XX:XX:XX:XX:XX:XX_X] controller reporting command DOF 1/27/2023, 12:47:07 [pg3] info: NSChild: VUE(7) /bin/sh: Failed to build pycryptodome

Not sure if something like this would be useful but Initial State is great for data visualization: https://www.initialstate.com/ This is one tile showing voltages on an Initial State dashboard. Following are the network resource settings for voltage from an Aeotec Smart Switch 6. Protocol Information: https POST Host = groker.initialstate.com Port = 443 Path = /api/events Encode URL = unchecked Use SNI = unchecked Timeout (ms) = 5,000 Mode = Raw Text Headers: Content-Type = application/json X-IS-AccessKey = [your Initial State access key] X-IS-BucketKey = [your key for an Initial State "bucket" you create] Body: [ {"key": "Sump Pump Volts", "value": ${sys.node.ZW005_143.CV.raw}}, {"key": "Sump Pump Watts", "value": ${sys.node.ZW005_143.ST.raw}}, {"key": "Sump Pump Amps", "value": ${sys.node.ZW005_143.CC.raw}}, {"key": "Sump Pump kWh", "value": ${sys.node.ZW005_143.TPW.raw}} ]

I had the same symptom due to psutil not being found during YoLink installation. The solution was to connect using SSH (using PuTTY for example) and installing psutil: sudo pkg install py39-psutil This is the thread about this: