Jimbo.Automates

Never mind all fixed. Tried air gapping for 10 seconds, then writing, still failed. Tried air gaping again and full reset by holding button in until beep stops, then restore device and write changes was successful.

This is a 2334-2 that works fine, even controlling 2 large scenes, but it has a change and won't write. I'm not good at reading Insteon log but looks like the communication is good but still get a Failed Writing error? Any help would be appreciated. Mon 06/03/2024 06:17:05 PM : [22 F4 37 1 ] Link 1 : 0FF0 [A27A500143FF1F02] Writing [A27A500143FF1F02] Mon 06/03/2024 06:17:05 PM : [INST-TX-I2 ] 02 62 22 F4 37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1 Mon 06/03/2024 06:17:05 PM : [INST-ACK ] 02 62 22.F4.37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1 06 (00) Mon 06/03/2024 06:17:05 PM : [INST-SRX ] 02 50 22.F4.37 50.01.43 AB 2F FF (FF) Mon 06/03/2024 06:17:05 PM : [Std-Direct Nack] 22.F4.37-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 06/03/2024 06:17:10 PM : [INST-TX-I2 ] 02 62 22 F4 37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1 Mon 06/03/2024 06:17:10 PM : [INST-ACK ] 02 62 22.F4.37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1 06 (00) Mon 06/03/2024 06:17:11 PM : [INST-SRX ] 02 50 22.F4.37 50.01.43 AB 2F FF (FF) Mon 06/03/2024 06:17:11 PM : [Std-Direct Nack] 22.F4.37-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 06/03/2024 06:17:16 PM : [INST-TX-I2 ] 02 62 22 F4 37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1 Mon 06/03/2024 06:17:16 PM : [INST-ACK ] 02 62 22.F4.37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1 06 (00) Mon 06/03/2024 06:17:16 PM : [INST-SRX ] 02 50 22.F4.37 50.01.43 AB 2F FF (FF) Mon 06/03/2024 06:17:16 PM : [Std-Direct Nack] 22.F4.37-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 06/03/2024 06:17:16 PM : [22 F4 37 1 ] Link 1 : 0FF0 [A27A500143FF1F02] *Failed Writing [A27A500143FF1F02] Mon 06/03/2024 06:17:16 PM : [D2D EVENT ] Event [22 F4 37 1] [ERR] [0] uom=0 prec=-1 Mon 06/03/2024 06:17:16 PM : [22 F4 37 1 ] ERR 0

Works fine for me on my Android phone. Sent from my Pixel 8 Pro using Tapatalk

Thanks! I agree, log level should also be retained. Sent from my Pixel 8 Pro using Tapatalk

Thanks @bpwwer , one other question. When it sets the values at install time, does it know not to set them for an update install? Sent from my Pixel 8 Pro using Tapatalk

That is bizarre, @johnnyt has reported similar issues. But, the nodeserver itself has no control over the short/long poll values, it can only read them, not set them. Will need help from @bmercier or @bpwwer if they have a clue. I've also been discussing with @bmercier to add a custom polling that is settable by the nodeserver, so hopefully that can be implemented soon. But in the meantime we need to understand how/why PG3 is resetting the short poll value.

It helps to tag the person, otherwise I assume you are talking to me. I've never seen this issue before, and it's out of my control so doesn't help to keep on it. Post to the ticket. But, I would suggest moving it to a different slot, something is not right with that one, or delete all the nodes in the PG3 UI Nodes page and restart the node server, but that might not help either. The "will try to discover on next poll" is because you really pissed off the Airthings servers and they are not allowing access. I did this earlier today because I had my production and test servers running at the same time and it took almost 40 minutes before it gave me access again.

As I mentioned, nothing I can do about that, it's on the PG3 side.

That's exactly what was fixed in the new version if you read the release notes...

PG3 Airthings Consumer node server 1.1.2 released, see OP.

Tracking of Polled devices fixed in 1.1.2.

Looks like an internet or Airthings server issue, but plugin should handle it better: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/22

Re-installing in the same slot should not overwrite the config, I've never seen this happen. Restart is not necessary after a re-install since it stops the plugin, installs it, then starts it up. I've reinstalled on mine with each update an none of that is necessary. But in any case, those would be PG3 issues @bmercier would have to look into it.

Driver ST is set by PG3 on startup so you won't see it in the Plugin log. GV6 is only set on startup based on settings in the plugin, so it won't show in the log either. It will show if you can change the Poll Sensor in the AC. In the log you sent I see VOCLVL being set 2024-05-27 11:14:59,999 MQTT udi_interface.interface INFO interface:_message: Successfully set s_2930071732 :: VOCLVL to 1 UOM 96 I reviewed the log and it is pushing the profile to IoX so not sure what the issue is. 2024-05-27 09:16:03,410 Thread-11 udi_interface INFO Controller:handler_start: Started Airthings-Consumer NodeServer 1.1.1 2024-05-27 09:16:03,436 Thread-11 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot.

Please download log package and PM it to me and reference this post. Sent from my Pixel 8 Pro using Tapatalk

This tells me you must have a keypad connected to the RS485 and the 7TS is essentially a UI using the same API the ELK Plugin uses. Sorry, no idea, I don't have a test system so will have to upgrade mine when I have time to debug if there are issues. But I seriously doubt there will be any issues.

None of those steps should be necessary, all you should need is: Update plugin Wait till installation is complete Make sure it shows 1.1.1 in the PG3 UI Start Admin Console, the AC loads the profile from the IoX on startup so it must not be running to see the new info. PG3 handles loading the profile into the IoX so if it's not happening will need help from @bmercier to review.

Sorry, I forgot to add it to the doc. Each sensor should have a poll device option when you select it in the AC. Make sure you have closed and opened the AC since updating the plugin. Sent from my Pixel 8 Pro using Tapatalk

PG3 Airthings release seems to have caused licensing issues, if you are unable to upgrade please submit a support ticket and include your UUID.

You are not the only one, something seems to have happened with the new release. Please submit a support ticket and give them our UUID to check.

Sorry I should have said to include your uuid in the ticket which theyll need to check licenses. Sent from my Pixel 8 Pro using Tapatalk

PG3 Airthings Consumer node server 1.1.1 released.

The unhandled errors are all related to PG3, not the plugin itself. Are you still seeing those? The unhandled param is VirusRisk and I've asked Airthings support to explain these numbers and what the min/max can be but no response so I can't add it until I get this info. It does not cause any problem, simple a notice that the API is sending info that it doesn't expect.

Sorry, not sure. You'll have to submit a ticket for @Michel Kohanim or @bmercier to look at. Sent from my Pixel 8 Pro using Tapatalk

As documented in https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/blob/main/README.md The VOC value is in driver GV4. PG3 now allows us to set a name to show up on that page so I will try to add that tomorrow.