garhul / aurora Goto Github PK

I'm testing the last build after PR #6 an I got an issue with the IP address. After store the settings successfully, the ESP(mini D1) is connecting to the Wifi (It seems) but it's not in the right IP subnet. Somehow is not getting the IP from DHCP.

The ip should be on the 192.168.1.XXX subnet and it's on 192.168.4.XXX

As part of a bigger refactor we need to:

• Refactor strip class to be a namespace the same way as Mosquitto and Network
• Migrate from HSL to HSB color space
• Implement animations api with easing (partially integration with neopixel animator object)

Implment OTA with signed package

Implement websockets server as in Firefly project

This is a security concerrn
The newly implemented webserver blindly serves files from the filesystem without checking for anything. This means that the stored settings can be accessed, protentially exposing credentials.

Check this doesn't happen

That ^

New cmd for send just RGB color format and the strip will fill with it.

@garhul Are you okay if I add this feature?

I saw that we have a cmd like this but for set HSL called 'set', so it will be very similar code to it and I will call it 'setRgb'

As part of the streaming api we would need to implement UDP messaging, which up to certain extent is provided by mqtt, however mqtt also requires a broker, and UDP doesn't.
Maybe we can implement UDP too but I'd like to have some tests done on the performance of a streaming api so this isn't worthless effort.

While I was doing #12 I found out that send HSL color by the cmd set is not working properly..

If you send the color for eg. 360 100 30 which has to be some red.. It's playing another color. There is a mistake in the conversion to NeoPixel color format I think. So I'm checking it out

In addition I would like to rename the cmd set to setHsl. "Better explicit than implicit"