Michel Kohanim

@mmb, Please send your error log to support@universal-devices.com. With kind regards, Michel

@jfai, As Einstein once said "Education is that which remains, if one has forgotten everything he learned in school", when you have 8MB RAM and 2MB flash, and limited resources to handle/parse things, you ignore what you learned in school or links. You just do whatever it takes. With kind regards, Michel

@MrBill, That's pretty amazing. Now, you can create a node server for Polisy and ConBee. Are you up for it? @Techman, You can either one of the USB ports (for 2413U) or the DB9 (for 2413S). With kind regards, Michel

@Bumbershoot, We still haven't worked on migration. The main issue is all the INSTEON .REC files, otherwise, everything else is easy. @MrBill, I played with Conbee and I like it. Just need someone to develop a node server for Zigbee. With kind regards, Michel

My goal: make this topic as wildly successful as the PLM discontinued one! So, everyone, please chime in: any topic welcome! 1. @larryllix Stocking up and reselling: not our cup of tea simply because a) our shipping rates are very high compared to Amazon or The Smartest House and b) administrative cost of handling POs, returns, etc. and c) upfront cost. In short, your cost will be much lower from Amazon or The Smartest House 2. @simplextech Why not reference design? Because it's a reference design and not a commercial one available to all. Are we going to point customers to Mouser or Digikey? And, as @io_guy, the serial api is 100% identical to the reference design 3. @MrBill you are 100% correct: we have not had official releases since 5.3.1 for ISY994. The reason is that we are still trying to figure out the balance of when to release an official version since, the word "official" has major implications for Z-Wave Certification. i.e. every official release must be certified. And, we simply cannot afford spending $10K for Z-Wave certification for every release 4. @Teken, you are also 100% correct when you take Z-Wave cert into consideration In short, all our Polisy/ISY releases should be considered beta for now. Should we change the first topic to mention Beta and/or remove all references to ISY994? On the other hand, if I were to do that, I would be going against my goal ... With kind regards, Michel

All, 1. Z-Wave is working in the lab but cannot give you an ETA 2. We are using Zooz 700 Series stick. They seem to be in stock 3. The first iteration will be based on what we have in ISY since certification is a nightmare and will take months With kind regards, Michel

Hello all, This is a rather major release for ISY on Polisy: 1. Fixed websocket causing crash 2. ISY Launcher can now automatically find ISY on Polisy (no need to add) 3. Just like regular ISY, you will be notified of available upgrades on the Admin Console. And you can choose Help | Automatically Upgrade to have Polisy upgrade ISY. Unlike regular ISY, you cannot manually upgrade ISY from the Admin Console (you can still do through ssh). So, hopefully no more ssh 4. Added lat/long for Oswego (minor) Instructions: sudo pkg upgrade udx sudo pkg upgrade isy sudo service udx restart sudo service isy restart With kind regards, Michel

@MWareman, They shall be resurrected. The main issue is that, as you can see, we are trying to move things out of the Java Admin Console + want to make sure we use existing OS functionality as much as possible. For instance, we no longer manage DST calculations, months, days of the week, etc. In the meantime, if you have specific lat/long, please send to support@universal-devices.com and we'll include it in the list in Polyglot. @MrBill, yes, thank YOU very much. With kind regards, Michel

@MWareman, It should use whatever is the system time zone as set by Polyglot. This information comes from another service called udx (which is an abstraction layer for OS and used by both Polyglot and ISY). I suspect udx is back leveled. Please: sudo pkg upgrade udx sudo pkg upgrade isy sudo service udx restart sudo service isy restart With kind regards, Michel

@MWareman, There is a difference in BSD. Although the underlying protocol is UDP, the sock options are different. With kind regards, Michel

@MWareman, I don't thing it's supported through UDP. Did you also try Multicast? With kind regards, Michel

@Jimbo , @bpwwer and @xKingwere not invited either. The three of you do not require invitations. You guys are automatically invited and any node server event without you, is like the signing ceremony of the Declaration of Independence without the founding fathers. With kind regards, Michel

Drinks and lunch/dinner on UD. Just have to find a good venue for hosting if more than 10. With kind regards, Michel

This is so interesting. As part of our business plan, this is what I have (verbatim): Grow the Developer Community by offering discounts on hardware, services, tools and instituting annual developer events with perks and prizes. I guess this will be our first! With kind regards, Michel

Absolutely! A hackathon of sorts ... lunch/dinner on UD. With kind regards, Michel

@MWareman, Please check that ftdi driver is loaded (kldstat) ... or, you can simply restart isy and it will tell you whether or not it's loaded (sudo service isy restart). If loaded and if INSTEON is enabled, then most probably either the PLM is dead or the cable is bad. With kind regards, Michel

@Snibley, We are slowly moving node servers to PG3 and thus the slowdown. With regard to OS, there has been couple of updates to isy and udx since plus many more python modules. With kind regards, Michel

@dinostop, Did you hear beeps during boot up? Polyglot talks to udx (for sys config) using secure MQTT. The only reasons you would see that banner: 1. udx is not running ... please check the status of lights. Only the left most should be on 2. for some reason mqtt is not running. If your node servers work, then this cannot be the case 3. Browser cache With kind regards, Michel

@breischaft, Very strange. What's the output of uname -a? With kind regards, Michel

@MWareman, What's the output of uname -a? I suspect you are missing the driver for FTDI because your OS version is still 12. If that's the case: sudo pkg update && sudo pkg upgrade cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now With kind regards, Michel

Hi @dinostop, What node servers have you installed? With kind regards, Michel

@larryllix, LOL ... what happened to: I am your faatthheerrrr! With kind regards, Michel

@johnstonf, Thank you. We are quite paranoid when it comes to security and, specifically, cloud services. And, as time progresses, things get more complicated. Just have to stay vigilant and keep ahead of these dark forces. With kind regards, Michel

Hello all, Apologies for not getting back sooner. The root cause was the load balancer. At the highest levels, and for obvious reasons, we are continuously strengthening cyber security for all our infrastructure. We migrated the load balancers to have the connection end at the balancer rather than direct traffic to the web servers. There should have been zero impact. Alas, some got impacted. I apologize for the inconvenience. With kind regards, Michel

Hello everyone, Sincere apologies for the inconvenience. We are trying to find the root cause since it seems to not have impacted everyone. With kind regards, Michel