Need RS232 to Zigbee or Z-Wave

The board I have is an older one. I wouldn't recommend it unless you want to use one of my carrier boards. The "newer" boards have different pinout.

Note the pinout spacing is 0.050 making it a little bit of a challenge to solder.

1 Like

@fcwilt, I have a similar setup to control some MiLight bulbs. I have an ESP8266 with a radio daughter board. Hubitat talks to the ESP over WiFi and the ESP talks to the lights over the radio. Thankfully there was a community driver already available.

It works great. The only issue I had was the ESP would go to sleep and it would take a couple of seconds for the lights to turn on. I solved that by sending a command to a dummy light every two minutes to keep the microcontroller awake. It has been running in my living room for a couple of years now. I should probably modify the ESP code to keep it awake but so far this works fine. I don’t expect a two second delay would cause an issue for your use case.

1 Like

Another possibility to investigate.

Thanks, Frederick

I installed the HPM but I don't see how to search by @thebearmay.

Could you elaborate a bit?

Thanks, Frederick

If you're familiar with Github, you may find it simpler to go directly to the repo at hubitat/synaccess at main · thebearmay/hubitat · GitHub to view the code.

1 Like

I will give that a try.

Thanks, Frederick

1 Like

simply use the keyword synaccess in your search...

Thanks,

What threw me off was I was looking for something like "Find A Package".

I wasn't thinking of installing a package so I didn't select that option.

Frederick

1 Like

Yeah @thebearmay is a freaking magician when it comes to HE programming.

3 Likes

What do you use for a driver with PTVO and HE?

I wrote my own. Here is a general version I used getting started:

 //Hubitat driver for  PTVO CC2530 Zigbee Board


metadata
{
    definition(name: "Zigbee Raw Message", namespace: "johnrob", author: "johnr")
    {
        capability "Actuator"
        capability "Sensor"
        //capability "Configuration"    // currently no configuration settings.
        capability "Initialize"
        capability "TemperatureMeasurement"
        capability "PressureMeasurement"
        capability "RelativeHumidityMeasurement"

        attribute "lastActivity", "String"
        attribute "I2Caddress", "string"

        //fingerprint profileId: "0104", inClusters: "0000", outClusters: "0000, 0B05, 0006"     // per PTVO firmware.

    }
    preferences{
       // input name: "logEnable", type: "bool", title: "Enable debug logging", defaultValue: true
       // input name: "logInfo", type: "bool", title: "Enable Info logging", defaultValue: false
       // input name: "tempUnitsDegC", type: "enum", title: "Temperature Units", options: ["1":"°C","0":"°F"], defaultValue: 1, required: false
       // input name: "altitudeMeters", type: "number", title: "Meters above sea level", description: "meters", defaultValue: 0, range: "0..200"

    } //  --- metadata ---
}

def parse(String description){

    log.info  "Raw Description#$description"

    Map map = [:]
    def event = zigbee.getEvent(description)

    //if (event) sendEvent(event)

    if (description?.startsWith('read attr -')){

        def descMap = zigbee.parseDescriptionAsMap(description)

        if (descMap.cluster == "000C" && descMap.attrId == "0055"){     // zigbee spec 0x000C= read analog cluster  0x0055 = present value
            ZigbeeHexMap = descMap.value
            log.info "Zigbee Msg#$ZigbeeHexMap"
            float SensorValue = ConvertHexToFloat(ZigbeeHexMap)
            def otherAttrs = descMap?.additionalAttrs
            otherAttrs.each{
                unitaddress = it.value
            }
            log.info ("$unitaddress")
            def (units, address) = unitaddress.tokenize( ',' )   //   <--- units and I2C address



        } // --- if cluster ---
    } // --- if "read attr" ---
} // --- parse ---


1 Like

Thanks. I found it a bit odd that there wasn't much discussion on drivers etc for using the device with the various hubs.

The author is focused on MQTT.
I have a few of these also one of Dr Haas' Thinkshield firmware. All of them are very solid.

Makes sense I guess. Wish there was a comprehensive driver the HE. I'm looking at the MonaLisa and anything that gets me to a simple and stable place with supporting my own sensors etc. I'm frustrated with the lack of control over the various off the shelf zigbee devices and would prefer to create some of my own. I also need to support some older audio matrix devices that have serial control as an option. Would prefer Zigbee or at least I'm willing to exhaust that as an option before moving on.

I've only found these zigbee boards (TI CC2530) are plug and play enough for me. I have not interest in learning how to fully program the CC2530 so I have to use either the HAAS or the PTVO firmware.
There was a Z-Wave board but it was quite expensive.

I think "comprehensive driver" and "lack of control over the various off the shelf zigbee devices" are mutually exclusive. If you want to control a wide variety of devices you will have to learn how to modify drivers. I consider myself "fair or lower" in my ability to write/modify these drivers. I started looking at examples and have learned enough to "talk" to the devices I'm interested in.

I'm a software engineer. I'm just hoping to save time by using something existing. Testing the waters. Not sure I want to swim the channel, but I'm willing to do a few belly flops.

So I'll throw down the gauntlet..... I'm a hardware engineer and I did it :slight_smile:

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.