tlightne Posted June 28 Share Posted June 28 @bpwwer My Eisy crashed while upfrading PG3 to 3.2.27 and had to send it in to UDI to be reflashed. After returning and reloading PG# backups my Ambient Plugin loads all the nodes to my Eisy and the data gets updated except one an indoor sensor that I measure AC supply temps get any data. I have rebooted Eisy a couple of times with no luck. I have deleted the plugin from Eisy and PG3 rebooted EISY then reinstalled the plugin but still do not get the one node to update in EISY. I see the all the nodes in the AC console it just will not update the data. I have looked in the logs for the plugin and I can see the data get updated from the API. I have attached the log file here as well. EISY Firmware is 5.8.3 and PG3 is 3.2.27. Thank you.. AmbientWeather_6-28-2024_31954_PM.zip Quote Link to comment
bpwwer Posted June 28 Share Posted June 28 @tlightne You'll need to describe your setup a bit better for me to understand what I'm looking at in the log. However, I don't really see anything that looks obviously wrong. I see 6 nodes being created: Brad East with address e8db84e738 main with address e8db84e738_1 indoor with address e8db84e738_2 one with address e8db84e738_3 two with address e8db84e738_4 three with address e8db84e738_5 All of those appear to be getting data from Ambient.net and publishing the values to PG3. Is the node on the eisy that's not getting updated one of those? If it's not, then it's probably an orphaned node that the plug-in doesn't know anything about. The plug-in creates the nodes and determines what data it can get from Ambient.net by parsing the data returned when it makes a query for all data. Anything it sees in that data that it doesn't understand is ignored. To do any more debugging I'd need you to do a couple of things. First set the plug-in's log level to debug, then restart the plug-in. Let it run long enough to do a couple of queries to Ambient.net. Then download the log package (not just the plug-in log). The package will include the PG3. That way I can see if PG3/IoX is rejecting updates from the plug-in. After downloading the log, you can set the plug-in's log level back to INFO. Quote Link to comment
tlightne Posted June 28 Author Share Posted June 28 (edited) @bpwwer Hi Bob, Main with address e8db84e738-1 is the outdoor array and is working as designed. indoor with address e8db84e738_2 is as labeled the indoor sensor and is working as designed. one with address e8db84e738_3 is a sensor in a chest freezer and is working as designed. Two with address e8db84e738_4 is monitoring temps in my bedroom and is working as designed. Three with address e8db84e738_5 is the temp sensor the is not being updated. Attached is the download Package. Thank you.. AmbientWeather_6-28-2024_63232_PM.zip Edited June 28 by tlightne Quote Link to comment
bpwwer Posted June 29 Share Posted June 29 So this is what's at the bottom of the logs. The plug-in reports successfully sending the dewpoint value of 52.2 for node three. 2024-06-28 18:32:06.477 MQTT udi_interface.interface INFO interface:_message: Successfully set e8db84e738_5 :: DEWPT to 52.2 UOM 17 2024-06-28 18:32:06.397 [pg3] info: Received commands on topic udi/pg3/ns/status/00:21:b9:02:66:d1_11: set 2024-06-28 18:32:06.432 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:66:d1] :: - http://127.0.0.1:8080/rest/ns/11/nodes/n011_e8db84e738_5/report/status/DEWPT/52.2/17 2024-06-28 18:32:06.432 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:66:d1] :: [200] :: 0.867211ms - http://127.0.0.1:8080/rest/ns/11/nodes/n011_e8db84e738_5/report/status/DEWPT/52.2/17 In the PG3 log we see that it received the command from the plugin (set command to set the value). That log message isn't all that good as it don't provide much. But following that we see PG3 making the request to IoX to update the value. Then, we immediately see IoX respond with a status of 200, which means it was successful. From these log messages, it does appear that the plug-in is sending updates (so nothing wrong with the plug-in) and PG3 is sending those to IoX (so nothing wrong with PG3). I'm not sure what else to do at this point. You could check the IoX logs, but since it is reporting success back to PG3 I don't think you'll see any errors there. Quote Link to comment
tlightne Posted June 29 Author Share Posted June 29 @bpwwer Ok thanks for looking into this. I may order another sensor from Ambient and add it as an additional sensor to see what happens... Quote Link to comment
Solution tlightne Posted July 5 Author Solution Share Posted July 5 Purchased and installed an additional temp sensor today and now all the sensors show and update properly in admin console Plugin nodes on EISY.... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.