This object is in archive!
HEX (hexadecimal) for UDP socket (only UTF8 now) - wifi bulbs control as philips Hue
Under Consideration
All new wifi bulbs from china are controled by UDP sockets in HEX but Zipabox can only send UDP sockets with UTF8 language for the moment.
Chinese bulbs that you could find under the brand Easybulb, MiLight, iBulb, LinkUP and Kepsun are all dimmable with led economic and ecologic. It is the best alternative to the expensive Philips HUE.
Control wifi bulb with scripts, is I think, one of the most important thing that a box must do.
A video to introduce these bulbs :
http://www.youtube.com/watch?v=sW4X6wN-SSw
Thank for you support.
I like this idea 
No connection
Real-time notifications may not work
I think it is very easy to add Hexadecimal data in the upcoming firmware.
I think it is very easy to add Hexadecimal data in the upcoming firmware.
I have the same bulb, nice !
I have the same bulb, nice !
The easybulb is wonderful because it can be controlled using my iphone and ipad and plus it is only 6 Watts and can last for up to 25 years. I love these bulbs. I got mine at http://www.easybulb.com and even got 20% discount with their promo code.
The easybulb is wonderful because it can be controlled using my iphone and ipad and plus it is only 6 Watts and can last for up to 25 years. I love these bulbs. I got mine at http://www.easybulb.com and even got 20% discount with their promo code.
Vera by Micasaverde support MiLight/Easybulb/LimitlessLED lamps now perfectly.
http://forum.micasaverde.com/index.php?topic=14471.0
Vera by Micasaverde support MiLight/Easybulb/LimitlessLED lamps now perfectly.
http://forum.micasaverde.com/index.php?topic=14471.0
http://community.zipato.com/responses/how-create-a-virtual-switch-to-command-lamp-with-udp-socket-
http://community.zipato.com/responses/how-create-a-virtual-switch-to-command-lamp-with-udp-socket-
2+ years and still nothing, what a sad situation...
I have those bulbs and it is such a shame not being able to have the possibility to integrate them with the rest of my home automation system because I bet on Zipato ability to deliver and innovate in 2014.
No RGBW color picker, no ON/OFF switch for them, not even the possibly to send them a packet without manually converting control codes...
Why is this?
Those bulbs can be controlled through a documented UDP HEX based API (http://www.limitlessled.com/dev/), and we can't even use it straightforward because Zipato restrains use since 2+ years to UDP UTF-8 only.
Yes, we are in 2015, almost 2016... Such a sad situation. I'll definitely reconsider betting and buying a Zipabox should I imagined such a long "development cycle". This product has such a great potential, I don't understand...
2+ years and still nothing, what a sad situation...
I have those bulbs and it is such a shame not being able to have the possibility to integrate them with the rest of my home automation system because I bet on Zipato ability to deliver and innovate in 2014.
No RGBW color picker, no ON/OFF switch for them, not even the possibly to send them a packet without manually converting control codes...
Why is this?
Those bulbs can be controlled through a documented UDP HEX based API (http://www.limitlessled.com/dev/), and we can't even use it straightforward because Zipato restrains use since 2+ years to UDP UTF-8 only.
Yes, we are in 2015, almost 2016... Such a sad situation. I'll definitely reconsider betting and buying a Zipabox should I imagined such a long "development cycle". This product has such a great potential, I don't understand...
+1
Still waiting and hoping Zipato could integrate wifi bulbs with UDP in hex.
+1
Still waiting and hoping Zipato could integrate wifi bulbs with UDP in hex.
I waiting too for buy these led bulbs.
Zipato dont move...
I waiting too for buy these led bulbs.
Zipato dont move...
"Zipato dont move..."
Zipato seems move but to devlop and debug more used "old and used in mass " protocols (433Mhz, Enocean , ... ). 3 years developping to catch 15 or 20 years technology is a good result... no?
meanwhile i find wifi protocol very interesting ... when a zipato WiFiextension ?....no?
"Zipato dont move..."
Zipato seems move but to devlop and debug more used "old and used in mass " protocols (433Mhz, Enocean , ... ). 3 years developping to catch 15 or 20 years technology is a good result... no?
meanwhile i find wifi protocol very interesting ... when a zipato WiFiextension ?....no?
This would be great! I am controlling a Milight RGB-lamp with my Zipato, but i can't send all the commands (like half brightness). I was able to convert some commands like on/off by using the idea from above (hex to ascii), but if the Zipabox could do hexcodes directly would be much better.
This would be great! I am controlling a Milight RGB-lamp with my Zipato, but i can't send all the commands (like half brightness). I was able to convert some commands like on/off by using the idea from above (hex to ascii), but if the Zipabox could do hexcodes directly would be much better.
Hello Zipato Team!
This is really a little bit annoying that such a basic function does not work! Please let us send hex commands via udp!
Hello Zipato Team!
This is really a little bit annoying that such a basic function does not work! Please let us send hex commands via udp!
Yes. please add hex support to socket requests
Yes. please add hex support to socket requests
This topic is under consideration since more than 3 years now...
@Zipato dev team: some special escaped characters are already working - maybe not on purpose... - such as \t
=> do you need some help for UDP sockets to support \u encoding for instance?
I'm certainly not familiar with your code base but I'll consider all strings as they are today everywhere expect when encoding the UDP payload, where I would pay some extra attention to look for \u encoding to process it appropriately.
Including testing and documentation, this really should not take more than 4 hours of work.
This topic is under consideration since more than 3 years now...
@Zipato dev team: some special escaped characters are already working - maybe not on purpose... - such as \t
=> do you need some help for UDP sockets to support \u encoding for instance?
I'm certainly not familiar with your code base but I'll consider all strings as they are today everywhere expect when encoding the UDP payload, where I would pay some extra attention to look for \u encoding to process it appropriately.
Including testing and documentation, this really should not take more than 4 hours of work.
Replies have been locked on this page!