Michel Kohanim

Hello wrj0, Thank you. That might explain the issue. I think the problem is translation from UTF-8 and somehow our Java UI is considering it as ASCII instead of UTF-8. We'll look into it more once we have more time. Thanks again for reporting it and your willingness to go the extra mile to provide all this valuable information which will help us in debugging. With kind regards, Michel

Hi Harold, thanks. Got it and responded. Please take a look at your router's firmware level. With kind regards, Michel

Hi Harold, I do not think your unit is defective. I think it's either getting a different IP address from your router, you have an IP conflict, or do you have Verizon/AT&T FIOS or DirecTV? In all cases, please send your Error Log to support@universal-devices.com. With kind regards, Michel

Hello wrj0, I think I understand the issue. Are you entering the degree sign as the sign itself in the content pane? With kind regards, Michel

Hi Joe, Exactly what does not work? Please try REST: http://wiki.universal-devices.com/index ... #Variables With kind regards, Michel

Hello sanders2222, Unfortunately not. With kind regards, Michel

Hello wrj0, I do not think the recipient is processing HTML because it must work! Would you be kind enough to save the contents in an html file as described here: http://wiki.universal-devices.com/index ... e_Creation Let me know if you are still getting the strange characters. If you are not, please try the following as the content-type: text/html Happy New Year to you as well. With kind regards, Michel

Hi jyingling, There shouldn't be but this feature has not been maintained for more than 5 year and slated to be completely removed. With kind regards, Michel

Hello wrj0, Thanks so very much for the feedback. Unfortunately this seems to be what ISY is adding incorrectly assuming the output is html (°). This is something we will need to fix but the problem is that it's buried deep in the code and intermingled with a lot of other formatting stuff. I have already reported it as a bug (#130). In the meantime, you might want to try changing the content type to HTML in which case both devices "must" convert the symbol properly. With kind regards, Michel

Hi Kyle, If you do not have anything in the Else path, you really do not need "is not Switched Off". In short, it's only used to negate the condition. With kind regards, Michel

Hi Harold, Please do let me know if you can access locally when you get back. With kind regards, Michel

Hi bigscience, Sincere apologies ... I had it confused with Leak Sensor. Unfortunately, there isn't a hearbeat signal for this device. I am so very sorry. With kind regards, Michel

Hi Harold, Are you using MobiLinc Connect? If not, which part of MobiLinc is not working? Also, when this stops working, can you connect to your ISY locally? And, finally: 1. What's your ISY's firmware version? 2. Do you have Verizon or AT&T/FIOS or DirecTV? With kind regards, Michel

Hi bigscience, You can use the hearbeat node for that (if you have 994 + 4.0.5 and above). With kind regards, Michel

Hi Roger, Just responded to you via PM as well. 16 bytes = 12 + 4 CRC ... as such, please use 12. This said, you MUST see ISY going through Scanning, and then Down status. If you don't get those, please contact me directly via support@Universal-devices.com. With kind regards, Michel

Hello toflaherty None whatsoever! They should all work. From management perspective (ease of figuring what what is forwarded to what) it's best to have both ports be the same (i.e. change ISY's port to the forwarded port). For obscurity purposes, it's best to change ISY's port to an obscure number and choose another obscure number for the public port. I very much doubt this would get you any additional security though. With kind regards, Michel

Hi outsider, It's the same problem as multiple login: http://wiki.universal-devices.com/index ... r_Your_ISY With kind regards, Michel

Hi outsider, I suspect your 99 was excluded from your anti-virus/firewall whereas 994 is not. Here are some instructions for configuring firewalls: http://wiki.universal-devices.com/index ... r_Your_ISY With kind regards, Michel

Hi Harold, thank you and Happy New Year to you as well. Did you enable internet access by doing a File | Enable Internet Access or have you created port forwarding rules in your router? With kind regards, Michel

Hi NNilsen, http://wiki.universal-devices.com/index ... structions. Please note that with Z-Wave, you might need at least 4 to 6 (depending on the sq footage) other Z-Wave devices to create a mesh. With kind regards, Michel

Hi haroldunger, ISY is definitely not defective if your programs continue to work. If you have Verizon FIOS or DirecTV, please upgrade to 4.1.1. Also, as BrianH suggest, if you used File | Enable Internet Access, then - and in all likelihood - your ISY's IP address has changed but the router does not know anything about it. And, in the meantime, please send your Tools | Error Log to support@universal-devices.com. With kind regards, Michel

Hi blartyo, MAC? With kind regards, Michel

Hello wrj0, Is rule 116 the one you are working with. Again, the error code means that ISY could not make a TCP socket connection and therefore I suspect networking issues. That's unless rule 116 is something else. With kind regards, Michel

Hi blartyo, I am so very sorry to hear. Can you please let me know what you mean by "not recognized"? Please note that you need a Zip utility (not Windows compression) to look inside ISY's backup zip file. With kind regards, Michel

Hi apostolakisl, Agreed. With kind regards, Michel