Thanks for the quick reply! I have read this. For some reason my light bulb hasn’t come on! I’m sure it’s something I am missing. I will keep trying.
Hey Andy, thanks for making this. I've been having fun playing with the one I bought off eBay. I mainly make LoRa/LoRaWAN sensors, but this has been a good diversion.
Any other neat new stuff coming down the road for this? You going to keep making/supporting these?
Jason
I still have like 100 left to sell in stock. I plan to keep making them / supporting them.
The main issue at this point is more on the software side. I'm not happy with the Hubitat ability to make a "tile" on the dashboard that can interact fully with all the MonaLisa has to offer. At least I haven't figured it out. And SmartThings has totally destroyed its custom device handler abilities since Samsung took them over. But hopefully these things will get resolved.
I've also been busy with my new project: Maxwell | Crowd Supply
Also available on eBay (cheaper!): maxwell mesh wifi | eBay
1 Like
I don't use dashboards, so never really thought about that.
Interesting. I've been hiding out upgrading my mesh wifi until wifi 6e is more mainstream.... But maybe I'll pick a couple up to play with.
MonaLisa users: I've updated the hubitat driver a bit, to make it more Dashboard-friendly, etc.
Link is the same as before, bee below...
The main thing is it now parses the info returned by the board, and fills attributes. For instance, if digital input 1 changes, it fills the "digin1" attribute with "on" or "off". Same for adc values. By adding tiles to the dashboard using the "attribute" template, you can have that tile display any of these attributes from the MonaLisa. It'll look like this:
There's also 4 buttons defined so you can add a button 1 (or 2, 3, 4) to the dashboard to control each of the 4 digital outputs independently, and see the status of them using the digout1 (2, 3, 4) attribute(s). To add the button to the dashboard you select the "button" template, and enter the button number you want (1, 2, 3, 4).
I also exposed the "polladc0,1,4,5" and "nopolladc0,1,4,5" commands so you can tell the board to poll the adc0, 1, 4, or 5 or not. The adc polling is off by default when the board powers up (to prevent tons of messages if they're left floating - though in practice they seem pretty stable even when disconnected). The digital inputs are polled by default.
I know this is not really the "right" way to do these things. There is another driver available that makes child devices, which then expose the proper "capabilities". Personally I find that way more confusing, so I did it this way!
2 Likes
Exciting news: I've now developed a new firmware for the MonaLisa board that turns it into a BATTERY-powered device... see post here:
2 Likes
Catching this train a few years later, but finally decided to ride the coattails of @haas, @ogiewon, and @JohnRob.
I am not even 100% sure how I will end up using this newfound power, but I wanted to have it as an available option. I chose to trim it to a minimalist carrier board that is friendly to both breadboard and stripboard (as a backplane).
Add a CC Debugger tool ($9 on Aliexpress), and you are in business. I just loaded the firmware, installed the driver, and it added parent/child devices without a hitch. I sincerely appreciate everyone that provided the groundwork and inspiration!
3 Likes
Very nice. How do you connect the cc debugger though, to load the firmware? Are those the pins on the right?
Correct. The initial plan was to just use Dupont jumpers from the ribbon cable. Knowing the intended operator, it seemed prudent to make it more idiot resistant. So, I took advantage of the per-square-inch pricing at OSHpark to make a small adapter.
Curiously, have you ever tested any of the boards that have the range extender or PA chips? I picked up a couple of CC2530 + CC2592 modules, but wanted to test the known-good configuration first.
I've been using firmware from PTVO. I programed my CC2530 using a NodeMCU. Works great.
@haas Got a couple of these on the way and have read this thread plus the support doc. Just want to make sure I understand correctly...
You don't need an Arduino for the MonaLisa to interace with Hubitat. Using the driver from @ogiewon or your driver, MonaLisa can be added to HE as a Zigbee device, with whatever is attached to the GPIOs showing up as child devices - Is my understanding correct?
I have Arduino programming experience, but would prefer to just read and control the devices using rules in HE.
Correct. The Arduino is only needed for responding to custom commands.
1 Like
I have successfully added my MonaLisa to my Hubitat C7 and can control the outputs from the parent device. Thank You!
My use case is (initially) to send temperature data derived from 10 separate DS18B20 sensors connected to a Arduino MEGA over serial connection to the MonaLisa and then on to my Hubitat C7 where I can then display them on a dashboard. I have also equipped my MEGA to control 2 separate 8 channel relay boards which I will eventually want Hubitat to have control of.
What I do not understand is that the MonaLisa uses pins 2 & 3 for serial communication but the Arduino UNO & MEGA both use pins ) 0 & 1 for RX0 and TX0 respectively. On the MEGA I'd prefer NOT to use "serial 0" since that is the default for other uses. Should I just eliminate connections for pins 2&3 to the Arduino and hardwire the MonaLisa's serial connections from 2&3 to one the MEGA's other serial connections at 14 to 19?
Hi. The demo serial.ino script opens a second serial port on pins 2 3 on the Arduino. Then you can still use 0 1 for standard serial, typically back to a computer for serial debugging printouts.
1 Like
I have some pet-immune exterior PIRs I am wiring up to MCUs. Had no problem wiring up two in series to a Fibaro Smart Implant. Trying to do the same on my Mona-Lisa boards now, but not having any joy yet.
The PIR is powered up & did continuity test on the NC/COM outputs from it - working fine. Wiring from digital input 1 on the Mona-Lisa: Ground to COM and DIN1 to NC. On the driver side, have tried settings of Pulled up, Pulled down and No Pull. But watching the device page on HE during the tests and there is no change - contact remains closed.
Any suggestions please?
Hi, Maybe the digital signal is the wrong voltage levels?
Also check that you can see digital inputs at all, by holding / not holding the button on the monalisa and looking at digital input 3.
Try and analog input to the monalisa, and see if the analog value changes when the PIR is on/off.
Got it sorted, thanks @haas
Seems it was a connection issue between the Mona Lisa & the Zigbee network rather than a wiring issue.
I have this device connected to my habitat Hub c7 and it is working but I am not clear on what the attribute “text :” in Current States should be showing me. I think it’s whatever string is coming into the serial connection on pins 3&4 but what I’m getting isn’t exactly what I’m sending via an Arduino MEGA2560.
The string being sent should look something like this: “Temp1 xx.x Temp2 xx.x Temp3 xx.x Temp4 xx.x Temp5 xx.x Temp6 xx.x Temp7 xx.x Temp8 xx.x Temp9 xx.x”
What I’m getting is random pieces of the string preceeded by “60 “. An example is “60 Temp2 -196.” It does not even always include a complete pair of the string of space delimited "name value" pairs. Yet what it does return, eventually, covers most if not all of the string being sent each time the loop runs at 15 second intervals.
Changing the timing has no effect on the string length which the driver displays, only how often it updates.
Looking at the logs the text is identical to what is being displayed. Does the Thing Shield limit the string length it sends back to the hub?
Remember there is a 14 character limit to each send string. Also each string ends with a (.) period.
I would guess your string may be seen like:
Temp1 xx.
x Temp2 xx.
etc.
Btw I prepend each message with ! to make it easy to parse.
UPDATE
Thinking some more.... I suggest you do something like:
!T1xx,xx.
!T2xx,xx.
etc
When reveived replace the , with a period.
Or multiply the temp by 10 the after received divide by ten.
1 Like
Thanks I suspected there was a character limit to each string. That means I'll need to break up data into shorter strings. Any idea how much delay between strings will be required to allow the message to be forwarded and avoid conflicts?
