hart2hart Posted March 17, 2023 Posted March 17, 2023 (edited) @Goose66I've been using the nodeserver since PG2 and moved to PG3 year or more ago on Polisy asnd its worked flawlessly. Updated to latest version of nodeserver in last week or 10 days. Today it will not control ceiling fan lights and fans. I've Restarted Bond puck restatrted the nodeserver Restarted ISY Following error occurs during nodeserver restart: 2023-03-17 07:41:06,627 MainThread udi_interface INFO bondns:run: Starting Bond node server... 2023-03-17 07:41:06,629 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2023-03-17 07:41:06,631 MainThread udi_interface.interface ERROR interface:_get_server_data: get_server_data: failed to read file server.json: [Errno 2] No such file or directory: 'server.json' Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 480, in _get_server_data with open(Interface.SERVER_JSON_FILE_NAME) as data: FileNotFoundError: [Errno 2] No such file or directory: 'server.json' 2023-03-17 07:41:06,642 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '3.1.13'}} 2023-03-17 07:41:06,680 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) Edited March 17, 2023 by hart2hart
Goose66 Posted March 17, 2023 Posted March 17, 2023 The missing server.json error is expected (server.json files are deprecated). Future versions of PG3 should remove that error. can you send a log package - preferably one that contains attempted control actions for the nodes?
Goose66 Posted March 17, 2023 Posted March 17, 2023 @hart2hart Looking at the node server log file debug.log in the second DM you sent, I don't see any errors or warnings, but I also don't see any commands to control the ceiling fans or lights - just status updates on the shortPoll interval at 08:23:14 and 08:23:44. Can you provide a better understanding on what the symptoms are here? E.g., what action are you performing and what expected response are you not getting? Also, when checking the actual results, please use the status of the device as reported in the Bond Home app as the resulting status, and not the physical status of the fan or light itself, in that the node server communicates with the Bond Bridge (as the app does), but communications and failures between the bridge and the physical device are outside the scope of the node server.
hart2hart Posted March 17, 2023 Author Posted March 17, 2023 @Goose66 I have the node server nodes in scenes with Insteon switches. I tap the switch and turn on light or fan.
Solution hart2hart Posted March 17, 2023 Author Solution Posted March 17, 2023 (edited) @Goose66I realized that PLM was not registering the insteon device update so I did a restore PLM and all is working now -- sorry to have bothered you with it. Of course the PLM may need a replacement soon. I'll watch it. I prophylactically replaced the capacitators a couple years ago. Edited March 17, 2023 by hart2hart
Goose66 Posted March 17, 2023 Posted March 17, 2023 I do see some a couple of "Turn On" (DON) commands for the light at 07:50:23 and again at 07:50:26, followed by "Turn On" (DON) and then "Turn Off" commands for the fan at 07:51:08 and 07:51:12, respectively. While these were 30 minutes or so before the log file was put into debug mode, I don't see any errors or warnings or anything to suggest these commands didn't make it to the Bond bridge. Have you check the status of these devices in the Bond Home app to see if the status (as far as the bridge is concerned) is being changed by the ISY Scene commands?
Goose66 Posted March 17, 2023 Posted March 17, 2023 5 minutes ago, hart2hart said: @Goose66I realized that PLM was not registering the insteon device update so I did a restore PLM and all is working now -- sorry to have bothered you with it. Of course the PLM may need a replacement soon. I'll watch it. I prophylactically replaced the capacitators a couple years ago. Good to hear (that you found your problem - not that your PLM is dying )
Recommended Posts