Jimbo.Automates Posted October 18, 2023 Posted October 18, 2023 (edited) The Polyglot Version 3 Node server for ELK Security Version 3.10.15 is released. See the Release Notes Working on new documentation at ELK Node Server If you have issues or requests please check PG3 ELK Github issues to see it has already been listed. And if you want to thumbs up an issue I will try to prioritize fixing the ones with most votes. IMPORTANT: If using ELKID or ELKNAME you must enable the "Allow ISY Access by Plugin" on the configuration page. This will be required in PG3x Version 3.2.19 and beyond. Edited February 10 by Jimbo.Automates Change to 3.10.15
Jimbo.Automates Posted October 21, 2023 Author Posted October 21, 2023 The Polyglot Version 3 Node server for ELK Security Version 3.10.3 is released. See the Release Notes
Jimbo.Automates Posted November 11, 2023 Author Posted November 11, 2023 The PG3 Node server for ELK Security Version 3.10.4 is released. See the Release Notes
Jimbo.Automates Posted December 16, 2023 Author Posted December 16, 2023 The PG3 Node server for ELK Security Version 3.10.6 is released. See the Release Notes
dbwarner5 Posted December 16, 2023 Posted December 16, 2023 @Jimbo.Automates I dont see it in the store.. thanks.
Jimbo.Automates Posted December 16, 2023 Author Posted December 16, 2023 @Jimbo.Automates I dont see it in the store.. thanks. http://d2z8ydsemzif1x.cloudfront.net/monthly_2023_12/image.jpeg.4ea1dfdc1b9b0efb7554f852f4861463.jpegDid you manually refresh the store? It only auto refreshes once a day.Sent from my Pixel 8 Pro using Tapatalk 1
Jimbo.Automates Posted December 27, 2023 Author Posted December 27, 2023 The PG3 Node server for ELK Security Version 3.10.7 is released. See the Release Notes
DennisC Posted December 27, 2023 Posted December 27, 2023 2 hours ago, Jimbo.Automates said: The PG3 Node server for ELK Security Version 3.10.7 is released. See the Release Notes The newest update listed in the release notes is for v3.10.6?
Jimbo.Automates Posted December 27, 2023 Author Posted December 27, 2023 19 minutes ago, DennisC said: The newest update listed in the release notes is for v3.10.6? It's in the PG3 UI, but it's updated in github as well now. Thanks. 1
Jimbo.Automates Posted February 10 Author Posted February 10 (edited) PG3 ELK Plugin 3.10.15 released, see OP for info. IMPORTANT: If using ELKID or ELKNAME you must enable the "Allow ISY Access by Plugin" on the configuration page. This will be required in PG3x Version 3.2.19 and beyond. Edited February 10 by Jimbo.Automates 1
Jimbo.Automates Posted February 11 Author Posted February 11 Due to the issue below, do not upgrade until Monday after @bmercier releases the below and you update:
MBell Posted February 11 Posted February 11 What a joke. It appears you all need to communicate better. These kind of issues are so annoying. One person announces new version, only to tell people 4 hours later "oh please wait until Monday" Well all of the users that updated OH WELL. 1
Jimbo.Automates Posted February 11 Author Posted February 11 As soon as the issue was discovered I posted a warning, not sure how it can be communicated sooner than it's discovered.Sent from my Pixel 8 Pro using Tapatalk 3 1
jfai Posted February 11 Posted February 11 Dev version -> alpha release -> beta release (to select users) -> production release.
Jimbo.Automates Posted February 11 Author Posted February 11 That would be nice, but out of my control. If you are worried then don't update right away. I was responding directly to communication issues, not release methods. That should be discussed in another sub forum.Sent from my Pixel 8 Pro using Tapatalk
kzboray Posted February 11 Posted February 11 (edited) @jfai and @MBell you could always just wait a couple of weeks before installing something new and make sure there are no reported issues keeping in mind UD is a small company balancing client needs against potential risks. They also do an exceptional job of FREE support. So the occasional issue is quickly resolved with a support ticket. Edited February 11 by kzboray 5
MBell Posted February 11 Posted February 11 3 hours ago, Jimbo.Automates said: As soon as the issue was discovered I posted a warning, not sure how it can be communicated sooner than it's discovered. Sent from my Pixel 8 Pro using Tapatalk What I meant was - most developers are not out there on their own. The product owners should demand a first run at any updates that may affect their product. Most developers place their update in a repository so the rest of the development team can test against their dependncies. I get all of the love for this team, me included, I just think you all could be much better if tighter processes were put into place. Since the launch of PG3 I have witnessed countless issues, not only with the node development but with UDI as well. Im sure I will receive hate messages for this, but why can't a user ask the node developers and UDI to do better? Cheers,
Jimbo.Automates Posted February 11 Author Posted February 11 What I meant was - most developers are not out there on their own. The product owners should demand a first run at any updates that may affect their product. Most developers place their update in a repository so the rest of the development team can test against their dependncies. I get all of the love for this team, me included, I just think you all could be much better if tighter processes were put into place. Since the launch of PG3 I have witnessed countless issues, not only with the node development but with UDI as well. Im sure I will receive hate messages for this, but why can't a user ask the node developers and UDI to do better? Cheers,Because I am just an independent plugin developer who is compensated a little, but nowhere near the time spent developing and helping users. Starting out with "What a joke" is extremely offensive since I try very hard to not release with issues. This issue was out of my control and completely unrelated to my plugin Of course I tested on my production system and let it run for a while before announcing the release. If you have issues with UDI procedures then post in an appropriate forum so your criticism is directed appropriately and try to be considerate.Sent from my Pixel 8 Pro using Tapatalk 5
sjenkins Posted February 12 Posted February 12 4 hours ago, MBell said: Since the launch of PG3 I have witnessed countless issues, not only with the node development but with UDI as well. @MBell, if you looked at the communications which came out this also was not only a UDI issue, but a dependancy from Paho(MQTT) which pushed a breaking change. You might be right that their push was off or even that UDI needs to have their software protect itself better. There are many ways to ask for 'process improvements' but 'what a joke' is just plain rude. You have been on the forum for a while so you see the culture and how things work here. Perhaps you just had a bad day but you may want to think before hitting send next time. 5
Recommended Posts