Michel Kohanim

Hi jmed999, Thanks so very much for the explanations. With kind regards, Michel

Hi LeeG, Are you in Celsius by any chance? This does not look normal. With kind regards, Michel

Walt, thank you and very much looking forward to it. With kind regards, Michel

Hi Xathros, Can you please clear your Java cache and try the following URL instead: http://isy.universal-devices.com/99i/4.0.3/admin.jnlp ? With kind regards, Michel

Thanks wrj0, But, who are "various weather forum sites"? How can we help? With kind regards, Michel

Thanks everyone. Added it as a bug. With kind regards, Michel

Hi wrj0, Thanks so very much for the update. I wished they would put more details as to exactly what's causing all the issues. With kind regards, Michel

Hi Walt, I am not having any fun! I wished we could get PG&E, you, and I on the same call/remote session and figure out what's going on. This said, thanks so very much for your optimism and vote of confidence. They do mean a lot. With kind regards, Michel

Hi wwat, Fan status is really not Fan Status but it's what you did to the fan THROUGH ISY. The real fan status is the Fan Node. This has been the case since time immemorial and there are no changes. Xathros, thanks so very much for the detailed analysis and help. Are you using the Applet or JNLP? If Applet, which browser are you using? With kind regards, Michel

Hi Kevin, Perfect. Thank you ... at least we have something to work on which is well defined and can be implemented. I have added it to our Mantis #96. With kind regards, Michel

Hi Kevin, Thanks so very much for the feedback. It will take more than 7 years of support issues, calls, endless discussions to be able to reply to your subtle and well stated philosophical points of what should or should not be. From a practical perspective - and as I mentioned before - if you limit your requirement to only having Control (NOT status) events available for ISY scenes in programs, then we have something to work on. Statements like the following are things that make everything fall apart: "If I go to the "scene" page in the ISY GUI and click "On" (or any of the other actions) this is the equivalent of activating a physical switch that is linked as the controller of that scene." This is not true and that's why we have an ISY scene. The outcome of activating an ISY scene is NOT necessarily equivalent to activating a controller in a scene (physically). You can have 10 different controllers in the scene each one of which does something different and then ISY scene can do something totally differently which includes turning everything OFF. So, without getting into philosophical discussions, would having a control event for ISY scenes suffice? With kind regards, Michel

Hi Wayne, can you be more specific? Fan status never worked properly since the API didn't support it. What's changed in 4.0.3? With kind regards, Michel

Hi wojo, No, because without Zigbee you will not see all the channels. Includes radio and Zigbee related modules such as energy monitors and RCS Which radio? Where did it come from? With kind regards, Michel

Hi Walt N, Thanks so very much for the update. I am so very saddened to hear. Are you still seeing Joining->Down sequence in the dashboard? With kind regards, Michel

Hi ellesshoo, Do NOT do that as whatever is causing it will not go away on its own. Questions: 1. What's the firmware version? 2. Do you use HTTPS 3. Are you on a low bandwidth or heavily loaded network 4. Can you send your Error Log to support@universal-devices.com? With kind regards, Michel

Hi Josh, 2.6.5 is so old that the only way to get it back to life is through a remote session. Please submit a ticket with your request and provide a few available time slots between 10:00 AM and 4:00 PM Pacific Time. You do need a Windows computer. With kind regards, Michel

Hi Kevin, So far we agree! This is where everything falls apart. What does this mean and how is it different than what we already have? THANK YOU. It does mean a lot to us. Kevin

Hi Josh, As far as I know, we are still waiting for PG&E personnel to call back with. Basically - and unlike all other utilities - PG&E required 32 byte install codes. So, we immediately implemented support for 32 byte install codes and just released it in 4.0.3 beta. With kind regards, Michel

Hi Teken, My firmware version: Com firmware ver: 1.99 Engine1 firmware ver: 1.41 Please note that I was told that GEM does not send "Current" ... you might want to verify that with Brultech. With kind regards, Michel

Hi Teken, Thanks so very much. You do need to get GEM's latest firmware update. We did that because of two reasons: 1. Ben told us that the primary packet format should be ISY (11) and secondary should be none 2. That's the only way we can identify a GEM device is really a GEM device and not ECM. We expect a PKT response which is what we get 3. I do not think it would be a good idea to change that andyf0, sorry to report that we cannot reproduce your on level issues. I suspect that for some reason MAC has decided not to clear Java cache properly. The only thing I can recommend is to reboot your MAC. With kind regards, Michel

Hi Kevin, Thanks you for clarification. We have been trying to avoid confusion simply because, historically, no one could agree on what a scene status meant. If all you require is scene activation by ISY, then that's definitely something we can entertain/implement as long as it's not going to include other things such as the status of the scene based or whether or not the scene was activated by something else other than ISY. With kind regards, Michel

MAC users, Still cannot reproduce the FileChooser hang issue. andyf0, Will review and get back to you. Teken, First, you need to remove GEM from ISY: 1. Remove the nodes from the tree 2. Go to Configuration | Zigbee | Click on Diagnostics | Click on the record for GEM and then click on Remove GEM will try and reconnect at which point you should get 32 nodes. We are working with Brultech to see why values are so very much off. With kind regards, Michel

Hi johnnyt, You and I both ... I very much wish to know what caused the crash. With kind regards, Michel

Hi LeeG, Thanks so very much for the update and confirmation. From our perspective, that's normal on some of the older devices. Xathros, Thanks so very much for detailed explanation. We are running 10.7.5 and perhaps we should upgrade to 10.8.3 to see if that makes a difference. The only difference between your installation and ours is MAC's firmware version on which we cannot reproduce this issue at all. With kind regards, Michel

Hi LeeG, Thanks so very much for the update. You can now set the number of cleanup commands that should be sent from device to device as well as device to PLM/ISY. The instructions were buried in "What's in 4.0.3" ... I do apologize: http://wiki.universal-devices.com/index ... ed_Options Thanks again and with kind regards, Michel